How to add a Privacy Policy URL in Google Play (Fast)
Platform: Google Play
- Open Google Play Console and select the exact app you plan to update so that you don’t edit the wrong listing in a multi-app account.
- From the left navigation, go to ‘Policy’ and then ‘App content’; this is where Google centralizes disclosures, including the Privacy Policy field.
- Locate the Privacy Policy section and click ‘Start’ or ‘Manage’; Google expects a public HTTPS URL that loads quickly and does not require login.
- Paste your hosted Privacy Policy URL. Use a canonical link you can keep stable over time so future updates don’t break your listing.
- Click ‘Save’ and wait for the confirmation toast. If you are preparing a new version, also ensure your store listing text references the same policy language.
- If your app collects personal or sensitive data, confirm the policy explicitly names your company/app and explains what is collected, why, and how users can contact you.
- Open your policy URL in an incognito/private browser window to verify it is publicly accessible on both desktop and mobile screens without geo-blocking.
- Return to Play Console and submit your changes. If tied to a new release, complete the release flow so the policy link is evaluated with the build.
- Monitor the ‘Policy status’ area. If Google flags anything, adjust your policy wording or link targets immediately and resubmit to avoid removal from search.
FAQ
Does the URL have to be a web page, or can it be a PDF?
A web page is strongly preferred because it is easier for reviewers to read on mobile and simpler for you to update over time. PDFs sometimes load slowly or trigger downloads, which can frustrate reviewers.
Can I reuse the same Privacy Policy URL across Android, iOS, and my website?
Yes. Use a single canonical, public URL that clearly names your product and organization. Consolidating to one link reduces the risk of mismatches across stores.
What causes the most rejections?
Broken links, private or geo-blocked pages, policies that never mention the app’s name, or vague statements that don’t explain data collection and contact details are the most common issues.
Do I need to change the URL when my app’s features change?
Keep the same URL but update the content to reflect new data handling. Your goal is a permanent address with fresh, accurate text.
How fast should the page load?
Aim for under two seconds on a typical mobile connection. Slow pages can be treated like broken experiences during review.
Is cookie consent or UMP required for the policy page?
Consent banners are separate from the policy page. Your policy should link to consent preferences if applicable, but the policy itself must remain publicly readable.
Can the policy live on a subdomain?
Yes. Subdirectories are ideal for authority, but a consistent subdomain is fine as long as it’s stable, publicly accessible, and branded.
What about localization?
You can maintain one English page if that’s your audience, but if you serve multiple locales, add language toggles or separate sections for clarity.
Should I include a ‘Last updated’ date?
Yes. A visible date and a simple change log build reviewer confidence and reduce back-and-forth.
How do I test like a reviewer?
Open the URL on an LTE phone in a private tab, scroll the entire document, check contact email visibility, and verify the page works without cookies or login.