Disco Opt Out: Deletion Email, GPC and Privacy Steps

To request deletion of Disco data, email privacy@disconetwork.com or use the privacy policy's toll-free route, 1-866-467-8688 with code 2258#. The policy separately links sale/sharing opt-out and recognizes Global Privacy Control for the current browser or device. A promotional unsubscribe or browser signal does not by itself establish deletion of account or merchant-related records.

We checked Disco's public privacy policy on October 26, 2026. Its linked sale/sharing help page presented a security challenge, so we do not describe that page as a tested submission flow. The policy itself provides explicit request contacts and verification instructions. No email, phone call or privacy request was sent.

Identify the Disco relationship involved

Disco's policy covers its services and describes information including contact details, online identifiers and interactions. A shopper, a merchant using its services and a job applicant may each need a different record scope. Tell the privacy team which relationship concerns you without sending a complete purchase history or unrelated personal documents.

A merchant's own order, payment or customer-service records are a separate concern. Asking Disco to delete matching information does not establish cancellation of an order or deletion by every store involved. Contact the merchant separately when its records are the source of the issue.

Use the general data-broker removal guide to organize separate recipients. It is better to identify which company controls a record than to send one vague request and assume every participant in an advertising or shopping network receives it.

Submit a clearly scoped privacy request

Start from the published policy contact

Open the Disco privacy policy and find Individual Rights and Requests. It authorizes requests to know, correct or delete through privacy@disconetwork.com and the listed toll-free phone route. Recheck the address and code on the live policy before using them.

For email, identify the action in plain language. State that the request concerns Disco and describe the relevant account, email or interaction. Ask for acknowledgement, any necessary verification steps and a clear outcome for the requested action. The policy may ask for a full legal name and email to verify identity; avoid supplying additional sensitive information without an explanation.

Distinguish deletion from future sale or sharing

If both actions matter, state both. The policy links a separate sale/sharing route, while deletion uses the rights contacts. Because the linked help page was challenged during our check, we cannot document its final controls or claim a successful form submission.

If that page remains inaccessible, explain the problem to the privacy contact and ask for the appropriate alternative. Do not assume that a generic support message or browser cookie rejection has completed a sale/sharing request. Save the provider's confirmation of the action it accepts.

Follow identity confirmation carefully

Disco says it verifies requests consistent with applicable law and may ask the requester to confirm a deletion before carrying it out. An acknowledgement is therefore not the same as deletion. Monitor the reply address and respond only through the official process after checking what information is being requested.

The policy also permits authorized-agent requests but may require proof of authority and direct confirmation from the individual. If another person or service assists you, ask who is responsible for each verification message. Do not allow a missed confirmation to be mistaken for a completed removal.

Residency, GPC and retained records

The policy lists specific U.S. state residents in its rights section. Use your actual residency and ask the privacy contact about the applicable process if your location is not covered by the displayed list. This guide maps the provider's published instructions; it does not determine your individual legal entitlement.

Disco says it processes Global Privacy Control as an opt-out signal for the particular browser or device. That scope matters when you use multiple browsers, shop on a phone and laptop, or communicate through a separate merchant account. A signal sent from one context is not proof of deletion across all of them.

The policy describes an appeal route through the same request methods when action is refused. If that happens, keep the refusal, its reason and the date. Ask a focused follow-up about the disputed request rather than sending repeated identical messages. Do not invent a fixed appeal deadline where the policy only refers to a reasonable period.

For other commerce-related records, see the Bridg opt-out guide and Epsilon guide if those services are actually involved. A retail purchase record and a marketing network's profile can require separate requests. The Sojern guide similarly explains why partner-controlled customer records need their own scope check.

Verify the response and keep a useful record

A form submission, email acknowledgement and completed request are three different events. Save the date and the wording of the action you requested. If a response says only that a ticket was created, leave the case marked pending. Wait for a response that identifies the action actually taken and the records or identifiers it covers.

Keep this record somewhere private. It should contain the official contact route, the request type, a masked identifier and any case number. There is no need to put a full advertising ID, home address or exported data file into a public discussion. If you share a screenshot with support, remove unrelated browser tabs and information about other people.

• Record whether you requested access, deletion, an advertising opt-out or more than one action.
• Note the specific browser, device or account involved so you can repeat a check in the same context.
• Watch the reply address and spam folder for a verification message or a request for clarification.
• Save the outcome separately from the initial acknowledgement, including any exception or retained-data explanation.

When a response is incomplete, reply on the existing case with the missing scope. For example, ask whether an advertising preference was saved and whether the separate deletion request was completed. Repeated new submissions can make it harder to connect the answer to the original identifier. Keep a clear chronology instead of interpreting silence as success.

The public pages checked for this guide do not establish a measured end-to-end removal time. Do not turn an estimate for filling in a form into a promise about processing. Follow any deadline or verification window in the provider's response.

If it refuses part of your request, ask for the reason and the applicable escalation or appeal route. Availability depends on your location and the request involved.

What to check if data or targeting returns

A later advertisement does not, by itself, prove that a privacy request failed. Advertising can be contextual, delivered by a different company, or associated with another identifier. Compare the same scope before drawing a conclusion. A browser preference, an email-linked record and a mobile advertising identifier can represent different pieces of the problem.

Review the apps, websites or accounts that supplied the data as well as the receiving company's response. A request sent to one recipient does not establish what every other recipient holds. If you recognize the original publisher or service, use its own privacy settings or rights process for that relationship. Keep those case records separate so the answers remain understandable.

For named broker listings, a free data broker scan can help identify a separate public-exposure task. It is not a test of whether this provider erased a cookie, device identifier or internal audience record. Do not buy a removal subscription solely on the assumption that it covers the workflow in this guide; check the current supported sources and exclusions first.

The opt-out guide hub helps you find other provider-specific routes. Work from the companies actually connected to your information, rather than sending the same detailed identity packet to every company on a list. A targeted request is easier to verify and avoids sharing unnecessary personal details.

Frequently asked questions

Must I call rather than email?

The policy provides both routes for requests to know, correct or delete. Choose the one you can document and follow up on reliably. If using the phone route, retain the date, the code used and any case reference without recording unnecessary personal information.

Does GPC delete my Disco data?

The policy describes it as an opt-out preference signal for a particular browser or device. It does not establish a complete deletion request. Use the rights contact when you want deletion and ask for a separate outcome.

What if the sale/sharing link is blocked?

We encountered a security challenge on that linked help page. Return to the official policy and ask its privacy contact for an accessible route. Do not enter personal details into a third-party page that claims to bypass the challenge.

Will my shopping order disappear?

A Disco request does not establish deletion or cancellation in a merchant's own order system. Contact the seller about its records and any transaction question. Keep that case distinct from the network's privacy response.

Can an agent make the request for me?

The policy allows authorized-agent requests where applicable, with possible proof of authority and direct verification. Confirm the responsibilities before delegating. A service's status of request sent does not prove that all required confirmation steps were completed.