1. Controller

The controller responsible for data processing is:

Bitslix.com
Blücherstraße 27
04159 Leipzig, Germany

2. Hosting and server log files

Our hosting provider automatically collects and stores information that your browser transmits: IP address, request time, requested page, referrer, browser and operating system. This is necessary to deliver the site and to keep it secure and stable.

Legal basis: Art. 6(1)(f) GDPR, our legitimate interest in a secure, reliably operated website.

3. Accounts

You can create an account with Discord, Google or GitHub. We then receive the identifiers that provider passes on for sign-in, and we store a profile: display name, optional handle, optional tagline, optional avatar URL, profile visibility, whether you want your online status shown, and whether the picture from your social login should be displayed. You may add a passkey or a TOTP app as a second factor; we store the credential data needed to verify them, never your biometric data.

Legal basis: Art. 6(1)(b) GDPR, performance of the user relationship you asked for.

4. Activity tied to your account

While signed in we store what you do on the site so it can be shown back to you and to others: comments and their edit history, votes on matches and on comments, the karma derived from them, playlists and their entries, and who you follow.

Comments, their author name and karma, and public playlists are visible to everyone. Votes are stored per account so a vote can be changed or withdrawn, but they are only ever published as totals.

If you enable the online indicator, the site sends a short presence signal while the tab is open so your profile can show as online. Turning the setting off in Settings stops it.

5. View counts

Each match page counts one view per browser session. Your browser stores a marker under blxbench:viewed:… so a reload is not counted again. The marker stays on your device and is cleared when the session ends; only the resulting total is stored on our side.

Legal basis: Art. 6(1)(f) GDPR, legitimate interest in basic reach figures.

6. Local storage in your browser

A handful of preferences are kept on your device and never sent to us. None of them is used to recognise you:

blxbench-theme — your light/dark choice, so the site does not flash the wrong theme on the next visit.
blxbench:history:v1 — the replays you have watched, for the archive rail.
blxbench.graphics.v1 — quality overrides you set on the replay player.
blxbench:viewed:… — the per-session view markers described in section 5.
blxbench-ledger-v1 — the choice you made in the storage ledger, so you are not asked twice.

The storage ledger, reachable from the footer of every page, lists all of these with what each one is for, reads your browser live to show which are actually present, and can delete them.

7. No tracking or advertising cookies

We do not use analytics, advertising networks, or cross-site tracking. Sponsor plates on match pages are plain links; we do not embed sponsor scripts or pixels. Following such a link takes you to a third party whose own privacy policy then applies.

8. Error reports and session replay

When something breaks, our error monitoring provider Sentry receives the error itself, the page it happened on, and your browser and operating system version, together with page-load timings for a sample of visits. It does not receive the contents of the page.

Legal basis: Art. 6(1)(f) GDPR, our legitimate interest in a site that works. You can object under Art. 21 GDPR using the contact details in section 1.

Session replay is separate and is off unless you turn it on. If you allow it in the storage ledger, Sentry additionally records a reconstruction of your visit — the pages you moved through and where you clicked — so a bug you ran into can be reproduced. All text is masked and all images and video are dropped in your browser before anything is sent, and the arena replay canvas is not recorded at all. Recordings are kept for 90 days.

Legal basis: Art. 6(1)(a) GDPR and § 25(1) TTDSG, your consent. Withdraw it at any time by switching it back off in the storage ledger; the recorder stops immediately, and withdrawing does not affect what was lawfully recorded beforehand.

9. Recipients and processors

Data is processed by our hosting and infrastructure providers, and by Sentry for the error monitoring described in section 8, on our behalf under Art. 28 GDPR. Signing in with Discord, Google or GitHub means that provider processes the sign-in itself under its own policy. We do not sell personal data.

10. Retention

Server logs are kept for a short period for security and diagnostics. Account data and the content you posted are kept until you delete them or ask us to delete the account. Deleting a comment removes it from public view; totals derived from it may remain.

11. Your rights

You have the following rights vis-à-vis the controller:

Access to your personal data (Art. 15 GDPR)
Rectification of inaccurate data (Art. 16 GDPR)
Erasure (Art. 17 GDPR)
Restriction of processing (Art. 18 GDPR)
Data portability (Art. 20 GDPR)
Objection to processing based on legitimate interests (Art. 21 GDPR)

To exercise any of these, write to [email protected]. You also have the right to lodge a complaint with a supervisory authority.

12. Obligation to provide data

You are under no obligation to provide personal data. Watching replays needs none. Without an account, the features that depend on one (commenting, voting, playlists) are unavailable.

13. Automated decision-making

We do not use automated decision-making or profiling within the meaning of Art. 22 GDPR. The rankings on this site describe AI models, not people.

14. Updates

We update this policy when the service changes. The effective date at the top of this page always reflects the current version.