> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trueorigin.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Google Play Data safety

> What the TrueOrigin SDK collects on Android, for your app's Data safety form.

Google Play asks every app what data it and the SDKs in it collect and share. What your
app declares is your decision. This page lists what the TrueOrigin Android SDK sends and
where it fits in the form. The React Native package contains the same SDK on Android.

## What the SDK sends

Once, on the first launch after install, the SDK sends one install report to TrueOrigin
over HTTPS, then asks for the result until it is decided. The report holds:

| Data | Details | Play data type |
| - | - | - |
| IP address | As TrueOrigin's server sees it. TrueOrigin derives country, region and city from it. | **Location → Approximate location** |
| Install ID | A random ID the SDK creates. Removed with the app, left out of backups. | **Device or other IDs** |
| Install referrer | What Google Play hands your app after the install: the `referrer` of the Play link, when that link was opened, when the install began, and whether it was an instant app. | none on Play's list |
| Device | Manufacturer and model, Android version and API level, screen size and pixel density. | none on Play's list |
| App | Package name, version and version code, SDK version, and the app that installed it (for example Google Play). | none on Play's list |
| First launch | The time of the app's first launch. | none on Play's list |

The SDK does not read the advertising ID or the Android ID, and asks for no permission
beyond `INTERNET` and the install referrer library's `BIND_GET_INSTALL_REFERRER_SERVICE`.
It reads no location, contacts, files or clipboard. The full list is in section 5.2 of our
[privacy policy](https://trueorigin.dev/privacy).

## Answers for the form

For the SDK's data:

| Question | Answer |
| - | - |
| Does your app collect or share any of the required user data types? | Yes |
| Is all of the user data collected by your app encrypted in transit? | Yes: the SDK only uses HTTPS. |
| Collected | Approximate location, Device or other IDs |
| Processed ephemerally | No: TrueOrigin stores the install report. |
| Required or optional | Required, unless every user can decline before your app calls `configure`. |
| Purposes | Advertising or marketing (measuring ad performance), Analytics, Fraud prevention, security, and compliance |

TrueOrigin processes the data on your behalf, as your service provider. It also uses it
for a few purposes of its own: security, measuring its matching accuracy, and statistics
that identify no person or app (section 5.7 of the
[privacy policy](https://trueorigin.dev/privacy)). Whether that makes sending it to
TrueOrigin *sharing* in Play's sense is part of your decision.

<Warning>
  With [postbacks](/postbacks) on, TrueOrigin sends Meta or TikTok the install ID of each
  install matched to one of their ads. Declare **Device or other IDs** as shared too, for
  Advertising or marketing. The IP address and user agent in a postback are the tap's,
  from the tracking link's page, not data from your app.
</Warning>

## Deletion

TrueOrigin keeps an install's data while your app uses TrueOrigin, and deletes it when you
delete the app in the dashboard. When a user asks you to delete their data, we help:
write to [hello@trueorigin.dev](mailto:hello@trueorigin.dev) with the install ID
(`TrueOrigin.installId`).

Purchases reach TrueOrigin from RevenueCat's servers, not from the TrueOrigin SDK: declare
them as RevenueCat's own documentation says. `revenueCatAttributes()` puts the install ID,
and once matched the campaign, into RevenueCat's subscriber attributes, which the
RevenueCat SDK sends.