Security

Security is a priority, built with our customers in mind.

Zomma operates inside the most sensitive systems a firm runs, so security is the foundation, not an afterthought. We custom-built our security posture with large enterprises and financial services firms in mind — the kind of organizations that carry the strictest data, compliance, and audit requirements. We are SOC 2 compliant, we retain none of your PII, the desktop environment stays local on your machines, and every sandbox vanishes the moment it is done.

How we protect your data

Four commitments we design around.

SOC 2

SOC 2 compliant.

Zomma is built to SOC 2 standards, with the controls, monitoring, and independent audit trail you would expect of any system trusted with regulated work. Security is a posture we are reviewed against, not a checkbox.

Data minimization

We do not retain your PII.

Personally identifiable information is never stored on our side. Zomma reads what it needs to complete a task in the moment and holds onto none of it afterward — there is no client database for us to lose.

Stays on your machine

The desktop environment is local.

The desktop environment lives on your own machines. Your files, logins, and applications stay where they already are — that environment does not touch the cloud, so sensitive data never leaves your control.

Ephemeral by design

Sandboxes leave nothing behind.

Each run executes in a sandbox that spins up fresh for the task and shuts down the instant it is finished. Nothing is retained between runs — every session starts from a clean slate and disappears completely when it ends.

The sandbox lifecycle

Spins up, does the job, leaves nothing behind.

Every run is isolated and ephemeral. There is no persistent environment accumulating your data over time — just a clean sandbox for each task that is gone the moment the task is done.

  1. 01

    Spin up clean.

    A fresh, isolated sandbox is created for the run, with nothing carried over from any previous session.

  2. 02

    Do the work.

    The agent completes the task inside that isolated environment, reading only what it needs in the moment.

  3. 03

    Shut down completely.

    When the task ends, the sandbox is torn down and everything in it is gone. No state, no leftover data, nothing retained.

The short version: your sensitive data stays on your machines, we keep none of your PII, and the environment that does the work is created fresh and destroyed completely with every run.

Have a security review? We'll walk your team through it.