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 measures below are the security safeguards PIPEDA’s safeguards principle requires, appropriate to the sensitivity of the information.

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.
• Accolgo’s own platform operators can see that a check-in and a note exist, not their content, on an internal page open only to Accolgo’s own staff.

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.

Reporting a concern

If you believe you have found a vulnerability, email dermot@clickonic.co. We acknowledge reports promptly, do not pursue good-faith researchers, and ask that you avoid accessing other people’s data while demonstrating an issue.