Skip to main content
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

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.
Do not send personal data in event names or properties. Everything you pass to track and screen is stored as you send it.
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: 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.

​
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.
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.