This page explains what happens on www.onlyleaks.online itself, covering the small amount of visit data the site records, the one cookie it sets under specific conditions, and how that differs from the separate sites reached through outbound links.
What visit data does this site record?
When a visitor arrives from a search engine, the site records the page path, the type of event, the name of the referring search engine, and the text of any clicked outbound button. This happens only for arrivals from a search engine, not for every visit. The data is used solely to count page views and clicks on outbound buttons, and for no other purpose. It is stored in the operator's own logs on the same domain, not sent to an outside analytics company. Alongside this, the content delivery network reports only the country associated with a request — nothing more precise about where a visitor is located.
What does the site store in a visitor's browser?
- A first-party cookie, set only when a visit arrives from a search engine, kept for up to one hour, holding nothing but the name of that search engine. It exists so a later click on an outbound link can be matched to the search engine that brought the visitor.
- A session view flag, which lasts only for the current browser session and exists so that a single page view is counted once rather than multiple times.
No other browser storage is set, and no persistent identifier is created. Once the hour passes or the session ends, this information is gone.
How is the site built, and what does that mean for tracking?
The site is a set of static, self-contained pages served by a content delivery network, which acts as the hosting provider and processes the technical details of each request. Fonts used on the pages are embedded locally rather than pulled from an outside font service. No file needed to display a page is loaded from an outside host, so nothing is shared with a third party while a page is being viewed. There are no forms on this site, no third-party analytics scripts, no external subresources, and no contact channels — which is also why the site never asks for a name, an email address, or any other personal detail, and never requires an account or login.
What happens when a link leads to another site?
Outbound links point to third-party sites. A first-party outbound redirect means that clicking such a link first passes through a path on this domain before continuing on to the partner site — that redirect step is how a click can be counted before the visitor leaves. Once the visitor arrives at the partner site, that site receives the request directly from the visitor's browser and keeps its own separate record of it; nothing stored by this site is handed over to the partner in that process. This site has no visibility into, and no control over, what a partner site does with a visitor after that point. Anyone following an outbound link should treat the destination as a separate site with its own practices, and should not assume that anything explained on this page applies once they have left this domain.