Security & privacy
Designed with privacy and security in mind
Behavioral-health data deserves engineering that assumes scrutiny. This page describes what the platform does technically — and is candid about what remains your responsibility and what requires contractual review.
Encryption
TLS for every connection — the platform refuses to run without HTTPS in production. Encrypted storage volumes at rest. Backups encrypted with keys held outside the server.
Authentication & sessions
Hashed credentials (bcrypt — no one, including us, can read a PIN). Short-lived sessions with instant revocation, forced credential changes on first sign-in, automatic idle screen-lock, and progressive lockout against guessing.
Role-based access
Minimum-necessary visibility by role and unit. Facility staff can never see another facility; platform operators cannot browse clinical records through any built interface.
Data isolation
Every facility's data lives in a physically separate database. Sessions are cryptographically bound to their facility — a credential from one is rejected by every other, structurally.
Audit trails
Clinical records are append-only; corrections reference the original. Every sign-in, observation, change, and alert is attributed and timestamped.
Privacy in notifications
Lock screens are public. By default, alerts identify rooms, not names — including client names requires an explicit administrative decision.
Infrastructure
Hardened single-purpose servers: minimal exposed ports, no direct application access except through TLS termination, instance-metadata protections, and health monitoring.
Backups
Automatic nightly encrypted backups, per facility, synced off-server. Per-facility restore — one organization's recovery never touches another's data.
Privacy-conscious analytics
This website uses count-based analytics only: no advertising trackers, no cross-site identifiers, and never any information about clients or care.
The honest part: shared responsibility
Security claims in healthcare software are frequently oversold. Here is the accurate division:
What the platform provides
- The technical safeguards above, maintained and monitored.
- A Business Associate Agreement for covered entities — see BAA information.
- Incident-response preparation: monitoring, alerting, and a documented response process.
What remains yours
- Device policy for staff phones (passcodes, OS updates, what happens when someone leaves).
- Account hygiene: deactivating departed staff, scoping access to units appropriately.
- Your own privacy policies, consents, and workforce training.
- Deciding what optional features fit your risk posture (for example, names in notifications or SMS alerts, which traverse carrier networks).
Review the model before you reach out
The product and use-case pages show the operational flow. Send any remaining technical questions directly.