Transparency

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.

This site does not collect, store, or transmit the information you type. No analytics, no cookies, no tracking pixels, no form submissions. Everything runs in your browser.

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.
Your "reviewed" checkmarks on the Direct Search page — also memory only. They clear when you reload or close the tab.
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 localStorage or sessionStorage writes.
No third-party tracking pixels, embedded widgets, or social media beacons.
No third-party scripts, fonts, or CDNs. Every file the site loads comes from this site, and the site uses your device's built-in fonts.
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. The Dorks → Direct Search handoff

When you click "Continue to Direct Search" from the Dorks page, the fields you filled in are passed to the next page after a # in the link — for example: tools.html#first=Jane&last=Doe&city=Towson. Browsers never send the part after # to the server, so these values don't reach Vercel or its access logs. The Direct Search page reads them, fills in its tabs, and removes them from the address bar right away.

Worth knowing: for the moment before the page clears them, the values are visible in your address bar. If you'd rather avoid that, retype your inputs directly on the Direct Search page instead of using the handoff button.

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.

Your own history: the searches you open — your name, phone, address, or email in a Google or people-search link — are saved in your browser history like any other page you visit. If you're signed into Google, Google may also save them to your account activity. If other people use or can see your device or accounts, run these searches in a private or incognito window and sign out of Google first. You can also review and delete past searches at myactivity.google.com.

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, no XMLHttpRequest, 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.
Check the response headers in the Network tab. The site sends a Content-Security-Policy that tells your browser to block any script, font, style, or data connection from another domain, plus Referrer-Policy: no-referrer, so the sites you open from here aren't told you came from this site.

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: October 6, 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.