Draft for review. The United States has no single federal privacy law, so this wording is written to the strictest commonly applicable state standard, principally California’s CCPA as amended by the CPRA. It has not yet completed a legal review, so it does not yet bind anyone.

Security

Accolgo holds opinions given in confidence about named people, so it is built as if every row will one day be read by the person it concerns. The CCPA requires reasonable security procedures appropriate to the nature of the information, and creates a private right of action if a breach results from failing to provide them. These are the measures.

Access

Every organization’s data is isolated: row-level security on every table, zero anonymous table access, and org scoping enforced again in the application layer.
Check-in links are private, single-use, randomly generated tokens that expire after 14 days. A guessed URL opens nothing.
Managers see their own team; the owner and head of people see their organization; platform operators see activation metadata and aggregates, never check-in content.

Platform

Encryption in transit everywhere; encryption at rest at the database provider.
Secrets live in environment configuration, never in code or the repository.
Migrations are numbered, reviewed and applied with explicit grants; every change to grants is checked against prior revocations.
Error monitoring with per-organization tagging; an append-only email delivery log.

If something goes wrong

Every US state has a breach-notification law, and they differ on timing and on what triggers them. Our commitment is simpler than the patchwork: we will tell the affected organization without undue delay and in any event within 72 hours of becoming aware, with what we know and what we are doing, and we will support that organization in meeting whatever its own state requires of it.

Reporting a concern

Email dermot@clickonic.co. A security report goes to the front of the queue ahead of any feature work.