Privacy Policy
Last updated: August 2026
The short version
| Question | Short answer |
|---|---|
| Are there accounts or logins on this site? | None at all |
| What personal data is requested? | None; there is no registration form here |
| What is recorded? | Aggregate navigation statistics and short technical server logs |
| How long is it kept? | Server logs rotate out on the hosting cycle; statistics follow the analytics retention window |
| Where do privacy questions go? | The contact form on this site |
What is not collected
This section comes first because it is longer than its opposite. acgwin.biz has no account system, no checkout and no form asking for identity. It therefore does not request or store names, identity numbers, addresses, phone numbers, email addresses, card details or documents of any kind. There is no visitor database on our side, so there is nothing to leak, sell or hand over.
The site also runs no advertising pixels, no social media widgets and no third-party trackers beyond the analytics tool named below.
Aggregate statistics through Google Analytics 4
The only analytics tool in use is Google Analytics 4. What it produces are aggregate reports: which pages were opened, how long visits lasted, device and browser type, and an approximate region at a level that identifies nobody. The identifiers involved are anonymous and are not linked to any identity, because identity never enters our systems in the first place. Analytics cookies can be blocked from your browser settings without affecting a single page function.
The affiliate marker
Links from this site to the Acgwin platform carry a marker showing where the visit originated. It tells the operator the visit came from our pages; it carries no personal data because we hold none. Once you are on the platform, the operator privacy policy governs, and that document is worth reading before a single field is filled in.
Retention
Technical logs at the hosting layer exist for security and fault diagnosis, build no profiles, and rotate out automatically on the hosting cycle. Aggregate statistics follow the retention window set in Google Analytics, after which they are deleted at the provider. We keep no backup copies of either.
Your rights
Rights of access, correction and erasure presuppose that the party asked is holding personal data. Because we hold none, such requests are in practice addressed to two other parties: Google for analytics data, and the platform operator for your account data. Questions concerning this site itself are answered through the contact form, with no layered ticket system and no template replies.
Protection of minors
This site is written for readers aged 18 and over and does not target children. Because the zero-collection policy applies to every visitor without exception, no data is gathered from any age group. Limit tools and support contacts are on responsible gambling.
Changes to the analytics stack
If the analytics tool is replaced or added to, this page is updated before the new tool is switched on, not afterwards. Consent requested after the fact is not consent, and a notice published after collection has started is not a notice.
Outbound links
The only functioning outbound link on this site leads to the Acgwin platform. From the moment you follow it, all data processing moves to the operator side and is governed by their documents.
Cookies: what the browser actually stores
Cookies are small files stored by your browser, and they are not all equivalent. On an information site like this one only two categories are relevant: cookies holding a display preference, and analytics cookies counting which pages are read. There is no third category here, because there is no login session to preserve and no advertising to target.
Refusing analytics cookies blocks access to nothing. The setting lives in your browser and takes effect immediately. On the operator side the picture differs: there, session cookies are genuinely required to keep an account open, and the detail is set out in the operator own privacy policy.
Data on the operator side: what is collected and how it is protected
Everything typed into the cashier travels to the operator over an encrypted channel, so anyone watching the same public network sees only a meaningless string of characters. Connection encryption is the baseline expected of a licensed site, and the padlock beside the address is the quickest way to confirm it is on before a single field is filled. What the operator actually keeps is narrower than people assume: identity and contact details for verification, transaction history because financial regulation requires it, and technical records of logins and devices so that access by someone else becomes visible.
Data leaves in a few predictable directions: the payment provider that moves the money, the service that checks documents, and the regulator or bank on a formal request. All of that processing happens on the operator side rather than here, so a deletion request or a copy of your own file goes to their support desk through the in-account form. On the player side the useful habits are dull and effective: a password reused nowhere else, two-factor authentication switched on in account settings, and no signing in from someone else device. If a session was left open on a device you no longer hold, changing the password closes it faster than hoping nobody looks.
Revisions to this page
Changes are published with a date at the top of the page. Changes affecting what is collected or how long it is kept are flagged separately rather than slipped into an existing paragraph.