Some of the engineering choices behind this
HTTPS everywhere, enforced by the browser. Every request to Bilateral Calm is delivered over TLS, and the server tells your browser to refuse insecure connections for the next year via the HSTS header. There is no plain-text version of this app.
Strict security headers. Every page returned by our servers includes X-Frame-Options: DENY (no one can embed Bilateral Calm in a malicious iframe to trick you into clicking), Referrer-Policy: strict-origin-when-cross-origin (we don't leak the page you were on when you click outbound links), and a strict Content-Security-Policy that blocks scripts from anywhere we don't explicitly trust.
Session cookies marked HTTP-only and Secure. Even if a malicious browser extension tried to read your session token, it can't — the cookie is invisible to JavaScript and only sent over HTTPS.
Logs that don't leak. Our backend logs are written without personal identifiers like email addresses. An engineer triaging an issue sees opaque IDs only.
Field-level encryption for sensitive notes. Any free-text reflection or journal entry you write inside the app is encrypted with a separate per-app key before being stored. Even our engineers cannot read those entries by querying the database.
Your rights, in one place
Right to access. Download a complete JSON of everything we have stored about you, any time, from Settings → Privacy → "Download my data".
Right to erasure. Permanently delete your account and all associated data with one click — Settings → Privacy → "Delete my account". The deletion executes immediately; it is not a "marked for deletion" placeholder.
Right to portability. The export above is in standard JSON, so you can hand it to a successor service or just inspect it.
Right to ask questions. Email hello@bilateralcalm.com and a real person — not an AI agent — will reply.
If something goes wrong
In the unlikely event of a data breach affecting Bilateral Calm users, we commit to notifying affected users by email within 72 hours of discovery, with a clear description of what happened, what data was involved, and what steps you should take. We will publish a public post-mortem on this page within 30 days.