Wiki
Clone wikiAddApptrLandingPage / Device ID Handling
In General
AddApptr GmbH is a European company that processes and stores statistical and analytical data about the processes within AATKit (our SDK) on servers in Europe, amongst them device Identifiers e.g. for counting unique users in apps. Therefore, GDPR is always applicable for AATKit - even if it gets used by a non European user in a non European country using an app of a non European publisher. Based on this reasoning, AATKit handles device identifiers (IDs) as follows.
iOS
If the iOS version used is equal 14.5 or higher
If consent for IAB TCF purpose 1 is given
- If ATT (App Tracking Transparency) is consented
- read Identifier for Advertising (IDFA) and pass it to AddApptr's backend
- Else
- read Identifier for Vendors (IDFV) and pass it to AddApptr's backend
Else
- read no device identifier and instead pass a zero pattern to AddApptr's backend
If the iOS version used is lower than 14.5
If consent for IAB TCF purpose 1 is given
- If "limit ad tracking" is enabled
- read Identifier for Vendors (IDFV) and pass it to AddApptr's backend
- Else
- read Identifier for Advertising (IDFA) and pass it to AddApptr's backend
Else
- read no device identifier and instead pass a zero pattern to AddApptr's backend
Android
If consent for IAB TCF purpose 1 is given
- If "limit ad tracking" is enabled
- read no device identifier and instead pass a zero pattern to AddApptr's backend
- Else
- read Google Advertising Identifier (GAID) and pass it to AddApptr's backend
Else
- read no device identifier and instead pass a zero pattern to AddApptr's backend
Updated