PII & Privacy
Encrypted private profile, approval-gated change workflow, multi-country national ID framework, and DSAR-ready data export.
Employee SIN, SSN, dates of birth, emergency contacts, banking details — this data needs special handling. FrontLine keeps it in a separate encrypted store, behind a change-request workflow (no direct mutations), with every read and write captured in the audit trail. DSAR fulfillment is a single export, not a forensic project.
Approval-gated, encrypted at rest, exportable when a DSAR arrives
Private profile data lives in a separate table with field-level encryption at rest (AWS KMS-backed envelope encryption). Reads of PII columns require an explicit `pii.read` permission and emit a separate audit event. Writes are not direct: an HR Admin submits a change request, an approver reviews and approves, and the system applies the change. National identifiers are stored via a country-aware framework (SIN for Canada, SSN for US, etc.) so adding a new country is a configuration change, not a schema migration.
What's covered out of the box
Audit-ready artifacts your reviewers can lean on
- PIPEDA — fair information principles, accountability, safeguards
- CCPA / CPRA — DSAR fulfillment, right to delete
- GDPR readiness — Articles 15, 17, 20 workflows
- SOC 2 Type II — confidentiality controls
What security and compliance reviewers actually ask
Can an HR admin directly edit an employee's SIN?+
How quickly can we fulfill a DSAR?+
What about right-to-erasure?+
Who can read PII?+
Run this past your security team
We share security overviews, RLS policy DDL, audit-event schemas, and SOC 2 progress on request. Book a 30-minute security review with the founders.