Polybit
HomeTerms of UseSupportLaunch app
Privacy Policy

How Polybit handles beta data.

This Privacy Policy explains what data Polybit collects during the testnet beta, why it is used, and how demo, wallet, invoice, ledger, session, and technical data are handled.

Last updated: 8 September 2026

1. Testnet beta scope

Polybit's public beta is a testnet/demo environment used to evaluate market, account, wallet, transaction, and settlement workflows. Demo balances have no monetary value and the beta does not support live real-money settlement.

Do not use real funds with beta wallet, payment, transaction, or settlement flows.

2. Data we collect

Email account data: when you create or use an email account, Polybit may process your email address and password authentication data. Password credentials are stored using derived password hashes rather than as plaintext passwords.

Wallet or account identifiers: when supported wallet or signature features are used, Polybit may process public wallet identifiers, network information, signatures, and technical data needed to verify authentication or connection requests.

Session data: Polybit uses signed session cookies and related browser state to keep you logged in and route you to the correct user experience.

Market and position data: Polybit may process selected markets, position amounts, demo balances, position status, transaction or ledger references, and settlement status.

Lightning beta payment data: some beta workflows may process Lightning invoice and payment status information, such as invoice references, payment status, or related technical identifiers. These flows are part of the test/demo environment and do not represent live production settlement.

Technical logs: Polybit may collect request logs, timestamps, error messages, device/browser metadata, and operational diagnostics to monitor reliability, security, and beta performance.

3. How we use data

We use collected data to operate the beta, authenticate users, verify wallet and signature requests, display market, position, and account state, maintain demo ledger and transaction state, operate beta payment-testing workflows, diagnose technical problems, detect abuse or security issues, respond to support, and evaluate the beta.

We do not use demo balances or testnet activity as real-money account balances. Demo balances have no cash value and are only used to validate the product flow.

4. Cookies and local preferences

Polybit uses cookies for signed sessions and may use browser storage for local preferences such as default view, default amount, privacy display settings, and market filter preferences.

Privacy display settings such as masked balances and hidden identifiers change what appears on screen. They do not change ledger ownership, account access, or stored account records.

5. Data sharing

Polybit does not sell user data. During the beta, data may be processed by infrastructure, hosting, monitoring, or payment-testing systems required to operate the product.

Operational providers may receive technical data needed for hosting, logs, security, or invoice/status checks.

6. Security

Polybit uses signed sessions and separates the user and admin experiences. Admin routes and operational dashboards are protected separately from the user interface.

You should never share passwords, wallet private keys, seed phrases, or signing credentials. Polybit will never ask for a seed phrase.

7. Retention

Beta data may be retained for as long as reasonably necessary to operate, secure, test, troubleshoot, and evaluate the public beta, subject to applicable legal or operational requirements.

8. Changes to this policy

This Privacy Policy may change as Polybit moves from testnet beta toward production. Material changes should be reflected on this page before broader public use.

Questions

Contact beta support

For privacy or beta-data questions, contact support@polybit.app or use the public Support page.

Open Polybit
© 2026 Polybit
HomeTermsSupport