RapTor

By

Updated

Privacy

This is a complete list of what RapTor collects about a visitor, not a summary of the parts that sound good. It is short, because there is almost nothing on it: no analytics script, no advertising network, no cookies, no accounts, no comment forms, no fonts or scripts pulled from a third-party server. What is left after removing all of that is the part no site — including this one — gets to opt out of just by choosing to.

What this site does not do

  • No analytics. No Google Analytics, no Plausible, no Matomo, no pixel from any provider counting visits, sessions, or which page sent you here.
  • No cookies. Nothing is set to identify a return visit, remember a preference, or track a session across pages.
  • No accounts, forms, or newsletter. There's nothing to sign up for and nowhere on the site that asks for an email address, a name, or anything else typed into a box.
  • No third-party fonts, scripts, or embeds. Every asset a page loads is served from this site's own domain — no font loaded from a type foundry's server, no script pulled from a CDN, no embedded video or map that quietly reports back to whoever hosts it. Each of those is a second party learning a visitor was here, and none of them are in use.
  • No advertising or affiliate tracking. Nothing on this site earns money from a visitor's click, and there is no ad network here to track one.

What the hosting infrastructure still sees

RapTor is a static site: plain pages with no server-side application, no database, and no login system behind them. That removes most of what a typical site could leak, but it does not remove the one layer no website — static or not — gets to switch off: whatever a web server ordinarily records about the connections it serves, such as the requesting IP address, the time of the request, the page asked for, and the browser's user-agent string. That is standard behaviour for HTTP infrastructure generally, not a feature this site added, and this page will not promise a blanket "nothing is ever logged" that no static site can actually keep. If that changes — a CDN, a different host, anything added that logs or processes visitor data beyond this baseline — this page is rewritten in the same change that adds it, not sometime after.

The practical point for a visitor who wants to control this layer themselves: reaching this site over an ordinary browser and a home connection means an ordinary IP address sits in whatever log line that request produces. Reaching it over Tor Browser means the server sees a Tor exit relay's address rather than the visitor's own — the same protection this site's own Tor Browser guide and safety page describe for every other site a reader might visit, and it applies here exactly as it does anywhere else.

If a mirror of this site exists on Tor

Nothing about the collection described above changes depending on how a page is reached. A visitor arriving through a clearnet browser, a VPN, or a Tor-accessible mirror of this site is subject to the same short list above and the same host-level logging behind it — a mirror is a different address, not a different privacy policy.

Related pages

For who publishes this site and the standard it holds itself to, see About. For what the information on it is not, see the disclaimer. The front page routes to everything else.