# Project 996 Data Processing Agreement

Version 3.2 · Effective 1 November 2026

This Data Processing Agreement ("DPA") forms part of the agreement between the Customer and
Project 996 GmbH, Frankfurt am Main, Germany ("Processor") for the processing of personal data in
connection with the Project 996 event intelligence platform.

## 1. Roles and scope

1.1 The Customer is the Controller and Project 996 is the Processor for personal data submitted to
the platform, including contact details, OCR text, voice transcripts, meeting notes and approved
outbound email content.

1.2 Processing purposes: event lead capture, AI-assisted entity resolution, CRM synchronisation,
channel-conflict detection, outbound sequence scheduling and platform audit logging.

1.3 Duration: the term of the underlying subscription plus the deletion period described in
Section 6.

## 2. Data residency and sub-processors

2.1 All production compute, PostgreSQL volumes, Kafka brokers, object storage and AI inference run
in `eu-central-1` (Frankfurt) or `germanywestcentral`.

2.2 The Processor does not transfer Customer personal data outside the European Economic Area.

2.3 The current sub-processor register is published at `/security#sub-processors`. The Processor
will provide at least 30 days' notice before adding or replacing a sub-processor and will give the
Customer an opportunity to object.

2.4 AI inference is served by the configured transcription provider and EU-ringfenced language models. No Customer
prompt, transcript or audio is used to train, fine-tune or improve any model.

## 3. Security measures

The Processor implements and maintains:

- AES-256-GCM encryption at rest for database and object storage.
- TLS 1.3 in transit with HSTS and modern cipher suites.
- PostgreSQL FORCE ROW LEVEL SECURITY with per-tenant `tenant_isolation_*` policies.
- A per-transaction `app.current_tenant_id` setting enforced by a database connection interceptor.
- Envelope encryption for tenant CRM and outbound credentials with tenant-scoped keys.
- OIDC/SAML single sign-on, SCIM 2.0 provisioning and immediate refresh-token revocation on
  deactivation.
- Immutable, PII-scrubbed audit events for access, export, approval and erasure actions.
- Annual penetration testing and continuous dependency vulnerability scanning.

## 4. Ephemeral audio

4.1 Audio recordings are encrypted on the device before upload, stored only in EU object storage
and subject to a maximum 15-minute lifecycle rule.

4.2 Audio is deleted immediately after transcription has been verified. If transcription
fails, the object is deleted by the lifecycle rule and the capture is marked for rep review.

4.3 No audio is retained for quality monitoring, model training or analytics.

## 5. Data subject rights

5.1 The Processor provides API and workspace tooling to support access, rectification, restriction,
portability and erasure requests.

5.2 Erasure requests may be executed through
`DELETE /api/v1/privacy/erasure/{email}`. The Processor cascades deletion across PostgreSQL,
cancels pending outbound jobs and writes a PII-scrubbed immutable audit receipt.

5.3 The Processor will assist the Controller in responding to data subject requests within the
statutory timeframe, taking into account the nature of the processing.

## 6. Retention and deletion

| Data category | Default retention | Notes |
| --- | --- | --- |
| Audio blobs | 15 minutes | Deleted after transcription verification |
| Raw OCR text | 90 days | Configurable; removed after CRM sync by default |
| Voice transcript | 90 days | Retained for review audit |
| Lead and sequence records | Subscription term | Deleted within 30 days of termination |
| Audit events | 7 years | PII-scrubbed, immutable |
| Encrypted backups | 35 days | EU-resident, point-in-time recovery |

## 7. International transfers

No international transfers of Customer personal data occur. If a future feature requires a
transfer, the Processor will not enable it without the Customer's prior written instruction and an
appropriate transfer mechanism under Chapter V GDPR.

## 8. Incident notification

The Processor will notify the Customer without undue delay, and in any event within 24 hours, after
becoming aware of a personal data breach. The notification will include the nature of the breach,
affected data categories, likely consequences and remediation measures.

## 9. Audit and compliance

9.1 The Processor will make available all information necessary to demonstrate compliance with
Article 28 GDPR and will allow for audits, including inspections, by the Customer or an mandated
auditor with reasonable notice.

9.2 The Processor maintains an ISO 27001-aligned control mapping, SOC-style control narrative and
annual penetration test summary, available under NDA.

## 10. Return and deletion on termination

Upon termination, the Processor will make Customer data available for export in JSON and CSV for 30
days, then delete production data and expire encrypted backups according to the schedule in Section
6. The Processor will certify deletion in writing on request.

## 11. Contact

Privacy and security enquiries: privacy@project996.eu

Project 996 GmbH · Mainzer Landstraße 178 · 60327 Frankfurt am Main · Germany
