Build on it
Privacy and App Store disclosure
What the DL2App SDKs collect and suggested answers for Apple's App Privacy questions and Google Play's Data safety form.
When your app includes a DL2App SDK, you have to describe what it collects in App Store Connect and in Play Console. This page lists what the SDKs send and suggests answers. You are responsible for your app’s answers as a whole; anything else your app collects adds to these.
What the SDK sends
| Data | When | Why |
|---|---|---|
| Install ID: random, created by the SDK, not derived from the device | Every request | Deliver a deferred link once; tie events to a link |
| OS version, app version, SDK version | Every launch call | Matching and compatibility |
| Screen size, language, time zone | First launch | Match the install to the tap |
| IP address, as seen by our server. Stored only truncated or as a hash keyed with a secret that changes daily | Every request | Match the install to the tap; country for statistics |
| Play install referrer | First launch, Android | Exact match to the tap |
| Clipboard text | Only if you enable it and the user taps the paste button, iOS | Exact match to the tap |
Events you send with track | When you call it | Your own analytics |
Never collected: the IDFA, the Android advertising ID, any hardware identifier, contacts, precise location, or anything from other apps. The SDK does not track people across apps or websites, so you do not need the App Tracking Transparency prompt for it.
The iOS SDKs ship a PrivacyInfo.xcprivacy manifest (no tracking, no tracking domains, the UserDefaults required-reason entry), which Xcode merges into your app’s privacy report.
App Store: App Privacy
| Question | Suggested answer |
|---|---|
| Do you or your third-party partners collect data from this app? | Yes |
| Identifiers: Device ID | Collected (the install ID). Purposes: App Functionality, Analytics. Linked to the user: No. Used for tracking: No. |
| Usage Data: Product Interaction | Collected (link opens, and events if you call track). Purposes: App Functionality, Analytics. Linked: No. Tracking: No. |
| Diagnostics: Other Diagnostic Data | Collected (OS version, screen size, language, time zone). Purpose: App Functionality. Linked: No. Tracking: No. |
| Location: Coarse Location | Not collected by the SDK. DL2App derives country and city from the IP address on its servers for click statistics and does not store the address. |
| Purchases | Only if you send purchase values with track. |
| Is data used to track users? | No |
If your events include a user ID, or anything in props that identifies a person, answer “Linked to the user: Yes” for Product Interaction.
Google Play: Data safety
| Question | Suggested answer |
|---|---|
| Does your app collect or share any of the required user data types? | Yes |
| Is all of the user data collected by your app encrypted in transit? | Yes (the SDK only uses HTTPS) |
| Device or other IDs | Collected, not shared. Purposes: App functionality, Analytics. |
| App activity: App interactions | Collected, not shared. Purposes: App functionality, Analytics. |
| App info and performance: Diagnostics | Collected, not shared. Purpose: App functionality. |
| Location | Not collected. |
| Financial info: Purchase history | Only if you send purchase values with track. |
| Can users request that data is deleted? | Answer according to your own policy. We act on deletion requests you pass to us. |
DL2App acts as your service provider, so under Google’s definitions sending data to it is “collected”, not “shared”.
Your privacy policy
Say that your app uses a link service to open the right screen from links and after installation, what is sent (the table above), and that it is not used for advertising. Link to our privacy page for retention periods.