Google Play — Missing or invalid privacy policy
Google could not find a working privacy policy, or the one you linked does not describe what your app actually does with data.
What the rejection usually says
Your app does not have a valid privacy policy.
The privacy policy link provided is not functioning.
Wording varies between reviewers; the substance does not.
Why it gets triggered
- The URL is dead, geo-blocked, or behind a login.
- A generic template that never names your app or its data.
- The policy contradicts the Data safety form.
- No policy inside the app itself, only in the listing.
How to fix it
1.Host it publicly and permanently
A plain, always-reachable URL, no redirect chain, no login, reachable from every country.
2.Make it specific
Name your app, the data types it collects, why, who receives them, retention, and how users request deletion.
3.Link it in both places
In the Play listing and from inside the app, usually in settings.
A reply you can adapt
Short, specific, and stating what changed — reviewers read hundreds of these.
Thanks for flagging this. The privacy policy is now hosted at a stable public URL, names this app specifically, matches the Data safety declaration, and is linked from the app's settings screen as well as the store listing.
AppSubmit does this for your app, specifically
Paste the rejection and the decoder reads it against your actual listing, build and release history — then writes the fix plan and drafts the reply. It also watches your submissions, so the next rejection reaches you as a notification rather than a surprise.
Decode a rejection free