Quadrant Opt Out Guide: Device ID and Manage My Data Form

To request a Quadrant opt out or deletion, open its Manage My Data page and complete the privacy form. The current form asks for an email, device ID, requester role, residence and request type.

You can also contact privacy@quadrant.io. Quadrant checks identity or representative authority before acting, so a request without a usable identifier may need follow-up.

This Quadrant opt out guide uses the public form and privacy policy checked on September 26, 2026. The company identifies itself as Quadrant Global Pte. Ltd., an Appen company.

This guide concerns Quadrant’s location and device-data workflow; it does not substitute for a request about unrelated Appen accounts or work-platform records.

What does Quadrant’s privacy process cover?

Quadrant describes mobile location and point-of-interest data services. Its privacy policy discusses technical information including mobile advertising identifiers and device information. That creates a different request process from removing a named profile from a public people-search website.

The policy also covers ordinary contact information collected through its own interactions. State which activity concerns you: device-linked location information, website use, a business contact or another record. A single request label cannot explain every data source without that context.

The page’s company and parent references do not establish that one form covers every business in the group. If the record belongs to another service, ask which controller and process apply. The presence of a shared corporate owner is not proof of a shared consumer database.

How do you complete the Manage My Data form?

Open the official Manage My Data page and navigate to the form near the lower part of the page. At the time of our check, the route also displayed the privacy policy and request metrics. A reader could therefore mistake the long policy text for the end of the workflow unless they continued to the form.

Prepare the identifier and contact details

The form visibly requires a Device ID. Use the identifier relevant to the device and data in question, following current device guidance. Do not guess an identifier or paste a random value to pass validation.

If you cannot obtain the relevant ID, contact privacy@quadrant.io and explain the matching problem.

Use an email you control and can monitor for verification. An email establishes a communication channel but does not necessarily identify historical mobile location data. If your concern is an old device, make that distinction explicit so the provider can explain whether it has a usable match.

Choose the role, residence and requested action

Complete the current requester and residence controls truthfully. Select the request type that matches your goal, such as the relevant deletion or opt-out choice shown in the live form. Available choices can change, so use the labels actually presented rather than a remembered dropdown list.

If acting for another person, establish the authority needed for that request. Quadrant’s published process says it validates authorized representatives. Possessing another person’s email or device ID does not by itself establish authorization.

Read the declarations before submission

The form includes scope and accuracy statements, information about HubSpot’s role as a processor, and permission for Quadrant to contact you to verify identity and process the request. It also presents a required processing-consent statement. Read the live wording because these statements explain how the submitted request information will be handled.

• Identify the device or other record you want addressed.
• Supply accurate matching and correspondence information.
• Select the appropriate role, residence and request type.
• Review the declarations instead of treating them as decorative checkboxes.
• Save the acknowledgment and any verification instructions after submitting your own request.

We inspected the empty form only. No device identifier, consent, CAPTCHA, file or personal request was submitted, and the post-submission confirmation screen was not tested.

What if the device ID is missing or verification fails?

Quadrant’s privacy-request reporting identifies incomplete identity verification and missing valid device identifiers as reasons requests may not be completed. That is a useful operational warning: a readable form does not mean every submission can be matched to the data concerned.

Use the published privacy inbox if a required identifier is unavailable or the form fails. Explain whether you are asking about mobile data or a different interaction. Ask what matching evidence is acceptable and how to supply it securely. Do not attach a complete location history or identity document without a specific, verified reason.

If an agent submits the request, keep the authorization evidence and the provider’s verification instructions together. Ask for clarification when the provider cannot validate the representation. Repeatedly filing a request with the same missing information is unlikely to resolve the underlying matching issue.

The policy also describes an appeal route where applicable. It directs readers to privacy@quadrant.io with the subject “Privacy Request Appeal,” enough information to identify the original request and the basis for the appeal. Eligibility depends on jurisdiction and circumstances; the existence of an appeal inbox does not establish that every case has the same legal entitlement.

How long does Quadrant take, and what can remain?

The policy describes responses within applicable legal timeframes. It does not establish one tested turnaround for every identity, request type and country. We did not submit a request or verify a completion, so this guide makes no measured processing claim.

Distinguish three stages in your own log: the form was sent, the requester was verified, and the requested action was completed or declined with an explanation. A receipt email only confirms the first stage. If a deadline is supplied for verification, respond through the legitimate channel and keep the message.

The form’s scope statement says not all information may need to be deleted and gives contact or payment information as examples. Retention and processing exceptions can therefore matter even when a request is accepted. Ask which categories remain and why, rather than treating an affirmative response as proof of erasure from every system.

Location-data exposure also differs from public profile visibility. You may not have a public URL you can revisit to check the result. In that situation, the provider’s response, the identifiers covered and any available access information are more useful than searching your name on an unrelated people-search site.

Can location data be collected again?

Later app activity, new devices or changed advertising identifiers can create new data contexts. Removing one historical record does not automatically configure every app or data supplier. Review relevant location permissions and app privacy choices separately from the Quadrant request.

That follow-up is not a claim that reappearance was observed in a test. It is a practical distinction between a request about data already held and later collection or sharing. Keep the identifier and scope of your request so you can compare any later issue with the earlier response.

Other location-data workflows include the Foursquare opt-out guide, Unacast opt-out guide and Adsquare opt-out guide. Each company’s matching and verification requirements should be handled separately. A request to Quadrant does not establish an instruction to those providers.

The data broker opt-out list and opt-out guide hub help organize broader work. To check publicly searchable contact details as a separate exposure, run a free data broker scan. That scan does not inspect private location datasets or certify completion of this device-ID request.

Frequently asked questions

Can I submit only my name and address?

The inspected Manage My Data form requires a device ID. If your concern is a different category of information, contact the privacy team to ask for the correct matching route rather than entering a made-up identifier.

Does an Appen account deletion cover Quadrant?

The parent relationship does not prove a shared request scope. Ask the relevant privacy team which records and entities a response covers. This guide uses the dedicated Quadrant workflow.

Why does the form mention HubSpot?

The declarations describe HubSpot as a processor supporting the request form. Read those statements before submitting. Their presence does not mean the privacy request is directed to HubSpot’s unrelated products or consumer records.

Can someone submit a request for me?

Quadrant says it validates authorized representatives. The requester must meet the applicable authority and verification requirements. Ask the privacy team what evidence is needed for your situation.

How can I check deletion without a public profile?

Keep the completed-request response and the identifiers it addresses. Ask the provider for a clear scope explanation. A name search on the public web cannot establish whether a private mobile-data record was deleted.

Sources and verification

Official sources checked September 26, 2026: Quadrant’s Manage My Data page and privacy policy, including request verification and appeal instructions. Browser evidence captures the public form. No request, consent, identifier, purchase or consumer verification was submitted, and no successful deletion or processing time was measured.