Demyst Data Ltd: data broker profile and opt-out route
This record explains how to contact Demyst Data 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 Demyst Data Ltd accepted, processed, or completed a request.
Quick answer
To request removal from Demyst Data Ltd, first verify the current request route because the latest read-only page observation is cross-domain request-route candidate; entity review required using privacy@demystdata.com. The catalog currently records Email as the request method, an estimated processing time of 14-30 days, and latest evidence dated 2026-08-13.
Demyst Data Ltd at a glance
- Domain
- demyst.com
- Request method
- Catalog difficulty
- 3/5
- Processing estimate
- 14-30 days
- Standard ID flag
- Not flagged in standard workflow
- Country scope
- US
- Evidence grade
- Cross-domain request-route candidate; entity review required
- Evidence status
- Cross-domain request-route candidate; entity review required
- Independent route observation
- URL observed; semantics pending
- Read-only semantic disposition
- Cross-domain request-route candidate; entity review required
- Legal operator
- Demyst Data 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
- credit/risk identity, fraud prevention, insurance data, credit data
- Source checked
- 2026-08-13
- Entity reviewed
- 2026-08-11
- Next route review
- 2026-09-27
How to use this Demyst Data Ltd opt-out record
- 1
Open the provider route and confirm that it matches Demyst Data 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 Full Name And Professional/Contact Context, The Specific Demyst Record Or Source Context, The Requested Access, Correction, Deletion, Objection, Or Opt-Out 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 Data
- Correct Personal Data
- Delete Account Or Personal Data
- Object To Processing
- Opt Out Sale Or Sharing
Submission channels
- Privacy Email
- Legal Email
- Privacy Policy Route
Required fields
- Full Name And Professional/Contact Context
- The Specific Demyst Record Or Source Context
- The Requested Access, Correction, Deletion, Objection, Or Opt-Out Action
Optional or contextual fields
Not recorded in this workflow snapshot.
Extra steps
- Ask Demyst Whether It Is Acting As Controller Or Service Provider For The Relevant Record.
- If Demyst Processes The Data For A Customer, The User May Need To Direct The Request To That Customer’S Privacy Route.
- For California Requests, State Whether The Request Is Access, Deletion, Or Opt-Out Of Sale; Legal Exceptions May Apply.
Completion evidence to keep
- Email Record
- Controller Or Customer Response
- Source Recheck
What this record is associated with
The catalog and matched registry evidence associate this provider with the following data domains:
- credit/risk identity
- fraud prevention
- insurance data
- credit data
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: Demyst’s current privacy notice says individuals may contact privacy@demystdata.com to exercise rights but also explains that the notice does not cover data processed as a service provider for a customer. The cited notice does not state a universal government-ID requirement.
Government-ID expectation: not_required_by_default_in_current_notice;_customer_controller_may_control_request
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: Demyst Data Ltd.
Registry jurisdictions: US-VT.
Registered websites: https://demyst.com/.
Catalog legal operator: Demyst Data 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-VT | Demyst Data Ltd | 376423 | ACTIVE | 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: Cross-domain request-route candidate; entity review required. Useful evidence: this record tracks 91/258 tracked fields across 105 evidence facts. Cross-domain request-route candidate; entity review required (date not recorded). 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 |
|---|---|---|
| provider-published workflow source | https://demyst.com/privacy-policy ↗ | 2026-08-11 |
| provider-published workflow source | https://console.demystdata.com/privacy ↗ | 2026-08-11 |
| provider-published workflow source | https://demyst.com/terms-and-conditions ↗ | 2026-08-11 |
| read-only observation · Cross-domain request-route candidate; entity review required | https://console.demystdata.com/privacy ↗ | 2026-08-13 |
Evidence label: Official Current Source Confirmed. Source checked: 2026-08-13.
Latest independent provider URL observation: 2026-08-11 · reachable · HTTP/status 200 · final URL https://console.demystdata.com/privacy · observed URL https://console.demystdata.com/privacy. 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.
Read-only semantic disposition: Cross-domain request-route candidate; entity review required. Observed 2026-08-13 · final URL https://console.demystdata.com/privacy.
Next evidence action: Confirm the legal operator, brand relationship, and request scope before relying on this cross-domain page.
This is a bounded page observation. It does not prove entity identity, route ownership, request delivery, acceptance, or deletion.
Latest email-domain observation: 2026-08-11 · DNS reachable · demystdata.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 | 7/14 fields | 50.0% | partial |
| contact routes | 7/22 fields | 31.8% | partial |
| data categories | 5/32 fields | 15.6% | partial |
| entity identity | 10/20 fields | 50.0% | partial |
| privacy risk | 7/28 fields | 25.0% | partial |
| registry profile | 14/39 fields | 35.9% | partial |
| request workflow | 13/41 fields | 31.7% | partial |
| route checks | 11/38 fields | 28.9% | 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 Credit, Risk & Identity profiles
These records are grouped with Demyst Data Ltd under the same catalog category. The grouping is for discovery; it does not establish common ownership, shared suppression, or a shared request outcome.
- 700Credit, LLC
700credit.com
Current route evidence recorded
- Accuity Inc.
accuity.com
First-party request-route candidate; manual review required
- ACUTRAQ Background Screening
acutraq.com
Current route evidence recorded
- Adttribution Inc
adttribution.com
Current route evidence recorded
- Advantage Credit, Inc.
advcredit.com
Privacy or consumer-rights context page; submission route not confirmed
- Advertise4Sales LLC
4legalleads.com
Ambiguous page observed; submission route not confirmed
Demyst Data Ltd opt-out FAQ
How do I opt out of Demyst Data Ltd?
Use the recorded privacy contact at privacy@demystdata.com and keep a copy of what you sent. The catalog record was checked on 2026-08-13.
Does Demyst Data Ltd require government ID?
not_required_by_default_in_current_notice;_customer_controller_may_control_request
How long does Demyst Data 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 Demyst Data 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.