Public web
Removal from the source site, followed by a separate delisting request if the page remains indexed.
Our removal method
Each piece of data needs the right removal method
Data Knight assesses data found in your name, identifies the appropriate privacy contact and prepares a suitable removal request. Only the information needed for that request is shared with the target organisation.
Before sending
An effective request starts with assessing the data found.
The same identifier can appear in very different contexts. We first check who holds the data, what is actually shown and which action suits the situation.
Who holds the data?
The site, broker, platform or search engine determines the right contact and available channel.
Which data is involved?
An email, number, record, URL or profile does not require the same identifying details.
Which action is appropriate?
Removal, delisting, objection, correction or securing an account: the action depends on the trace and context.
What about people with the same name? Results are checked against other identifiers before any action. Understand how we distinguish namesakes
A context-based method
The process adapts to each trace found.
Data Knight does not send an identical generic request everywhere. The source, the data held, the accepted contact channel and the relevant action shape the request.
Data brokers
The broker's procedure, privacy email or form, with identifiers present in its record.
Social media
Settings, content removal or a platform request according to the account and content.
Data breaches
Secure accounts first, then act with services still holding the information.
Only what is needed
Each organisation receives only what it needs.
Your entire report is never sent. Information is selected request by request to identify the right record without exposing the rest of your footprint.
Information linked to this trace
- The identity or username needed to find the record.
- The email, phone number or identifier actually associated with that organisation.
- The exact URL, record or data targeted by the request.
- The selected action and authorisation where needed.
Anything that is not necessary
- Your full scan and organisations unrelated to the request.
- Your contact details that do not appear in the relevant trace.
- Results found elsewhere online.
- An identity document by default or one stored by Data Knight.
This follows the data minimisation principle: data must be adequate, relevant and limited to what is necessary. We follow CNIL recommendations
A managed process that stays understandable.
You can see what is prepared, what is sent, which steps need your input and the result obtained.
The trace is assessed
The organisation, data, source and risk level are identified.
You make the decision
Choose the traces and authorise Data Knight to act on them.
The request is tailored
Wording, legal basis, recipient and channel are chosen for the specific case.
Data is limited
Only details useful for identification and processing the request are included.
The action is sent
By email, through a compatible form or with your input when a site requires a manual step.
Tracking stays centralised
Sending evidence, replies, follow-ups and outcomes stay visible in your account.
A CAPTCHA blocks the form?
You receive the link and prepared information. You complete the manual step, while the request remains tracked in your account.
An identity check is justified?
You send supporting documents directly to the organisation. Data Knight does not collect or store your identity document.
A method that evolves
We review our methodology every week.
Brokers change, forms evolve and new organisations appear. We update the process rather than relying on a list frozen in time.
Brokers and organisations
The monitored list grows and known organisations are rechecked.
Channels and forms
Addresses, privacy pages, forms and manual steps are checked.
Templates and follow-ups
Requests and suggested next steps evolve with the cases encountered.
Ongoing visibility
Every request keeps its history.
Your account brings progress together. You do not need to search scattered conversations to know what happened or what is pending.
Prepared
See the request and planned channel.
Sent
The date and sending evidence are kept.
Pending
Replies and any follow-ups are tracked.
Completed
The received outcome and conclusion remain accessible.
Organisations generally respond within one month, with a possible extension for complex requests. Results depend on the context and removal cannot be guaranteed. Understand the conditions and your options
Frequently asked questions
See all FAQsWhat to know about our method
Why aren't all traces handled in the same way?
The right contact, legal right and available channel depend on the trace. A broker listing, public page, social profile and credentials exposed in a breach do not call for the same action. Data Knight therefore assesses each result before preparing a request.
What information does Data Knight send to an organisation?
Only what is useful to locate the data and process the request: for example, the necessary identity details, the email address or phone number held by that organisation, the relevant URL or listing, the chosen request and the mandate where required. Results unrelated to that organisation are not shared.
Is my full report sent to the brokers or websites you contact?
No. Each recipient only receives what is necessary for its own request. It does not receive your full report, traces found on other websites, brokers or platforms, or contact details unrelated to its own listing.
Do I have to provide an ID document to request removal?
Not by default. An organisation can ask for further verification if it has reasonable doubts about the requester's identity. When this happens and the request is justified, you send the supporting document directly to the organisation. Data Knight neither collects nor stores it.
What happens when a form contains a CAPTCHA?
If a manual step prevents submission, Data Knight provides the direct link, useful details and, where relevant, prepared wording. You complete the CAPTCHA and submit the request yourself, and it remains tracked in your account.
How are the broker list and methods kept up to date?
Every week, Data Knight reviews its methodology, expands the list of monitored brokers and checks the addresses, forms, procedures and templates it uses. When an organisation changes its process, the corresponding method can be adjusted.
What happens if there is no reply or a request is refused?
The response and status remain visible in your account. Depending on the channel, time elapsed and reason given, Data Knight may prepare a follow-up, ask for clarification or explain the next step. A refusal is not automatically unjustified: some data may be subject to a legal obligation or another right.
Can Data Knight guarantee every removal?
No. The final decision rests with the organisation holding the data and depends on the legal context. Data Knight handles the practical process, keeps it traceable and makes follow-ups easier, without promising that every request will be accepted.
Verifiable foundations
The legal principles behind our method.
These official resources explain data minimisation, the right to erasure and applicable response deadlines.
Keep learning