Apple App Privacy and Google Play Data safety
Both stores ask what your app collects, including through SDKs. These answers follow from the fields a signal carries. They cover Pulse only.
Read this first
Written on 2026-11-13 from the categories of both forms as we know them. The stores change their forms. Check the current wording in App Store Connect and Play Console. You are responsible for your answers, and this is not legal advice.
Two things decide your answers
- Whether you set a user in the SDK. Without it, every native SDK still sends a hashed random install id so that users are counted. It is created by the SDK, stored only in the app's own storage and not derived from any device identifier.
- What you put in props. The answers below assume props hold no personal data.
Apple: App Privacy
The Swift SDK ships a privacy manifest. It lists Product Interaction, User ID and Other Data Types as linked to the user, and Device ID as not linked, all for analytics and none used for tracking. Device ID is the anonymous install id. User ID is listed as linked because your app can set one with setUser; a manifest cannot depend on what your app does. The App Store form is yours to answer, for your whole app. The answers below are our advice for the Pulse part.
| Question | Answer for Pulse | Why |
|---|---|---|
| Do you or your partners collect data from this app? | Yes | Signals leave the device and are stored. |
| Usage Data: Product Interaction | Yes | This is what a signal is: a screen opened, a level started. |
| Identifiers: User ID | Only if your app calls setUser | The SDK manifest always lists it, because a manifest cannot be conditional. Your own form can follow what your app does. The value is hashed on the device and again on the server. |
| Identifiers: Device ID | Yes | The SDK manifest lists it, not linked to the user. Device ID is the anonymous install id: random, stored only in the app's own storage and sent only as a SHA-256 hash. No advertising ID and no vendor ID is sent. |
| Location | No | No location field is sent. Our server derives a country from the IP address when a signal arrives, then discards the address. Nothing finer than a country is kept. |
| Diagnostics | No | Unless you send crash or performance signals yourself. |
| Purchases | No | Unless you send purchase signals yourself. |
| Contact Info, Contacts, User Content, Health, Financial Info, Sensitive Info | No | No such field exists. Keep them out of props. |
| Purpose | Analytics | The data is used for statistics about your app, nothing else. |
| Linked to the user? | Device ID: no. User ID, if your app calls setUser: yes. | The install id is not linked to the user's identity. A hashed user ID is still one ID per user. |
| Used for tracking? | No | The data is not combined with data from other companies and not passed to data brokers or ad networks. |
Google Play: Data safety
Pulse ships no Data safety declaration for Google Play. The form is yours to answer, for your whole app. The answers below are our advice for the Pulse part.
| Question | Answer for Pulse | Why |
|---|---|---|
| Does your app collect or share any of the required user data types? | Yes, it collects | Signals leave the device and are stored. |
| Is all collected data encrypted in transit? | Yes | The ingest address is HTTPS. Your other SDKs decide the answer for the whole app. |
| App activity: App interactions | Collected | This is what a signal is. |
| Personal info: User IDs | Only if your app calls setUser | Google counts hashed and pseudonymous IDs as user IDs. |
| Device or other IDs | Collected, not shared, purpose Analytics | This is the anonymous install id: random, stored only in the app's own storage and sent only as a SHA-256 hash. It is not a hardware or advertising ID, but it identifies one install of your app. The session ID is random. |
| Location | No | No location field is sent. Our server derives a country from the IP address when a signal arrives, then discards the address. Nothing finer than a country is kept. |
| App info and performance: Diagnostics | No | Unless you send crash or performance signals yourself. |
| Financial info: Purchase history | No | Unless you send purchase signals yourself. |
| Is the data shared? | No | Pulse processes the data for you as a service provider. Google does not count that as sharing. |
| Purpose | Analytics | Choose Analytics for each collected type. |
| Is the data processed ephemerally? | No | Signals are stored for the raw history period of your plan. |
| Is collection required or optional? | Your choice | Optional if your app offers an analytics opt-out. Otherwise required. |
| Can users request deletion? | Your answer | It covers your whole app. For Pulse, see the Trust page for how long data is kept. |
If your props change the picture
A prop is data you chose to send. If you attach an email address, a precise location, a purchase or free text from a user, declare the matching data type in both forms and update your privacy policy.