This page describes how www.proxyalert.online handles visit data, based only on what has been verified for this build. It covers the mechanisms that exist on this site, the data they touch, and the boundary between this static page and the outside sites it links to.
Scope
This site is a set of static files served by a content delivery network, which acts as the hosting provider and processes the technical data of every request it delivers. The pages themselves are self-contained: everything a page needs to display loads from this domain, including locally embedded fonts, so no outside host is contacted while a page is being shown.
Visit Tracking
When a visitor arrives from a search engine, a first-party visit beacon sends a small set of details to an edge analytics endpoint on this same domain: the page path, the type of event, the name of the referring search engine, and the text of a clicked outbound button. This information is used only to count page views and clicks on outbound buttons, for the operator's own traffic counting, and for nothing else. It is stored in the operator's own logs on this domain. Alongside this, the content delivery network reports the country associated with the request, with nothing more precise about location.
Cookie and Session Flag
| Mechanism | Detail |
|---|---|
| First-party cookie | Set only when a visit arrives from a search engine; holds the name of that search engine; kept for up to one hour; used to match a later outbound-link click to the search engine that brought the visitor |
| Session view flag | Kept in the browser only for the current session; ensures a single page view is counted once |
Neither of these is a persistent identifier. No other browser storage is set beyond these two mechanisms.
Outbound Links
Outbound links to third-party sites use a first-party outbound redirect: the link first points to a path on this domain, then forwards the browser to the partner site. This site does not pass any stored visit data to the partner during that redirect. Once the redirect completes, the partner site receives the request directly from the visitor's browser and keeps its own separate record of that visit. This site has no control over what a partner site does with that request, and this page describes only the mechanisms on this domain, not the practices of any linked destination.
Absences
This site has no forms, no contact channels, no third-party analytics, and no external subresources loaded into its pages. It has no login, no registration, and no user account. These absences, together with the limited and locally logged analytics described above, are why this site does not ask visitors for consent, an account, or any personal detail. Readers should not submit personal data through any linked destination on the assumption that this page's description applies there — each linked site keeps its own record and sets its own terms for what it does with a visit.