The short version
Helix records what agents do so runs can be supervised, audited and replayed. That record is the product, not a byproduct, and it belongs to your workspace.
- · We do not sell personal data, and we do not use your session content to train models.
- · Session content is processed by the model provider bound to your workspace. On Enterprise that can be your own inference account.
- · You can export a workspace in full at any time, and deleting a workspace deletes its sessions, artifacts and event log after a seven-day grace period.
- · Audit records are kept for the retention window you configure, because their purpose is to outlast the session.
What we collect
Three categories, kept separate because they have different lifetimes and different reasons to exist.
| Category | Examples | Why it exists |
|---|---|---|
| Account data | Name, email, authentication method, workspace membership and role | To identify who may open a session and whose approval authorises a tool call |
| Workspace content | Objectives you write, agent messages, tool call arguments and output, artifacts, memory entries | It is the work itself; the event log is what makes a run replayable |
| Operational data | Event timestamps, token counts, spend, sandbox backend, gate decisions, IP address at sign-in | To meter usage, enforce ceilings, and produce an audit trail |
We do not collect analytics on how you move through the interface beyond what is needed to keep sessions working, and we do not embed third-party advertising or tracking scripts.
Model inference
When a fiber calls a model, the messages in that turn reach the provider bound to your workspace through the model capability seam. What that means in practice depends on your configuration.
- · When using the unified Helix AI Router, inference runs through enterprise provider accounts we operate under zero-data-retention agreements that prohibit training on your content.
- · When using Bring Your Own Key (BYOK) across any of the 19 supported providers, your API keys are encrypted at rest with AES-256-GCM envelope encryption and requests go directly to your provider account.
- · When bound to local or private substrates (Ollama, LM Studio, vLLM), prompts and completions never leave your hardware perimeter.
- · Prompts and completions are written to your event log so the turn can be replayed deterministically. That copy lives in your workspace and follows your retention setting.
Sandboxes and tool output
Tool calls run inside an isolated sandbox: a local namespace process, a Docker container, a fuel-metered WASM runtime, or a Firecracker microVM (Fly.io Sprites). Anything the tool reads or writes exists inside that sandbox for the life of the session.
Container sandboxes are destroyed when the session ends. MicroVM sandboxes can be checkpointed so a world survives an idle period; those checkpoints hold the sandbox filesystem and are encrypted at rest, deleted with the world.
How long we keep things
| Data | Personal | Team | Enterprise |
|---|---|---|---|
| Session event log | 7 days | 90 days | Configurable |
| Artifacts | Until you delete them | Until you delete them | Until you delete them |
| Sandbox checkpoints | Not applicable | Deleted with the world | Deleted with the world |
| Audit records | 7 days | 90 days | Configurable, up to 7 years |
| Account data | While the account exists | While the account exists | While the account exists |
| Backups | 30 days rolling | 30 days rolling | 30 days rolling |
Deleting a workspace starts a seven-day grace period during which you can restore it. After that, its sessions, artifacts and event log are removed from primary storage, and they age out of backups within thirty days.
Subprocessors
These providers process data on our behalf. We give notice at least thirty days before adding one that touches workspace content.
| Provider | Purpose | Data touched |
|---|---|---|
| Model provider bound to your workspace | Inference | Messages in the turn |
| Cloud compute host | Application and sandbox execution | Workspace content in transit and at rest |
| Object storage | Artifact bodies and sandbox checkpoints | Workspace content at rest |
| Managed Postgres | Event log, memory entries and metadata | Workspace content at rest |
| Transactional email | Sign-in links, invitations, digests | Name and email |
| Paddle.com (Merchant of Record) | Global payments, subscriptions, VAT/GST invoicing | Billing contact, payment method, transaction history |
| Chat integration you enable | Approval prompts and summaries | Request details you route there |
Security
Data is encrypted in transit with TLS 1.3 and at rest (including AES-256-GCM envelope encryption for workspace credentials). Tool execution is isolated by the sandbox backend, and strict sandboxes enforce zero network egress. Every tool call passes the ordered 8-gate defense pipeline before it runs, and both the decision and its cryptographic W3C PROV-O lineage are recorded.
Our security practices, including the shared responsibility boundary, are set out on the security page.
Your rights
Under the EU/UK GDPR, the India Digital Personal Data Protection (DPDP) Act, and applicable privacy laws, you have the right to access, correct, export, restrict or erase your personal and workspace data. You can exercise these directly in Settings → Governance.
- · Portable Export: download a complete machine-readable JSON bundle of your workspace, sessions, artifacts, and installed domain packs directly from Settings.
- · Correction: account and workspace details are editable in Settings; write to us if anything else requires adjustment.
- · Right to Erasure: trigger a cascading workspace erasure in Settings and receive a 64-byte SHA-256 cryptographic audit receipt confirming permanent deletion, or ask us to delete your account entirely.
- · Complaints: you may lodge a complaint with your supervisory authority or Data Protection Board, and we encourage you to contact our Data Protection Officer first.
Requests reach us at privacy@helixloop.ai. We respond within thirty days.
International transfers
We operate in more than one region. Where data leaves its region of origin, the transfer relies on the European Commission’s standard contractual clauses or an equivalent mechanism. Enterprise workspaces can be pinned to a single region.
Children
Helix is not intended for anyone under sixteen, and we do not knowingly collect their data. If you believe a child has created an account, write to us and we will remove it.
Changes to this policy
We will post a notice in the app at least thirty days before a material change takes effect, and the effective date at the top of this page will change. Continuing to use Helix after that date means the revised policy applies.
Write to legal@helixloop.ai . For data requests, include the workspace name so we can locate the right records.