Security and data handling

Implemented controls

Saved Decision Intelligence operations verify Supabase sessions, derive organization membership on the server, and enforce module permissions and tenant-scoped queries. Imports have size, schema and value limits. Reports require authorization and respect current reporting safeguards.

Pilot leads are stored privately. Only separately allowlisted, verified platform administrators can access the pilot management APIs; being an organization administrator is insufficient. Important lead changes have append-only audit history and optimistic revision checks.

Public forms use server validation, expiring signed verification, a honeypot and database-backed rate limits. Secrets belong in environment settings, never browser bundles or source control.

Deployment and assurance

The main domain uses Cloudflare Workers. Database and integration configuration varies by environment. Deployment to a particular vendor does not establish a PsychFlo certification, regional residency guarantee, contractual uptime guarantee or independently audited security posture.

PsychFlo does not claim SOC 2, ISO 27001, or clinical certification. Local tests and synthetic tenant-isolation checks do not replace an independent assessment or verification against the configured production services.

Retention and incident handling

Use aggregate inputs and exclude unnecessary employee identifiers or health information. Organization retention settings document policy; automatic deletion and legal hold require separately reviewed operations. New first-party usage data has an administrative 90-day cleanup operation; pilot request retention is reviewed with the engagement and deletion requests.

Contact support@psychflo.com for access, retention, deletion or security issues. Do not email workforce datasets or credentials.