Lotame (Epsilon Data Management): data broker profile and opt-out route
This record explains how to contact Lotame (Epsilon Data Management), 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 Lotame (Epsilon Data Management) accepted, processed, or completed a request.
Quick answer
To request removal from Lotame (Epsilon Data Management), use the recorded provider route at legal.epsilon.com ↗. The catalog currently records Both as the request method, an estimated processing time of Confirmation within 10 days; good-faith fulfillment within 30 days, and latest evidence dated 2026-08-13.
Lotame (Epsilon Data Management) at a glance
- Domain
- lotame.com
- Request method
- Both
- Catalog difficulty
- 4/5
- Processing estimate
- Confirmation within 10 days; good-faith fulfillment within 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
- Not recorded
- Parent entity
- Not recorded
- Catalog lifecycle
- Active Catalog Record
- Lifecycle status
- Active Catalog Record
- Registry matches
- None recorded
- 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 Lotame (Epsilon Data Management) opt-out record
- 1
Open the provider route and confirm that it matches Lotame (Epsilon Data Management) 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 Email Address Or Device Identifier Relevant To The Request, Access To The Email Account Supplied For Email-Based Requests Unless Prohibited By Applicable Law, Location Or Jurisdiction Information For The Applicable Privacy Law.
- 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 Or Sharing
- Opt Out Targeted Advertising
- Access Personal Information
- Delete Behavior Profile
- Restrict Or Object To Processing
- Data Portability
Submission channels
- Epsilon Privacy Request Form
- Privacy Email
- Telephone
- Browser Or Device Opt Out Tools
Required fields
- Email Address Or Device Identifier Relevant To The Request
- Access To The Email Account Supplied For Email-Based Requests Unless Prohibited By Applicable Law
- Location Or Jurisdiction Information For The Applicable Privacy Law
Optional or contextual fields
- Mobile Advertising ID
- Connected-TV Identifier
- Lotame Panorama ID Or Lotame PID
- Name Of A Lotame Business Customer When The Request Concerns Customer-Controlled Data
Extra steps
- Lotame States That Epsilon Data Management, LLC Provides Lotame Services And That Lotame Solutions, Inc. Ceased To Exist As A Separate Legal Entity After Its 2025 Merger.
- Browser Opt-Out Applies Only To The Relevant Browser And Device Identifiers; Repeating It May Be Necessary On Other Browsers Or Devices.
- Requests Submitted Through The Lotame Route Apply To Data In Lotame'S Data Exchange Marketplace. Data Processed Strictly For A Business Customer Must Be Requested From That Customer.
- Lotame May Delete A Behavior Profile While Retaining Certain Identifiers To Honor Future Opt-Out Choices; Do Not Promise Complete Erasure Of Every Identifier.
Completion evidence to keep
- Privacy Form Confirmation
- Email Sent Record
- Broker Response
- Future Browser Or Device 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: Lotame says requests generally require some form of verification. Its email privacy-request route verifies access to the supplied email account, and the form collects IP information to determine the requester's state; other identifiers may be needed for device-level matching.
Government-ID expectation: No universal government-ID requirement is stated in the current Lotame services notice or Epsilon request route.
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
No matched government-registry profile is recorded for this catalog entry yet. Treat the provider name and route as source-backed catalog data, not as a confirmed legal-entity relationship.
Evidence, freshness, and limitations
Evidence grade: First-party route checked. Useful evidence: this record tracks 73/258 tracked fields across 100 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://legal.epsilon.com/dsr ↗ | 2026-08-13 |
| provider-published workflow source | https://www.lotame.com/privacy/services-privacy-notice/ ↗ | 2026-08-12 |
| provider-published workflow source | https://www.lotame.com/privacy/information-privacy-choices-services/ ↗ | 2026-08-12 |
| provider-published workflow source | https://legal.epsilon.com/dsr ↗ | 2026-08-12 |
Evidence label: Official First Party Policy And Request Route Confirmed. Source checked: 2026-08-13.
Latest web route observation: 2026-08-13 · reachable · HTTP/status 200 · final URL https://legal.epsilon.com/dsr.
Latest independent provider URL observation: 2026-08-13 · reachable · HTTP/status 200 · final URL https://legal.epsilon.com/dsr · observed URL https://legal.epsilon.com/dsr. 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 · epsilon.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 | 16/22 fields | 72.7% | partial |
| data categories | 2/32 fields | 6.3% | partial |
| entity identity | 4/20 fields | 20.0% | partial |
| privacy risk | 5/28 fields | 17.9% | partial |
| registry profile | 0/39 fields | 0.0% | missing |
| request workflow | 12/41 fields | 29.3% | partial |
| route checks | 12/38 fields | 31.6% | partial |
| source provenance | 15/24 fields | 62.5% | 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 Lotame (Epsilon Data Management) 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
Lotame (Epsilon Data Management) opt-out FAQ
How do I opt out of Lotame (Epsilon Data Management)?
Use the provider route at https://legal.epsilon.com/dsr. Review the fields and verification steps before submitting. A reachable page does not prove that the provider accepted or completed a request.
Does Lotame (Epsilon Data Management) require government ID?
No universal government-ID requirement is stated in the current Lotame services notice or Epsilon request route.
How long does Lotame (Epsilon Data Management) take to process an opt-out?
The catalog estimate is Confirmation within 10 days; good-faith fulfillment within 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 Lotame (Epsilon Data Management)?
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.