Security posture

    Zero-trust from the first line of code.

    Built from the ground up with a zero-trust security model. Your data is protected at every layer, and the strongest layer is that the confidential value never reaches the AI at all.

    Data residency, answered differently

    We don't keep confidential data in your country. We make sure there isn't any confidential data to keep.

    Every other “compliant AI” answers the residency question with a location, a region you select and a policy you trust. Untraceable answers it upstream: the real value is cloaked on your computer before any model sees it, so the thing residency laws exist to protect never enters the pipeline. In the meantime, we do store the sensitive-value stripped audits inside your selected residence, and per-project, so you can serve customers in multiple countries and respect local laws.

    Step 1

    The architecture is the compliance.

    Confidentiality law, HIPAA, PIPEDA, Quebec Law 25, the disclosure clauses in an NDA, is built around a moment of disclosure: a confidential value leaving your control and reaching someone else. Untraceable removes that moment. The AI never receives the value, so the obligations that hinge on disclosure don't even attach to the AI step in the first place. The safest way to comply with a rule about sharing data is to never share the data.

    We don't stop there. We still run the assessments, still honor residency, still keep an audit trail of every cloak and every submission, not because the law forces us to at that step, but because regulated clients deserve to see the belt and the braces. Doing the work you're not strictly required to do is the whole posture.

    Zero-trust architecture

    Every route authenticated via JWT. Least privilege on Key Vault, database, and Graph. No exceptions.

    No documents to AI

    AI models receive only cloaked data, never your files, never your raw text. Documents stay in your vault.

    Four gates before transmission

    A cloak-coverage test, a sentinel that catches stray numerical and alphanumeric values, a breach test in which a separate model tries to reconstruct the real values, and a compulsory human certification. Recover even one value and the submission is rejected, zero tolerance, not a threshold.

    Never used for training

    Contractual guarantee: your inputs are excluded from AI model training. Period.

    Guaranteed deletion

    No memory retention. Session data is cleared immediately after processing. Nothing persists.

    Regional data residencyEU: coming soon

    Choose your server location: US East Coast or Canada, which is enforced, not just selected. West Europe (Netherlands) is planned and not yet available.

    Regulatory alignedSOC 2 Type I: late 2026

    Privacy-by-design tools aligned with HIPAA, PIPEDA and GDPR principles. This is an alignment claim, not a certification: no third-party attestation is held today.

    Regional Security & Compliance

    Where cloaks, audit records and compute do live, they stay put. Each region has its own isolated compute and storage. AI inference is the exception and we say so plainly: no model we offer is deployed in Canada, so inference runs in the US or on global deployments, on cloaked text, disclosed up front, never a silent cross-region switch.

    🇨🇦

    Canada

    Compliance
    • Quebec Law 25 (privacy)
    • PIPEDA-aligned architecture
    Infrastructure
    • Compute & storage in Toronto
    • AI inference: no model runs in Canada; Claude and GPT run in the US or on global deployments, on cloaked text (disclosed)
    • Backup in Quebec City
    🇺🇸

    United States

    Compliance
    • HIPAA-aligned architecture
    • SOC 2 Type INot held: initiating late 2026
    • SOC 2 Type IINot held: planned H1 2027
    Infrastructure
    • Storage and compute in East US 2 (Virginia)
    • AI inference: GPT-5.4 in the US data zone; Claude and GPT-5.6 on Azure global deployments: cloaked text only
    🇪🇺

    EuropeComing soon

    Compliance
    • GDPR enabler: privacy-by-design architecture
    Infrastructure
    • Planned: all storage, compute and AI inference in the Netherlands, not yet live

    Trust center

    The documentation a security review asks for.

    Subprocessors, residency, retention, encryption, key custody and certification status stated plainly. Where a row is not yet answerable it says so rather than inferring an answer.

    Subprocessors

    Third parties that receive data in the course of delivering the service. AI providers receive cloaked text only, never a confidential value.*

    AI model providers
    Anthropic, OpenAI and Google. Flagship tier: GPT-6 Astra. Premium tier: Claude Opus 5.5, Claude Opus 5.0, Claude Sonnet 4.6, Claude Haiku 4.5, GPT-6 Sol, GPT-5.6 Sol, GPT-5.6 Terra, GPT-5.6 Luna, GPT-5.4, GPT-5.4 mini. Standard tier: Claude Sonnet 4.6, Claude Haiku 4.5, GPT-5.6 Luna, GPT-5.4 mini.
    What they receive
    Cloaked text only.* Real values are replaced on the customer's own device before any call is made.
    Training on inputs
    Contractually excluded across all model providers.
    Cloud infrastructure
    Microsoft Azure only: compute, storage, gateway and key management. Everything else in the workflow runs client-side in the customer's own Microsoft 365 tenant. There are no separate analytics, email or support subprocessors.
    Customer document storage
    The customer's own Microsoft 365 tenant. Documents are not copied into Untraceable's infrastructure.

    Residency by region

    Where cloaks, audit records and compute live. AI inference runs in-region where the provider offers an in-region endpoint; where it does not, the model runs in the US or on a global deployment, on cloaked text,* disclosed up front, never a silent cross-region switch.

    Canada
    Compute and storage in Toronto; backup in Quebec City. No AI inference runs in Canada, Claude and GPT run in the US or on global deployments, on cloaked text (disclosed).
    United States
    Storage and compute in East US 2 (Virginia). AI inference: GPT-5.4 in the US data zone; Claude and GPT-5.6 on Azure global deployments, cloaked text only.
    EuropeComing soon
    Planned: all storage, compute and AI inference in the Netherlands. Not yet available to select.
    Cross-region fallback
    None. The residency check is fail-closed: if a region cannot be honored, the request stops rather than rerouting.

    Data retention

    Never retained
    Confidential values, source documents and per-document keys. None of these reach Untraceable's infrastructure at any point.*
    Retained: cloak audit trail
    Cloak labels, run identifiers, model and timestamp for each submission. No real value appears in the record. Retained for 6 years per regulated-industry standards, or for a customer-defined period.
    Retained: conversational tools
    No prompt or response text is kept on our servers for VaultChat or VaultDelphi: only who ran a session, when, which model answered and which cloak decisions were made. The full cloaked transcript is saved to your own SharePoint, so a run can be reopened and audited there.
    Session data
    Cleared immediately after processing; no memory retention across sessions.
    Deletion on request
    On written request. Cloak-level records held by Untraceable are deleted within 48 hours and deletion is confirmed; documents and keys live in the customer's own tenant and are theirs to delete.

    Encryption & key custody

    In transit
    TLS 1.2 minimum across the website and both API gateways (Canada and United States); TLS 1.0 and 1.1 handshakes are refused. Connections negotiate TLS 1.3 with AES-256-GCM by default. Legacy TLS 1.2 suites (static-RSA key exchange, and CBC with SHA-1) remain enabled on the platform for backward compatibility and are not disabled at our tier; in practice no supported client selects them, since Microsoft 365 sign-in already requires modern suites. Verified by handshake test 2026-08-23.
    HTTPS and HSTS
    Web properties are served over HTTPS only and send Strict-Transport-Security with a two-year max-age, includeSubDomains and preload. The API gateways do not send HSTS; they are not browser-navigated origins.
    At rest
    AES-256 with Microsoft platform-managed keys, on both the database and blob storage. Customer-managed keys for the platform store are not offered today. Note this is separate from cloak keys, which are always per-document and held in the customer's own tenant. Verified 2026-08-24.
    Key custody
    Cloak keys are per-document and held in the customer's own Microsoft 365 tenant. Untraceable never holds a key and cannot decloak a document.
    Platform secrets
    Azure Key Vault under RBAC, least privilege on database, Key Vault and Graph.

    Controls

    Breach-test gate
    Before transmission, a separate model is given the cloaked text and told to reconstruct the real values. If it recovers even one, the submission is rejected. Zero tolerance, not a threshold.
    Cloak-coverage test
    Confirms the model receives exactly what the user reviewed; nothing added, nothing uncloaked.
    Closing sentinel
    A final screening pass that catches stray numerical and alphanumeric values the user may have missed.
    Human certification
    Compulsory. The automated gates cannot certify a run on their own: a person reviews and certifies before the submission is released.
    Authentication
    Every route authenticated; the health check only is open. Tenant isolation is enforced in the database at the row level.
    Audit trail
    Every cloak and every AI submission recorded, exportable for a given deliverable, referencing cloak labels and run IDs only.

    Certifications & attestations

    No third-party attestation is held today. The rows below state status, not aspiration.

    SOC 2 Type IInitiating late 2026
    Not held. To be initiated in late 2026.
    SOC 2 Type IIPlanned H1 2027
    Not held. Planned for H1 2027.
    ISO 42001Planned H1 2027
    Not held. Planned for H1 2027.
    HIPAA
    Architecture aligned to HIPAA principles.
    PIPEDA / Quebec Law 25
    Architecture aligned; a Privacy Impact Assessment is completed voluntarily.
    GDPREU region coming soon
    Privacy-by-design architecture. EU residency not yet available.
    Microsoft AI Cloud Partner Program
    Member.
    Penetration testingPlanned Q4 2026 / Q1 2027
    No third-party penetration test has been completed yet. Testing is planned for Q4 2026 and Q1 2027.

    * One exception, and only by the operator's explicit choice. When assigning Advanced (SSA) dimension flags, an operator may elect to have a model propose them instead of assigning each one by hand. That request sends the paragraph text, including the clinical values, to an Azure OpenAI deployment Untraceable operates, so for that request those values do reach our infrastructure and the model does see them. Identifier classes are replaced with labels first: names, patient and investigator identifiers, dates, locations, organisations and email addresses, including ones the operator did not flag. The values are used to produce the flags and are not stored: the audit record replaces every value with a hashed label. The feature is off by default, requires a per-run confirmation showing exactly what will be sent, and every use is recorded in the Untraceable Protocol, value by value. We offer it as an accelerator and recommend assigning the flags manually, or staying with Rapid (SLC) cloaking, wherever the effort allows.

    Need something not listed here? Ask us directly, or read the Untraceable Protocol.

    Where each AI model runs

    Every model receives cloaked text only, never a real value. Storage and compute follow your project's region; AI inference does not.

    ModelProviderBandServed viaUS projectsCanadian projects
    Claude Opus 5.5Anthropic
    Frontier
    All plans
    Azure AI Foundry, East US 2 · DataZoneStandard (US data zone)US East 2: in-region (US data zone)Served from the US, not in Canada
    Claude Opus 5.0Anthropic
    Frontier
    All plans
    Azure AI Foundry, East US 2 · GlobalStandardUS East 2 / global deploymentServed from the US, not in Canada
    Claude Sonnet 4.6Anthropic
    Near-Frontier
    All plans
    Azure AI Foundry, East US 2 · GlobalStandardUS East 2 / global deploymentServed from the US, not in Canada
    Claude Haiku 4.5Anthropic
    Near-Frontier
    All plans
    Azure AI Foundry, East US 2 · GlobalStandardUS East 2 / global deploymentServed from the US, not in Canada
    GPT-6 SolOpenAI
    Frontier
    All plans
    Azure AI Foundry, East US 2 · DataZoneStandard (US data zone, Responses API)US East 2: in-region (US data zone)Served from the US, not in Canada
    GPT-6 AstraOpenAI
    Flagship Frontier
    Lite+, Advanced, Enterprise
    Azure AI Foundry, East US 2 · GlobalStandard (Responses API)US East 2 / global deploymentServed from the US, not in Canada
    GPT-5.6 SolOpenAI
    Frontier
    All plans
    Azure AI Foundry, East US 2 · GlobalStandard (Responses API)US East 2 / global deploymentServed from the US, not in Canada
    GPT-5.6 TerraOpenAI
    Near-Frontier
    All plans
    Azure AI Foundry, East US 2 · GlobalStandard (Responses API)US East 2 / global deploymentServed from the US, not in Canada
    GPT-5.6 LunaOpenAI
    Near-Frontier
    All plans
    Azure AI Foundry, East US 2 · GlobalStandard (Responses API)US East 2 / global deploymentServed from the US, not in Canada
    GPT-5.4OpenAI
    Frontier
    All plans
    Azure AI Foundry, East US 2 · DataZoneStandard (US data zone)US East 2: in-region (US data zone)Served from the US, not in Canada
    GPT-5.4 miniOpenAI
    Near-Frontier
    All plans
    Azure AI Foundry, East US 2 · DataZoneStandard (US data zone)US East 2: in-region (US data zone)Served from the US, not in Canada

    As of 2026-09-24. Flagship Frontier models are included with the Lite+, Advanced, Enterprise plans; every other model is available on every plan. No model in this list runs in Canada; Canadian projects are served from the US or a global deployment, on cloaked text.