Privacy information

Operator: Chat Admin. Contact chat@bittrees.org.

Accounts and public identity

Chat uses wallet addresses and shared Bittrees sign-in to identify an account. Users choose their public display labels and optional public profile information. Shared sign-in does not grant mailbox access, room membership or transaction authority.

Messages and email

Wallet messages and email have different privacy boundaries. Wallet conversations use their messaging protocol; delivered copies can remain on recipients’ devices and messaging networks. Connected email uses your Mail account and is not end-to-end encrypted wallet messaging.

Mail access requires your selected read, send and optional read/unread permissions. A connection can last until revoked. If you choose durable access, Chat can remain connected after signing out of Mail. Use Disconnect Mail and check the result; if source revocation could not be confirmed, revoke the connection in Mail too.

Storage and retention

Local message history, preferences and recovery data can remain on your device. Optional encrypted sync and service-side connection records have their own storage. Removing local data or disconnecting does not erase delivered messages, your mailbox or copies held by other participants.

Where wallet-to-email forwarding is enabled, encrypted queued message payloads expire after 24 hours and delivery metadata after 30 days. Operational backups, suppression records and delivery journals have separate retention and are not erased by disconnecting. Automatic backup deletion is not configured for this release.

Connected services

Depending on the feature used, Chat contacts messaging networks, wallet connectors, chain/RPC services, Bittrees identity and Mail services, and hosting/storage or email-delivery providers. These services process the requests and connection metadata needed for the feature. Public help pages also load Bittrees Insights’ consent controls.

Your controls

You can change your public profile choices, disconnect Mail and manage authorized permissions in the source service. Contact Chat Admin about retained service data, backups or a deletion request. Ownership must be verified before account-specific action; decentralized and recipient-held copies cannot be erased through a local reset.

Never send seed phrases, private keys, authentication tokens or private message contents to support. Report vulnerabilities through private security reporting.