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

# Privacy

> What the Appeeky Analytics SDK collects and what it does not, App Store privacy labels, and how data is deleted

Appeeky Analytics is built to attribute installs without tracking users across apps. It never reads advertising identifiers and never needs the App Tracking Transparency prompt.

***

## What the SDK Sends

| Data | Details |
| - | - |
| Install id | A random id created by the SDK and stored in the app. It is not tied to the device or to other apps. |
| App context | Platform, app version, build number, OS version, device model and locale |
| Events | Screens, sessions, foreground time and the custom events and properties you track |
| RevenueCat app user id | Only when you call `identify` |
| First-launch attribution | Once per install: the Apple Search Ads attribution token and Apple's answer (iOS), the Play Install Referrer (Android), and the URL the app was first opened with |
| Ad revenue | Only when you call `adRevenue` |

The server also stores the country of each install, from the network location of the request when available, or from the device locale.

## What It Does Not Collect

* No IDFA, no Android advertising id, and no App Tracking Transparency prompt.
* No device fingerprinting.
* No names, emails or other personal data, unless you put them in event properties or use them as the RevenueCat app user id.

> [!WARNING]
>
> Do not send personal data in event names or properties. Everything you pass to `track` and `screen` is stored as you send it.

### Smart link clicks

For each click on a smart link, Appeeky stores the link, a random click id, the platform (iOS, Android or other) and the country. It does not store the IP address or the user agent.

### SKAdNetwork postbacks

Postback copies from Apple carry the app's Apple ID, the ad network, a campaign or source identifier and a conversion value. They never identify a device or a user.

***

## App Store Privacy Label

In App Store Connect, declare:

| Data type | Linked to the user | Used for tracking |
| - | - | - |
| Usage Data → Product Interaction | No | No |
| Purchases | No | No |

If your RevenueCat app user id is a real account id (for example your own user id after login), declare those data types as **linked** to the user instead.

***

## Opt-Out

To stop collection for a user who opts out, start the SDK with `disabled: true`. The SDK then collects and sends nothing.

```ts theme={"theme":{"light":"github-light","dark":"github-dark"}}
Appeeky.init({ key: "apk_pub_...", disabled: userOptedOut });
```

***

## Deleting Data

Turning off Analytics for an app **deletes the app and all of its analytics data**: installs, events, revenue records, smart links and their clicks, and SKAdNetwork postbacks. This cannot be undone.

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
curl -X DELETE "https://api.appeeky.com/v1/analytics/apps/YOUR_APP_ID" \
  -H "X-API-Key: YOUR_APPEEKY_KEY"
```

Builds that still use the app's old publishable key stop sending. Turning Analytics on again creates a new, empty app with a new key.

***

## Where Data Is Stored

On the hosted service, each Appeeky account's analytics data is kept in its own isolated database. When self-hosting, all data stays in your own Cloudflare account. See [Self-Hosting](https://docs.appeeky.com/docs/analytics-self-hosting.md).

***

## Related Docs

* [SDK Reference](https://docs.appeeky.com/docs/analytics-sdk-reference.md)
* [Smart Links](https://docs.appeeky.com/docs/analytics-smart-links.md#click-privacy)
* [SKAdNetwork](https://docs.appeeky.com/docs/analytics-skadnetwork.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.