Digital security
The room is protected. So is the network.
Boron's physical-privacy layers are paired with modern encryption, access controls, and abuse defenses. We don't store plaintext messages, and don't run ads or trackers.
Open Security CenterManage sessions and signed-in devices from inside Boron.
End-to-end encrypted messaging
- 1:1 chats are end-to-end encrypted by default; message content is encrypted on your device and stored server-side only as ciphertext.
- Attachments are encrypted with per-file keys and kept in private storage buckets; the server sees only encrypted blobs plus minimal metadata.
Account protection
- App-authenticator (TOTP) multi-factor authentication is supported, so a password alone is not enough when MFA is enabled.
- Idle auto-lock and optional auto-sign-out after short inactivity windows protect sessions on shared devices.
Session & device control
- A Security Center shows your active sessions and recent logins, including new-device activity.
- Remotely sign out this device, other devices, or all devices from inside Boron.
Abuse & brute-force defenses
- Login failures and security events are monitored and rate-limited by IP and email hash, with structured audit trails and Retry-After guidance.
- Onboarding and recovery links are rate-limited and logged, reducing spam and automated attacks.
Privacy-by-design
- Boron never stores message plaintext on the server, does not include ads or tracking scripts, and uses a strict Content Security Policy.
- IP addresses are stored only as salted hashes plus coarse masked values for security alerts; anonymous events use hashed email identifiers.
Security FAQ
What's protected. What isn't.
Straight answers about how Boron treats your messages, your account, and your devices — including where our protections stop.
ProtectedYes. 1:1 chats are end-to-end encrypted by default. Content is encrypted on your device and stored on our servers only as ciphertext.
LimitsEncryption protects messages in transit and at rest on our side. It can't protect content that's already visible on an unlocked, in-use device.
ProtectedThe minimum needed to run the service: your account, encrypted messages and attachments, and coarse security signals for abuse defense.
LimitsWe don't store message plaintext, ad identifiers, or precise IPs — IPs are kept only as salted hashes plus masked values, and anonymous events use hashed identifiers.
ProtectedBoron focuses on casual snooping, shoulder surfing, and typical network and server-side risks.
LimitsIt isn't a defense against a fully compromised device, a targeted forensic adversary, or someone holding your unlocked phone. It also can't hide that you use a chat app — only what's inside it.
ProtectedNo ad networks and no analytics trackers inside the app. A strict Content Security Policy blocks inline and third-party scripts.
LimitsThis marketing site may load minimal first-party analytics to measure interest, only after you grant consent and only if your browser hasn't set Do Not Track. It never has access to your account or messages.
ProtectedYes. Boron supports app-authenticator (TOTP) MFA, idle auto-lock, and short-inactivity auto-sign-out for shared or public devices.
LimitsMFA and auto-lock only help if you turn them on. We strongly recommend enabling both on any shared device.
ProtectedThe in-app Security Center lists active sessions and recent logins, flags new-device activity, and can remotely sign out this device, other devices, or all devices.
LimitsRemote sign-out revokes future access; it doesn't retroactively erase content already viewed on a device before you signed it out.
ProtectedWe're open about our digital-security posture — encryption, MFA, session control, abuse defenses, and privacy-by-design principles.
LimitsSome implementation details are not public while patent protection is in progress. Certain mechanism details remain confidential during that process.
Review active sessions, new-device alerts, and remote sign-out inside the Boron Security Center.