Who are we looking for?
Every field is optional. Skip anything you would rather not type — the console tells you honestly what that costs before you start.
Your attack surface
What someone could actually do with what is known about you — computed from your details alone, before any searching. Risk is not additive; it is the combinations that matter.
Your identity graph
Every identifier we can search on, and how they connect. Each one is another way to find you — and another thread someone else could pull.
What a data broker might have filed you under
Generated from what you typed. This is what the search plan hunts for — records are rarely stored the way you write your own name.
Your search plan
Ordered by how sharply each one identifies you. Phone- and email-only searches come first because almost nobody else matches them — those find listings a name search never will.
Scan for me
Runs the whole search plan for you and reads what it finds. Nothing to open, nothing to paste.
Paste your search results
Ran a search and can see listings that are you? Select the whole results page (Ctrl/Cmd+A), copy, and paste it here. The console reads every result at once, works out which ones are you, and adds them — no need to open them individually.
Broker snippets usually contain the record itself — age, city, relatives — which is often enough to judge without opening the page.
Or check one page in detail
Opening an individual listing gives a fuller read than a snippet — worth doing for anything ambiguous.
Paste the whole page. More text means a better read.
Delete from all of them at once
Overall exposure
Exposures
Highest privacy risk first. Every one answers the same four questions: how the site got your information, why it believes the record is you, what someone could actually do with it, and the fastest way to make it go away.
Actually submit these — automatically
This page can do everything up to the submit button, and then it has to stop. That is not a missing feature; a web page is forbidden from filling in and submitting a form on somebody else's site, and that same rule is what stops any tab you have open from posting from your bank. The removal engine therefore runs on your machine, where it can drive a real browser.
What this page did
- Built your identity profile and every form a record might be filed under
- Ran the searches and read the results
- Decided which records are really you
- Worked out what can be removed, and drafted the request
What the agent does next
- Fills in and submits each opt-out form for real
- Stops and asks you about CAPTCHAs, ID requests and anything wanting payment
- Reads the confirmation and records the case number
- Comes back weeks later to check the record actually stayed gone
Hand it over — three commands
- Export your work below.
- Install the agent once:
git clone https://github.com/paddyriyer/paddyspeaks && cd paddyspeaks/privacy-agent && npm install - Import and let it work:
node bin/privacy-agent.mjs init node bin/privacy-agent.mjs import ~/Downloads/privacy-console-export.json node bin/privacy-agent.mjs run --mission
Nothing is submitted without your say-so. --mission asks
once and then works unattended; --review asks before every single filing. Either
way it never pays a site, never fills in a government ID, and never treats "request
submitted" as "removed" — it goes back and looks.
Your export contains your identity details. It is a file on your own machine; delete it once imported.
Your data
Held in this browser only.