Company

Privacy

Honest description of what Droplit stores. This is not a lawyer-reviewed policy; it matches how the product actually works.

Sigma identity

Dashboard sign-in uses Sigma at auth.sigmaidentity.com. The Better Auth plugin on this host receives OAuth callbacks and stores user state in the browser (Zustand plus local storage). Identity keys stay in the Sigma domain. Signing for BRC-103/104 happens through the Sigma iframe wallet, not by exporting a private key into Droplit. Wallet connectivity via 1Sat is a separate payment-wallet concern and is not the same as Sigma identity. Sigma has its own privacy policy for the identity service; this page covers Droplit.

Bitcoin SV public chain

Deposits, taps, pushes, funds, and mints become Bitcoin SV transactions. Amounts, output scripts, OP_RETURN payloads, and transaction identifiers are public and permanent. Droplit cannot unpublish a confirmed transaction. Do not put secrets, personal data, or credentials into push-data or inscription content. Paymail handles of the form {name}@droplit.dev are aliases for receiving BSV, not private inboxes.

Tenant metadata in Redis

This Next.js app uses Upstash Redis (environment variables KV_REST_API_URL and KV_REST_API_TOKEN) for tenant and related records. Droplit tenant data is keyed as subdomain:{name}. OAuth client records, when used, are keyed by Bitcoin public key. Redis holds metadata needed to route multi-tenant subdomains and look up clients. It is not a place we store WIFs. The Go backend at api.droplit.dev keeps droplit configuration, UTXOs, and activity history in its own database.

Keys and request signatures

This application does not embed WIFs and must not. Service agents that call the API hold their own signer material in their environment (for example DROPLIT_SIGNER_WIF) and present BRC-103/104 signatures through AuthFetch. The API sees public keys, signed handshake material, and JSON bodies. Private keys that live in Sigma never leave Sigma. Delegated API keys on a droplit are allowlisted public keys plus scopes, not shared owner secrets.

Logs, cookies, and this website

Reading docs and marketing pages does not require an account. Hosting and CDN infrastructure typically record standard request logs (IP address, URL, user agent) to operate and secure the site. The application source does not include a third-party advertising or product-analytics SDK. Authenticated dashboard use relies on client-side Sigma session state. Activity feeds for a droplit use the same mutual-auth protocol over a WebSocket to the API.

Sharing, retention, and changes

Droplit is operated by bOpen / Open Protocol Labs. Account and tenant data is used to run the wallet service, not sold as a marketing list. Subprocessors needed to host Redis, the API, and this site see the data those systems already store. On-chain data is outside any deletion request. Questions about this page go through Contact. Material changes will be published here. Last updated 27 August 2026.