Document Version: 1.0
Last Updated: 2025-10-03
Owners: Privacy Office & Identity Engineering
This policy formalises the workflows that fulfil GDPR/CCPA data-subject rights across the Auth service.
Supported Rights#
- Access (DSAR) – export profile, consent history, sessions, and personalization artifacts in JSON or CSV.
- Deletion (Right to be forgotten) – schedule, cancel, and execute account erasure with audit tracking.
- Portability – exports provide machine-readable formats suitable for portability requests.
- Rectification/Preference Updates – handled via profile & consent endpoints
(see
docs/security/PERSONALIZATION_PRIVACY.md).
Export Workflow#
POST /v1/users/:id/data-exporttriggers immediate export (JSON default, CSV optional) with category filters.- Audit entries capture requester, categories, and format.
GET /v1/users/:id/data-export-historyexposes immutable export trail.
Export payload guarantees:
- Pseudonymised identifiers (
email_hash). - Consent history (type, version, granted).
- Session metadata without bearer tokens.
Deletion Workflow#
- User submits
POST /v1/users/:id/data-deletionwithconfirmation_token(I_CONFIRM_DELETION). - Requests default to a 30-day grace period unless
immediate: trueis supplied. GET /v1/users/:id/data-deletion-historyserves an auditable log.- Deletions can be
cancelledprior to execution. POST /v1/users/:id/data-deletion/:deletionId/executeperforms erasure: profile, sessions, refresh tokens, consents, personalization vectors, and budgets.
Data Mapping & Discovery#
GET /v1/users/:id/data-mapenumerates data categories, locations, retention, legal bases, and processing purposes.- Optional
include_processing=truelists current processing activities.
Compliance Endpoints#
GET /v1/privacy/compliance-statussummarises GDPR/CCPA status, supported rights, and next audit windows.GET /v1/privacy/retention-policiesreturns category-specific retention periods, deletion methods, and legal bases.
Audit & Monitoring#
All DSR operations append to the auth audit log (user.data_export.*,
user.data_deletion.*). Metrics feed the privacy reporting dashboard and can be
consumed programmatically from /metrics.
References#
- Implementation:
services/auth/src/dsr.ts - Automated coverage:
tests/auth.dsr-dsar.spec.ts - Personalization privacy controls:
docs/security/PERSONALIZATION_PRIVACY.md