Privacy
What the Android SDK sends, what it stores on the device, what it never touches, and how to fill in the Google Play data safety form.
The SDK is built to collect as little as possible. This page lists exactly what it does, so you can fill in your Google Play data safety form with confidence.
What the SDK sends
Every request goes to the Lander API (api.golander.link) over HTTPS.
| Data | When |
|---|---|
| The install ID (a random UUID v4) | Every request |
Platform (android), app version (versionName), OS version (Build.VERSION.RELEASE), SDK version | Each launch report (POST /v1/sdk/init) |
| Whether this is the first launch | Each launch report |
| The Play Install Referrer string | First launch only |
| The URLs that opened the app | When a link is resolved |
| The events you track, with the properties you pass | When the event queue flushes |
| The short links you create, with the fields you pass | createLink |
The user ID you pass to claimHandoff | claimHandoff (Lander stores only a salted hash) |
The device model, locale, Android ID, advertising ID (GAID) and any device fingerprint are not collected. The SDK never reads the clipboard and asks for no permission besides INTERNET.
What the SDK stores on the device
A few small files in noBackupFilesDir/lander: the install ID, a first launch marker and the event queue. Android never includes noBackupFilesDir in Auto Backup or device transfers, so they never move to another device, and you do not need to add backup rules for them. They are deleted when the app is uninstalled or its data is cleared.
Deferred links without fingerprinting
Deferred links on Android use the Play Install Referrer, which Google Play provides for exactly this purpose, or your own sign in (authenticated handoff). Probabilistic matching, when a project turns it on, only applies to iPhone clicks; the SDK sends nothing extra for it on any platform. See Deferred deep linking.
Google Play data safety
A starting point for the parts of the form the SDK touches. Your own use (the events and properties you send, the user IDs you pass) may add to it.
| Data type | Collected | Shared | Purpose |
|---|---|---|---|
| Device or other IDs (the random install ID) | Yes | No | Analytics, App functionality |
| App interactions (link opens, the events you track) | Yes | No | Analytics |
User IDs (only if you call claimHandoff) | Yes | No | App functionality |
Data is encrypted in transit (HTTPS). The install ID is not linked to an advertising ID and is not used for tracking across apps.