Back to all posts
Google Play7 min read·October 25, 2026

How to Prepare Your Google Play Data Safety Answers

TB
ThynkBlox Apps Team
App Engineering

To complete the Google Play Data safety form, first map what information your app and its included SDKs send, where it goes and why. Use that evidence to prepare answers about collection, sharing, purposes and deletion. Check the current form definitions and official guidance before choosing an answer: a permission name or an SDK’s marketing description is not enough evidence.

What should you gather before opening the form?

Start with the app version you intend to release. Ask the people responsible for the app, its server and its integrations to help assemble one evidence sheet.

Gather:

  • The features available to users, including optional features.
  • The SDKs included in the release and their enabled settings.
  • The information sent from the app and passed between services.
  • The recipients, storage locations and reasons for each transfer.
  • The controls for consent, optional features and deletion.
  • The current privacy policy and any deletion instructions users receive.

Use the Google Play release checklist to place this review alongside the rest of your release preparation. Give unresolved questions an owner before submission.

How do you map the app’s actual data flows?

Follow information through complete journeys. For sign-in, start with what the user enters, then trace the request, the receiving service, stored records and any onward transfers. Repeat this for purchases, support requests, diagnostics and other features your app actually includes.

Do not stop at the first server. Ask whether information is forwarded, copied into support tools or recorded in logs.

A useful evidence sheet looks like this. These rows are illustrative questions, not suggested declarations.

Possible flowWhat to establishEvidence to retain
Account creationWhich details leave the phone, who receives them and whyRequest fields, receiving service and storage record
Crash reportingWhich diagnostic details are sent and whether identifiers accompany themSDK settings and an inspected report
Product analyticsWhich events and properties are sent, and under which conditionsEvent list, configuration and observed requests
Support attachmentWhere the file goes and which recipients can access itUpload journey, access settings and deletion test
Account deletionWhich records are removed, retained or handled separatelyTested process and documented retention reasons

For each flow, record whether it happens automatically, follows a user action or depends on a setting. Mark unknowns explicitly. An empty cell should mean “unresolved”, not “nothing happens”.

How should you decide what counts as collection?

Read the current Google Play definition of collection before classifying any flow. Check how the guidance treats processing on the device, transfers off the device and any exceptions relevant to your app.

Then compare the definition with observed behaviour. Ask what information leaves the phone, which destination receives it and what happens next. If you think an exception applies, retain the specific guidance and explain how your implementation meets its conditions.

Do not infer the answer from a permission. Instead, inspect the feature that uses it. For example, if users can select a photo, establish whether the app only displays it locally, uploads it to your service or sends it elsewhere.

Likewise, check information that does not appear in a permission prompt. Review account fields, diagnostic properties and information attached to requests. The question is what the release does, not what its permission list appears to suggest.

How should you review included SDKs?

Give every included SDK a separate review, even when its purpose seems obvious. Ask the person responsible for the integration to identify:

  • The included version and enabled features.
  • When the SDK starts running.
  • Its configured destinations and automatic behaviour.
  • Any identifiers or extra properties supplied by your app.
  • What changes when a user declines an optional feature.

Read the provider’s current documentation, then compare it with your configuration and test observations. Keep any unanswered questions visible.

A provider’s disclosure guidance is useful evidence to examine, but do not copy it without checking the conditions it assumes. Your review should explain which features are enabled and how the SDK behaves in this release.

Include SDKs used for functions such as notifications, diagnostics or sign-in in the inventory. Review based on what is included, rather than limiting the exercise to tools labelled “analytics”.

How do you distinguish collection from sharing?

Treat collection and sharing as separate decisions. Consult the current form definitions for each, including any treatment of service providers, user-directed transfers and other exceptions.

For every recipient, write down what it receives, what it does with the information and the relationship under which it receives it. Review the relevant service terms alongside the technical flow.

Avoid shortcuts such as “we pay this provider, so it cannot count as sharing”. Also avoid assuming that every outside recipient automatically requires the same answer. Document how the current definition applies to the particular transfer.

If the technical evidence and the service terms describe different behaviour, resolve that difference before submitting the declaration.

How do you choose the purposes and optionality answers?

Write a plain-language reason for each flow before selecting a purpose from the form. For example, “send a sign-in code” is more useful evidence than “improve the experience”.

Map that reason to the current purpose choices. Review each use separately when the same information supports more than one function.

Next, test whether the user can actually avoid the flow. Ask:

  • Does the flow start before the user makes a choice?
  • Can the relevant feature be declined?
  • Does declining it prevent the transfer?
  • Does the app later send the information through another route?

Do not describe a flow as optional simply because a settings switch exists. Test the switch from a fresh installation and after changing the choice. Use the Android testing guide to make these journeys part of release testing.

What should you verify about deletion?

Check the current deletion questions and requirements separately from collection and sharing. Establish which apply to your app, then compare them with the process a user can actually complete.

Trace a deletion request from the user’s first action through to completion. Record which information is deleted, which recipients need a separate request and whether anything is retained for a documented reason.

Be precise about scope. If the process deletes an account but handles uploaded files separately, your evidence should show that distinction. Avoid promising complete or immediate deletion unless you can substantiate the promise.

Test both the request and its result. A confirmation message shows that the request was acknowledged; verify the relevant records and recipient actions as well.

Who should own the answers and supporting evidence?

Give the declaration one accountable owner, with named contributors for the evidence. A product owner can coordinate the submission while technical contributors verify behaviour and someone familiar with the privacy commitments reviews the wording.

For each answer, retain:

  • The conclusion and the current definition used.
  • The relevant app version and configuration.
  • Supporting observations or documentation.
  • The person who verified it.
  • Any unresolved question and the action needed to close it.

Keep evidence free of unnecessary personal information. Prefer test accounts and sanitised examples.

Revisit the sheet when features, SDKs, recipients or deletion behaviour change. Our guide to app maintenance after launch helps place this review within ongoing upkeep. For the Apple equivalent, see how to prepare App Store privacy nutrition labels.

What common mistakes should you avoid?

Answering from permissions alone. Trace the information used by each feature and compare it with the current definitions.

Copying another app’s answers. Similar screens do not establish identical data flows.

Treating a policy document as proof of behaviour. Compare its statements with the release you tested.

Accepting an SDK’s defaults without inspection. Record the actual settings and observed requests.

Choosing the least concerning answer when evidence is missing. Assign the uncertainty to someone who can resolve it.

Checking only successful journeys. Include declined choices, failed requests, signed-out use and deletion.

What should be ready before you submit?

Use this final checklist:

  • Every included SDK has been reviewed.
  • Every identified flow has a destination, purpose and owner.
  • Collection and sharing answers use the current definitions.
  • Optionality matches tested behaviour.
  • Deletion answers match the process users can complete.
  • The privacy policy and declaration describe consistent behaviour.
  • Each answer has evidence, with no unresolved assumption presented as fact.

Frequently asked questions

Can I prepare the answers before the app is finished?

Prepare a draft inventory early, but validate it against the release before submission. Label planned behaviour clearly until it has been implemented and checked.

Can I use an SDK provider’s suggested answers?

Use them as a starting point for review. Confirm the version, configuration and conditions behind the guidance, then compare them with your app.

What if I cannot explain a data transfer?

Keep the answer unresolved while you investigate the destination, information and purpose. Ask the integration owner or provider for evidence rather than guessing.

Does this exercise replace a privacy review?

Treat it as one part of release preparation. Review the app’s disclosures, user choices and privacy commitments together, and seek qualified advice where an obligation is unclear.

Ready when you are

Planning an app of your own?

Tell us where your project is today. We will help you work out the scope before you commit to a budget.