Why this blocks so many submissions
A privacy policy URL is a hard requirement on both stores, and it is the field that catches indie developers out most often — not because the document is hard to write, but because it needs somewhere to live. A Google Doc link, a Notion page or a file in your repo either breaks, requires a login, or quietly changes address, and the store finds out at review time.
Generate the document
Answer a short brief — your company or developer name, a contact email, your website, and what your app actually collects — and you get a privacy policy and a terms of service drafted around those answers. Both are editable before you publish; nothing goes live until you say so.
- Privacy policy — what you collect, why, who you share it with, and how someone asks for deletion.
- Terms of service — acceptable use, your liability, and how the agreement ends.
- Draft and published states — edit freely, publish when the wording is right, unpublish if you need to pull it.
Publish it somewhere permanent
Published pages get a stable public path on your Edok Studio site, served over HTTPS, with no login and no expiry. On the top plan you can point your own domain at it, and the certificate is issued automatically — so the URL in your store listing is one you control and can keep forever.
Your app also needs a support URL and, for most reviewers, a real website. The app landing page covers both, on the same domain as your legal pages.
Publish your privacy policy free
Design once with device frames and export every required App Store & Google Play size in one ZIP — watermark-free on the free plan.
Start free — no cardWhat this is not
A generated policy is a reasonable starting point for a straightforward app, and it is far better than the copy-pasted template most first submissions use. It is not legal advice, and it cannot know things you did not tell it. If your app touches health, finance, or users under 13, get it reviewed.