The Google Play Data Safety Form: A Plain-English Walkthrough
Short answer: The Data safety section in the Google Play Console wants to know which data your app gathers, whether it shares that data with third parties, how it is protected in transit, and whether users can ask for it to be deleted. Answer it from your app's actual behaviour, including the software development kits inside it. Two distinctions cause most of the mistakes. Data that leaves the device and is stored by you or a vendor counts as collected. Data that is passed to a third party counts as shared, with some exceptions for service providers acting on your behalf. Review the form before every release, because a new feature can change several answers at once.
Why the form matters
The Data safety section appears on your store listing. Users read it before they install, and Google uses it when it reviews your app. An answer that understates what the app does is a problem even if you did not intend to mislead anyone. Treat the form as a plain description of the app, written for someone who has never seen the code.
Start by gathering the facts. Open the app as a new user would. Note each screen that asks for information, each permission prompt, and each place where data leaves the phone. Then list the libraries your developers added, such as sign-in, analytics, crash reporting, payments and advertising.
Section by section
The form moves through several parts. Work through them in order.
Data collection and sharing. Start with a clear yes or no on whether the app collects user data at all. If it does, go through each data type and mark whether it is collected, shared, or both. Examples include name, email address, phone number, precise location, app activity, device identifiers and purchase history.
Purpose. Next, pick the reasons each item is gathered for, such as app functionality, analytics, account management or fraud prevention. Tick every reason that applies, not just the main one.
Optional or required. State whether the user can avoid providing the data and still use the app. If the sign-in requires an email address, that data is required. If a newsletter sign-up asks for a phone number but is optional, mark it as optional.
Security practices. Say whether data is encrypted in transit, and whether users can request deletion of their data. Only answer yes if it is true for every data type you declared.
Collected or shared: the core distinction
This is the point most owners get wrong. Collected means the data is sent off the device to you or a service that stores it for you. Shared means the data is transferred to a third party for that party's own use. Sending data to a service provider that processes it only on your instructions is generally treated differently from handing it to an advertising network, but you should read the current Google definitions in the Play Console help before deciding.
Here is a worked example for a small booking app:
| Data type | Sent to | Collected | Shared |
|---|---|---|---|
| Email address | Your sign-in service | Yes | No, if the service only processes for you |
| Appointment history | Your backend | Yes | No |
| Device identifier | Analytics kit | Yes | Yes, if the vendor may use it for its own purposes |
| Crash logs | Error tracking vendor | Yes | No, if the vendor only processes for you |
The analytics row is the one people miss. Many analytics kits can use data for their own product improvement, which makes the transfer a share, not just a collection. Read each vendor's data processing terms before answering.
Login, payments and analytics examples
Three common SDK families cause repeated questions:
- Login. Sign-in with email, a social account, or a phone number creates account data. Declare the identifiers, the contact details and the account management purpose.
- Payments. A payment provider often receives payment details directly. Your app may only see a transaction reference. Declare purchase history, and check whether card details reach your servers at all.
- Analytics. Declare the events you record, such as screens viewed or buttons tapped, and any device or advertising identifiers. If the kit sends data to its own servers, note that it is a collection, and check whether it is also a share.
Checklist before each release
- Compare the list of libraries with the answers on the form.
- Check each vendor's documentation for changes in what it collects.
- Confirm that deletion requests are honoured, and that the answer reflects the real process.
- Check whether new features collect data you did not declare before.
- Verify the encryption answer against what the app sends over the network.
- Save the form and check the public preview on the store listing.
Store the completed answers in a shared document, so the next person knows what was declared and why.
Keeping the form aligned with updates
A form that was correct at launch can drift within a few months. An update that adds a push notification library, a new location feature or a second payment option changes the answers. Put the form review into your release process, alongside the testing checklist, so it is not left to memory.
Read the policy alongside it on the same day. Both documents must describe the same data flows, although the form is terser.
Common mistakes
- Declaring nothing because the app has no account. Analytics and crash data still count.
- Confusing collected with shared. Each data type has its own answer for each question.
- Forgetting SDK data. Every software development kit in the build counts, even ones you never configured yourself.
- Answering from the design brief. Check the actual build, not the plan.
- Not updating after a release. New features add new data flows.
FAQ
Do I have to fill it in if my app is free and has no ads?
Yes. Every app published on Google Play must complete the Data safety section, and free apps with analytics or sign-in still have data to declare.
What if a vendor will not tell me what it collects?
Do not guess. Ask in writing, check its public data processing terms, and if you still cannot confirm the answer, reconsider using that library, because you will be answering for its behaviour.
Do I need to declare data that stays on the device?
Data that never leaves the device is generally not collected under the form's definitions. Check the current definitions carefully, because a single outgoing request can change the answer.
Can the form be wrong after publishing?
Yes, and it should be corrected quickly. Update the form, then check that the store listing shows the new answers and that your privacy policy agrees with them.
Send us the list of services behind your sign-in, payments and analytics, and we will draft the Data safety answers from that list: get in touch.