How to Remove Your Data from Kochava: Step-by-Step Guide 2026
To request action from Kochava, open its current Opt-Out & Do Not Sell route and in Step 1 choose at least one search method: Mobile Ad ID, Email Address, or Personal Info consisting of your full name and mailing address. In Step 2 choose the request type, including Delete My Data + Opt Me Out, selected data categories, or a copy of data found; provide a valid notification email and submit. The separate customer/device endpoint uses the account ID, app GUID, device-ID type, and device ID that Kochava publishes. The current catalog does not record a routine government-ID requirement for Kochava; that is not a promise that the live route will never ask for verification. A mobile-data provider with a device-specific opt-out route and an FTC location-data case.
Free exposure check
Select recognizable services from a public breach index to see relevant broker coverage; optional context signals explain the estimate. No name or email needed.
Check my exposure
Your record may be duplicated across related databases or sister sites like LiveRamp, Nielsen, Merkle, Acxiom. Removing your data from Kochava does not prove that these other properties changed.
Request Removal Now| Cost | Check Kochava's current privacy notice; this catalog does not establish a fee or guarantee a no-charge route. |
|---|---|
| Opt-out method | Official opt-out form or email to privacy@kochava.com |
| Verification | No routine government-ID requirement recorded; verify the live route |
| Difficulty | Moderate (3/5) · see the catalog difficulty index |
| DIY priority | Medium impact. This is a routing label, not a removal success rate or legal conclusion. |
| Evidence depth | Deep evidence: 153/258 tracked fields, 230 evidence facts. |
| Minimum-effort path | Form first, email fallback. Current route checked 2026-10-13. |
| Re-check | Provider- and risk-dependent; verify when a new listing, source change, or safety concern warrants it |
Manual DIY Removal vs. OfflistMe Request Drafts
Provider routes, verification, fees, and scope vary. This is a workflow comparison, not a timing, monitoring, legal, or removal-outcome promise.
| Feature / Effort | Manual DIY Opt-Out | OfflistMe Request Drafts |
|---|---|---|
| Time required | Depends on the provider route and number of records | Draft creation is local; review and sending remain yours |
| Number of forms to submit | One route per provider or source where required | Selected workflows still require review |
| Email & ID verifications | Provider-specific verification | User reviews and sends from their own inbox |
| Re-exposure monitoring | No automatic result is promised | Keep evidence and re-check as needed |
| Subscription commitment | Provider terms and any applicable fee | Review the current plan and access terms |
Generate Your Kochava Opt-Out Request
Review the current route for Kochava and any other selected workflows.
Request Removal NowGenerate your Kochava opt-out email draft
No name, email, or sign-up is needed to open the draft. Review the privacy-request language, fill in only the details needed to identify you, and send it directly to Kochavaif the provider's current route accepts email.
Sends to privacy@kochava.com · Prefer their form? Opt out on kochava.com directly
Want to review selected data brokers at once? OfflistMe records 1,000+ data brokers and can prepare reviewable drafts; you choose what to send and keep the submission evidence.
What is Kochava?
Kochava provides mobile-app analytics and advertising-related services and is described by the Federal Trade Commission as a data broker in its Kochava case materials. The FTC sued Kochava in 2022, alleging that its collection, use, and disclosure of precise location data could reveal movements to sensitive locations. The FTC case page was last updated June 26, 2026, lists the case as pending, and links a stipulated order; the FTC says a stipulated final order has the force of law when approved and signed by the district court. Do not treat the case as fully resolved without checking the current court and FTC records.
Catalog-described data types for Kochava
- •Mobile advertising identifiers such as Apple IDFA and Android ADID, where available and relevant to the provider route
- •Kochava or device identifiers and app/device attribution data described in Kochava SDK documentation
- •IP address and general location derived from network communication, as described in Kochava SDK documentation
- •Precise location data alleged in the FTC Kochava case materials
- •Other data points that vary by SDK, platform, customer configuration, and service; this is not a complete live inventory
Why Your Data Appears on Kochava
Kochava's support documentation identifies an account ID, app GUID, device-ID type, and device ID as relevant to some privacy requests, while its SDK documentation says transmitted data varies by platform, SDK, and configuration. An app or customer using a Kochava route may therefore associate a device identifier or app-attribution data with the provider. This guide does not establish that any specific app sent your data or that every Kochava service uses location data.
Where Kochava gets your data
- →Kochava SDK integrations and customer/app configurations described in provider documentation
- →Mobile-device and location-data sources described in the FTC Kochava case materials
- →Other provider or customer sources that are not established as a complete live inventory in this guide
Step-by-Step: How to Remove Your Data from Kochava
The provider may offer a no-charge request route, but terms can change. Verify the result against the live listing after submitting.
Choose how Kochava should find your data
In Step 1, select at least one search method: Mobile Ad ID, Email Address, or Personal Info. The Personal Info option asks for your full name and mailing address. A Mobile Ad ID request is device-specific, so keep the device scope clear when that method applies.
Select the request type and notification email
In Step 2, select the request type shown by the form, such as Delete My Data + Opt Me Out, a request for data categories, or a copy of data found. Provide a valid email address for notification, complete the form's ownership or authorization certification and CAPTCHA, then submit.
Use the separate customer/device endpoint when needed
For the separate customer/device privacy-request endpoint, Kochava lists four data points: account ID, relevant app GUID, device-ID type, and device ID. The same documentation says not to send a name, email address, physical address, or other unrelated personal information to that endpoint.
Review device and app privacy settings separately
Kochava's opt-out page links to Apple and Google guidance for device-level ad-tracking choices. Those settings may affect future advertising or data collection, but changing an advertising identifier does not by itself delete provider records already associated with an earlier identifier.
Save the submission evidence
Keep the exact route, date, device identifier scope, and any confirmation or provider response. The current provider materials reviewed here do not establish a universal verification-email step or a universal processing deadline for every request type.
Re-check the exact scope yourself
After following the provider's current instructions, use any available acknowledgement or access channel to ask what happened to the submitted identifier. A changed ad-setting, a provider acknowledgement, a source deletion, and removal from search results are different outcomes; do not assume one proves the others.
How Long Does Kochava Removal Take?
This guide has no verified processing time for Kochava. Keep the confirmation or acknowledgement from the request, then search for the exact listing again after the route's last step to see whether it changed.
OfflistMe Scores for Kochava
Two published formulas applied to the same evidence as every other broker in our 1,034-record catalog, so Kochava can be compared like for like. The burden score measures the documented opt-out route; the reach score measures how widely the company is formally present in the data trade. Neither predicts whether a request will succeed.
Opt-Out Burden Score
How much effort does Kochava's documented opt-out route ask of you?
23/ 100Light
Higher than 5% of the 1,034 brokers OfflistMe tracks.
- Documented difficulty
- 22.5 / 45
- Catalog difficulty 3 of 5
- Government ID required
- 0 / 15
- No routine ID request recorded
- Sensitive identifiers requested
- 0 / 10
- No SSN, date-of-birth, or ID-number field recorded
- Confirmation loop
- 0 / 5
- No confirmation step recorded
- No self-serve web route
- 0 / 10
- A web form or opt-out link is listed
- Opt-out page hidden from search
- 0 / 15
- Not in the noindex scan
OBS v1 (2026-10-31). Weighted sum of recorded inputs; a missing input scores 0. How this is calculated
Score by OfflistMe · offlist.me
Exposure Reach Score
How widely is Kochava registered and connected in the data trade?
13/ 100Narrow
- State broker-registry footprint
- 12.5 / 50
- Matched in 1 of 4 state registries (VT)
- Corporate family in catalog
- 0 / 25
- No sibling brands under a shared parent in the catalog
- People-search catalog category
- 0 / 25
- Filed under Advertising & Adtech
ERS v1 (2026-10-31). Weighted sum of recorded inputs; a missing input scores 0. How this is calculated
Score by OfflistMe · offlist.me
What Documents Kochava May Request
No routine ID requirement recorded
- •At least one consumer-form search method: Mobile Advertising ID, email address, or full name plus mailing address
- •A valid notification email for the consumer form
- •For the documented privacy-request endpoint: account ID, relevant app GUID, device-ID type, and device ID
Safety note on ID uploads
The consumer form and the customer/device endpoint have different scopes. Kochava's endpoint documentation says not to send a name, email address, physical address, or other personal information beyond the listed device and app identifiers to that endpoint. Provide only what the selected current route requests.
Evidence and data profile
This guide is enriched from the current broker dossier. It helps you choose a route and limit unnecessary disclosure; it is not proof that the broker has every listed data type or that a request will succeed.
Tracked evidence
153/258 tracked fields across 230 evidence facts
Route and freshness
Current route checked 2026-10-13. Next route recheck due 2026-11-27.
Legal operator & parent company
Kochava Inc. The catalog records no distinct external corporate parent for this entity.
Evidence areas
- request workflow
- source provenance
- data categories
- registry profile
Recorded data-domain signals
- Advertising & Adtech
Minimum-effort path
- Try the official form first when it matches your record.
- Use the prefilled privacy email only as a fallback or follow-up.
Direct evidence sources
These links support the route and workflow fields shown above. A reachable page or source record does not prove that a request was accepted, completed, or that data was deleted.
- https://www.kochava.com/opt-out-do-not-sell-request-process/ ↗
- https://support.kochava.com/articles/reference-information/28477-kochava-privacy-request ↗
- https://www.kochava.com/privacy/opt-out/ ↗
- https://www.kochava.com/legal/website-visitor-privacy-policy/?int-link=menu-website-privacy ↗
Workflow source checked 2026-09-02. Evidence label: official current first party privacy request guide and opt out page.
Medium impact and data-depth labels prioritize DIY routing. They are not removal success rates, legal conclusions, or proof that a broker deleted data.
What to Do If Kochava Removal Fails
If the standard opt-out process does not work, follow these escalation steps in order:
If the current route fails, record the exact URL, date, error, and identifier scope. Kochava publishes privacy@kochava.com as an assistance address; use the provider's current instructions and send only the identifiers required for the request type.
If Kochava acknowledges a request but does not explain the outcome, ask for a status update using the current provider notice and the law that applies to your request. Do not assume a 30-day or 45-day deadline applies to every route or request type.
If Kochava does not respond within the period stated by its current notice or the law that applies to you, keep the request and any acknowledgement, then use the relevant regulator or complaint channel.
Alternative Options
Manual removal
Kochava describes its consumer opt-out as device-specific, so a submission may cover only the MAID you provide and does not establish what happens to other identifiers, sources, or downstream copies. Review the current route and submit separate device identifiers when appropriate.
Request drafting (OfflistMe)
OfflistMe's public catalog contains 1,034 US/global data brokers, including Kochava where a route is recorded. It can help prepare a reviewable request for the identifiers you choose to provide; check related mobile-data providers separately and verify what each provider actually changed.
Request Removal NowFrequently Asked Questions
A provider can receive data through an app or customer integration without the provider having a consumer-facing app of its own. Kochava's current SDK materials say transmitted data varies by platform, SDK, and configuration, while the FTC case materials describe mobile-device location data allegations. This guide cannot determine whether a particular app sent your data; review the app's disclosures and the provider's current route before submitting identifiers.
In August 2022 the FTC sued Kochava under FTC Act § 5, alleging that its collection, use, and disclosure of precise location data could reveal movements to sensitive places. The FTC case page, last updated June 26, 2026, lists the case as pending and links a stipulated order; the FTC says a stipulated final order has force of law when approved and signed by the district court. The current sources do not support ranking the case as one of the most significant privacy-enforcement actions in US history.
No such guarantee follows from resetting an advertising identifier. It may affect future advertising or attribution signals, but it does not by itself delete records associated with an earlier identifier. Kochava describes its consumer opt-out as device-specific, so review the provider's current route and keep the scope of any request explicit; a VPN is not a deletion mechanism.
The current sources reviewed for this guide do not establish a complete, current list of Kochava buyers or a universal government or law-enforcement practice. The FTC case materials address alleged location-data sales and sharing. Review Kochava's current disclosures and any applicable order; a consumer opt-out does not by itself establish what happened to every downstream copy or buyer-held record.
No. The current Kochava page describes a device-specific Kochava route, not a universal opt-out from every app, platform, broker, or downstream recipient. Review device and app privacy settings and other providers separately, and do not treat one provider confirmation as proof that mobile ad tracking or all related records have stopped.
Know the laws behind this request
A request to Kochava may involve a privacy law, provider policy, or no statutory route depending on your location and the data. These explainers are starting points; read the relevant legal context, then check the current law, scope, exemptions, and provider role before citing one.
Regulatory enforcement history
Kochava has been the subject of government enforcement action. The detail page below links to the primary-source government press release and consent order.
Kochava FTC Enforcement (2022), location data sold without consent→Official registry entries for Kochava
Under state data-broker laws, Kochava must publicly register and disclose opt-out contact info. These are the official filings.
Generate requests in under 60 seconds
Don't stop at Kochava
Reviewable Request Draft
Prepare a reviewable Kochavarequest draft, then send it yourself after checking the provider's current route.
Request Removal Now