Trust and security

Your work, sealed.

Every computer runs sealed off on its own. What it keeps is encrypted with your key, on hardware we can’t read. And your data is never used to train AI.

Report a vulnerability security@19pine.ai

We never train AI on your data. Pine and its AI providers don’t use what your product or your users send Pine Computer to train models. Our own model learns only from synthetic data.
Your key, on hardware we can’t read. Each computer’s saved state is encrypted with your own key, protected by hardware (TPM) in the cloud.
Every computer sealed off. Each one runs isolated in its own container under gVisor, never reused, and cut off from other computers.
Your users stay in control. One driver at a time. A person can take over, do what only they should, and hand back.

How we protect your work

The controls in place on every computer, today.

Isolation

Each computer runs in its own container under gVisor, a kernel that stands between it and the host.
Containers are single-use: one is never reused for another computer.
Network policy blocks other computers, private networks and the cloud’s metadata service.
Each session on a computer works in its own workspace.

Encryption

Saved state is encrypted with AES-256-GCM, with a fresh key for every save.
Keys are protected by hardware (TPM) and wrapped by managed keys that rotate every 90 days.
A save opens only with your private key. We can’t read it.
Every connection is encrypted with TLS, and our services talk over mutual TLS.

Secrets and sign-ins

Secrets reach a run as a locked file, never in the model’s prompt.
They’re scrubbed from events, results and logs, and never saved.
Blind sessions let a person type a password or a code the AI can’t see.
What a skill learns at a sign-in or a payment never runs by itself.

Access

API keys are shown once and stored only as a keyed hash (HMAC-SHA256).
Tokens are short-lived: 15 minutes for your backend, 2 minutes for a browser’s live view.
Pine staff can’t see your computers. A diagnostic you start through the SDK or API runs inside your computer.
Every change to keys, members, roles and access is audited.

Your data

Ephemeral computers save nothing at all.
Tabs, working files, history and secrets are never part of saved state.
Deleting a computer is final: its saved state is purged within 24 hours.
Your data stays in the United States, encrypted at rest and in transit.

People in control

One driver at a time: the AI, your code or a person.
Only your backend can hand the controls to a person.
Taking over stops the AI until the person hands back.
A browser’s live view can watch, and can’t drive until your backend says so.

Compliance

SOC 2: Our SOC 2 Type II audit is in progress.
Privacy: A data processing agreement and our subprocessors are available on request, for GDPR and CCPA.
Incidents: We investigate and contain security incidents, and tell the customers they affect.
Reviews: For a security review or a questionnaire, write to security@19pine.ai.

Questions

What a security review asks about your data.

Do you use our data to train AI models?

No. Pine and its AI providers don’t use what your product or your users send Pine Computer to train models. The models process the work to do the job, and nothing is kept for training. Our own model is trained only on synthetic data.

Can Pine read what our computers keep?

No. Saved state, the sign-ins, cookies and skills a computer keeps, is encrypted with AES-256-GCM under your own key, protected by hardware (TPM) in the cloud. A save opens only with your private key.

Where is our data stored?

In the United States, encrypted at rest and in transit. What a computer keeps opens only with your private key. The country you choose for a computer sets where it browses from, not where your data is stored.

How are passwords and other secrets handled?

Pass them as secrets: they reach the run as a locked file, never in the model’s prompt, are scrubbed from events and logs, and are never saved. For what only a person should type, a blind session hides the screen from the AI.

Who can take control of a computer’s screen?

One driver at a time: the AI, your code, or a person your product lets in. Only your backend can hand the controls to a person, and a browser’s live view can only watch until it does. Taking over stops the AI until the person hands back.

What is kept when a computer stops, and for how long?

A computer keeps its saved state, encrypted with your key, until you delete it. Tabs, working files, history and secrets are never saved. Ephemeral computers keep nothing.

What happens when we delete a computer?

It’s final. Its saved state is purged within 24 hours, and its id is never used again.

Can Pine staff see our data?

No. Pine staff can’t see your computers or what they keep. If one needs troubleshooting, you start a diagnostic through the SDK or API: it runs inside your computer, and we help you debug from what it reports, without access to the computer.

How are API keys protected?

An API key is shown once, stored only as a keyed hash, and can be revoked at any time. The tokens your backend uses last at most 15 minutes, and a browser’s live view gets one that lasts 2.

Do you have SOC 2?

Our SOC 2 Type II audit is in progress. For its status, a data processing agreement, our subprocessors or a security questionnaire, write to security@19pine.ai.

How do we report a vulnerability?

Write to security@19pine.ai with what you found and how to reproduce it.

Report a vulnerability