Alloy: data broker profile and opt-out route
This record explains how to contact Alloy, 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 Alloy accepted, processed, or completed a request.
Quick answer
To request removal from Alloy, first verify the current request route because the latest read-only page observation is ambiguous page observed; submission route not confirmed using privacy@alloy.us. The catalog currently records Email as the request method, an estimated processing time of 7-45 days, and latest evidence dated 2026-08-13.
Alloy at a glance
- Domain
- alloy.us
- Request method
- Catalog difficulty
- 2/5
- Processing estimate
- 7-45 days
- Standard ID flag
- Not flagged in standard workflow
- Country scope
- US
- Evidence grade
- Ambiguous page observed; submission route not confirmed
- Evidence status
- Ambiguous page observed; submission route not confirmed
- Independent route observation
- URL observed; semantics pending
- Read-only semantic disposition
- Ambiguous page observed; submission route not confirmed
- 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
- marketing audience, data aggregation, demographics, household data
- Source checked
- 2026-08-13
- Entity reviewed
- 2026-08-11
- Next route review
- 2026-09-27
How to use this Alloy opt-out record
- 1
Open the provider route and confirm that it matches Alloy 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 Identity Details For Record Matching.
- 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
- Delete Personal Information
Submission channels
Required fields
- Identity Details For Record Matching
Optional or contextual fields
- Email Address
- Phone Number
- Street Address
Extra steps
- Review The Prepared Request In Your Own Inbox, Press Send, Save The Sent Copy, And Complete Any Broker Confirmation Link Or Form.
Completion evidence to keep
- User Saved Sent Request Copy
- Broker Acknowledgement If Received
- Future Source Recheck
What this record is associated with
The catalog and matched registry evidence associate this provider with the following data domains:
- marketing audience
- data aggregation
- demographics
- household 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: The request should include enough information for the broker to match the consumer record. Follow the first-party route instructions and provide only what is needed to locate the record.
Government-ID expectation: The official source capture does not establish a government-ID requirement. Do not upload one unless the first-party route explicitly requires it.
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: Ambiguous page observed; submission route not confirmed. Useful evidence: this record tracks 71/258 tracked fields across 80 evidence facts. Ambiguous page observed; submission route not confirmed (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://www.alloy.us/privacy-policy/ ↗ | 2026-08-11 |
| read-only observation · Ambiguous page observed; submission route not confirmed | https://www.alloy.us/privacy-policy/ ↗ | 2026-08-13 |
Evidence label: Official Registry And Declared Privacy Contact. Source checked: 2026-08-13.
Latest independent provider URL observation: 2026-08-13 · not reachable · HTTP/status 404 · final URL https://www.alloy.us/privacy-policy/ · observed URL https://www.alloy.us/privacy-policy/. 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: Ambiguous page observed; submission route not confirmed. Observed 2026-08-13 · final URL https://www.alloy.us/privacy-policy/.
Next evidence action: Review the page and confirm its route role, provider identity, and request scope before relying on it.
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-13 · DNS reachable · alloy.us. 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 | 14/22 fields | 63.6% | partial |
| data categories | 2/32 fields | 6.3% | partial |
| entity identity | 4/20 fields | 20.0% | partial |
| privacy risk | 7/28 fields | 25.0% | partial |
| registry profile | 0/39 fields | 0.0% | missing |
| request workflow | 13/41 fields | 31.7% | partial |
| route checks | 9/38 fields | 23.7% | 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 Marketing & Audience Data profiles
These records are grouped with Alloy under the same catalog category. The grouping is for discovery; it does not establish common ownership, shared suppression, or a shared request outcome.
- 01Advertising Inc
01advertising.com
Current route evidence recorded
- 180 by Two, LLC
180bytwo.com
First-party request-route candidate; manual review required
- 33 Mile Radius LLC
33mileradius.com
First-party request-route candidate; manual review required
- 360 Media Direct
360mediadirect.com
Current route evidence recorded
- 365DataSolutions, LLC
365datasolutions.com
Current route evidence recorded
- 4EYES AI Inc
4-eyes.ai
Ambiguous page observed; submission route not confirmed
Alloy opt-out FAQ
How do I opt out of Alloy?
Use the recorded privacy contact at privacy@alloy.us and keep a copy of what you sent. The catalog record was checked on 2026-08-13.
Does Alloy require government ID?
The official source capture does not establish a government-ID requirement. Do not upload one unless the first-party route explicitly requires it.
How long does Alloy take to process an opt-out?
The catalog estimate is 7-45 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 Alloy?
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.