BDEX Opt Out: Stop Data Sharing and Request Deletion

BDEX opt out requests work best when you match the route to the record and outcome. The current process uses a provider-owned form that accepts an email and offers data-sharing opt-out and information-display choices, plus privacy email, phone, and postal channels for other covered rights. An advertising preference, sale or sharing opt-out, access report, correction, and deletion are different actions. Save the confirmation, complete only necessary verification, and recheck the same identifier because a new source or environment can create another match.

BDEX opt out at a glance

BDEX Data Sharing form showing opt-out and information-on-file choices — BDEX's current sharing and information-request form checked on September 3, 2026; no email address or request was submitted.

Question	Current answer
Official route	a provider-owned form that accepts an email and offers data-sharing opt-out and information-display choices, plus privacy email, phone, and postal channels for other covered rights
Likely data scope	names, addresses, phone numbers, email, IP, device and online identifiers, age and household characteristics, internet activity, geolocation, commercial information, and other identity-graph data
Verification	BDEX says an email address is required to verify a consumer request. An authorized agent can use the same channels but may be asked for valid power of attorney.
Timing	The current policy says most requests receive a response within 45 to 90 days depending on residence, with written notice if more time is needed. Its historical one-day median is not an individual guarantee.
Expected result	A sharing opt-out preference applies to the matched account and BDEX databases, including offline sales, while access, correction, deletion, profiling, or targeted-advertising requests require the matching right.

This summary is based on provider-owned material checked September 3, 2026. It provides practical privacy guidance and does not promise that every record or downstream copy will be found or removed.

What information BDEX handles

BDEX’s policy describes an identity graph built from information submitted by consumers, cookies, tracking pixels, data brokers, and other sources. The listed categories include direct identifiers, device and online identifiers, protected characteristics, internet activity, geolocation, and commercial information.

The visible form offers two separate choices: opt out of sharing information on the BDEX platform, and show the information on file. Selecting an information view should not be described as deletion, and a sharing opt-out should not be described as an access report.

Choose the right BDEX request

Use a sale, sharing, or targeted-advertising opt-out when the goal is to stop a defined disclosure or targeting use without necessarily deleting every retained record.
Use deletion when the goal is erasure of a matched record, subject to identity verification, legal exceptions, public-source boundaries, and necessary suppression data.
Use access or portability when you first need to see what the provider can match. Use correction when an accurate retained record is better than deletion.
Treat cookie, browser, device, marketing, and universal opt-out settings as separate controls unless the provider explicitly connects them to its main data record.

The policy says a contact-based opt-out is applied to the account and databases, including offline sales. It also lists state-dependent access, portability, correction, deletion, sale, sharing, targeted-advertising, profiling, and sensitive-data rights.

How to submit the BDEX opt out

Open the official BDEX Data Sharing page and enter the email address that is most likely to match the identity-graph record.
Select the opt-out checkbox to stop sharing on the BDEX platform. Select the information option as well if you want the provider to show what it has on file.
Submit the form and save the date and response. Use the published privacy email, phone number, or postal address for deletion, correction, access, portability, profiling, or another covered request.
Complete email-based identity verification through the official domain. Ask what additional identifier is required before sending broader personal data.
An authorized agent should be ready to provide valid power of attorney through the provider’s current channel rather than placing authorization evidence on a public page.
Recheck the submitted email and named request after the stated window. Appeal a refusal through the same published privacy contacts when the applicable state right provides that option.

Open the BDEX Data Sharing opt-out form and compare it with the BDEX embedded Privacy Policy before submitting. Provider routes and applicable rights can change.

Verification and privacy precautions

BDEX says an email address is required to verify a consumer request. An authorized agent can use the same channels but may be asked for valid power of attorney.

Start with only the fields shown on the provider-owned form or listed in the current policy.
Do not email passwords, full government identifiers, financial records, or unrelated household data unless the official process explains why a narrower verification method cannot work.
Check the domain, save the request number, and keep replies in the original thread so follow-up can be tied to the request.
An authorized agent should prove authority through the provider’s current route and should never claim authority the person did not grant.

How long the request can take

The current policy says most requests receive a response within 45 to 90 days depending on residence, with written notice if more time is needed. Its historical one-day median is not an individual guarantee.

Submission, identity matching, verification, provider processing, source-owner action, and public search reindexing can be separate stages. A confirmation that one stage finished does not prove every copy or use changed at the same time.

Why BDEX data can reappear

An alternate email, offline identity, new device or household identifier, fresh broker feed, or client-held copy can create a separate match outside the submitted address.

Record the identifier, request type, date, ticket, verification state, response, and next check date. That log helps distinguish a newly sourced record from an unfinished first request.

Common problems and what to do

The provider cannot find a match

Reply with one additional matching field at a time, such as an old email, address, device, company, or profile detail that the current policy says it uses. Ask what is missing before sending broader identity evidence.

The request changed only one outcome

Review the selected right. A sale opt-out, marketing unsubscribe, browser choice, correction, access request, and deletion request solve different problems. Submit a second request only when the first selection could not produce the intended result.

A partner, customer, or public source controls the record

Use the controlling organization’s privacy route when the provider processes data only for a client or republishes a public source. Keep the first ticket because it documents the boundary and can help identify the controlling organization.

The policy publishes a 180-day retention period for listed identifying, protected-classification, and internet-activity categories, but the useful consumer evidence remains the response to the specific request. Do not infer that every client or upstream record disappears on day 180.

Manual requests versus recurring monitoring

A manual request gives you direct control over one known provider but does not inventory the wider ecosystem. Learn how to remove yourself from data brokers, use the data broker opt-out list, and browse the opt-out guide hub.

You can also run a free data broker scan to find other exposed records. Related guides: Data Axle opt-out guide, Acxiom opt-out guide, and NextRoll opt-out guide.

Frequently asked questions

Does the BDEX opt out delete everything?

No. The result depends on the selected right, matched identifiers, location, controller or processor role, legal exceptions, and source boundaries. Use deletion separately when that is the intended outcome and keep the provider response.

How do I know the BDEX request worked?

Use the ticket, completion message, access result, corrected record, preference status, or a recheck of the same identifier. A short-term change in ads, email, calls, or search results is not reliable proof by itself.

Should I submit another request for a second identifier?

Yes when the provider describes the match as email-specific, address-specific, device-specific, network-specific, household-specific, professional-profile-specific, or customer-specific. Do not assume one confirmation covers every variation.

Can an authorized agent submit the request?

Often yes, but the provider may require direct written authorization, power of attorney, or confirmation from the person. Follow the current form and do not expose more identity data than verification needs.

What if the form or policy changes?

Return to the provider’s current privacy page and follow its official rights, privacy-center, or contact link. Compare the new route with the saved confirmation and avoid third-party forms that cannot show where the data goes.

Sources

Official BDEX Data Sharing page, checked September 3, 2026 for the email field, platform-sharing opt-out, information-display choice, and provider-owned route. Open official route.

BDEX Privacy Policy embedded from the provider page, last updated May 15, 2026 and checked September 3, 2026 for data categories, offline-sale scope, verification, agents, timing, appeal, retention, and state-dependent rights. Open BDEX embedded Privacy Policy.