To support publishers compliance with Apple’s requirements around App privacy details, AdColony has provided this wiki page to provide clarity on what data is being collected in publishers’ apps via AdColony’s SDK.
Types of data
|Coarse Location||Information that describes the location of a user or device with lower resolution than a latitude and longitude with three or more decimal places, such as approximate location services|
|Customer Support||Data generated by the user during a customer support request.
Note: This information is only collected if a user clicks on the AdChoices logo on AdColony advertising, reaches the AdColony support website, and emails our support team at email@example.com. This information is not actually collected through our SDK embedded in the publisher app.
|User ID||Customer number generated during a customer support request.
AdColony also generates an AdColony User-Generated ID and may accept user IDs from publishers such as hashed email IDs.Additionally, AdColony also collects the IDFV where it has been made available.
|Device ID||Such as the device’s advertising identifier, or other device-level ID|
|Purchase History||An account’s or individual’s purchases or purchase tendencies
Note: This is an elective piece of information, which some publishers choose to send to our SDK. It is not enabled by default, and will not need to be included for the Apple review process unless you choose to send this information to AdColony.
|Product Interaction||Such as app launches, taps, clicks, scrolling information, music listening data, video views, saved place in a game, video, or song, or other information about how the user interacts with the app.
Note: Product Interaction data AdColony collects through our SDK is limited to interaction with the ads we serve through our SDK; for example we may count ‘app opens’ in terms of how many times our SDK is initialized.
Beyond this, Product Interaction data is elective. Publishers may choose to send us app events such as ‘ad watched’ or ‘tutorial complete’, but it is not enabled by default.
|Advertising Data||Such as information about the advertisements the user has seen.|
|Crash Data||Such as crash logs|
|Performance Data||Such as launch time, hang rate, or energy use|
|Other Data Types||Any other data types not mentioned
Note: Other “Data Types” are elective; some publishers choose to send “Other Data Types” to our SDK. It is not enabled by default, and will not need to be included for the Apple review process unless you choose to send other types of information to AdColony which are not included.
AdColony uses the Types of Data listed above for the following purposes:
|Third-Party Advertising||Such as displaying third-party ads in your app, or sharing data with entities who display third-party ads, and performing ad targeting and anti-targeting functions such as targeting, device suppression and frequency capping.|
|Analytics||Using data to evaluate user behavior, including to understand the effectiveness of existing product features, plan new features, or measure audience size or characteristics|
|Other Purposes||AdColony is registered with the IAB utilizing collected data for the following purposes under the TCF v2.0 framework: purposes 1,2,3,4,7,9, 10; special purposes: 1,2; features: 3|
Data linked to the user
AdColony will link all of the above collected data to Apple-provided device ID.
Exceptions to these linkages are:
- The publisher has chosen to provide us an alternative ID for advertising purposes, for which we may link data to that ID instead.
- the user has otherwise opted-out directly to AdColony or via a LAT signal (in which case we will restrict linkages of collected data to a user)
- AdColony is under obligation under legal frameworks to not track (in which case we will restrict linkages in compliance with legal frameworks)
- AdColony has received privacy-related signals from the publisher to our SDK Privacy API (in which case we will restrict linkages in compliance with privacy signals)
All data collected by AdColony via our SDK when connected to an apple device ID is considered to be tracking.
Unless otherwise noted as exceptions in the “Data Linked to the user” section above.