Trust and Security

How we protect member, practitioner, and organisation data.

Authentication and access

Every account is authenticated through a managed identity provider with email/password and Google sign-in. Role based access controls separate members, practitioners, ops, and admins. Sensitive HR, compensation, and clinical-licensing fields are restricted to admin/ops roles and are not exposed to practitioners or members.

Data protection

All application traffic is served over HTTPS. Data is stored in a managed Postgres database with row-level security policies on every table. Privileged operations run through server functions that verify the caller's session before touching data.

Secrets and integrations

Third-party API keys (scheduling, email, AI) are stored as server-side secrets and never shipped to the browser. Webhook endpoints verify signatures before processing payloads.

Privacy

Clinical notes and risk information are visible only to the assigned practitioner and authorised ops staff. Members can request access to or deletion of their personal data by emailing the team.

Reporting a vulnerability

If you believe you've found a security issue, please contact us so we can investigate and respond.

This page describes our current security posture and is maintained by the Rebuilding Thoughts team. It is not an independent certification.