LoopMe Limited: data broker profile and opt-out route
This record explains how to contact LoopMe Limited, 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 LoopMe Limited accepted, processed, or completed a request.
Quick answer
To request removal from LoopMe Limited, use the recorded provider route at legal.loopme.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.
LoopMe Limited at a glance
- Domain
- loopme.com
- Request method
- Both
- Catalog difficulty
- 3/5
- Processing estimate
- 14-30 days
- Standard ID flag
- Not flagged in standard workflow
- Country scope
- US, EU/UK, 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
- Not recorded
- Parent entity
- Not recorded
- Catalog lifecycle
- Active Catalog Record
- Lifecycle status
- Active Catalog Record
- Registry matches
- 3 profiles
- Evidence conflicts
- None recorded
- Recorded data domains
- advertising adtech, location data, device identifiers, behavioral events
- Source checked
- 2026-08-13
- Entity reviewed
- 2026-08-13
- Next route review
- 2026-09-27
How to use this LoopMe Limited opt-out record
- 1
Open the provider route and confirm that it matches LoopMe Limited 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 Device Or Browser Advertising Identifier For The Device-Level Opt-Out When Applicable, Details Sufficient To Locate The Record For Access, Correction, Or Deletion Requests, Requested Privacy Action.
- 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
- Access Personal Information
- Correct Personal Information
- Opt Out Sale Sharing
- Opt Out Targeted Advertising
- Delete Personal Information
- Restrict Processing
- Appeal Privacy Request Decision
Submission channels
- Web Privacy Route
- Device Advertising Identifier Settings
- Browser Opt Out Signal
Required fields
- Device Or Browser Advertising Identifier For The Device-Level Opt-Out When Applicable
- Details Sufficient To Locate The Record For Access, Correction, Or Deletion Requests
- Requested Privacy Action
Optional or contextual fields
Not recorded in this workflow snapshot.
Extra steps
- LoopMe'S Advertising Opt-Out Is Device- And Browser-Specific; Repeat It On Each Browser, Mobile Device, Or Connected-TV Device Where Needed.
- LoopMe Says An Advertising Opt-Out May Still Leave Contextual Advertisements Visible; It Changes Personalization Rather Than Blocking All Ads.
- Access, Correction, Deletion, And Appeals Use Privacy@Loopme.Com; The Opt-Out Page Is Primarily A Browser/Device Identifier Choice.
- LoopMe Distinguishes Its Own Controller Processing From Partner-Controlled Data And May Direct Requests To The Relevant Partner In Those Cases.
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
- • Geolocation: true
Published sharing context
- • ForeignActor
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: LoopMe may request additional information to verify an access, correction, or deletion request and says a request containing only a name or email may be insufficient because it does not process those identifiers in isolation.
Government-ID expectation: No universal government-ID requirement is stated in the cited current LoopMe privacy notice or opt-out page.
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: LoopMe Limited; Chartboost, LLC; LoopMe Ltd.
Registry jurisdictions: US-CA, US-TX.
Registered websites: https://loopme.com; https://www.loopme.com; https://loopme.com/.
Entity review: 2026-08-13.
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 | Chartboost, LLC | Not recorded | Not recorded | Not recorded |
| US-CA | LoopMe Limited | Not recorded | Not recorded | Not recorded |
| US-TX | LoopMe Ltd | 20250008 | Not recorded | 2026-08-11 |
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 114/258 tracked fields across 195 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.loopme.com/privacy-center/loopme-opt-out?v=3.4 ↗ | 2026-08-13 |
| provider-published workflow source | https://legal.loopme.com/privacy-center/loopme-privacy-notice?v=5.1 ↗ | 2026-08-13 |
| provider-published workflow source | https://legal.loopme.com/privacy-center/loopme-opt-out?v=3.4 ↗ | 2026-08-13 |
Evidence label: Official Current First Party LoopMe Privacy Notice And Privacy Center Opt Out Confirmed With Device Scope Caveats. Source checked: 2026-08-13.
Latest web route observation: 2026-08-13 · reachable · HTTP/status 200 · final URL https://legal.loopme.com/privacy-center/loopme-opt-out?v=3.4.
Latest independent provider URL observation: 2026-08-13 · reachable · HTTP/status 200 · final URL https://legal.loopme.com/privacy-center/loopme-opt-out?v=3.4 · observed URL https://legal.loopme.com/privacy-center/loopme-opt-out?v=3.4. 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 · loopme.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):
- Optional Or Contextual Fields
- 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 | 16/22 fields | 72.7% | partial |
| data categories | 13/32 fields | 40.6% | partial |
| entity identity | 10/20 fields | 50.0% | partial |
| privacy risk | 7/28 fields | 25.0% | partial |
| registry profile | 16/39 fields | 41.0% | 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 LoopMe Limited 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
LoopMe Limited opt-out FAQ
How do I opt out of LoopMe Limited?
Use the provider route at https://legal.loopme.com/privacy-center/loopme-opt-out?v=3.4. Review the fields and verification steps before submitting. A reachable page does not prove that the provider accepted or completed a request.
Does LoopMe Limited require government ID?
No universal government-ID requirement is stated in the cited current LoopMe privacy notice or opt-out page.
How long does LoopMe Limited 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 LoopMe Limited?
This snapshot does not record source-backed values for Optional Or Contextual Fields, Parent Entity, Suppression Group. Confirm legal name, DBA names, ownership, shared suppression routes, and lifecycle from an official source.