BLXBenchBLXBench UI
blxbench

Benchmark

Levels

Misc

DocsDownload blxbenchOur TestsPassSponsor / Partnership
DocsDownload blxbenchOur TestsPassSponsor / Partnership

Legal

Privacy

How BLXBench handles account data, benchmark submissions, cookies, API keys, and billing metadata.

Last updated

April 24, 2026

01

Operator

This page, domain, and the public BLXBench service are operated by bitslix.com. BLXBench uses the information described below to run the benchmark site, account features, public submissions, and related services.

Official operator, privacy contact, and security contact information is available through https://bitslix.com.

02

What we collect

We collect information needed to operate BLXBench: account details such as email, display name, avatar, authentication sessions, passkeys, two-factor settings, API keys, and blxbench device login tokens.

Benchmark activity may include submitted report metadata, model identifiers, provider labels, scores, costs, run configuration, timestamps, and submitter profile information shown on public pages.

03

How we use data

We use data to authenticate users, secure accounts, enforce quotas, process submissions, display leaderboards, debug service issues, improve benchmark quality, and communicate about account or billing events.

We do not need your provider API keys for normal web browsing. Keys used for model providers should stay in your local environment unless you intentionally submit related run metadata.

04

Cookies and local storage

Essential cookies support sign-in, sessions, security, CSRF protection, and account features. The cookie banner stores your preference in local storage so we do not ask on every visit.

Optional analytics, when enabled, may help us understand product usage and documentation quality. You can choose essentials only from the banner.

05

Payments and third parties

Billing and subscription flows may be handled by Stripe. We receive subscription status, plan, invoice, and checkout metadata needed to provide pass features, but payment card details are handled by Stripe.

Authentication providers, hosting, analytics, email, and infrastructure vendors may process data as needed to provide the service.

06

Retention and deletion

Account data is kept while your account is active or as needed for security, legal, billing, and operational reasons. You can revoke sessions, blxbench device tokens, and API keys from account settings.

Public benchmark submissions may remain visible or be retained in aggregates to preserve leaderboard history and reproducibility unless removal is required or appropriate.

07

Security

We use authentication controls such as email verification, sessions, passkeys, two-factor authentication, scoped API keys, and account-level revocation tools. No service can be perfectly secure, so avoid submitting secrets or private data in reports.

Report suspected vulnerabilities privately through https://bitslix.com.

08

Contact

For privacy questions or data requests, contact the operator through https://bitslix.com. Include enough context for us to identify your account or submission without sending secrets.

Legal links

Terms of UsePrivacy

These pages describe the public BLXBench service. Enterprise or private deployments may use separate agreements.

BLXBench

Community driven leaderboardPublic benchmark runner — run in your environment, share results with the community.

© 2026 BLXBench by bitslix.com

ProvenanceAggregated from user runs
Scope6 / 7 / 372
Latestrun_be5c42 / 7 / $0.0019
TermsPrivacy