Typical wording
Issue found: Invalid privacy policy URL. Your app's privacy policy link is not valid or does not lead to a privacy policy that covers your app.
Common causes
- The URL 404s, redirects to a home page, or sits behind a login, consent wall or region block
- The policy is a generic template that never names the SDKs, data types or purposes in the build
- The policy belongs to the company rather than the app, and does not mention the app at all
- The policy contradicts the Data safety form (collection, sharing, deletion, encryption)
- The policy is a PDF or a document-sharing link rather than a public web page
- The in-app link and the listing link point at different documents
What to check
- Open the URL in a private window from a different country and device — it must load without login or consent gate
- Does the policy name the data types, purposes, third parties and retention the app actually uses?
- Does it describe account deletion, including the web deletion request path, where accounts exist?
- Does it match the Data safety declaration line by line?
- Is the same URL used in the store listing and inside the app?
Fix, reply or appeal guidance
- Host the policy on a stable public URL under your own domain, with no login or interstitial
- Write it from the app's real data flows — inventory the SDKs first, then describe collection, sharing, purpose and deletion
- Reconcile it with the Data safety form before resubmitting; the mismatch is what triggers repeat rejections
- Link the same URL in the listing and in the app, and keep it current when SDKs change