Whatthefirstbetamaycollect.

Early access data

A connected signup form collects email, optional ISP and FACEIT level, and consent. In this private review, details are not saved unless the configured endpoint confirms receipt.

Website accounts

Creating a Hopzen web account sends your name, email address, password, and confirmation of the Terms and Privacy notice to the Laravel account service. The service stores a password hash, not the original password, along with account and consent timestamps. It may send email-verification and password-reset links. Never send a password or sign-in code to support.

Sign-in sessions

The website uses a secure Laravel session cookie and CSRF protection. Session records include the session identifier, account association, IP address, browser user-agent, and last activity time as required by Laravel’s database session driver. Sessions expire according to the configured service lifetime. The website does not store a bearer token in browser storage. During the Pakistan-only beta, connection and location signals may also be reviewed to assess eligibility and detect VPN, proxy, or out-of-country access.

Device and session data

App version, OS compatibility, match destination, selected relay, and session timing may be needed for route selection. Final collection and retention details must be published before client access.

Diagnostics consent

Optional reports require separate consent and an explanation of fields sent. This website does not upload client diagnostics automatically.

Support requests

When the API is configured, the support form sends your name, email, category, subject, message, and consent to Laravel. Staff may review the request and add private handling notes. Ticket lookup returns only its reference, status, subject, and update time. The current site preview does not accept or store support requests. Do not include passwords, authentication tokens, or unrelated sensitive details.

Traffic scope

For the initial CS2 beta, only the active match destination is targeted. Browsing, downloads, and unrelated applications retain their normal ISP path. Hopzen does not promise anonymity. If future titles require different data, the collection details will be updated before those features are offered.

Before launch

Retention periods, deletion requests, mail and hosting providers, operator details, and a verified privacy contact require finalization and legal review before public account or beta signup. The account and support data should not be treated as having a finalized retention schedule until those details are published.