▸ PRIVACY TERMINAL
~/privacy
Last updated: 2026-03-17
├ TL;DR ┤

This site uses no analytics scripts, no cookies, and no tracking of any kind. We have zero visibility into individual visitor behavior. We don't know who you are, where you came from, what you clicked, or how long you stayed.

Verify this yourself — view source.

├ WHAT WE DON'T COLLECT ┤
✗ Analytics scripts — no Google Analytics, no Plausible, no Fathom, no Matomo, nothing
✗ Cookies — we set zero cookies of any kind
✗ Tracking pixels — no beacons, no pixels, no 1x1 images
✗ Fingerprinting — we don't fingerprint visitors (our fingerprint tool only runs on-demand for YOU)
✗ IP logging — we don't operate any server that logs your IP
✗ Session recording — no heatmaps, no replay tools
✗ Third-party scripts — no external JavaScript loaded
✗ Advertising — no ad networks, no retargeting
✗ Personal data — no forms that send data to us, no email collection
├ HOW OUR TOOLS WORK ┤

All Privacy Terminal tools run entirely in your browser. When you use the fingerprint analyzer, the threat profiler, the hash generator, or the metadata stripper — all computation happens client-side in JavaScript. No data is transmitted to any server.

Exception — Leak Tester: The leak tester tool communicates with our own Cloudflare Worker (privacyterminal-api.workers.dev) to detect your visible IP address and DNS configuration. This is the only tool that makes an external request. The Worker processes the request in real-time and stores nothing — no logs, no IP addresses, no request data. The code is open source.

Progress System: The gamification/progress system (privacy score, achievements) is stored entirely in your browser's localStorage. No progress data is sent to any server. If you clear your browser data, your progress is gone — we have no backup because we never had your data.

├ CLOUDFLARE HOSTING ┤

This site is hosted on Cloudflare Pages as a static site. Cloudflare, as our CDN and hosting provider, processes requests to deliver this site to you. This means:

→ Cloudflare sees standard HTTP headers (IP, User-Agent, etc.) to serve the page
→ Cloudflare provides aggregate analytics in their dashboard (total requests, bandwidth, country-level distribution)
→ We see aggregate numbers only — we cannot identify or track individual visitors
→ Cloudflare's own privacy policy applies to their infrastructure: cloudflare.com/privacypolicy

We chose Cloudflare Pages specifically because it requires zero code on our part to get basic traffic numbers. No JavaScript analytics needed. No cookies needed. The dashboard metrics come from Cloudflare's infrastructure, not from anything running in your browser.

├ VERIFY OUR CLAIMS ┤

We don't ask you to trust us. We ask you to verify.

1. View source — Right-click → View Page Source on any page. No hidden scripts.
2. DevTools → Network — Watch every request. No analytics endpoints, no tracking pixels.
3. DevTools → Application → Cookies — Zero cookies set by this domain.
4. Read the code — Full source on GitHub. MIT licensed. No obfuscation.
5. Use uBlock Origin — It will confirm: nothing to block.
├ LOCAL STORAGE ┤

The site uses your browser's localStorage (not cookies) to remember:

→ Your privacy score progress and achievements
→ Boot animation state (so it doesn't replay every visit)
→ Optional: your threat profile results (if you choose to save them)

This data never leaves your browser. We cannot read it. There is no sync, no backup, no server component. Clear your browser data and it's gone forever — because we never had it.

├ CONTACT ┤

If you have questions about this policy or find something that contradicts our claims, please report it via our security.txt contact or open an issue on GitHub.

This privacy policy is as simple as our data collection: both are effectively zero.