Privacy policy clauses for AppsFlyer
AppsFlyer is a mobile attribution and marketing analytics platform that tracks app installations, user events, and campaign performance. Websites and apps use AppsFlyer to measure marketing effectiveness, attribute user actions to specific campaigns, and optimize advertising spend across channels.
Free scan · No signup · Results in 60 seconds
What data AppsFlyer collects
Your privacy policy must disclose each of the following data types when you use AppsFlyer.
When does AppsFlyer trigger privacy obligations?
AppsFlyer's SDK begins collecting data the moment it initializes in your app—before any user action. It immediately captures device identifiers (IDFA on iOS, GAID on Android), device model, OS version, carrier, IP address, and geographic location. This triggers obligations instantly:
GDPR (if users are in EU/EEA)
AppsFlyer processes personal data (device IDs, IP addresses, location) as a data processor. You must have a Data Processing Agreement (DPA) in place with AppsFlyer *before* deploying the SDK—this is a GDPR Article 28 requirement, not optional. You must also obtain lawful basis for processing; consent (Article 6(1)(a)) is common but legitimate interest (Article 6(1)(f)) may apply if properly documented. You must disclose in your privacy policy (Article 13/14) that AppsFlyer receives IDFA/GAID, device data, and IP address, and name AppsFlyer as a processor.
