Data Privacy
Beak implements comprehensive data privacy controls to protect sensitive information across all product pillars, supporting regulatory requirements for data residency, encryption, PII handling, and retention.
Encryption
Encryption at Rest
All data stored by the Beak platform is encrypted at rest:
| Data Store | Encryption Method |
|---|---|
| PostgreSQL | AES-256 Transparent Data Encryption (TDE) |
| Redis | AES-256 encryption for RedisJSON data |
| OpenSearch | AES-256 index-level encryption |
| S3 / Azure Blob | Server-side encryption (SSE-S3 / SSE-KMS / Azure SSE) |
| Backups | AES-256 encrypted backup files |
Encryption in Transit
All data in transit is encrypted:
- External Traffic — TLS 1.2+ for all API and web traffic
- Internal Service Communication — Mutual TLS (mTLS) between microservices
- Database Connections — SSL-encrypted database connections
- Cache Connections — TLS-encrypted Redis connections
Key Management
- Encryption keys are managed through AWS KMS or Azure Key Vault
- Key rotation occurs automatically on a configurable schedule (default: 90 days)
- Tenant-specific encryption keys for multi-tenant data isolation
Data Residency
Regional Deployment
Beak supports regional deployment to meet data residency requirements:
| Region | Availability |
|---|---|
| US East | Available |
| US West | Available |
| EU (Frankfurt) | Available |
| EU (Ireland) | Available |
| UK (London) | Available |
| Asia Pacific (Singapore) | Available |
Data Residency Controls
- All tenant data is stored within the selected region
- Cross-region data transfer is disabled by default
- Audit logs confirm data location compliance
- Configure data residency under Organization > Data Residency
PII Handling
PII Detection
Beak automatically identifies and classifies personally identifiable information:
| PII Type | Detection | Products |
|---|---|---|
| Email addresses | Automatic | All products |
| IP addresses | Automatic | All products |
| Names | Automatic | Desk, ITAM |
| Phone numbers | Configurable | Desk |
| Custom PII fields | User-defined | All products |
PII Protection
- Masking — PII is masked in logs, dashboards, and exports based on user role
- Access Controls — PII access requires explicit permissions
- Redaction — PII can be redacted from audit log exports
- AI Guardrails — AI agents are prevented from exposing PII in responses
PII in AI Operations
Special protections apply when AI agents process PII:
- LLM prompts are scanned for PII before transmission
- AI guardrails block PII from appearing in agent outputs
- Agent data access is logged and auditable
- PII masking applies to AI Observability traces
Data Retention
Default Retention Policies
| Data Type | Default Retention | Configurable Range |
|---|---|---|
| Operational data | 1 year | 6 months – 7 years |
| Audit logs | 2 years | 1 year – 10 years |
| Ticket data | 3 years | 1 year – 7 years |
| Asset records | Until deletion | N/A |
| AI agent traces | 90 days | 30 days – 1 year |
| Security scan results | 1 year | 6 months – 5 years |
| Backups | 30 days | 7 days – 90 days |
Configuring Retention
- Navigate to Organization > Data Retention
- Set retention periods per data type
- Configure automatic purge schedules
- Review data volume estimates before applying
Data Deletion
When data reaches its retention limit:
- Operational data is permanently deleted
- Audit logs are archived to cold storage (configurable)
- Deletion events are themselves logged in the audit trail
- Deleted data cannot be recovered after purge
Data Subject Requests
Beak supports data subject rights under GDPR and similar regulations:
Right to Access
Export all data associated with a user:
- Navigate to Data Privacy > Subject Requests
- Enter the user's email address
- Click Generate Access Report
- Download the report (available in JSON and PDF)
Right to Erasure
Delete all data associated with a user:
- Navigate to Data Privacy > Subject Requests
- Enter the user's email address
- Click Initiate Erasure
- Confirm the erasure (irreversible)
- An audit record of the erasure is retained for compliance
Right to Portability
Export user data in machine-readable format:
- Data is exported in JSON format
- Includes all product data associated with the user
- Available via the admin UI or REST API
Related
- Compliance Frameworks — Framework-specific privacy requirements
- Audit Logging — Audit trail for data access events
- Compliance Reporting — Privacy compliance reports