This page is maintained by MedAestheticsOS™ to answer common security and compliance questions about our clinical operating system. It describes controls that are enabled in the product today; it is not an independent certification.
TLS 1.3 enforced on every route; HSTS on the primary domain.
AES-256 on database volumes and object storage.
PostgreSQL Row-Level Security on every PHI-adjacent table; enforced by the has_role security-definer pattern.
Client-facing surfaces read redacted views; full records require signed-in staff with a scoped role.
Roles stored in a dedicated user_roles table (never on profiles) to prevent privilege-escalation vectors.
8 failed attempts per 15-minute window per identifier triggers a temporary block.
Available for staff accounts via authenticator app; enforceable per tenant.
Server functions require an authenticated Supabase bearer token; anonymous access is rejected before any query runs.
Every consent, chart edit, refund, gift-card adjustment, and admin action is written to an append-only audit log with actor, IP, and timestamp.
SHA-256 hash of the exact document text bound to signer identity, IP, timestamp, and BAA version.
Database linter flags any table missing RLS or any over-permissive policy before deploy.
Documented in /legal/hipaa; mapped to §164.308, §164.310, §164.312.
Mandatory cryptographic BAA signature during /onboarding; versioned and retrievable per tenant.
Auto-generated at booking with signed patient acknowledgement.
Export (/app/export) and tenant-scoped deletion supported; documented in /legal/privacy.
Underlying infrastructure inherits Cloudflare (SOC 2 Type II, ISO 27001) and Supabase-on-AWS (SOC 2 Type II) attestations. MedAestheticsOS-level attestation is on the roadmap.
≤ 5 minutes — continuous WAL streaming.
≤ 60 minutes — documented failover runbook on /status.
/status — uptime, incident history, DR posture.
Documented playbook; 60-day HIPAA notification path pre-wired.
Booking, waitlist, contact, support, and abuse-report endpoints are throttled per-IP.
Math-based challenge on /contact, /support, /report-abuse.
Edge WAF, DDoS mitigation, and TLS termination handled by Cloudflare.
See /.well-known/security.txt or email support@medaestheticsos.io.
MedAestheticsOS™ provides the platform controls listed above. Each facility remains responsible for workforce training, physical safeguards inside its clinic, appropriate role assignment for its staff, and lawful use of client data. The signed BAA formalizes this shared-responsibility model.