Bloom peerCookies & device storage
Effective 24 October 2026
Bloom peer uses no advertising, analytics or optional tracking cookies. The product website serves pages without a first-party login cookie. Requests still require temporary processing of network information to deliver the service; production application/access logs are not retained.
Necessary app storage
| Storage | Purpose | Retention and controls |
|---|---|---|
| Session and bearer credential | Authenticate your account. Stored in native app storage or web local storage. | Until sign-out, account deletion on the device, or clearing app/site data. |
| Local contacts, messages, unsent messages and drafts | Show history and retry pending delivery. Native uses SQLite; web uses browser local storage. | Until clearing history, account deletion, or clearing/eviction of app data. Signing out preserves history; recipients may keep their copies. |
| Deleted-message keys | Prevent duplicate peer and server retries from restoring deleted messages. These keys do not retain message text. | Until account deletion on the device or clearing app/site data. |
| Theme, video quality, local profile and debug preferences | Remember your choices on this device. | Until changed or app/site data is cleared. Account deletion clears account-specific profile settings; device-wide settings can remain. |
| Optional temporary device debug log | Show technical connection information when you turn on Debug mode. | Bounded to 256 entries in temporary app storage; the OS controls cleanup. Normal customer builds do not upload it. Disable Debug mode to stop new collection. |
| App files, browser cache and an installed service worker | Load the app and website. | Controlled by the OS/browser; uninstall or clear site data to remove it. |
Your controls
Use Me → Clear local messages, Sign out or Delete account. Clear app/site data to remove remaining device preferences and local storage. Check pending messages/drafts first: local data cannot be restored from our server. Camera/microphone permissions are controlled in your device or browser settings. OS/cloud device backups, if you enable them, are separate from Bloom peer's servers.
See the privacy notice or contact support@bloompeer.com for questions.
Temporary server delivery
Messages normally travel directly over encrypted WebRTC. When temporary server delivery is enabled, undelivered message text, reply references and delivery/read receipts may be held in a server mailbox over HTTPS. The service can read queued content; this mailbox is not end-to-end encrypted. Call media is not stored in the mailbox.
Each accepted copy is held for the configured period, normally up to one day, and removed sooner after the recipient confirms successful local processing. Fetching alone does not remove it. A mailbox or host restart loses queued copies. The sender keeps pending messages locally and may upload a fresh copy after expiry or loss, starting a new retention period. One day is a limit per accepted copy, not across every retry of a message. “Sent to server” does not mean delivered or read.
This is not a history backup or synchronization service. Clearing local history cannot recall uploaded server copies or erase another person's copies. Account deletion revokes mailbox access; remaining copies expire under the same retention policy. Message content is excluded from server logs and backups. Push providers receive neither message text nor message IDs.