What the URL has to do
Whatever you choose, the page must meet the same basic rules that Apple and Google check:
- Public: it opens without a login, an invitation or a paywall.
- Reachable everywhere: it isn't blocked in some countries or by bot protection.
- A web page, not a file: Google Play doesn't accept PDFs.
- Read-only: visitors can't edit it.
- Clearly a privacy policy: titled "Privacy Policy" and naming you, the same developer or company as your store listing.
- Stable: the address doesn't change, so the link in your app keeps working.
Free options compared
| Option | Setup | Updating | Watch out for |
|---|---|---|---|
| GitHub Pages | A repository with an HTML or Markdown file, with Pages turned on | Commit and push | Free accounts need a public repository; you need basic Git |
| Google Sites | Build a page with your Google account and publish it | Edit and republish | Publish it to the public, not only to your organization |
| Google Docs | Use "Publish to the web" | Edits republish automatically | Share the published link, never the editing link; looks less professional |
| Notion | Publish the page to the web | Instant | Turn off editing and comments for visitors; check it loads in a private window |
| PDF file | Upload anywhere | Upload again | Not accepted by Google Play |
| Legiflare | Start from a template and publish | Edit online; the URL stays the same | Pages show the Legiflare header and footer |
Using GitHub Pages
GitHub Pages is a solid choice if you already use GitHub:
- Create a repository, for example
privacy-policy, and add anindex.htmlorindex.mdwith your policy. - In the repository settings, open Pages and publish from your main branch.
- Your policy appears at
https://your-username.github.io/privacy-policy/.
You still need the policy text itself. The privacy policy template works well as a starting point.
Using Legiflare
- Create a free account and start from the privacy policy template, or describe your app to get a first draft.
- Edit the sections so they match what your app really collects, and publish.
- Copy the link and paste it into App Store Connect, the Play Console and your app's settings screen.
When something changes, edit the text online. The link stays the same, so you don't have to update your store listings.
Before you paste the link
- Open it in a private browser window to confirm it doesn't need a login.
- Open it on your phone, on mobile data, to confirm it loads and is readable.
- Check the title says "Privacy Policy" and the developer name matches your store listing.
- Check it covers the platform rules for iOS and Android.
Frequently asked questions
Do I need my own domain for a privacy policy?
No. Apple and Google accept any public URL that meets their rules. Your own domain looks more professional, but it isn't required.
Can I use a Google Doc as my privacy policy?
Only through "Publish to the web", which gives a read-only page. Never paste a sharing link that lets people edit or request access.
What happens if I move my privacy policy to a new URL?
Update the link in both stores and inside your app, and keep the old page online until all of them point to the new one.
Is hosting on Legiflare really free?
Yes. Templates, editing and hosting are free, with no limit on the number of documents.