v2026.04
Read release notes
exAI Agentic OSexAI
PRIV · 26
Legal · Privacy PolicyPlain-English, audit-friendlyFor end-users, DPOs, procurement.
Effective 2026-04-01 · in force
exAI Agentic OS · Privacy

What we collect, why we use it.

This is the operator memory for our data-handling. It is the contract we hold ourselves to — written so a developer, a procurement officer, and a regulator can all read it without a translation layer. Workspace data is yours; we process it on your instruction and we do not train on it. Prompts and completions default to 0-day retention. Audit logs are hash-chained and retained for seven years. Everything below is an expansion of those four sentences.

Effective · 2026-04-01supersedes 2025-10-15changelog at bottom
01 ·

Who we are

exAI, Inc. is a Delaware C-corporation registered at 251 Little Falls Drive, Wilmington, DE 19808, United States. Our operating offices are in Athens (Marousi, 15125), Berlin (Mitte, 10117), and San Francisco (Mission, 94110). When this policy says "we", "us", or "exAI", it means exAI, Inc. and its wholly-owned operating subsidiaries — exAI GmbH (Germany) and exAI Hellas IKE (Greece). The legal entity that controls your data depends on where your account was created; the section below lists the contact points for each.

For all privacy correspondence, write to privacy@exai.cloud. For postal mail, address the Data Protection Officer at our Athens office (Agiou Konstantinou 40, 15124 Marousi, Greece). We answer inside ten business days. For an EEA representative under GDPR Art. 27 and a UK representative under UK-GDPR, see § 11.

Legal entity
exAI, Inc.
Jurisdiction
Delaware, USA
EU controller
exAI GmbH (Berlin)
DPO
Dr. M. Lefebvre · dpo@exai.cloud
02 ·

What we collect

We organize what we hold about you into three categories. The boundaries are real: each category is governed by a different legal basis, retained for a different period, and accessible to a different set of internal roles. The categories are listed below, with the specific elements inside each.

Account datacategory
Identity & billing

What is needed to give you an account, bill it, and support it.

  • Name, work email, company
  • Hashed password (Argon2id)
  • IdP claims (SAML / OIDC sub, groups)
  • Billing address, last-4 PAN, VAT ID
  • Support tickets and their attachments
Workspace datacategory
Code, prompts, completions

Whatever you put into a workspace. Yours under the contract; we are a processor.

  • Source code, files, secrets you mount
  • Prompts, tool inputs, model completions
  • Diffs, branches, commit metadata
  • Workspace logs and stdout / stderr
  • Files generated by Builder and Composer
Telemetry datacategory
Latency, errors, usage

Aggregate operational signals from the runtime — never the contents of your code.

  • API latency p50 / p95 / p99
  • Error rates and stack frame hashes
  • Workspace boot, snapshot, idle counts
  • Feature usage at the action level
  • User-agent, IP (truncated), region
03 ·

Why we use it

Three reasons, no fourth. We do not sell personal data. We do not rent it. We do not train models on your workspace data — not on inputs, not on outputs, not on byproducts. The processing purposes that do exist break down into three columns.

Provide the service
Run the runtime
  • Authenticate sessions and authorize calls
  • Boot, snapshot, and bill workspaces
  • Route prompts to the model you selected
Improve the service
Operate it well
  • Diagnose errors using opt-in stack-frame hashes
  • Capacity-plan from aggregate workspace counts
  • Measure feature adoption at the action level
Required by law
Meet our obligations
  • Retain audit logs for SOC 2 and ISO 27001
  • Respond to lawful disclosure requests
  • Honor sanctions and export-control screening
04 ·

Legal bases

For users in the EEA, the UK, and Switzerland, processing happens under one of the five GDPR Article 6 legal bases below. CCPA, LGPD, and PIPEDA equivalents are mapped onto these in the underlying records of processing activities (RoPA), available to your DPO under NDA.

  1. a
    Performance of contract — Art. 6(1)(b)
    Processing required to deliver the workspace, the IDE, the agent runtime, the orchestrator, and the support service you signed an order form for. Without this, there is no service.
  2. b
    Legitimate interests — Art. 6(1)(f)
    Limited operational uses balanced against your rights — fraud and abuse detection, runtime telemetry, security monitoring, internal analytics. We document each balancing test on file (LIA), available to your DPO under NDA.
  3. c
    Consent — Art. 6(1)(a)
    Used only where the law requires opt-in. Examples: marketing email to free-tier users, optional research-program participation, non-essential cookies. Consent is granular, recorded with a timestamp, and withdrawable in one click.
  4. d
    Legal obligation — Art. 6(1)(c)
    Tax records, sanctions screening, retention of audit logs to meet SOC 2 and ISO 27001 control objectives, and compliance with binding regulatory orders. We narrowly scope these processes and review them annually.
  5. e
    Vital interests — Art. 6(1)(d)
    Used only in the rare case where life or physical integrity is at risk — a credible safety threat surfaced through a workspace, for example. Has never been invoked in production; documented for completeness.
05 ·

Sharing

We share personal data with three kinds of third parties: sub- processors who help us run the service, professional advisers under confidentiality, and authorities where the law compels us. We do not sell personal data, and we do not share it with advertisers — there is no advertising stack on this product.

The full, current list of sub-processors with entity name, region, purpose, and DPA links is published on the Trust Center — /trust — and updated within 30 days of any material change. The categories below summarize the live list.

Category
Purpose
Region
Cloud infrastructure
Compute, storage, KMS
EU · US · APAC
Model providers
Inference for prompts (configurable)
Per-tenant routing
Identity providers
SSO, SCIM provisioning
Customer-controlled
Observability
Aggregate telemetry, error tracing
EU · US
Payments & billing
Card capture, invoicing, tax
EU · US
Email & support
Transactional email, ticketing
EU · US
● We do not sell personal dataAll sub-processors bound by SCCs + DPALive list →
06 ·

Retention

Retention is set by category, not by mood. The defaults below are aligned to GDPR storage-limitation, HIPAA recordkeeping, and the control objectives of SOC 2 and ISO 27001. Where a category can be shortened by a tenant administrator, the "control" column says so.

  • Workspace artifacts (code, files, diffs)
    Your control · default for life of workspace
    Delete via UI or API · purged within 24h
  • Prompts and completions
    0-day default · configurable up to 30 days
    Tenant-level retention setting
  • Audit logs
    7 years · configurable upward to 10
    Immutable · WORM storage · hash-chained
  • Account data
    Life of account + 30 days
    Deletion request honored within 30 days
  • Billing records
    10 years · tax-law obligation
    Cannot be deleted before period
  • Telemetry (aggregate)
    13 months
    Rolled up to monthly aggregates after 90 days
07 ·

Your rights

The rights below are guaranteed under GDPR (EEA, UK), CCPA / CPRA (California), LGPD (Brazil), PIPEDA (Canada), and parallel regimes where applicable. They are honored regardless of where you live — we apply the strictest standard globally.

  • 01
    Access
    Get a copy of the personal data we hold about you, in machine-readable form.
  • 02
    Rectification
    Correct inaccurate or incomplete data — directly in-product or via a request.
  • 03
    Erasure
    Have your personal data deleted, subject to legal-retention floors (audit, billing).
  • 04
    Restriction
    Pause our processing while a complaint or correction is being resolved.
  • 05
    Portability
    Export your account and workspace data as JSON or tar.zst at any time.
  • 06
    Objection
    Object to processing on legitimate-interests grounds; we honor unless overridden.
  • 07
    Automated-decision opt-out
    We do not run solely-automated decisions with legal effect; you can confirm in writing.
Submit a request:privacy@exai.cloudWe respond within 30 days · no fee · no questions asked beyond identity verification
08 ·

Children

The exAI service is not directed at users under 16, and we do not knowingly collect personal data from minors. Our customer is, in all cases, a working engineering team or an enrolled enterprise — not a consumer audience. Account creation requires confirmation that the registrant is at least 16 (or 18 in jurisdictions where that is the local age of digital consent).

If you are a parent or guardian and you believe a minor has created an account or that we hold data about a minor, write to privacy@exai.cloud and we will delete the account and all associated data within ten business days. We do not market to children, do not profile them, and do not run age-gated experiments on the service.

09 ·

Cookies & similar tech

We use three categories of browser-side storage. There are no advertising trackers, no third-party retargeting, and no cross-site identifiers anywhere on this product. The cookie banner exposes per-category controls that take effect immediately.

Strictly necessarycat
Cannot be turned off

Required to keep you signed in, route traffic to the right region, and stop CSRF and session-fixation attacks.

session idcsrf tokenregion routing
Performancecat
Aggregate, opt-out

Anonymous timing for page loads, action latency, and error rates. Used to tune the runtime, never to identify you.

paint timingfetch p95error pings
Preferencescat
Your choices

Remember your theme, your language, your sidebar layout, and which model you last selected in Composer.

themelocalelast-model
Manage your choices any time:Open cookie controls● No advertising trackers, by design
10 ·

Updates

We notify you by email and in-product banner at least 30 days before any material change to this policy takes effect. "Material" means a change to who controls the data, what we collect, why we use it, who we share it with, or how long we keep it. Editorial fixes (typos, link rot, clearer wording) are listed in the changelog without notice.

The current version is shown at the top of this page. Each prior version remains accessible at /privacy?v=YYYY-MM-DD for at least 36 months after supersession.

Changelog · last 3 versions
  1. 2026-04-01
    v2026.04
    Added LGPD mapping in § 07. Cut prompts/completions retention default from 24h to 0d. Added EU-representative and UK-representative blocks in § 11.
  2. 2025-10-15
    v2025.10
    Restructured into 11 numbered sections with per-section anchor IDs. Published machine-readable sub-processor list at /trust. Documented vital-interests basis for completeness.
  3. 2025-04-01
    v2025.04
    First public version of this policy. Established 0-day prompt retention as a contractual default. SOC 2 Type II reissued with privacy as an in-scope criterion.
11 ·

Contact

For privacy questions, rights requests, or breach notifications, please reach out via the channel that matches your jurisdiction. We acknowledge inside 72 hours and respond substantively inside 30 days — usually inside ten business days.

Privacy team
exAI, Inc. · Privacy Operations
privacy@exai.cloud
251 Little Falls Drive, Wilmington, DE 19808, USA
Data Protection Officer
Dr. M. Lefebvre
dpo@exai.cloud
Agiou Konstantinou 40, 15124 Marousi, Greece
EU representative · GDPR Art. 27
exAI GmbH
eu-rep@exai.cloud
Friedrichstraße 68, 10117 Berlin, Germany
UK representative · UK-GDPR
VeraSafe UK Ltd.
uk-rep@exai.cloud
37 Albert Embankment, London SE1 7TL, United Kingdom
You may also lodge a complaint with your supervisory authority.EEA: lead authority is the Hellenic DPA (HDPA)
Still got something to ask?

Have a privacy question?

A real human reads every message — not a bot, not a triage queue. We answer inside ten business days, usually faster.

Privacy Policy · v2026.04 · in forceEffective 2026-04-01 · supersedes 2025-10-15See also: Trust Center