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.

TLS on every connectionEncrypted at rest and in backupsOne database per facilityBAA for covered entities

bcryptHashed credentials — no one, including us, can read a PIN

Append-onlyClinical records are never overwritten; corrections reference the original

NightlyEncrypted backups per facility, synced off-server

Rooms, not namesLock-screen alerts identify rooms by default

Technical safeguards

What the platform does

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 of what the platform provides and what stays with your program.

Support Scan does not claim HIPAA compliance as a product badge — no software alone can be "HIPAA compliant." Compliance is a property of your program: technology, agreements, policies, and training together. We provide the technical safeguards and the BAA; the compliance program is built with your privacy officer.

What the platform provides	What remains yours
The technical safeguards above, maintained and monitored.	Device policy for staff phones — passcodes, OS updates, what happens when someone leaves.
A Business Associate Agreement for covered entities — see BAA information.	Account hygiene: deactivating departed staff, scoping access to units appropriately.
Incident-response preparation: monitoring, alerting, and a documented response process.	Your own privacy policies, consents, and workforce training.
Per-facility data export at any time, and a complete export at off-boarding.	Deciding what optional features fit your risk posture — for example, names in notifications or SMS alerts, which traverse carrier networks.

Documents

For your privacy officer

Everything a privacy or compliance review usually asks for is published, not gated behind a sales call.

Review the model before you reach out

Technical and contractual questions go straight to the person who built the platform.

Ask a technical question