Legal

Security

Chaperone is designed for private, sensitive support conversations. Our security program uses layered technical and organizational controls to protect information, restrict access, monitor for misuse, and support recovery when something goes wrong.

No Third-Party Trackers

No advertising, analytics, or session-replay trackers in the user product.

Chaperone uses no third-party analytics, advertising, or cross-site tracking technologies in the user-facing product. Product analytics are first-party and use a constrained event schema that excludes free-text content and personal data fields. We set only session, security, preference, and short-lived sign-in and onboarding cookies. We do not use advertising or cross-site tracking cookies.

Encryption

Data in transit is protected with industry-standard transport encryption across browser-to-application, application-to-database, and application-to-third-party connections. Data at rest is encrypted across our managed database and file-storage infrastructure.

Application secrets are held in encrypted, environment-scoped secret storage, strictly separated between production and non-production. Storage encryption keys are managed by our infrastructure providers.

Least-Privilege Access

Access to production infrastructure and administrative consoles requires multi-factor authentication, and workforce accounts are enrolled in multi-factor authentication. Chaperone enforces granular role-based access controls so users, Coaches, administrators, and operational teams receive only the capabilities appropriate to their role.

Authorization is enforced in the application by policy. Additional row-level-security policies are defined and tested for member-data tables. Deployment of these additional protections varies by environment; application-level authorization remains the primary enforced control. Role assignment, revocation, and time-bound elevated access are administrative actions, and temporary elevated access requires a written justification and expiration.

Audit Logging

Chaperone maintains audit records for sensitive administrative and member-data actions to support accountability and investigation. Audit access and retention are governed by security controls.

Logging and Monitoring

Platform, application, and database activity is logged by our hosting and database providers and reviewed during incident response. Sensitive actions are additionally written to the audit trail described above.

We do not send application errors, transcripts, or other support content to third-party error-monitoring or session-replay services.

Production Isolation, Backups, and Recovery

Production operates on separate application and database infrastructure from non-production environments, with separate credentials, secrets, and session state. Production releases are deliberately promoted rather than automatically promoted from development environments.

Backups are encrypted and our managed database supports point-in-time restore.

AI Security and Governance

AI features are delivered through a single governed egress path. No application code calls a model provider directly, and that constraint is enforced by a lint rule in our build pipeline.

Every request to our primary AI provider carries a provider-level instruction excluding providers that log or train on prompts. The exclusion is applied on the request path by default rather than left to individual developer choice, and our build refuses a production configuration that disables it.

AI use is governed alongside the rest of the security program, with separate safety-classification workflows, evaluation controls, consent gating, and human oversight.

Chaperone does not use identifiable member content for internal model improvement. Any user-derived information used for internal model improvement is de-identified, minimized, and quality-reviewed before it enters an improvement dataset.

Vendor and Service-Provider Controls

Chaperone evaluates service providers based on the nature of the information they process and the role they perform. Chaperone requires appropriate privacy, confidentiality, security, retention, and deletion protections for providers handling sensitive information, including contractual protections where applicable. The status and scope of individual vendor agreements are verified as part of vendor oversight. Credentials are scoped by environment, and integrations are designed to receive only the information reasonably necessary for their function.

Vulnerability Management and Testing

Automated build and test pipelines include access-control and row-level-security testing.

Incident Response

Chaperone maintains an information-security incident-response process covering escalation, containment, and notification.

This process covers information-security events. It is separate from the member-safety and crisis-escalation procedures that govern a member’s immediate wellbeing.

Report a Security Concern

If you believe you have identified a security issue involving Chaperone, contact privacy@chaperone.health. Privacy questions and requests may also be sent to that address.

For information about how we use personal information, see our Privacy Policy and Consumer Health Data Privacy Notice.

Let’s talk

Controls we can show, not just describe

Have a security question, or something you want to report? Start a conversation and we’ll route it to the people who own the answer.