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: 3 June 2026Polybit is currently operating as a testnet beta. The product is intended for testing user experience, account access, demo ledgers, market review, invoice flows, and settlement behavior.
Real-value mainnet payments are disabled in this beta. Do not send mainnet BTC or production Lightning funds to Polybit during this phase.
Email account data: when you create or use an email account, Polybit stores the email address, password authentication metadata, and account session state required to provide access.
Wallet or account identifiers: when you use wallet-based access, Polybit stores the wallet/account identifier needed to associate positions, invoices, and ledger history with that session.
Session data: Polybit uses signed session cookies and related browser state to keep you logged in and route you to the correct user experience.
Demo ledger data: for email accounts, Polybit stores simulated demo credits, demo positions, stake amounts, payout estimates, settlement status, and demo transaction history.
Invoice and payment data: when invoice flows are enabled, Polybit stores invoice status, payment status, amounts, expiry, and ledger references needed to track the payment lifecycle.
Technical logs: Polybit may collect request logs, timestamps, error messages, device/browser metadata, and operational diagnostics to monitor reliability, security, and beta performance.
We use collected data to authenticate users, keep account history isolated, show available and historical positions, calculate demo balances, track invoices, debug failures, improve product reliability, and protect the beta from abuse.
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.
Polybit uses cookies for signed sessions and may use browser storage for local preferences such as default view, default stake, 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.
Polybit does not sell user data. During the beta, data may be processed by infrastructure, hosting, monitoring, or payment-related systems required to operate the product.
Operational providers may receive technical data needed for hosting, logs, security, or invoice/status checks. User-facing screens do not expose internal execution providers.
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.
Beta data may be retained while Polybit validates product behavior, audits ledger outcomes, investigates bugs, or improves reliability.
Because the beta is still evolving, account deletion and automated retention controls may be limited. Support requests can be used to request review of account or demo data.
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.
For privacy questions, demo account questions, or beta data requests, contact Polybit support from inside the app or through the public support channel when it becomes available.