illuma Opt Out: Advertising and Privacy Rights Steps

illuma opt out choices are not one universal deletion switch. The official End User Agreement and Privacy Policy directs people to Browser-level advertising controls first, then the privacy email for access, correction, deletion, restriction, or objection requests. illuma says it may need extra personal data to connect a person with device-specific data, and it may still be unable to identify the individual. Use the route that matches the data and device involved, save the confirmation, and recheck the same environment before expanding the request.

illuma opt out quick facts

Last checked August 26, 2026. Privacy centers, policy sections, request forms, and device controls can change. Start from the current provider policy rather than relying on an old form URL copied from a forum or an undated guide.

How to opt out of illuma

1. Open illuma’s official End User Agreement and Privacy Policy and confirm that the page belongs to Illuma Technology Ltd.
2. Use the browser or advertising opt-out controls referenced by the policy before sending extra identifying information. Repeat the choice in each browser profile and device you use.
3. If you need access, correction, deletion, restriction, or an objection beyond the browser choice, email the official privacy contact and state the precise right and device context.
4. Provide only the device or campaign details needed for matching. Ask what additional information is necessary before sending sensitive identifiers.
5. Save the response and recheck the same browser first. Contact the originating website or advertiser when illuma explains that the client controls the source data.

Choose the correct request before sharing information

Decide whether you want to stop interest-based advertising, stop a sale or sharing use, access data, correct it, delete it, restrict processing, or appeal a denied request. These outcomes are not interchangeable. A cookie choice usually applies to one browser. A mobile control usually applies to one advertising identifier. A broader rights request may cover information that the provider can authenticate and match.

Use the smallest amount of information the official workflow needs. Verify the provider domain before entering an address, device identifier, screenshot, or identity document. If the page offers a confirmation number, verification email, deadline, or appeal route, keep it with the submission date. That record is more reliable than judging success from whether the number of advertisements changes.

illuma describes itself as an advertising intermediary and processor acting for clients. It says clients decide why data is processed and collect the information before sending it to illuma. That boundary matters because a publisher or advertiser may be the correct controller for a broader deletion request.

The policy describes limited device-level data rather than names, postal addresses, phone numbers, or emails. It says the company generally cannot identify a person from those identifiers alone. A direct rights request may therefore require extra matching information, while a browser-level opt-out can be the more proportionate first step.

illuma says its contextual and statistical processing is not a sale, sharing, or targeted advertising use as those terms are defined by certain U.S. laws. This guide avoids promising a U.S. sale opt-out and instead follows the provider’s published device-control and privacy-contact sequence.

Verification and expected processing behavior

illuma says it may need extra personal data to connect a person with device-specific data, and it may still be unable to identify the individual. Verification protects against an unauthorized person requesting access to or deletion of another person’s information. It also creates the most useful checkpoint for follow-up. If the message does not arrive, check the supplied address, spam folder, request status, and identifier before opening a duplicate ticket.

No single completion time applies to every request described here. Timing can depend on residence, request type, matching, publisher or client instructions, partner systems, security retention, and statutory deadlines. Use the date stated in the confirmation for your case. If no date appears, send a dated follow-up with the original ticket rather than submitting the same request repeatedly.

• Save the request type, date, provider domain, confirmation, and next check date.
• Record the browser, device, app, television, household, cookie, or identifier covered.
• Complete verification promptly and retain the provider response.
• Recheck the same environment first, then handle other environments separately.

What the opt-out changes and what it does not

Browser controls can limit advertising processing for that environment; a verified rights request may address data illuma can locate under applicable law. Advertising choices can reduce profiling or interest-based selection without stopping every advertisement, contextual placement, measurement event, security use, or required record. Deletion can also have permitted exceptions. Read the outcome narrowly and use the separate provider route when you need a different result.

Publishers, apps, device makers, browsers, advertisers, clients, and websites can maintain independent controls. A request to this provider does not automatically change those systems. When the policy points to browser, operating-system, publisher, industry, or connected-device settings, record each change as its own layer.

Why a preference can reappear or stop working

illuma cookies can last up to 120 days, typically around 14 days, while clearing cookies, changing browser profiles, or using another device creates a separate environment. Opt-out cookies are intentionally stored in the environment they cover, while mobile and connected-device choices can depend on an advertising identifier. Some privacy requests retain a limited suppression record so the provider remembers the choice. Removing that record is not always helpful because it can prevent the provider from recognizing the same identifier later.

Recheck after clearing browser data, reinstalling an app, resetting an operating system, replacing a phone, switching browsers, using a new connected television, or resetting an advertising identifier. If the provider receives new data from a client or supplier later, compare the new exposure with the scope of the old confirmation before deciding whether a new request is required.

Broader privacy rights and manual removal

This guide is a practical map of the provider’s published controls, not a legal opinion or a promise about a legal outcome. Rights depend on the person, location, relationship with the provider, and information involved. An access response can help identify which system or identifier matched. A deletion request should be read together with the provider’s verification, retention, processor, and service-effect explanations.

For a broader manual workflow, use the data broker opt-out list and the guide to removing yourself from data brokers. The opt-out guide hub groups related provider instructions.

Build a repeatable recheck routine

Manual requests work best with a small log. Keep the provider, official route, request type, identifier scope, submission date, verification state, confirmation, response, and next check date. This makes later reappearance easier to diagnose and prevents a browser-cookie choice from being mistaken for a device-wide or account-wide deletion.

You can also run a free data broker scan to identify other exposed records. Related reading: GumGum contextual advertising guide, Seedtag advertising privacy guide, and Simpli.fi privacy guide.

Frequently asked questions

Does the illuma opt out delete all data?

No. The result depends on the selected control. Advertising, profiling, sale, or sharing choices can stop or limit a defined use without deleting every retained record. Choose the provider’s deletion route separately when that is your goal and review any verification, controller, security, or retention exception.

How do I know the illuma request worked?

Keep the provider confirmation and recheck the same browser, device, app, account, or identifier first. A changed ad experience alone is weak proof because contextual ads can continue. A completed-request message, saved opt-out status, access response, or ticket resolution is stronger evidence.

Should I repeat the choice on another device?

Yes when the provider describes it as browser-specific, device-specific, app-specific, television-specific, household-specific, or identifier-specific. Do not assume a desktop cookie covers a phone, another browser profile, mobile advertising ID, connected television, or publisher account.

What should I do if the form or policy changes?

Return to the provider’s current privacy policy and follow its privacy-center, rights, or opt-out link. Compare the new route with your saved confirmation. If the form is unavailable, use the published privacy contact and state the request type and original ticket without sending more personal information than necessary.

Sources

Official illuma End User Agreement and Privacy Policy, last updated August 2025 and checked August 26, 2026. Open official source.

Official illuma privacy contact and browser-control guidance, checked August 26, 2026.