Privacy Notice
This is a privacy-education tool, so we hold ourselves to the same standard we ask of other sites: honest, specific, no vague reassurances. Here's exactly what happens when you use it.
What runs entirely in your browser
- The inputs you type — names, addresses, phone numbers, usernames, emails — stay in your browser's memory and are only used to build search links.
- Your hit/no-hit marks and exposure score — stored in memory only, gone when you close the tab. Nothing is persisted anywhere.
- The generated dork queries and direct-search URLs — built locally by JavaScript. Nothing is sent to us to construct them.
What we don't use
- No Google Analytics, Plausible, Fathom, PostHog, or any other analytics service.
- No cookies. This site sets zero cookies.
- No
localStorageorsessionStoragewrites. - No third-party tracking pixels, embedded widgets, or social media beacons.
- No sign-in, no accounts, no email collection.
- No server-side processing of your inputs — we don't run a backend that sees them.
What we should be honest about
A privacy tool that pretends nothing at all is happening would be lying. Three things are worth knowing:
1. Hosting logs (Vercel)
This site is hosted on Vercel. Like every web host, Vercel automatically logs standard access requests: your IP address, browser user-agent, request path, and timestamp. This is baseline infrastructure logging — not something this app collects or has access to. Vercel retains these logs per their privacy policy, typically for a limited period.
What Vercel does not see: the words you type into the input fields. Those never get sent to the server. Vercel only sees which page URL you loaded.
2. URL parameters during the Dorks → Direct Search handoff
When you click "Continue to Direct Search" from the Dorks page, your inputs are passed to the next page in the URL — for example: tools.html?first=Jane&last=Doe&city=Towson. This is convenient (no retyping) but it means those values briefly appear in your browser's address bar and in Vercel's access logs for that one page load.
If this bothers you: retype your inputs directly on the Direct Search page instead of using the handoff button. The URL will stay clean.
3. When you click a search result
Every "Search" and "Open" button on this site is essentially a bookmark — it opens the destination site in a new tab, the same as if you typed the URL yourself. From that point on, you're a normal visitor on that site, subject to its own privacy practices.
A helpful tip: if you'd like an extra layer of privacy while running these searches, a browser with built-in tracking protection (like Brave or Firefox in strict mode) or a VPN can help. It's optional — the tool works fine without either.
How to verify this yourself
Don't take our word for it — the tool is fully client-side and inspectable:
- Open your browser's DevTools (right-click → Inspect) and watch the Network tab while using the tool. You'll see the initial page, CSS, and JS load — and nothing else. No
fetch, noXMLHttpRequest, no beacons. - Check the Application → Cookies tab. Empty.
- Check Application → Local Storage. Empty.
- View source (Ctrl/Cmd+U) and search for common tracker domains. None appear.
Changes to this notice
If the site's behavior ever changes — for example, if we add opt-in analytics or accept feedback via a form — this page will be updated first. Last updated: August 2, 2026.
Questions
This tool is educational and open. If something on this page is unclear or you find behavior that contradicts it, the fastest way to verify is DevTools (above). This site is maintained by In Charge Consulting.