IDMAP Opt Out Guide: Email, Device IDs and Privacy Requests

To opt out of IDMAP, email the privacy contact listed in its policy: michael.belsky@idmap.ai. State which data or device identifier your request concerns and whether you want deletion, a sale/sharing opt-out, or both.

This guide uses that documented email route because the advertised website opt-out control did not expose a usable form during our check.

IDMAP opt out quick facts

Use IDMAP official request instructions as the starting point. The instructions and public evidence were checked September 10, 2026. No consumer request was submitted, so this guide reports the documented process rather than a tested removal result.

How to submit your IDMAP request

Official route: IDMAP privacy email

1. Open IDMAP’s privacy policy from its own website and verify the current privacy contact. Use the address shown there rather than a sales enquiry mailbox copied from a directory.
2. Choose the identifier you want IDMAP to act on. For a mobile advertising request, identify the existing AAID or IDFA and device type. Do not substitute a phone number, serial number, or unrelated business email.
3. Send a short email specifying sale/sharing opt-out, deletion, or both. For contact-record requests, identify the relevant email or other matching record. Ask how to supply anything additional securely if verification is needed.
4. If you need a browser-cookie or connected-TV request, describe that scope and ask for the current working mechanism. The policy describes those choices, but we could not verify the advertised web form.
5. Keep the sent message and ask IDMAP to confirm the identifiers, data categories and affiliated services covered. Follow up in the same thread if it acknowledges receipt without explaining the outcome.

Choose the scope before sending personal information

• Mobile advertising ID: use the identifier and platform type described in the policy; business-contact fields are not a stated requirement for this route.
• Contact information: identify the particular email or profile that concerns you, rather than sending every address you have ever used.
• Browser or connected TV: ask for the matching mechanism appropriate to that environment; a mobile-ID request should not be assumed to cover it.
• Newsletter unsubscribe: handle unwanted subscription emails separately from a request about IDMAP’s marketing data.

Write down the outcome you want before starting. A useful request identifies the relevant record and states whether you want a disclosure stopped, a field corrected, or stored information deleted. If several actions matter, list them separately and ask the provider to confirm the disposition of each one.

Use identifiers tied to the record rather than a large bundle of personal documents. A name alone may match another person, while an unrelated address can confuse the request. Supply the minimum accurate details needed for the particular workflow, then respond to any explained verification step.

What the provider controls

IDMAP’s public material describes data products that link business, consumer and device information. A person therefore may need to distinguish a contact record from a device identifier instead of looking for a conventional public people-search listing.

The privacy policy names affiliated services. Shared ownership is a reason to ask which records a response covers, not proof that one email automatically removes data everywhere. Keep any affiliate-specific response with the original case.

Our browser check found the homepage control labeled Do Not Share My Personal Information. Activating it did not display usable fields. The policy’s privacy email remains an explicit request route; the guide does not invent a hidden submission screen.

The five-to-ten-business-day wording in the policy concerns newsletter changes. It does not establish a completion promise for deletion of marketing data. Ask for a case-specific estimate and distinguish receipt from completion.

Verification and processing: what to keep

For a mobile identifier request, the policy permits Device ID plus AAID or IDFA type without email or business-contact details.

No verified end-to-end deletion deadline; newsletter timing is a separate process.

Retain the submission date, the contact address or form URL, the identifiers used, and any case number. Keep the provider’s acknowledgement separate from its completion response. An automatic email that says a case was received does not establish that the record was removed or that every requested action was accepted.

When the provider asks for more information, check that the message belongs to the case you opened. Ask what is missing and how to supply it securely. Do not repeatedly send unrelated documents to multiple addresses. A precise reply in the existing thread usually makes the record easier to follow.

Reappearance and follow-up checks

Changing or resetting an advertising identifier can make a later identifier different from the one in the request. Record which identifier was submitted, and ask how future data will be suppressed.

Recheck the same record or environment first. Compare its identifying details with the request you submitted. A different email, employer, profile URL, or browser preference may explain why the later result is outside the original match. Ask the provider to clarify before describing the entire process as unsuccessful.

A practical privacy log can be brief: provider, relevant record, requested action, submission date, confirmation, and next check. Choose a reminder based on the response you receive. If no completion date is given, ask for one instead of treating a historical average or another provider’s deadline as a promise.

Connect this request to the next useful cleanup

Use the data broker opt-out list to track other providers and the opt-out topic hub to find current instructions. The broader manual data broker removal guide explains how to organize a multi-provider cleanup.

Relevant follow-up workflows are Intent IQ device-map choices, Fog Data Science identifier requests, and Tapad opt-out instructions. Use each only when it matches a separate exposure; one provider’s confirmation does not serve as proof about another database.

For wider exposure checks, run a free broker scan. If recurring follow-up would help, compare the scope and cadence of services in the data removal comparison hub. A scan is a starting point, not proof that every private database was searched.

IDMAP opt out FAQ

Can I opt out without a work email?

IDMAP’s policy says its mobile-ID opt-out needs only the Device ID and device type, not business-contact information. The verified alternative here is an email request, so the sender address will still be visible to the recipient.

Is the website form working?

The advertised control did not open a usable form in our September 10 check. Use the current privacy-policy email and ask for a working browser or CTV route when that is the data you want addressed.

Does an unsubscribe delete my data?

Do not assume so. Specify deletion and sale/sharing opt-out separately from newsletter cancellation. The provider should explain which action it completed.

Do I need to reset my advertising ID first?

Keep the identifier you want the request to cover. Resetting it first can make the previous value harder to supply. Ask the provider how to handle an identifier you can no longer retrieve.

Can I prove removal with a public name search?

A public search is not a complete check of private marketing or device data. Ask for a written response describing the matched identifier and action rather than treating an empty search as universal deletion proof.

Sources and verification notes

IDMAP official request instructions and the official cookie policy were checked on September 10, 2026. Screenshots document public instructions only. Request timing, eligibility, exceptions, and identity checks remain subject to the provider’s current process.

These are practical instructions based on the cited provider material, not an individual legal assessment. If a request is denied, keep the reason and consult the relevant regulator’s official guidance for your location. Do not assume that a request available in one jurisdiction has identical terms everywhere.