App Store / App Privacy answers

App Privacy answers

Adding the Uplift Funnel SDK changes what your app collects, so it changes your App Privacy answers. Here is exactly what to tick, and the one question whose answer depends on your own flows.

The short version

The SDK reports which onboarding screens a user saw and what they answered. It generates its own anonymous identifier for that, scoped to your app. It does not read the advertising identifier (IDFA), the vendor identifier (IDFV), or any other cross-app identifier, and it never shares data with a data broker.

That means the answer to "Is this data used to track you?" is No for everything Uplift Funnel collects — and adding the SDK does not, by itself, oblige you to show an App Tracking Transparency prompt.

What to declare

Under App Store Connect → your app → App Privacy, these are the data types the SDK contributes. Everything else in Apple's list stays untouched by us.

Data typeCollectedLinked to identityUsed for trackingPurposes
Usage Data → Product InteractionYesOnly if you call identify()NoApp Functionality, Analytics, Product Personalization
Identifiers → User IDOnly if you call identify()YesNoApp Functionality, Analytics
Identifiers → Device IDNoThe SDK generates its own app-scoped id instead
Purchases → Purchase HistoryNot by the SDK — see belowNoAnalytics

Why Purchase History is a footnote

Uplift Funnel does receive your subscription transactions, but not from the device. They arrive server-to-server by webhook from RevenueCat or Adapty, if you connect one. Apple's questionnaire is about data collected from the app, so this is already covered by the declaration you make for your subscription provider — our SDK adds nothing here.

The question only you can answer

App Tracking Transparency

If Uplift Funnel is the only thing you added, you do not need an ATT prompt for it. The identifier we use cannot follow anyone into another app or website, and nothing is shared with advertising networks or data brokers.

The exception is your own choice: if you enable the AppsFlyer or Adjust attribution integration, those SDKs collect the advertising identifier themselves and send it to us in a postback. That collection is theirs, it happens whether or not we are involved, and it is what triggers ATT — declare it under their requirements, not ours.

Data deletion requests

For end users of your app, you are the data controller and we act on your instructions. You can export and delete end-user records from your dashboard, which is what you need to satisfy a deletion request. The contractual side is in our Data Processing Agreement.