The profile belongs to a different career
The name matches, but the company, job or dates do not fit your background.
Loading page…
Data Knight distinguishes your traces from those of people who share your name.
Each scan adapts to the useful information available about you. We cross-check results with contextual signals such as your city, background, username, email or phone number when relevant to reduce false positives. There is no zero-risk guarantee: you can exclude any result that is not about you in one click.
A result may look relevant at first and still refer to someone else. Context helps distinguish a personal trace from a namesake.
The name matches, but the company, job or dates do not fit your background.
An incompatible city, address or organisation may reveal a namesake.
A social profile can share your name but have clearly different details.
The method adapts to each person and source. An exact email address and a page containing only a name do not provide the same evidence.
Your name and, depending on what you provided, contact details, location or background set the initial search context.
City, employer, school, username, photo, dates or other useful public details confirm or contradict the match.
Consistent signals strengthen the result. Insufficient or conflicting context sends it for review or excludes it.
Signals are not simply added together. Their precision, consistency and possible contradictions determine how a result is presented.
Name, city and background match the information available in your scan.
The source lacks enough detail to attribute the result with sufficient confidence.
Location, profession or identity suggests this is probably someone else.
Public information can be incomplete, outdated or shared by several people. Data Knight reduces false positives without claiming to eliminate them entirely.
The “This is not me” button remains available on public web results.
The result no longer counts in your footprint and disappears from recommendations.
Data Knight does not build a removal request from a result you excluded.
Assessment helps clean up the report. Your validation and checks before sending help prevent ambiguity from becoming an automatic request.
A shared name alone does not automatically turn a page into a personal trace.
Explicitly select the data you want to act on before any request.
An ambiguous match is held for review rather than sent automatically.
A first and last name do not always identify just one person. A page, profile or public listing may belong to someone who shares your name. Data Knight looks for additional context before retaining the result.
Matching is adapted to the useful information available for each person and source. Where available, Data Knight cross-checks signals such as city, approximate age, work history, school, username, photo, email address or phone number. Several consistent signals strengthen a match; conflicting or insufficient context makes it uncertain.
A false positive is a result attributed to you that actually concerns someone else, often someone with the same name. Data Knight uses strict matching criteria to reduce them, without claiming it can eliminate them entirely.
No. Public information can be incomplete, outdated or shared by several people. Cross-checking several signals greatly reduces the risk but cannot remove it completely. That is why ambiguous results are flagged and you can always exclude anything that is not yours.
It immediately removes the result from your report and prevents Data Knight from preparing an action based on that trace. If you are signed in, the exclusion is saved so that the same result does not reappear in later scans. Without an account, it applies for the current session.
No. Exclusion corrects your Data Knight report. It does not delete the other person's page or remove it from search results. A deletion or delisting request should only concern data that actually relates to you.