Exa Labs Inc.: data broker profile and opt-out route
This record explains how to contact Exa Labs Inc., 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 Exa Labs Inc. accepted, processed, or completed a request.
Quick answer
To request removal from Exa Labs Inc., first verify the current request route because the latest read-only page observation is privacy or consumer-rights context page; submission route not confirmed using compliance@exa.ai. The catalog currently records Email as the request method, an estimated processing time of 14-30 days, and latest evidence dated 2026-08-13.
Exa Labs Inc. at a glance
- Domain
- exa.ai
- Request method
- Catalog difficulty
- 3/5
- Processing estimate
- 14-30 days
- Standard ID flag
- Not flagged in standard workflow
- Country scope
- US
- Evidence grade
- Privacy or consumer-rights context page; submission route not confirmed
- Evidence status
- Privacy or consumer-rights context page; submission route not confirmed
- Independent route observation
- URL observed; semantics pending
- Read-only semantic disposition
- Privacy or consumer-rights context page; submission route not confirmed
- Legal operator
- Not recorded
- Parent entity
- Not recorded
- Catalog lifecycle
- Active Catalog Record
- Lifecycle status
- Active Catalog Record
- Registry matches
- 2 profiles
- Evidence conflicts
- None recorded
- Recorded data domains
- b2b sales intelligence, professional identity, employment data, company affiliation
- Source checked
- 2026-08-13
- Entity reviewed
- 2026-08-10
- Next route review
- 2026-09-27
How to use this Exa Labs Inc. opt-out record
- 1
Open the provider route and confirm that it matches Exa Labs Inc. 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 Authoritative Registry Entry Does Not State The Complete Current Field List; Confirm The Live Route Before Sending., Use The Minimum Profile-Matching Details Needed To Locate The Consumer Record..
- 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
- Registry Email
- Registry Phone
- Registry Postal Address
Required fields
- The Authoritative Registry Entry Does Not State The Complete Current Field List; Confirm The Live Route Before Sending.
- Use The Minimum Profile-Matching Details Needed To Locate The Consumer Record.
Optional or contextual fields
- Profile Url Or Search Result
- Email Address Or Phone Number As Held By Broker
- State Or Jurisdiction If Requested
Extra steps
- Use The Registered Privacy Route Above And Confirm The Live Form Fields Before Submitting.
- Match The Request To The Broker Brand, Profile URL, Email, Phone, Or Other Identifier The Broker Actually Holds.
- Do Not Assume The Registry-Listed Data Categories Are Current First-Party Form Requirements.
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:
- b2b sales intelligence
- professional identity
- employment data
- company affiliation
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
- • Name: Collect, Sell
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 authoritative registry entry does not specify the current identity-verification method. Follow the live route and provide only the minimum information needed to verify the request.
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: Exa Labs Inc.; EXA LABS INC.
Registry jurisdictions: US-CA, US-OR.
Registered websites: https://exa.ai.
Entity review: 2026-08-10.
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 | Exa Labs Inc. | Not recorded | Not recorded | Not recorded |
| US-OR | EXA LABS INC | DATA-00440 | ACTIVE | 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: Privacy or consumer-rights context page; submission route not confirmed. Deep evidence: this record tracks 117/258 tracked fields across 165 evidence facts. Privacy or consumer-rights context page; 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://oag.ca.gov/data-brokers ↗ | 2026-08-10 |
| provider-published workflow source | https://exa.ai ↗ | 2026-08-10 |
| read-only observation · Privacy or consumer-rights context page; submission route not confirmed | https://exa.ai/ ↗ | 2026-08-13 |
Evidence label: Official Ca Registry Snapshot. Source checked: 2026-08-13.
Latest independent provider URL observation: 2026-08-11 · reachable · HTTP/status 200 · final URL https://exa.ai/ · observed URL https://exa.ai/. 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: Privacy or consumer-rights context page; submission route not confirmed. Observed 2026-08-13 · final URL https://exa.ai/.
Next evidence action: Use the recorded catalog contact only after checking the page for the current request route and applicable request type.
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 · exa.ai. 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 (2 total):
- 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 | 12/32 fields | 37.5% | partial |
| entity identity | 11/20 fields | 55.0% | partial |
| privacy risk | 7/28 fields | 25.0% | partial |
| registry profile | 22/39 fields | 56.4% | partial |
| request workflow | 14/41 fields | 34.1% | 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 B2B & Sales Intelligence profiles
These records are grouped with Exa Labs Inc. under the same catalog category. The grouping is for discovery; it does not establish common ownership, shared suppression, or a shared request outcome.
- 6sense Insights, Inc.
6sense.com
Current route evidence recorded
- Accurate Append Inc.
accurateappend.com
Current route evidence recorded
- Acquire Media U.S., LLC (Moody's Analytics NewsEdge)
newsedge.com
Current route evidence recorded
- Adapt.io
adapt.io
First-party request-route candidate; manual review required
- AdeptID, Inc.
adept-id.com
Current route evidence recorded
- AeroLeads
aeroleads.com
First-party request-route candidate; manual review required
Exa Labs Inc. opt-out FAQ
How do I opt out of Exa Labs Inc.?
Use the recorded privacy contact at compliance@exa.ai and keep a copy of what you sent. The catalog record was checked on 2026-08-13.
Does Exa Labs Inc. require government ID?
not_stated_in_authoritative_source
How long does Exa Labs Inc. 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 Exa Labs Inc.?
This snapshot does not record source-backed values for Parent Entity, Suppression Group. Confirm legal name, DBA names, ownership, shared suppression routes, and lifecycle from an official source.