App privacy details on the App Store (often nicknamed Apple’s nutritional label) is a privacy feature introduced in iOS 14. Starting December 8th, 2020, every app submission will require disclosure of information that your app collects, including information that third party services that you use may collect (such an advertising platform).
To assist with meeting this requirement DT is providing developers with easy-to-use guidance on its data collection practices in the context of Apple’s new App Store privacy details requirement. For each data type Apple is asking you about, we provide guidance if DT also collects this data, and if so, how and for what purpose.
DT is required to provide a clear data use purpose for each data type. In all cases, DT uses your data for the purpose of Third Party Advertising, "such as displaying third-party ads in your app, or sharing data with entities who display third-party ads."
|Relevance to DT's Data Collection Policies
|Such as First or Last name
|Including but not limited to a hashed email address
|Including but not limited to a hashed telephone number
|Such as home address, physical address or mailing address
|Other User Contact Info
|Any other information that can be used to contact the user outside the app
|Health and Fitness
|Health and medical data, including but not limited to data from the Clinical Health Records API, MovementDisorderAPIs, or health-related human subject research or any other user provided health or medical data
|Fitness and exercise data, including, but not limited to the Motion and Fitness API
|Such as form of payment, payment card number, or bank account number. If your app uses a payment service, the payment information is entered outside your app, and you, as the developer never have access to the payment information. It is not collected and does not need to be disclosed.
|Such as credit score
|Other Financial Info
|Such as salary, income, assets, debts or any other financial information
|Information describing the location of a user or device with the same or greater resolution as a latitude and longitude with three or more decimal places
|It is optional for publishers to share "precise location" and allow DT to collect it. This means that only if the publishers allows its app to collect location data from users after obtaining user's explicit consent to such data collection, then such data is also collected via the DT SDK. DT does not collect or attempt to collect such information independently.
|Information describing the location of a user or device with lower resolution than a latitude or longitude with three or more decimal places - such as Approximate Location Services
|It is optional for publishers to share "coarse location" and allow DT to collect it. This means that only if the publishers allows its app to collet location data from users after obtaining user's explicit consent to such data collection, then such data is also collected via the DT SDK. However, DT does not collect or attempt to collect such location information independently.
|Such as racial or ethnic data, sexual orientation, pregnancy or childbirth information, disability, religious or philosophical beliefs, trade union membership, political opinion, genetic information or biometric data
|Such as a list of contacts in the user's phone, address book or social graph
|Emails or Text Messages
|Including subject line, sender, recipients and contents of the email or message
|Photos or Videos
|The photos and videos of the user
|Voice or sound recordings of the user
|Such as user-generated content in-game
|Data generated by the user during a customer support request
|Relevant to Offer Wall Customers Only:
As part of the DT Offer Wall service to publishers, users may contact DT 's customer support with queries that are related to the engagement with an offer. When submitting a query, the user may provide his/her name (or nickname) and email address. Depending on the type of request, users may be requested to provide additional information to DT to establish proof that a certain offer was completed which may be in the form of a screenshot, proof of purchase, a receipt, a bank statement etc...
|Other User Content
|Any other user-generated content
|Information about content the user has viewed that is not part of the app, such as websites
|Information about searches performed in the app
|Such as screen name, handle, account ID, assigned user ID, customer number, or other user- or account-level ID that can be used to identify a particular user or account
|DT may collect a publisher/app specific user identifier if provided by the app. DT collect or attempt to collect such information independently.
|Such as the device’s advertising identifier, or other device-level ID
|DT collects IDFA (Identifier for Advertisers) when made available by the user per the device settings (i.e. LAT is disabled) and IDFV (Identifier for Vendors) for the purposes such as counting Daily Active Users, Frequency Capping, and Server Side Rewarding.
|An account's or individual's purchases or purchase tendencies
|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
|Such as information about the advertisements the user has seen
|DT collects information related to the ads served to users of the app via the DT services (e.g. impressions, advertiser name, clicks, completions).
|Other Usage Data
|Any other data about user activity in the app
|Such as crash logs
|DT monitors the crash logs of the app.
|Such as launch time, hang rate or energy use
|Other Diagnostic Data
|Any other data collected for the purposes of measuring technical diagnostics related to the app
|Other Data Types
|Any other data types not mentioned