Repository navigation
|
My app was flagged or rejected on Google Play for this. Data Safety form does not match runtime behavior. Which guideline is this, how do I find it in my project, and how do I fix it before I resubmit? |
Replies: 1 comment
|
Guideline. Data Safety (Google Play) Severity in the playbook. critical What triggers it. Analytics, ads, or tracking SDKs are present that collect or share data not declared in the Data Safety section. This is the number one Google rejection cause. What to search your code for. How to fix it. Audit every SDK and runtime data flow and declare every collection, sharing, and security practice accurately in the Data Safety form. The guard reports this as This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
Guideline. Data Safety (Google Play)
Severity in the playbook. critical
What triggers it. Analytics, ads, or tracking SDKs are present that collect or share data not declared in the Data Safety section. This is the number one Google rejection cause.
What to search your code for.
firebase-analytics,com.google.android.gms.ads,facebook,appsflyer,adjustHow to fix it. Audit every SDK and runtime data flow and declare every collection, sharing, and security practice accurately in the Data Safety form.
The guard reports this as
GOOGLE-DATASAFETY-MISMATCH. The full pattern is in data/rejection-patterns.json.This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submiss…