Get Blee ↓
Privacy policy
Last updated September 23, 2026. This policy explains how Blee handles information when you use the Blee app or paywithblee.xyz.
Blee is self-custodial payment software designed to help people discover nearby Blee users and make blockchain payments. Blee does not need your private key in order to operate the website, and the app is designed so transaction authorization happens on your device.
Depending on the features you use, Blee may process information such as your chosen display name, profile photo, public wallet addresses, support messages, and settings you submit. If you enable nearby visibility, the app may make the identity information you selected for nearby discovery visible to other Blee devices in Bluetooth range.
Public wallet addresses, transaction signatures, balances, transaction status and other onchain information may be retrieved from or submitted to Arc, Solana, NEAR, Zcash and related infrastructure providers. Blockchain records may be permanent. Shielded Zcash transfers can conceal certain details on-chain, but do not guarantee anonymity. Blee cannot delete or reverse data already recorded on a public blockchain.
Blee is intended to keep private signing material under the user's control. Do not send Blee your private key, seed phrase, recovery secret or backup passphrase. If a backup or recovery feature stores encrypted backup material with a service provider, that encrypted material may be processed to provide the feature; users remain responsible for protecting credentials needed to restore or decrypt it.
The website maintains aggregate visit and APK-download counters. The Blee counter code records a page view each time a page loads and does not use that counter to create a unique visitor profile. Hosting, security, network and infrastructure providers may independently receive standard technical request data such as IP address, user agent, timestamps and request logs as part of operating their services.
Where needed to operate features, prevent abuse, diagnose failures or deliver notifications, Blee may process limited app, device, network and diagnostic information. Third-party providers used for hosting, blockchain access, notifications, databases, analytics, crash reporting or similar infrastructure process information under their own terms and privacy practices.
Information may be used to provide nearby discovery and payment functionality, maintain account or app settings, reconcile transaction state, secure the service, prevent abuse, provide support, understand aggregate usage, improve reliability, and comply with lawful obligations.
Blee may share information with infrastructure and service providers only as reasonably needed to operate the relevant feature, with authorities when legally required, or as part of a legitimate reorganization or transfer of the service. The aggregate website visit/download counters are not designed to create advertising profiles.
Blee retains information only for as long as reasonably needed for the purposes described above, subject to legal, security, backup and technical requirements. No software, wireless connection, storage system or blockchain interaction can be guaranteed perfectly secure. Keep your device, keys, backup credentials and recovery material protected.
You can stop nearby discovery by disabling the relevant visibility controls or Bluetooth permissions, and you can stop using the service at any time. Where applicable law gives you rights to access, correct, delete or restrict personal information held by Blee, you may request those rights through the current contact channel published at paywithblee.xyz or @paywithblee. Onchain records cannot be erased by Blee.
Blee may update this policy as the app, infrastructure or legal requirements change. The updated version will be posted here with a revised date. Material changes may also be highlighted through the website or app.
This policy should reflect the services actually enabled in production. If Blee adds new analytics, identity, backup, notification, token or account features, the policy should be reviewed and updated before or when those features launch.