What TradeDesk does
TradeDesk reviews reported record-quality issues and personal-data concerns, then corrects, annotates, restricts or routes them where appropriate.
PRODUCT GUIDE
How to ask TradeDesk to review a record issue
If something in TradeDesk appears wrong, incomplete, duplicated, misattributed or missing context, you can ask us to review it.
Search is the entry point.Review is the outcome.
01What this page explainsHow to raise wrong, incomplete, duplicated, misattributed or missing-context data concerns.
02Who it is forUsers, reviewed companies and customer teams who need a clear route for corrections or disputes.
03After readingYou should know what to include, which route applies and what TradeDesk may be able to change.
Quick answer
At a glance
The short version reviewers should understand before reading the detailed methodology.
What it does not do
TradeDesk does not promise to change upstream public records that must be corrected by the source authority.
What users should verify
Include the company name, company number, exact page or source item, what appears wrong and evidence supporting the request.
Method
How it works
Simple steps first, with the detailed source and caveat text below.
- 01
Identify the record
Provide company name, company number where known, and the exact TradeDesk page or source item.
- 02
Explain the issue
Separate what appears wrong from interpretation, and say whether it concerns personal data.
- 03
Attach evidence
Include supporting source links, documents or context that help TradeDesk verify the request.
- 04
TradeDesk reviews the route
The request is handled as product data quality, privacy or upstream-source correction context.
Product surfaces
What users see in the product
The methodology connects directly to surfaces where users inspect evidence or record review work.
Company OverviewThe starting view for identity, filings, status, source coverage and profile context.Operational FootprintMapped and unmapped location evidence, address/place context and operational signals where covered.Review WorkspaceThe workflow area for review cases, checks, owners, notes, monitoring and evidence links.Evidence modeA company-profile view for inspecting source-backed rows, grouped evidence and coverage notes.
Labels
What the labels mean
Short definitions for terms that appear across evidence, footprint and review views.
| Label | Meaning for reviewers |
|---|---|
| Product data-quality issue | A duplicate, stale link, wrong attribution, entity-match issue or missing context in TradeDesk's presentation. |
| Personal-data concern | A privacy or accuracy concern about displayed personal information. |
| Source authority | The public register or upstream source that controls the underlying record. |
| Correction request | A request asking TradeDesk to review and update, annotate or route an item. |
Detail
Method detail and caveats
Use these sections when you need the source-level detail behind the quick answer.
Report an issue
If you believe something in TradeDesk is wrong, incomplete, duplicated, misattributed or missing important context, please ask us to review it.
Send review requests to support@tradedesk.io. Include the company name, company number if known, the page or signal you are challenging, a short explanation and any evidence that supports your request.
Think something is wrong or incomplete? Ask for review and include your evidence.
Two routes, one entry point
| Request type | Examples | How we route it |
|---|---|---|
| Product or data-quality issue | Duplicate company, stale link, incorrect source attribution, wrong website, entity-matching issue, missing context. | Reviewed as a record-quality issue by support and data operations. |
| Personal-data concern | Inaccurate personal data, rectification request, privacy rights request or concern about displayed personal information. | Routed to the privacy process. You can also contact privacy@tradedesk.io. |
What TradeDesk may do
- Correct or complete TradeDesk's own presentation where evidence supports the change.
- Add context or source notes where a record needs careful interpretation.
- Temporarily restrict or adjust display of a contested item where appropriate while it is reviewed.
- Refer the requester to the source authority when the underlying public record must be corrected there.
- Explain when a requested change cannot be made from the evidence supplied.
What to include
| Information | Why it helps |
|---|---|
| Company name and number | Helps us identify the correct entity. |
| The exact page, source item or signal | Keeps the review focused. |
| What appears wrong or incomplete | Separates factual issues from interpretation. |
| Supporting evidence or source links | Lets us verify the request more quickly. |
| Whether it concerns personal data | Allows privacy requests to be triaged correctly. |
Contact routes
For company record and product data-quality issues, email support@tradedesk.io.
For privacy rights or personal-data concerns, email privacy@tradedesk.io.
A dedicated corrections form is planned, but it is not live yet.
Limits and caveats
What the view cannot prove on its own
These limits keep methodology pages readable without hiding uncertainty.
TradeDesk can correct or annotate its own presentation where evidence supports the change.
Some upstream records must be corrected by the source authority.
Requests need enough detail to identify the company, item and evidence behind the concern.
Personal-data concerns are routed through the relevant privacy process.
FAQ
Common questions
What should I include in a correction request?
Include the company details, the exact item you are challenging and evidence that supports your request.
Can TradeDesk remove or change source records?
TradeDesk can change its own presentation and may direct you to the source authority where the underlying record must be corrected there.
What if my request concerns personal data?
TradeDesk will route it through the relevant privacy process and apply the appropriate safeguards.
Do you promise a fixed timeline?
No fixed product timeline is promised here. Personal-data rights requests are handled under applicable legal requirements.
Related pages
Keep reading by review question
Email supportAsk TradeDesk to review a record-quality issue.Email privacyRaise a personal-data concern or rights request.Data Sources & CoverageWhat sources are covered, what no match means and why recency varies.Evidence MethodologyHow scattered source records become review-ready evidence.Operational Footprint MethodologyHow mapped locations, source rows, group scope and footprint caveats should be read.Review Workspace GuideHow reviews, checks, owners, notes and evidence links work together.Trust CentreSecurity, AI transparency, legal and governance resources.