Play rejection: data safety answers do not match the policy

Google compares what you declared in the Data safety form against what your privacy policy says. A contradiction is treated as a false declaration.

Updated 2026-09-18 · Written from the same rules terms.gg uses to generate documents

What the rejection means

Google compares what you declared in the Data safety form against what your privacy policy says. A contradiction is treated as a false declaration.

The usual causes

• The form says no data is collected, the policy describes analytics.
• The form omits a category the app clearly uses, like location.
• The policy was updated and the form was not.

What to change

Fill the form from the policy, not from memory, and re-check it whenever the policy changes.

Before you resubmit

• Open every URL you entered in a private window.
• Read the reviewer's message again and answer the specific point, not the general topic.
• Reply in Resolution Center saying what you changed and where to see it.

Keeping it true after launch

A legal page stops being true the moment the product moves past it, usually by adding a payment provider, an analytics SDK or a sign-in. No store re-checks your pages against your build, so the drift is yours to notice.

• Re-read it whenever you add a dependency that sees user data.
• Re-check what loads on the page after any change: the cookie notice and the policy have to agree.
• Keep the URL stable. Changing where a policy lives breaks every listing that points at it.