Eyeota Pte Ltd: data broker profile and opt-out route
This record explains how to contact Eyeota Pte Ltd, 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 Eyeota Pte Ltd accepted, processed, or completed a request.
Quick answer
To request removal from Eyeota Pte Ltd, use the recorded provider route at eyeota.com ↗. The catalog currently records Both as the request method, an estimated processing time of 14-30 days, and latest evidence dated 2026-08-13.
Eyeota Pte Ltd at a glance
- Domain
- eyeota.com
- Request method
- Both
- Catalog difficulty
- 3/5
- Processing estimate
- 14-30 days
- Standard ID flag
- Not flagged in standard workflow
- Country scope
- Us
- 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
- Eyeota Pte Ltd
- 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-11
- Next route review
- 2026-09-27
How to use this Eyeota Pte Ltd opt-out record
- 1
Open the provider route and confirm that it matches Eyeota Pte Ltd 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 The Official California Data-Broker Registry Entry Does Not State The Complete Current Field List..
- 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
- Opt Out Sale Sharing
- Delete Personal Information
Submission channels
- Web Privacy Route
- Phone
- Postal Mail
Required fields
- The Official California Data-Broker Registry Entry Does Not State The Complete Current Field List.
Optional or contextual fields
Not recorded in this workflow snapshot.
Extra steps
- Use The Registered Privacy Route Before Relying On The Legacy Email Field In This Record.
- Confirm Current Form Fields, Identity Checks, And Any Email-Confirmation Step Before Presenting A Final User Instruction.
- Registry Context: Eyeota'S Privacy Center (Https://Www.Eyeota.Com/Privacy-Center) Gives More Information About How We Manage Our Privacy Compliance Globally, Highlight How We Protect And Manage Personal Data And Provide Details How You Can Exercise Your Rights As A Data Subject. With Regard To The Submitted Metrics, When An Individual Submits A “Right To Know” Request We Advise The Individual What Personal Information We Have Collected About Them, What Personal Information Was Sold Or Shared, And To Whom It Was Sold Or Shared. Therefore, The Numbers For Both Questions Regarding The “Right To Know” Are The Same. With Regard To The Number Of Requests That Have Been “Complied With In Whole Or In Part”, We Do Not Have Separate Metrics As We Have Interpreted “Comply” To Mean Comply With The CPRA And “In Whole OR In Part” As One Figure. As We Fully Comply With The CPRA We Do Not Have Any Requests That Were Partially Complied With.
Completion evidence to keep
- Form Confirmation
- Email Sent Record
- Broker Response If Provided
- Source 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
- • GenAI
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: The official California data-broker registry entry does not specify the current verification method.
Government-ID expectation: not_stated_in_authoritative_source
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: Eyeota Pte Ltd.
Registry jurisdictions: US-CA.
Registered websites: https://www.eyeota.com.
Catalog legal operator: Eyeota Pte Ltd.
Entity review: 2026-08-11.
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 | Eyeota Pte Ltd | 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. Deep evidence: this record tracks 108/258 tracked fields across 138 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://www.eyeota.com/data-subject-request-form ↗ | 2026-08-13 |
| provider-published workflow source | https://oag.ca.gov/data-brokers ↗ | 2026-08-11 |
| provider-published workflow source | https://www.eyeota.com/ ↗ | 2026-08-11 |
| provider-published workflow source | https://www.eyeota.com/privacy-center ↗ | 2026-08-11 |
| provider-published workflow source | https://www.eyeota.com/how-to-opt-out ↗ | 2026-08-11 |
| provider-published workflow source | https://www.eyeota.com/data-subject-request-form ↗ | 2026-08-11 |
| provider-published workflow source | https://www.eyeota.com ↗ | 2026-08-11 |
| provider-published workflow source | https://cppa.ca.gov/data_broker_registry/registry.csv ↗ | 2026-08-11 |
Evidence label: Official Ca Registry Snapshot. Source checked: 2026-08-13.
Latest web route observation: 2026-08-13 · reachable · HTTP/status 200 · final URL https://www.eyeota.com/data-subject-request-form.
Latest independent provider URL observation: 2026-08-13 · reachable · HTTP/status 200 · final URL https://www.eyeota.com/data-subject-request-form · observed URL https://www.eyeota.com/data-subject-request-form. 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-11 · DNS reachable · eyeota.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 (4 total):
- Optional Or Contextual Fields
- 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 | 8/14 fields | 57.1% | partial |
| contact routes | 14/22 fields | 63.6% | partial |
| data categories | 13/32 fields | 40.6% | partial |
| entity identity | 9/20 fields | 45.0% | partial |
| privacy risk | 7/28 fields | 25.0% | partial |
| registry profile | 13/39 fields | 33.3% | partial |
| request workflow | 13/41 fields | 31.7% | 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 Eyeota Pte Ltd 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
Eyeota Pte Ltd opt-out FAQ
How do I opt out of Eyeota Pte Ltd?
Use the provider route at https://www.eyeota.com/data-subject-request-form. Review the fields and verification steps before submitting. A reachable page does not prove that the provider accepted or completed a request.
Does Eyeota Pte Ltd require government ID?
not_stated_in_authoritative_source
How long does Eyeota Pte Ltd take to process an opt-out?
The catalog estimate is 14-30 days. 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 Eyeota Pte Ltd?
This snapshot does not record source-backed values for Optional Or Contextual Fields, Aliases, Parent Entity, Suppression Group. Confirm legal name, DBA names, ownership, shared suppression routes, and lifecycle from an official source.