Consent and privacy controls for app measurement
Review how Linkrunner handles ATT, Google consent signals and opt-in PII hashing. Find the hosting details and processing documents your team needs for its review.
What the user chose
What Linkrunner receives
Join 400+ growth teams using Linkrunner.
Make collection settings part of your integration
Configure your app's consent handling and the SDK settings to match the data you intend to send. Certifications, sign-in security and Change History are on the trust and security page.
ATT decides what iOS measurement uses
The IDFA is collected only when the user allows tracking. Without it, installs are measured through SKAN 4 postbacks and, on iOS 17.4 and later, AdAttributionKit.
Allow
Ask App Not to Track
Hosted in India, or in your own cloud
Hosted Linkrunner stores data in India on Google Cloud asia-south1. Bring Your Own Cloud keeps every row in your cloud account.
Hosted Linkrunner
- Region
- India
- Location
- Google Cloud asia-south1
- Deletion
- Verified requests within 30 days
Bring Your Own Cloud
- Region
- Your cloud account
- Clouds
- GCP first, AWS planned
- Operator access
- RBAC and SSO
Allow
Ask App Not to Track
Include consent settings in your SDK setup
- 01
Ask for consent first
Plan your consent flow and review the SDK setup for your platform before sending production data.
- 02
Report what the user chose
Use the documented consent signals to pass the choices your app has collected. Confirm project-specific forwarding requirements with the team.
- 03
Update it when they change their mind
Consent is stored between launches. Call setConsent again whenever a user withdraws or grants consent in your settings.
What happens to each privacy signal
- ATT on iOSIDFA collected only when the user allows tracking
- SKAN and AdAttributionKitAggregated postbacks, no user-level ID
- Google consent (setConsent)Sent as the user chose; unknown is never sent
- TCF on iOSRead by the SDK from your consent platform
- PII hashingOpt in: SHA-256 in the SDK before it is sent
- AAID on AndroidCan be turned off for apps built for families
Trusted by teams that care about more than attribution.
“The level of customisation that Linkrunner was able to offer was unmatched by any of the other competitors we looked at. Their team took the time to understand our exact requirements and delivered a solution that felt tailored to our needs, rather than forcing us into a fixed framework. That flexibility made a significant difference for us and was one of the key reasons Linkrunner stood out.”
Ronald M Thomas
Digital Marketing, Playo
34%
CPI reduction in 3 months
₹20.30 → ₹13.39
Google Ads CPI drop (Dec '25 → Feb '26)
Where Linkrunner stands, and where you decide
The Trust Center lists GDPR, DPDPA, CCPA and COPPA alongside SOC 2 Type II and ISO 27001:2022. The Data Processing Agreement and the sub-processor list are public. As the app owner you decide what consent to ask for and what to send; Linkrunner processes end-user attribution data on your behalf under your agreement and the DPA.
On Android, Google consent forwarding depends on your project's configuration, so confirm it with the team before you rely on it for the Digital Markets Act. For apps built for children or families, setDisableAaidCollection stops the SDK from collecting the advertising ID.
Installs are matched deterministically first, through the Google Play Install Referrer, ad click IDs, device IDs where the user allows it and Apple AdServices, with IP and user-agent matching only when no deterministic signal exists. This page explains how the product works and is not legal advice.
Frequently asked questions
Consent, hashing, hosting and deletion, answered.
Review your measurement settings with the team
Check consent handling, hashing and hosting requirements before release. Use the Trust Center and DPA for your privacy and security review.