1. Access and isolation
Data is separated by organization and authorized recipient. Account linking transfers no organization role. Public codes/PINs confer only their issued grant. Sensitive changes require recent authentication, MFA belongs independently to each login, and sessions have expiry, revocation and traceable events.
2. Files and secrets
Files use private storage with authorization checks on retrieval. Security values are hashed or encrypted according to purpose; linking responses expose no API tokens to browser code. PINs and OTPs do not appear in general administrative diagnostics. Professional evidence is separated, encrypted and available only to an authorized, audited reviewer.
3. Administration and incidents
Operational access uses separate capabilities; sensitive actions require recent authentication and audit. Support uses limited metadata and has no unrestricted customer impersonation. Do not include medical files or secrets in a ticket. Report a vulnerability or incident to [email protected] with a safe description, time and support code.
4. Validation and limits
The code contains abuse controls, safety checks and archive/deletion workflows. Scanner, TLS, storage, backup, restoration, log minimization and supplier operation must be demonstrated in an approved environment. We assert no ISO/SOC certification, absence of risk, general end-to-end encryption or production readiness based on code tests alone.