Sandboxes

Annex 2 - Sandbox Addendum

Part of the Data Processing Agreement, version 1.1

How sandbox data is processed and retained, the no-content-retention mode for stricter data-protection requirements, and our commitments for data covered by professional or official secrecy. This page is Annex 2 to our Data Processing Agreement and is included in the counter-signed PDF you can generate from Settings → DPA. To enable no-content-retention mode or request a jurisdiction-specific document, write to legal@orkestr.eu.

This Annex applies to Controller's use of sandboxes and supplements the DPA. Part A describes standard sandbox processing. Part B applies when no-content-retention mode is active on Controller's account. Part C applies when Controller notifies Orkestr that data is protected by statutory professional or official secrecy.

Part A - Standard sandbox processing

A1. Nature. Sandboxes are isolated virtual machines that run code and process files supplied by Controller or by software acting for Controller, including AI agents. Controller decides what data enters a sandbox.

A2. While running. Files, memory, and environment variables exist inside the sandbox's virtual machine. Environment variables passed to a sandbox are not written to Orkestr's databases or logs. Attached volumes are stored on the host's disk, with checkpoints in EU object storage.

A3. Activity records. Orkestr records sandbox lifecycle operations and command invocations, including command text (up to 500 characters), file paths with a preview of written content (up to 280 characters), and short samples of code output. Records are kept for the life of the account unless Controller chooses a shorter retention period in the console, and are sent to webhooks Controller configures.

A4. Paused sandboxes. Pausing saves the sandbox's memory and disk state as a snapshot on the host's local disk. The snapshot is deleted when the sandbox is resumed or terminated, or at the end of the paused retention period: 7 days on plans without a payment method, 30 days on pay-as-you-go, and no automatic expiry on Enterprise, unless Controller chooses a shorter period. Agent workspaces are kept for at most 14 days.

A5. Named snapshots are kept until Controller deletes them.

A6. Termination. Terminating a sandbox destroys its virtual machine and memory. Volumes persist until Controller deletes them.

Part B - No-content-retention mode

B1. Activation. Orkestr enables this mode for Controller's account on request. It applies to sandboxes created while it is active; each sandbox keeps the setting it was created with for its whole life.

B2. Activity records. Only the operation type, outcome, exit code, duration, data size, timestamps, and, for lifecycle events, the platform's reason (for example, a timeout) are stored and sent to webhooks. No command text, code, file paths, file contents, or output is stored. Results are still returned to Controller in the response to each API call.

B3. Paused sandboxes. Snapshots are written directly to storage encrypted with AES-256 (XTS) and a key generated for that pause; they are never written to disk unencrypted. The key is held only in the control plane, encrypted (Annex 1, Section 5), and never stored on the host. It is deleted from the platform database when the sandbox is resumed, terminated, fails, or reaches the end of its retention period; copies in database backups expire within 30 days. Without its key, a snapshot cannot be decrypted. If a host cannot write an encrypted snapshot, the pause is refused and the sandbox keeps running.

B4. Retention. Paused sandboxes are deleted after at most 30 days on every plan, including Enterprise. Controller may choose a shorter period in the console.

B5. Named snapshots are not available, because they would outlive the sandbox.

B6. Volumes created while the mode is active are always encrypted (Annex 1, Section 5).

B7. Data that is still retained. Account, billing, and usage records (size, duration, region); sandbox configuration (template, size, region, network mode, timestamps, and any metadata labels Controller attaches); names of volumes and templates; custom templates, including any filesystem captured when building them, until Controller deletes them; volume contents until the volume is deleted; webhook endpoint URLs; and network connection metadata in host logs (addresses, destination hostnames, and ports, but no request contents) for no longer than 90 days. Controller should not place confidential content in metadata labels, names, or template definitions.

B8. Outside the Service. This Part does not cover data that Controller's code sends from a sandbox to third parties.

Part C - Professional and official secrecy

C1. Scope. This Part applies where Controller, or Controller's own clients, are subject to a statutory duty of professional or official secrecy (for example in healthcare, legal, tax, social-services, or public-administration work), and Controller notifies Orkestr in writing, including by email to legal@orkestr.eu, naming the affected account or accounts.

C2. Undertakings. From that notice, for the affected accounts, Orkestr will: (a) treat the data as confidential and access it only to the extent strictly necessary to provide, maintain, or restore the Service, or as Controller instructs; (b) ensure that every person at Orkestr who may gain knowledge of the data has undertaken in writing to keep it secret and has been informed of the consequences of a breach under applicable law; (c) involve Sub-processors and their personnel in processing that data only where necessary and under written terms imposing confidentiality obligations at least equivalent to this Part; (d) not disclose the data except as required by law, in which case Section 15 applies; and (e) cooperate with Controller in meeting the documentation requirements that apply to it.

C3. Jurisdiction-specific documents. Requirements differ by Member State and profession. On request, Orkestr provides confidentiality undertakings and declarations in the form Controller's jurisdiction requires. Examples include: for Germany, an undertaking covering persons who contribute to the work of professional secrecy holders under Section 203 of the German Criminal Code (StGB); for Italy, confidentiality commitments supporting the professional secrecy protected by Article 622 of the Italian Criminal Code; and for Sweden, confirmation of the duty of confidentiality of service providers and their subcontractors under the Act on Confidentiality When Outsourcing Technical Processing or Storage of Data (SFS 2020:914). Other jurisdictions are available on request.

C4. Recommended settings. Orkestr recommends enabling no-content-retention mode (Part B) for accounts covered by this Part.

C5. Controller's responsibility. This Part does not replace Controller's own assessment of whether its use of the Service is permitted under the rules that apply to it.