Security & trust

Isolation is enforced by the database, not just the app

Every organization's data — residents, staff, documents, billing, everything — is scoped by row-level security policies inside the database itself. Even a bug in application code can't leak one organization's data into another's view, because the database refuses the query before it ever runs. This is tested directly: every new table ships with automated tests that simulate a second organization trying to read the first one's data and confirm it's refused.

Sensitive records can't be quietly rewritten

Incident reports, discharge records, grievances, medication custody logs, and drug-test draws are kept as permanent entries once saved — there's no delete or silent-edit path, even for an administrator. Corrections happen by adding a dated follow-up, not by changing history. Every edit or deletion that IS allowed elsewhere in the app is captured in an audit trail: what changed, who changed it, and when.

Authentication runs on established infrastructure

Sign-in, password resets, and session handling are built on Supabase Auth rather than a homegrown login system. Staff and resident accounts are separated by role at both the application and database layers, so a resident account is never able to reach staff-only or admin-only data or actions.

Encrypted in transit and at rest

All traffic to the app runs over HTTPS. Uploaded files (documents, photos, signatures) are stored in access-controlled cloud storage and served through short-lived signed links rather than public URLs, so a file's address alone is never enough to view it.

Cross-organization access is allowlisted and logged

Only a small, explicitly-maintained allowlist can ever see roster-level information across more than one organization — and that view is deliberately narrow (organization names, counts, and billing status; never resident-level data). Every time that access is actually used, it's recorded with who, what, and when, so it's not just restricted, it's accountable.

Built for the recordkeeping recovery housing actually needs

Structured, dated documentation for incidents, discharges, grievances, inspections, and medication custody exists because operators are expected to produce exactly this kind of record for an inspector, a referral partner, or a court. The goal throughout is a complete, trustworthy operational record — not the fastest way to log something and move on.