GrowthCode Opt Out Guide: Email, Matching and Deletion

To opt out of GrowthCode, use its official privacy-rights form or email delete@growthcode.io with the subject Do Not Sell or Share My Personal Information. State whether you want sale/sharing opt-out, deletion, or both. GrowthCode's current notice explicitly says its general privacy inbox does not action opt-out requests. Use the dedicated address rather than relying on an older search excerpt.

This GrowthCode opt-out guide is based on its public pages and browser controls checked September 25, 2026. We did not submit a request. Matching is especially important here: GrowthCode's platform policy says deletion requests are matched against hashed email addresses.

What kind of data are you trying to remove?

GrowthCode describes an identity-resolution platform for publishers and advertising partners. Its platform policy discusses hashed emails, identity IDs, mobile advertising identifiers and audience information. This is a different problem from removing a publicly searchable page containing your name and street address.

A hashed email is a transformed identifier used for matching. It does not mean a record is automatically beyond the reach of a privacy request, but it can make the email you provide decisive. GrowthCode says it cannot use one email address to find identity-graph records associated with a different address belonging to the same person.

Before requesting removal, identify which email was used with the relevant publisher or service. Do not send passwords, inbox access, government identifiers or medical information. A request should help locate the relevant record, not create an unnecessary new collection of personal data.

The data broker removal overview explains how to separate a provider request from changes to the source website that originally collected information.

Which GrowthCode route should you use?

The current opt-out page provides the dedicated deletion inbox and explains the form route. Its platform policy also describes direct requests and says a self-service portal is in development. Public wording is not fully aligned across the pages, so use the currently visible form or explicit email route.

A search-result excerpt reviewed during research still named the general privacy inbox. That excerpt is not the current instruction shown on the live rights page. Check the official page again when acting, because routing details can change.

How to send a GrowthCode opt-out or deletion request

1. Open the current privacy-rights page

Go to the official do-not-sell page linked above. Read its current instructions before choosing the form or email. The page explains more than one route; a website cookie choice and an identity-record deletion should not be treated as interchangeable.

The browser inspection found a form with a verification-consent statement, a human-verification control and a Submit Opt-Out Request button. We did not complete that control or submit data. Email is a documented alternative when you prefer a written request or cannot use the form.

2. Use the dedicated inbox and a precise request

Address your message to delete@growthcode.io. Use the subject requested on the page, then state the action you want. For example: “Please opt my associated information out of sale and sharing, and process a deletion request for records linked to the email address below.”

Adapt that sentence to your actual intention. If you only want an opt-out, do not accidentally ask for an access report containing additional personal data. If you want deletion as well, state it rather than assuming a browser preference does both.

3. Provide matching information carefully

GrowthCode asks for enough information to locate and verify the record. Its platform policy identifies hashed email as the deletion-matching key. Supply the email you have reason to believe is associated with the relevant data, and explain if your reply address differs.

If more than one email is genuinely involved, ask how to include those identifiers in the same case or submit the additional requests the provider requires. Do not assume a request from your current address covers every older or alias address automatically.

4. Keep the response and resolve clarification

Save the sent request, date and any case reference. GrowthCode says it will provide written confirmation about matching and the action taken. Respond to relevant verification questions through the official thread, limiting disclosure to what is necessary.

A no-match message is not a deletion confirmation. Ask which supplied email was checked and whether another known identifier needs its own request. Do not repeatedly submit the same unchanged information and expect a different match.

How long does GrowthCode say processing takes?

The do-not-sell page says it processes opt-out requests and confirms completion within 15 business days. Its platform policy describes a 45-day response period for verified requests, including the deletion process. These are provider statements for different contexts, not two interchangeable promises.

An acknowledgment may clarify which process applies and whether verification is outstanding. Use that information when deciding when to follow up. We have not measured actual response times and do not claim that every deletion completes within the shorter opt-out window.

Keep a small request record with:

• The action requested: opt-out, deletion or both.
• The associated email identifiers you supplied.
• The date, official route and reference.
• Any verification question still awaiting your response.
• The outcome and whether it says matched, no match or retained for a stated reason.

If the stated period passes without a useful answer, reply to the same case and ask for status. Keep the question specific. “Was this email matched, and was deletion completed?” is easier to resolve than an unexplained repeat request.

Why GPC, opt-out and deletion are different

GrowthCode's rights page says it honors Global Privacy Control for California and Texas residents. Its platform policy qualifies signal handling at publisher level by technical feasibility and matching to an active identity record. Those statements should be read together.

A browser signal communicates a privacy preference in its applicable context. It does not give you a case-specific confirmation that every record linked to every email was deleted. When you need that confirmation, use the direct request route and read the response.

The company also says it retains an opt-out record for compliance. Retaining a limited preference record can support continued suppression; it is not the same purpose as making an audience record available to partners. Ask for clarification if the response does not explain what remains.

For related advertising identifiers, the LiveRamp opt-out guide and Acxiom opt-out guide describe separate provider processes. Their inclusion is a navigation aid, not evidence that either holds your particular GrowthCode record.

What can remain after a completed request?

A GrowthCode request addresses the information and processing within its scope. A publisher, advertiser or independent partner may hold its own data and have its own privacy choices. Contact the relevant organization when your concern concerns that separate copy.

Changing a website preference may help limit future collection, while a matched deletion addresses an existing record. Consider both when they are relevant. Neither action means you will stop seeing all advertising or that all companies will forget every prior interaction.

If a no-match result seems inconsistent with other evidence, review the email used. GrowthCode explicitly documents that different emails do not automatically match each other. This is a practical reason to keep a private record of identifiers and outcomes.

Use the opt-out guides hub for further workflows and the data broker opt-out list to track them. A free exposure scan can help with supported public records, but a scan does not inspect or prove deletion from GrowthCode's internal identity graph.

GrowthCode opt-out questions

Which email address handles deletion?

The current official page directs opt-out and deletion requests to delete@growthcode.io. It explicitly separates that address from general privacy inquiries. Recheck the live page if an old article or search excerpt gives different instructions.

Does GrowthCode have a public people-search listing?

The sources checked describe identity resolution and advertising data, rather than a public name-search profile to locate and remove. Start with the official rights route; do not invent a profile URL just because other broker guides use one.

Can I request both deletion and a sale opt-out?

You can state both actions in your message and ask how GrowthCode processes each. Their scope, matching and timing may differ. Read the response to confirm whether it addresses both requests.

What does a no-match response mean?

It means the supplied information did not establish a matching record under the process used. GrowthCode's policy says deletion matching uses hashed email and does not bridge different addresses automatically. Clarify the identifier rather than treating no match as universal erasure.

Will opting out remove every advertisement?

No. An opt-out concerns specified data uses, not all advertising. Contextual ads, another provider's records and a publisher's own processing can continue. Address any separately relevant source through its own privacy controls.

Sources and verification limits

Last checked September 25, 2026: GrowthCode's official do-not-sell page, platform privacy policy and general privacy notice. Browser evidence records the dedicated inbox instructions and visible form controls. No email, phone call, CAPTCHA completion or deletion request was performed.

This guide attributes processing and matching statements to the provider. It does not independently verify every legal-registration claim on those pages or promise a particular result for an individual request.