InfluToHelp
Privacy and App Store review
What the InfluTo SDKs collect and never touch, and exactly what to declare in App Store Connect's privacy label and Google Play's Data safety form.
This page lists what the InfluTo SDKs send, what they never access, and the answers to give in App Store Connect and the Google Play Console.
The short version
- No IDFA, no Advertising ID, no ANDROID_ID. The SDKs never read an advertising or system identifier.
- No App Tracking Transparency prompt. InfluTo does not track users across apps or websites, so ATT does not apply and must not be requested for InfluTo.
- No device fingerprinting. Attribution never matches by device characteristics, and nothing is shared with ad networks or data brokers.
- First-party, per app. Attribution links an install and its purchases to a referral code or link click for that app only.
- Deterministic first. Typed referral codes, in-app link parameters, the Play Install Referrer (web SDK) and the RevenueCat
influto_codeattribute attribute exactly; link-click matching is a window-limited fallback. See How attribution works.
What the SDK sends
All requests go to https://influ.to/api over TLS, authenticated with the app's SDK key.
| When | Data | Purpose |
|---|---|---|
| Initialize / first launch | SDK name and version, app version, platform, device brand and model, OS version, screen size, timezone, language, a random per-install ID generated by the SDK | Attribute the install to a referral code or link click; show SDK health on the Setup page |
| Code validation / application | The referral or access code the user entered, plus the fields above | Validate the code and record the attribution |
| Identify (optional) | Your app's user ID (for example the RevenueCat app user ID) | Match store and RevenueCat purchase events to the attributed install |
| Purchase report (store-direct only) | Store transaction proof (StoreKit 2 signed transaction or Google Play purchase token), product ID | Verify the purchase with Apple or Google before any commission exists |
| Custom events (optional) | Event name and the properties you pass | Funnel analytics on the dashboard |
InfluTo's servers also see the request's IP address, used to derive the country and to screen clicks and installs for fraud. The SDKs never access contacts, precise location, photos, the clipboard or other apps.
Apple: privacy manifest and App Privacy label
The iOS SDK ships a PrivacyInfo.xcprivacy manifest with NSPrivacyTracking = false, no tracking domains, and these collected data types — all declared not linked to the user and not used for tracking:
- Device ID (the SDK's random per-install ID) — App Functionality
- Product Interaction (only with
trackEvent) — Analytics - Purchase History (only with
reportPurchase) — App Functionality
Required-reason APIs used: UserDefaults, reason CA92.1 (the SDK stores its own attribution state). No other required-reason API is used.
App Store Connect answers for the InfluTo part of an app:
| Data type | Collected | Linked to user | Used for tracking | Purpose |
|---|---|---|---|---|
| Identifiers → Device ID | Yes | No | No | App Functionality |
| Purchases → Purchase History | Only with reportPurchase |
No | No | App Functionality |
| Usage Data → Product Interaction | Only with trackEvent |
No | No | Analytics |
If your app passes its own user ID to identifyUser, declare "Linked to user" according to how that ID is treated elsewhere in your app. Don't enable ATT or NSPrivacyTracking for InfluTo, and don't forward InfluTo data to an ad network.
Google Play: Data safety form
The core Android SDK (to.influ:android-sdk) declares only the INTERNET permission and doesn't request AD_ID. The optional android-sdk-billing artifact adds com.android.vending.BILLING for purchase capture.
| Data type | Collected | Shared | Purpose |
|---|---|---|---|
| Device or other IDs (SDK install ID; brand, model, OS version, screen size, timezone, language) | Yes | Yes (InfluTo, as processor) | App functionality, Analytics |
| App activity → Other actions (referral code, custom events) | With trackEvent / identifyUser |
Yes | App functionality, Analytics |
| Financial info → Purchase history | With reportPurchase |
Yes | App functionality |
| App info and performance (app and SDK version) | Yes | Yes | Analytics |
Advertising ID: No. Encrypted in transit: Yes. Users can request deletion: Yes.
A privacy policy paragraph for your app
This app uses InfluTo (influ.to) to attribute installs and purchases to referral and affiliate campaigns. It transmits non-advertising device information (brand, model, OS version, screen size, timezone, language), a random install identifier and, where you enter one, the referral code you used. InfluTo does not use advertising identifiers and does not track you across other apps or websites. You can request deletion of this data by contacting us or InfluTo at hello@influ.to.
Deletion and retention
clearAttribution()removes the SDK's local state on the device.- Server-side deletion of a user's attribution data is done on request — yours or the user's — at hello@influ.to. There is no self-service deletion API.
- Records of attributed purchases and payouts are kept for 7 years as financial records; everything else follows the Privacy Policy.
- Processing terms: Terms of Service and the Privacy Policy; a data processing agreement is available on request.
Consent in the EU
Attributing a referral the user was part of is processed on the basis of legitimate interest (paying the creator who referred them) and involves no profiling or advertising. Apps that gate all non-essential SDKs behind a consent screen can call checkAttribution() after consent, or lead with typed code entry, which works without any matching.