Direct answer_
What this covers
BTC Mixer Guide has no accounts, forms, newsletter or advertising. Traffic measurement runs only when a measurement ID is configured.
What remains true
Server and hosting logs sit outside the guide's code; this page explains what is known about them and what is not.
Status of this document
This document does not name the hosting provider or the party that operates the domain. Neither is identified in the available records, so there is no listed contact for a request about a server-side record. Domain registration and server billing sit outside this guide and may not identify a person.
What is processed when you read a page
A visit can leave four kinds of record: two at the server layer, one when analytics is enabled and one if a third-party script writes browser data.
Data map for a single page request
Scroll horizontally to compare all columns_
| What is processed | Who processes it | When it happens | Where it ends up |
|---|---|---|---|
| The address of the page you requested, and the time of the request | The web server and the hosting layer | On every request | Server logs outside this site's code |
| The network address your request came from, and the client details your browser sends | The web server and the hosting layer | On every request | Server logs outside this site's code |
| Traffic measurement events | The analytics provider | Only in a build configured with a measurement ID | With the provider, under the provider's own terms |
| Cookies or local storage written by a third-party script | That script's own provider | Only when such a script is loaded | In your browser's storage, and in the provider's systems |
Analytics, and the condition that switches it on
Analytics appears only when the published build includes a measurement ID.
You can check in your browser's network panel. Load a page and look for a request to an analytics domain; if none appears, no analytics script was fetched.
If a request appears, the build includes an ID and the visit is reported to the provider under its own terms. Read the provider's notice for what it keeps.
Server, network and hosting logs
Serving a page over HTTP can create a record at the server and hosting layer whether or not the page code asks for one. The guide's source files neither add to it nor remove it.
Any right to see, correct or delete that record belongs with the operator who holds it. This document cannot name that operator because no hosting provider is identified in the available records.
The server operator also decides how long the record survives. No retention period is given because nobody identified here can establish it.
No sale, no sharing, no profiling
The guide holds no first-party profile to sell or share.
The guide holds no personal data of its own to sell, rent, share or disclose. It builds no profile, serves no advertising, runs no mailing list and stores nothing that could be handed to a third party on request.
The commercial relationship is disclosed before the handoff. The thirteen content routes carry a labelled link to a commercial service; the five utility pages have no commercial CTA. Once you follow that link, the service's own data practices apply and this policy stops at the click.
Your choices
You can control four parts of the visit without contacting anyone.
- Block the analytics domain in your browser, in an extension or at your network. On a build with no measurement ID there is nothing to block.
- Refuse third-party cookies and site data in your browser settings.
- Use a browser that blocks trackers by default, which removes the third-party request with no configuration on this site's side.
- Send your request through a network layer you control, if you want the server-side record to show that layer rather than your own connection.
Changes to this policy
An edit changes this policy and moves its last-updated date.
No notification is sent because the guide has no way to reach a reader. The last-updated date is the only change signal provided.
Compare that date with the copy from your previous visit. An unchanged date means no edit was recorded; a changed date means the text changed, but no revision history shows how. Keep a copy when the difference matters.