Architecture overview, role model, privacy boundary, demo environment
Trust center
Security claims should be earned, specific, and verifiable.
Anivow Care is built for healthcare-adjacent recovery data. The security model starts with least privilege, clinic isolation, explicit sharing boundaries, and careful language about what is available today versus what still requires formal evidence.
Procurement readiness
Security overview, RLS test evidence, backup and retention review
BAA availability, SOC 2 plan, penetration-test summary, incident runbook
No Anivow SOC 2 report, penetration-test summary, or approved BAA is represented as currently available.
Control model
Designed around access boundaries, not trust in the UI.
Professional dashboards must not depend on hidden buttons or optimistic frontend checks. The important constraints belong in the data model, policies, and server-side mutation paths.
Implemented foundation
Role-aware access
Clinicians, clinic admins, organization admins, and platform admins are separated by role and clinic relationship.
Requires ongoing verification
Tenant isolation
Care data is scoped through clinic relationships and Supabase row-level policies, not only frontend routing.
Product boundary
Data minimization
Clinician workflows display permitted patient-entered records and exclude private Snow conversations.
Foundation in place
Audit-friendly records
Care events, invitations, staff status, and review timestamps are structured for operational traceability.
Authorization
Each role gets a narrow view of the care workspace.
Care-team access is based on clinic membership and patient-clinic relationships. A clinician should not be able to retrieve unrelated patients, and private Snow data should remain outside clinician-facing policies.
RoleCan accessBoundary
PatientOwn records and sharing choicesNo clinic-wide access
ClinicianAssigned or clinic-connected patientsNo unrelated patients
Clinic adminClinic staff, patients, programs, invitationsNo other clinics
Organization adminOrganization clinics and governanceNo unrelated organizations
Data protection
Minimize sensitive data before protecting it.
Supabase-backed care data
The platform uses the existing Supabase project and extends the care schema instead of creating a duplicate auth or database system.
Private content exclusion
Private Snow conversations and unshared journal entries are not part of clinician dashboard queries or care-team summaries.
Operational evidence needed
Backup retention, incident response, vendor review, access reviews, and production audit logs still need formal owner approval before broad deployment.
Procurement
Clear status beats vague trust language.
Centers should receive exact documents, exact owners, and exact dates. Until evidence exists, the site should say “in preparation” or “requires verification,” not imply a finished compliance program.
Security overviewIn preparation
BAA availabilityRequires legal and commercial verification
SOC 2Not represented as available
Penetration test summaryNot represented as available
Incident response procedureRequires owner approval
Security review
Bring your requirements into the conversation early.
We can review role boundaries, data-sharing assumptions, procurement gaps, and pilot requirements before any center deployment.
Contact security