AppLovin: data broker profile and opt-out route
This record explains how to contact AppLovin, what the catalog currently records about its request workflow, what information may be needed to match a record, and what evidence to keep. It is a source-backed routing reference—not proof that AppLovin accepted, processed, or completed a request.
Quick answer
To request removal from AppLovin, use the recorded provider route at applovin.com ↗. The catalog currently records Link as the request method, an estimated processing time of About 1 day for automatically verified requests; otherwise varies, and latest evidence dated 2026-08-13.
AppLovin at a glance
- Domain
- applovin.com
- Request method
- Link
- Catalog difficulty
- 4/5
- Processing estimate
- About 1 day for automatically verified requests; otherwise varies
- Standard ID flag
- Not flagged in standard workflow
- Country scope
- Global
- Evidence grade
- First-party route checked
- Evidence status
- Current route evidence recorded
- Independent route observation
- URL route observed
- Read-only semantic disposition
- Not recorded
- Legal operator
- AppLovin Corporation
- Parent entity
- Not recorded
- Catalog lifecycle
- Active Catalog Record
- Lifecycle status
- Active Catalog Record
- Registry matches
- 1 profile
- Evidence conflicts
- None recorded
- Recorded data domains
- advertising adtech, location data, device identifiers, behavioral events
- Source checked
- 2026-08-13
- Entity reviewed
- 2026-08-12
- Next route review
- 2026-09-27
How to use this AppLovin opt-out record
- 1
Open the provider route and confirm that it matches AppLovin and the type of record you want to address.
- 2
Prepare only the matching information the provider asks for. The catalog records required fields as Valid Email Address For Ecommerce-Linked Access Or Deletion Requests, Advertising Identifier Or Device Context For App-Linked Requests.
- 3
Review the request, submit it yourself, save any confirmation, and re-check the source listing after the provider window. A prepared draft is not a completed deletion.
Recorded workflow details
Request types
- Delete Personal Information
- Access Personal Information
- Opt Out Sale Or Sharing
- Opt Out Targeted Advertising
Submission channels
- Privacy Management App
- Web Form
- In Ad Opt Out Control
- Device Settings
Required fields
- Valid Email Address For Ecommerce-Linked Access Or Deletion Requests
- Advertising Identifier Or Device Context For App-Linked Requests
Optional or contextual fields
- Information Sufficient To Identify A Business-Contact Record
- Authorized-Agent Proof When Applicable
Extra steps
- Use The Privacy Management App For Data Linked To An Advertising Identifier In Mobile Apps Or Games.
- Use The Privacy Rights Request Portal For Email- Or Phone-Linked Ecommerce Data.
- An In-Ad Or Device-Level Opt-Out Reduces Targeted Advertising But Does Not Mean All Advertising Stops.
Completion evidence to keep
- App Or Portal Confirmation
- Broker Response Or Deletion Confirmation
- Device Or Ad Choice Recheck
What this record is associated with
The catalog and matched registry evidence associate this provider with the following data domains:
- advertising adtech
- location data
- device identifiers
- behavioral events
These labels describe documented business or registry context. They do not prove that a particular person has a profile or that every listed domain uses the same request route.
Registry-declared data and regulatory signals
Data signals
Not recorded in matched registry rows.
Published sharing context
No positive sharing flag recorded.
Regulated contexts
No positive regulated-context flag recorded.
These are provider or registry declarations where available. They describe collection or business context; they do not prove that a particular person appears in the database or that removal will affect every downstream recipient.
Identity and verification boundary
Provider-specific expectation: AppLovin says app-linked requests can be verified through the advertising identifier; ecommerce-linked requests require a valid email address and may require additional identity verification.
Government-ID expectation: A standard government-ID requirement is not stated for the consumer routes; AppLovin may require additional verification where necessary.
Do not attach a government ID or other sensitive document unless the provider's current instructions require it for the request you are making. Redact unnecessary fields where the provider allows it.
Legal entity and registry context
Registered names linked to this catalog record: AppLovin Corporation.
Registry jurisdictions: US-CA.
Registered websites: https://www.applovin.com.
Catalog legal operator: AppLovin Corporation.
Entity review: 2026-08-12.
This is a registry match for entity and route research. It does not by itself prove that every listed legal entity uses the same consumer route, owns the brand, or shares one suppression result.
Registry evidence by jurisdiction
| Jurisdiction | Legal name | Registration | Status | Captured/updated |
|---|---|---|---|---|
| US-CA | AppLovin Corporation | Not recorded | Not recorded | Not recorded |
Registry rows are source context. They do not establish request acceptance, removal, suppression sharing, or current route availability.
Evidence, freshness, and limitations
Evidence grade: First-party route checked. Useful evidence: this record tracks 102/258 tracked fields across 139 evidence facts. Current route checked 2026-08-13. Next route recheck due 2026-09-27.
The source links below support the recorded route and workflow fields. A source page, HTTP response, registry row, or email address does not prove that a provider accepted a request, deleted data, or will not republish it.
Source ledger
| Evidence type | Source | Observed/checked |
|---|---|---|
| catalog route | https://applovin.com/en/privacy-data-request ↗ | 2026-08-13 |
| provider-published workflow source | https://legal.applovin.com/multistate-privacy-notice/ ↗ | 2026-08-12 |
| provider-published workflow source | https://applovin.com/en/privacy-data-request ↗ | 2026-08-12 |
| provider-published workflow source | https://legal.applovin.com/privacy ↗ | 2026-08-12 |
Evidence label: Official Source Confirmed. Source checked: 2026-08-13.
Latest web route observation: 2026-08-13 · reachable · HTTP/status 200 · final URL https://applovin.com/en/privacy-data-request.
Latest independent provider URL observation: 2026-08-13 · reachable · HTTP/status 200 · final URL https://applovin.com/en/privacy-data-request · observed URL https://applovin.com/en/privacy-data-request. This is a read-only observation of a provider-published URL; it does not by itself establish canonical route semantics, form submission, request acceptance, or deletion.
Latest email-domain observation: 2026-08-13 · DNS reachable · applovin.com. Mailbox acceptance was not tested.
What is still unknown in this snapshot
This profile is intentionally explicit about its limits. “Not recorded” means no source-backed value is present in this snapshot; it does not mean the provider lacks the information.
Missing or unknown tracked fields (3 total):
- Aliases
- Parent Entity
- Suppression Group
Next evidence actions:
- Confirm legal name, DBA names, ownership, shared suppression routes, and lifecycle from an official source.
- Classify the broker's products, data types, use cases, and operating scope from first-party or regulator evidence.
- Match regulator records to the legal entity and preserve jurisdiction-specific scope, collection, sharing, and request-metric evidence.
Incomplete evidence dimensions: Entity, Business, Regulatory, Workflow, Route, Privacy, Verification, Catalog, Provenance.
Evidence completeness by dimension
| Dimension | Documented | Coverage | Status |
|---|---|---|---|
| catalog metadata | 7/14 fields | 50.0% | partial |
| contact routes | 15/22 fields | 68.2% | partial |
| data categories | 9/32 fields | 28.1% | partial |
| entity identity | 9/20 fields | 45.0% | partial |
| privacy risk | 6/28 fields | 21.4% | partial |
| registry profile | 13/39 fields | 33.3% | partial |
| request workflow | 12/41 fields | 29.3% | partial |
| route checks | 14/38 fields | 36.8% | partial |
| source provenance | 17/24 fields | 70.8% | partial |
Coverage is the share of tracked fields with a recorded value in this evidence snapshot. It is not a quality score, removal rate, or proof that unrecorded information does not exist.
Related Advertising & Adtech profiles
These records are grouped with AppLovin under the same catalog category. The grouping is for discovery; it does not establish common ownership, shared suppression, or a shared request outcome.
- 33Across, Inc.
33across.com
Ambiguous page observed; submission route not confirmed
- ACREMAPS LLC
acres.com
Current route evidence recorded
- AdAdapted, Inc.
adadapted.com
Current route evidence recorded
- ADARA, Inc. (a RateGain company)
adara.com
Current route evidence recorded
- Adprime Media LLC
adprime.com
First-party request-route candidate; manual review required
- adsquare GmbH
adsquare.com
First-party request-route candidate; manual review required
AppLovin opt-out FAQ
How do I opt out of AppLovin?
Use the provider route at https://applovin.com/en/privacy-data-request. Review the fields and verification steps before submitting. A reachable page does not prove that the provider accepted or completed a request.
Does AppLovin require government ID?
A standard government-ID requirement is not stated for the consumer routes; AppLovin may require additional verification where necessary.
How long does AppLovin take to process an opt-out?
The catalog estimate is About 1 day for automatically verified requests; otherwise varies. This is an estimate, not an SLA or proof of deletion. Check the provider response and re-check the source listing yourself.
What is still unverified about AppLovin?
This snapshot does not record source-backed values for Aliases, Parent Entity, Suppression Group. Confirm legal name, DBA names, ownership, shared suppression routes, and lifecycle from an official source.