Add links to home page

[JamesA4E]

🔖 Feature description

When completing the Google verification, you need to provide links to privacy policy. I submitted mine and had verification request stating

Your homepage https://postiz.company.com/ does not include a link to your privacy policy: https://otherdomain.co.uk/privacy

The ability to set two values in the .env for privacy policy and terms of service, which are then put on the Postiz homepage, would fix this.

🎤 Why is this feature needed ?

This will allow users to verify their apps with Google for the YouTube integration.

✌️ How do you aim to achieve this?

Add two hyperlinks to the standard homepage that read a value from the environment as to where to connect the links to.

if the environment is missing the links then dont populate the homepage with the links

🔄️ Additional Information

No response

👀 Have you spent some time to check if this feature request has been raised before?

• I checked and didn't find similar issue

Are you willing to submit PR?

None

[j0lle]

Got here by googling the same issue

@JamesA4E if you are using nginx to host your app, you can work around this by statically hosting the files, by adding this to your domain config:

    location /privacy {
        alias /location/of/privacy.html;
    }

    location /terms {
        alias /location/of/terms.html;
    }

hope it helps

[JamesA4E]

Sadly, I don't think this alone will pacify Google. The issue I have is

Your app has not met homepage requirements. Please resolve the following issues:

• Your homepage does not include a link to your privacy policy.
  Make sure that your home page includes a link to your privacy policy.

They are looking to see the links on the homepage.

I have located the .tsx files required:

• apps/frontend/src/components/auth/login.tsx
• apps/frontend/src/components/auth/login.with.oidc.tsx

But I've not worked with Next.js (I'm guessing this is), so I have no experience with how to make changes. I have edited the files via nano in Docker, but the changes weren't reflected on the browser side.