• ISO 27001 certified
  • End-to-end confidentiality
  • End-to-end verifiability
  • Open source, reproducible builds
  • Hosted in the EU
ISO 27001 certified
End-to-end confidentiality
End-to-end verifiability
Open source, reproducible builds
Hosted in the EU

Verifiable, not just promised.

Privatemode keeps your prompts encrypted in memory while they are processed, and your client checks that before it sends your data.

Comparison

Where your prompt is protected.

Encryption in transit and at rest is standard. The difference is what happens in memory, and whether you can check it.

What conventional AI services and Privatemode protect
Proxyless

You call our API directly, with nothing to install.

Conventional AI services

Such as OpenAI or Anthropic

In transit and at restOn the way and in storage
Privatemode AI
+ Encrypted
Privatemode AI, proxyless
+ Encrypted
Conventional AI services
+ Encrypted
In memoryWhile the AI processes your promptHow it works
Privatemode AI
+ Encrypted and isolated
Privatemode AI, proxyless
+ Encrypted and isolated
Conventional AI services
– Plaintext
Remote attestationA check of the environment before anything is sentHow it works
Privatemode AI
+ Verified by your client software
Privatemode AI, proxyless
– Verified by us, not by your client software
Conventional AI services
– None
See it happenThe concepts explained.
Privatemode AI

How a prompt travels through Privatemode with the proxy

The proxy runs on your side, on your machine or in your own infrastructure. It verifies the attestation report before it sends any data, encrypts your prompt before it leaves, and decrypts the response.

Proxy quickstart

Step by step

The same trip as a sequence diagram. Read it from top to bottom.

  • Your app
  • Proxyclient-side
  • Privatemode
  1. Proxy to Privatemode: Asks for the attestation report

  2. Privatemode to Proxy: Attestation report, signed by the hardware

  3. Proxy: Verifies the report

  4. Your app to Proxy: Prompt, over localhost

  5. Proxy: Encrypts the prompt

  6. Proxy to Privatemode: Encrypted prompt

  7. Privatemode: Processes it: memory stays encrypted

  8. Privatemode to Proxy: Encrypted response

  9. Proxy: Decrypts the response

  10. Proxy to Your app: Response, over localhost

Privatemode AI, proxyless

How a prompt travels through Privatemode, proxyless

Memory stays encrypted while your prompt is processed. You rely on us to verify the environment for you, and on our zero data retention policy.

Proxyless guide

Step by step

The same trip as a sequence diagram. Read it from top to bottom.

  • Your app
  • Privatemode
  1. Your app to Privatemode: Prompt, over HTTPS

  2. Your app: Does not check the environment itself

  3. Privatemode: Verifies the environment for you

  4. Privatemode: Processes it: memory stays encrypted

  5. Privatemode to Your app: Response, over HTTPS

Conventional AI services

How a prompt travels through a conventional AI service

Encryption in transit and at rest protects your prompt and the response on the way and in storage, but not while they are processed.

Step by step

The same trip as a sequence diagram. Read it from top to bottom.

  • Your app
  • Provider’s server
  1. Your app to Provider’s server: Prompt, encrypted in transit

  2. Provider’s server: Stores it, encrypted at rest

  3. Provider’s server: Processes it: plaintext in memory

  4. Provider’s server to Your app: Response, encrypted in transit

Trust and compliance

Certified, assessed, and trusted.

Technology

Built on proven technology.

What Privatemode is built on, and where our technology already runs.

In detail

How the protection works.

The three pillars behind the comparison at the top: what keeps your prompt encrypted, how your client software verifies the environment, and how the architecture is designed so that neither we nor others have access.

  1. Data at rest and in transit, encrypted as standard, and memory that stays encrypted during processing

    Pillar 1

    End-to-end confidential computing

    • Prompts are encrypted client-side with AES-256
    • Prompts stay protected during processing
    • Prompts are decrypted only inside the isolated environment
  2. A chip issues a signed certificate, and your laptop verifies it

    Pillar 2

    End-to-end attestation and verification

    • CPUs and GPUs issue cryptographic certificates
    • Certificates cover all relevant software
    • Entire Privatemode service can be verified
  3. A crossed-out eye, cut off from the infrastructure provider, Edgeless Systems, and the model provider

    Pillar 3

    Zero-access architecture

    • No access for the infrastructure provider, by design
    • No access for Edgeless Systems, by design
    • No access for the model providers, by design

The architecture in detail

Every component and the full attestation flow are documented. With reproducible builds and public source code, your security team can verify the design.

Read the documentation

The architecture in detail

FAQ

Technical Details

Frequently asked questions about Privatemode's security and compliance

Your prompt is encrypted on your device and decrypted only inside the shielded environment. The Privatemode proxy or SDK does this, and verifies the environment first. The keys are shared only between your client and the isolated AI worker.

Try it with your own prompts.

Start with the proxy, or book a demo with our team.