COMPLIANCE & SECURITY
Compliance and security
The standards Pallas scans against, and the security and data-handling controls behind the platform.
Standards supported
Pallas scans against and reports on the following accessibility standards:
Configure which standard profile applies to each scan. Results are mapped to specific success criteria with severity ratings and remediation guidance. Section 508 and EN 301 549 mappings are derived from the WCAG scan. Automated scanning covers the criteria that can be machine-tested; a manual review checklist covers the rest, because most of WCAG cannot be verified by software.
Privacy architecture
Source file handling
Uploaded documents are analyzed and discarded by default. Scan results are retained; source files are not. Configurable retention policies let your organization set its own rules.
No third-party data sharing
Your scan results, findings, and documents are not shared beyond the sub-processors listed on our sub-processors page. No analytics trackers on your data. No model training on your content.
Configurable retention
Set retention policies for scan results, findings, and uploaded files, with a seven-year floor on the audit trail. Retention windows are enforced by a scheduled sweep in the application database.
Security
OAuth-only authentication
No passwords are ever stored. Authentication is handled through Google and Microsoft OAuth providers via Supabase Auth.
Row-level security
Every database query is scoped to the authenticated user's organization. RLS policies enforce data isolation at the database layer; server-side operator functions that bypass RLS by necessity are limited in scope and covered by the audit trail.
Encryption
Data encrypted at rest and in transit: TLS for all connections and database-level encryption, both provided and attested by Supabase and Cloudflare rather than implemented by Pallas.
Audit trail
Every action listed below is logged: who changed what, when, and why. The audit trail is a tamper-evident audit log (SHA-256): any modification, deletion, or reordering of history is detected, and any lawful erasure is recorded as a redaction entry with its reason. Each entry is timestamped and attributed to a verified actor identity derived server-side at write time (not client-supplied). Bulk export of the audit log is available on Growth and above; reading it is not gated.
- Finding status changes with user, timestamp, and previous value
- Assignment changes and role transitions
- Exception creation, approval, and review
- Scan initiation and completion
- Report generation and export events
- User and organization management actions