Data safety information.

Use this page as a preparation checklist for the Google Play Data safety form. It is not a substitute for the Play Console declaration.

Important: Do not submit Play Store declarations based on assumptions. Inspect the release build, permissions, dependencies, Firebase configuration, backend, and third-party SDK disclosures. Your Data safety form and privacy policy must agree.

Before submitting to Google Play

Inventory every data type collected or shared by the app and each SDK.
Determine whether data is processed on-device only or sent to a server or third party.
Document purposes, optionality, encryption in transit, retention, and deletion mechanisms as applicable.
Verify whether account creation is offered and implement the required account deletion experience if it is.
Ensure the public privacy policy is accessible, stable, and specific to the app.
Complete the Play Console Data safety form based on actual behavior, including third-party SDKs.
Recheck the form after adding analytics, advertising, authentication, crash reporting, or other SDKs.

Questions for the release audit

Does the app collect email or account identifiers? Does it send practice progress or analytics events off-device? Are advertising or crash-reporting SDKs included? Are support messages stored? Does the app allow account creation? Record the verified answers before publishing this page.

Account and data requests

For a privacy or deletion request, email support.gulfnurse@gmail.com. The final production policy should explain the actual identity-verification steps and any applicable exceptions.