Deletion
The record is withdrawn by the source at request.
Available only where the source offers deletion and the match is confirmed.
Public-data exposure, mapped
See where your information came from — and what can actually be done about it.
Unsource Me maps what is publicly visible about you, traces the source and consent relationships behind it, prepares the action each record actually permits, verifies the outcome, and watches for recurrence.
01 · How it works
Five steps, in order, and each one leaves a record.
The order matters. Nothing is prepared before the source relationship is traced, and nothing is called an outcome before a dated re-check says so.
- 01
Map
What is publicly visible, and where it sits.
Discovery runs only against identifiers you have verified control of. Each appearance is recorded with a dated snapshot, so a record exists whether or not anything can be done about it.
- 02
Trace
Which source fed which copy, graded by evidence.
Downstream copies are matched back to the record that supplied them. Conclusions carry an evidence tier; anything short of a direct disclosure or a canary hit is shown as a correlation and is never described as the origin.
- 03
Prepare
The action each record actually permits — not a form letter.
Routes are derived from what the source offers and what the law supports for that record class. A public filing does not get a deletion request drafted against it, because the filing cannot be deleted.
- 04
Verify
A dated re-check, with the proof kept.
An outcome is only recorded as verified absent when a later fetch returns the evidence of absence and a control assertion still passes. A source's acknowledgement on its own is not verification.
- 05
Monitor
Reappearance is expected, and is watched for.
Records that return are recorded as recurred rather than quietly re-opened, so the difference between a route that worked once and a route that holds is visible.
02 · What we prepare
Six action classes, and the bound on each one.
A record gets the action it actually permits. Where a route does not exist, the record is monitored and the reason is shown on the record rather than left blank.
Opt-out
A standing instruction not to list or sell the record.
Binds the source that accepted it. It does not bind that source's suppliers.
Correction
A wrong or stale value is amended in place.
The prior value may persist in copies already distributed.
Deindexing
A page is removed from a search index while it remains on its host.
The underlying page is untouched and stays reachable directly.
Suppression
A value is withheld from public display without deleting the record.
The record continues to exist and may still be disclosed under other rules.
Consent revocation
A previously given permission to process or share is withdrawn.
Applies going forward. It does not reach data already transferred.
03 · Limits
What this cannot do, stated before you ask.
Each of these is a constraint in the engine, not a disclaimer added to the page. The product refuses to draft an action that a record does not permit.
Public filings cannot be deleted
A filing with a county recorder or a Secretary of State is an authoritative public record. Only correction, replacement, redaction or monitoring may be available, and historical versions of the filing may remain public regardless of what we do next.
Ambiguous matches wait for a person
When the evidence that a record is yours is weak, it is held for human review rather than acted on. Nothing is prepared or sent from an unconfirmed match, and the queue is visible to you.
Records come back
Downstream listings are regenerated from upstream feeds. A record that returns is recorded as recurred and re-enters the queue. We do not describe a route as permanent.
Live source connections are limited
The engine is built and tested, but live connections and automated submissions are not broadly active. Where no route is connected, the record is monitored and the reason for that is shown on the record.
No efficacy figures
We publish no removal rate, no percentage, and no time-to-removal claim. There is not yet a defensible measurement to publish, and an indefensible one would be worse than silence.
04 · Data handling
Designed so it cannot be pointed at someone else.
A product that accepts a name and returns a consolidated location is a skip-tracing tool. The rules below are what stop this one from being usable that way.
Discovery is seeded only by verified contact identifiers
Addresses, phone numbers and email addresses you have proved control of. Names, aliases and business tax IDs are never discovery seeds, so the system cannot be pointed at a person who did not enrol themselves.
There is no person-search surface
No free-text search for a person exists anywhere in the product, at any layer. Discovery is a scheduled job keyed to a verified identifier, not a query someone can type.
Identifiers are masked by default
Values render masked in every view. Revealing one is a deliberate act that is recorded, and the record of it is visible to you rather than only to us.
No raw scraped content is shown
Snapshots are redacted before they reach any screen and only allow-listed fields are extracted. Third-party names found beside yours are not retained in the clear.
Evidence is dated and kept
Every claim about a record — that it was present, that a request was sent, that it was later absent — is backed by a timestamped artifact you can open.
05 · Request access
Request private pilot access.
Unsource Me is in a private pilot. Access is granted by invitation, one workspace at a time, so that every source route in use has been reviewed before anyone relies on it. There is no sign-up and no payment.
Tell us who you are asking on behalf of. If a sentence or two of context would help, add it — otherwise leave it blank.