GDPR Article 32
Annex 1 - Technical and Organisational Measures
Part of the Data Processing Agreement, version 1.1
The security measures we apply to the data we process for you. This page is Annex 1 to our Data Processing Agreement and is included in the counter-signed PDF you can generate from Settings → DPA in the console.
This Annex describes the technical and organisational measures Orkestr implements under Article 32 GDPR. It serves as Annex II to the Standard Contractual Clauses where those apply.
1. Hosting and physical security
Customer Personal Data is hosted in data centres in the EEA (currently Germany, Finland, and France) operated by Orkestr's hosting Sub-processors, which maintain ISO/IEC 27001 certified security programmes covering physical access control, power, cooling, and fire protection. Orkestr personnel have no physical access to these facilities.
2. Access control to systems
- Administrative access to servers uses SSH public-key authentication only; password login is disabled.
- Host firewalls deny inbound traffic by default and open only the ports a server's role requires. Servers communicate with each other over encrypted tunnels or private networks.
- Infrastructure credentials are stored encrypted and decrypted only when needed for deployment.
- Multi-factor authentication is enforced on all administrative accounts with upstream providers (cloud and hosting, domain registrar, payment processor, email provider, source-code hosting, object storage).
- Administrative access is limited to personnel who need it to operate the Service.
3. Access control to data
- Customer account passwords are hashed with bcrypt. API tokens are shown once, stored only as a hash, and can be limited in scope; sandbox tokens can be limited to sandbox operations.
- Settings that change how long data is retained can only be changed from a signed-in console session, not with an API token.
- Orkestr does not routinely access the contents of Customer applications, databases, or sandboxes, and has no console or administrative interface for viewing the contents of a sandbox. Server-level access is restricted as described in Section 2. Access to Customer Personal Data happens only where necessary for security investigation, to maintain or restore the Service, or at Customer's request.
4. Isolation and separation
- Application and function containers run without Linux capabilities, with privilege escalation disabled, a process limit, and CPU and memory caps, on a network separated from the platform's internal services.
- Builds run in a dedicated, short-lived virtual machine per build, without access to the image registry or platform services (a hardened, resource-limited build container is used for some repositories). Cloned source code is deleted at the end of every build.
- Each sandbox, and each function served from a sandbox host, runs in its own virtual machine with its own kernel. Sandboxes have no network access by default; restricted networking allows outbound connections only to an allowlist; sandboxes cannot reach the host's administrative services.
- Customer data is logically separated by account throughout the control plane.
5. Encryption
- In transit. TLS 1.2 or higher for the console, API, and Customer application URLs. Traffic between Orkestr servers is carried over encrypted tunnels or within the hosting providers' private networks.
- Secrets at rest. Environment variables, OAuth tokens, add-on credentials, and sandbox volume and snapshot keys are encrypted in the platform database with authenticated encryption (AES-128-CBC with HMAC-SHA256). The key is held only by the control plane and is not shared with Sub-processors.
- Sandbox volumes. Volumes created since 31 July 2026 are encrypted inside the sandbox with AES-256 (XTS) and a key unique to the volume, so the host disk and object-storage checkpoints hold only ciphertext.
- Paused sandboxes. In no-content-retention mode, snapshots are encrypted with AES-256 (XTS) and a key unique to each pause (Annex 2, Part B). Otherwise, snapshots are stored unencrypted on the host's local disk until they are deleted (Annex 2, Part A).
- Backups. The platform database is backed up daily as a compressed dump, transferred over TLS to object storage in the EEA, and kept for 30 days. Secrets inside it are encrypted as described above; the dump files are not otherwise encrypted.
- Server disks are not encrypted at the disk level beyond the measures above.
6. Logging and monitoring
- Account and administrative actions are recorded in an audit log.
- Sandbox activity records are kept as described in Annex 2.
- Host system logs, including network connection metadata, are kept for no longer than 90 days.
- Monitoring and alerting cover host availability, disk and memory capacity, resource and network anomalies, and container restart loops. Abuse detection relies on this metadata. The code of deployed applications and functions may be checked automatically against the Acceptable Use Policy on first deploy; the contents of sandboxes are not scanned.
7. Availability and resilience
- Daily backups of the platform database (kept 30 days) and of managed add-ons (retention per plan); sandbox volume checkpoints in EU object storage.
- Health checks and automatic restarts; sandbox hosts in three EU regions; documented restore procedures.
8. Deletion
Data is deleted as described in Section 11 and Annex 2. Deleting a project, add-on, volume, template, or account through the dashboard or API starts deletion immediately.
9. Vulnerability and change management
- Base images are built and verified in CI and use pinned versions; application dependencies are pinned.
- Host operating systems are patched on a regular cadence.
- Changes are tested in CI and in a separate development environment before reaching production.
- Security issues can be reported as described at orkestr.eu/security.
10. Organisational measures
- Personnel with access to Customer Personal Data are bound by written confidentiality obligations, work on a need-to-know basis, and are trained on data protection.
- A documented incident-response process is in place; Personal Data Breaches are notified within 72 hours (Section 13).
- Sub-processors are engaged only under written data-protection terms (Section 8).
- These measures are reviewed at least once a year and when the Service changes materially.