CITYDATA Opt Out: Device Data and Privacy Requests

To request a CITYDATA opt-out or deletion, email privacy@citydata.ai. For location data associated with an end user's device, its policy says you must provide the device's IDFA on iPhone or ADID on Android so it can locate the record. Names, email addresses and phone numbers are not stored with that device data, according to the policy.

If your request concerns a customer account or website inquiry, describe that relationship instead: CITYDATA says it verifies customers and visitors before providing or removing their information. We checked the public policy on November 11, 2026. We did not submit a device identifier or test a completed deletion.

First identify the kind of information involved

Use the official CITYDATA privacy policy to distinguish End Users, Customers and Visitors. This guide concerns citydata.ai, the location-data company. A similarly named website, directory or forum may have a different controller and will need its own request route.

The policy refers to a “Do not sell or share” web page, but our public policy inspection did not reveal a working link to that form. The explicit email route is reproducible, so this guide uses it. We do not invent a form address or describe fields we could not observe.

How to send the request

1. Describe the right relationship

Begin by saying whether you are asking about an end-user device, a customer account or information you supplied as a website visitor. Those categories have different matching requirements. If you are unsure, explain what prompted the concern and ask which identifiers are needed before sharing more information.

A location dataset is not necessarily searchable by your name. The absence of a public name-search result does not establish that a device record is absent. Conversely, a visit to a location is not proof that this specific company received your device data.

2. Provide the relevant identifier when available

CITYDATA says device-data removal requires an IDFA or ADID. These are advertising identifiers, not your phone number, IMEI, account password or government identification number. Do not substitute a more sensitive identifier just because it is easier to find.

If you cannot retrieve the relevant identifier through a trusted existing source, ask the privacy team about alternatives. Do not install an unfamiliar identifier-reading app solely to complete the request. Modern device settings and app permissions can restrict access to advertising IDs, and this guide does not promise a universal menu that reveals one.

If you have already reset or disabled the identifier, explain that. A replacement may not locate data collected under the old value. Ask how the provider handles that mismatch rather than assuming that a new identifier proves deletion of the old record. Never re-enable tracking merely to make a removal request easier.

3. State both the data and the action

Address the message to the privacy mailbox shown in the policy. Use a subject such as “Device-data privacy request.” Say whether you request deletion, an opt-out of sale/sharing, access, or another action. Identify the device-data category or customer/visitor relationship and ask for confirmation of the scope.

For example, a device owner can ask whether the supplied advertising identifier is present, request deletion where applicable, and ask for future sale/sharing restrictions. This is a suggested structure, not proof that every right applies in every jurisdiction. State your actual country or state if it is relevant to processing the request.

4. Verify the response and retain the outcome

Keep the original message, date and any provider acknowledgement. CITYDATA explicitly discusses identity verification for customer and visitor information. It does not publish a single universal post-submission email sequence for every device request, so we cannot promise a confirmation link or code.

Before sending additional evidence, confirm the official destination and ask what the evidence establishes. A useful final response identifies the record or identifier addressed, the completed action and any retained information. A generic “received” message is an acknowledgement, not proof of deletion.

Timing and escalation

The rights section does not provide a universal completion promise for these privacy requests. Ask for acknowledgement and the expected response date, then follow up in the same thread if that date passes. This article does not convert another section's timing into a data-removal deadline.

In particular, the policy contains separate dispute-resolution and arbitration opt-out provisions. Those are different from opting out of data sale or asking for deletion. Do not send an arbitration notice when your intended action is a device-data request, and do not treat its 30-day language as the promised deletion time.

The policy names dpo@citydata.ai for concerns about its use of device data. Use that contact for a relevant unresolved processing concern, referring to the earlier request. Applicable complaint or appeal rights depend on your circumstances; this guide does not determine a legal remedy.

Historical records and future collection are separate

Changing an app's location permission can reduce what it collects going forward. Tracking controls and advertising-ID choices can also change the signals available to apps. Those settings do not establish what previously reached CITYDATA or whether a historical record was removed.

Review apps that have location access and choose permissions appropriate to their function. Use current guidance from your device and app provider rather than copying an old menu path from a privacy policy. Keep a historical-data request separate from the decision to stop supplying new information.

The ModFx Labs guide covers another advertising-ID email workflow. The Veraset guide and Mobilewalla guide address separate location-data controllers. A reply from one company does not verify another company's dataset.

What deletion can and cannot establish

CITYDATA's policy describes device data and aggregate or de-identified information. Ask which data category a response concerns. Do not assume that removing an identifiable record reverses every historical aggregate output, or that an aggregate output necessarily exposes an identifiable individual.

Different devices, newly assigned identifiers and continued app sharing can create separate matching problems later. That is a reason to keep a request record and revisit changed circumstances, not evidence that CITYDATA inevitably re-adds every deleted record.

You can run a free data broker scan to investigate other exposure. Public people-search results cannot certify the contents of a device/location database. The manual removal overview helps track the distinction between a submitted request, a provider response and an independently observable result.

Before you close the request

• The request identifies device, customer or visitor data.
• Any advertising identifier is accurate and belongs to you.
• Deletion and sale/sharing requests are stated separately.
• Historical data and future app permissions are tracked separately.

Frequently asked questions

Can CITYDATA find device data using my email?

Its policy says names, emails and phone numbers are not stored with end-user device data and that it needs the advertising identifier to find the device. Customer and visitor records use a separate identity-verification process.

What if I no longer know the old advertising ID?

Explain the situation to the privacy team and ask which alternatives it accepts. Do not fabricate an identifier or install an untrusted tool. We have not verified a universal workaround for an unavailable historical ID.

Does disabling location access delete past data?

No such result is established. It changes an app's future access according to the device's controls. Historical deletion requires a separate request to the relevant holder and confirmation of what it did.

Does the policy's arbitration opt-out handle privacy data?

No. It addresses dispute terms. A privacy request should state the data action you want, such as deletion or sale/sharing opt-out, using the rights section's contact route.

Where can I find instructions for another provider?

The opt-out guide hub organizes separate workflows. Check the exact domain and controller before sending an identifier, especially when company names are similar.