Unlistd // continuous privacy removal
Remove exposed data.Keep it removed.
Unlistd scans data brokers, verifies personal records, submits removals, captures proof, and repeats the work when listings reappear.
built for records that keep coming back
A calmer loop for personal privacy cleanup.
01Broker scans
Catch profiles before they become a spreadsheet chore.
02Opt-out letters
Send the right request path for each data source.
03Proof capture
Keep readable evidence for every removal action.
04Rescan loops
Watch for relisted records after the first cleanup.
removal // what runs
A focused path from discovery to proof.
Render's page sells simple primitives by giving each section room. This page follows that pattern: one clear claim, one supporting module, then the next proof point.
Find the exposed records
Search broker, people-finder, public-record, and marketing-data sources for likely matches.
Separate signal from noise
Score results against your data sheet so obvious matches move fast and uncertain records go to review.
Run the broker workflow
Submit opt-outs, send CCPA letters, track status, and escalate the removals that need a human touch.
UNLISTD_REMOVAL_RUN
frontendexposure_score.check
brokeroptout_queue.submit
proofremoval_evidence.capture
live surface map
One status model across the product.
The UI should feel like infrastructure for privacy work: quiet, legible, and confident about the state of every record.
coverage // where it works
Remove records across the places people search.
Unlistd keeps the workflow simple: find the listing, choose the right removal path, then keep watching for the record to return.
A clear operating view for every listing.
See what was found, what was removed, what needs review, and what reappeared.
Playbooks for the uneven broker landscape.
Each source gets the right path: automation, letter, manual review, or concierge escalation.
Protection that scales beyond one person.
Teams can manage executive, public-safety, or sponsored-user coverage from one workflow.
output // deliverables
A privacy report users can act on.
The goal is not noise. It is precise removal work with enough context for users, families, and teams to trust the outcome.
- 1Exposure map
A plain-language view of where the user's records appear and which sources matter first.
- 2Removal timeline
Every queued, submitted, reviewed, and verified action in one status trail.
- 3Proof package
Screenshots and report payloads that show what changed after each removal cycle.
- 4Rescan loop
Recurring checks that catch relisted records before the user has to think about them again.
./start_scan
See what brokers already know.
Start with a free exposure score, then choose the level of removal coverage that fits the risk.