SECURITY

Built to hold other people’s keys.

Arc0 stores your users’ credentials so your agents can act for them. That makes security the product, not a page at the end of the site. Here is how it is designed, audited and hosted.

SOC 2 Type II · GDPR and DPA · Per-tenant encryption · Credentials never reach the model
01 · CREDENTIALS

How your users’ credentials are handled.

01+
Encrypted per tenant

Each of your customers gets its own encryption key. A problem in one tenant can’t expose another’s credentials.

PER-TENANT KEYS
02+
Never in the model’s context

Arc0 executes the call server-side and returns only the result. Tokens never pass through the agent or the LLM.

SERVER-SIDE EXECUTION
03+
Scoped at connect time

Users grant only the scopes your agent asks for. Policies can narrow them further per agent.

LEAST PRIVILEGE
04+
Refreshed and revocable

Tokens refresh before they expire. Users can revoke from their connected-apps page; you can revoke by API.

REVOKE ANY TIME
05+
Your OAuth apps

Use your own OAuth client for each provider, so the provider’s consent screen names you and the grant is yours.

BRING YOUR OWN CLIENT
06+
Exportable

Export your tokens whenever you want. Tokens issued to your own OAuth apps keep working after you export them, so leaving never means a mass reconnect.

NO LOCK-IN
02 · CONTROLS

What you control.

01+
Policies

Allow or deny by app and scope: read, write, destructive. Set them per customer and per agent.

READ · WRITE · DESTRUCTIVE
02+
Approvals

Route risky actions to a human before they run. The agent waits; nothing executes until someone approves.

HUMAN IN THE LOOP
03+
Fail closed, if you choose

Set a policy to block the call when a check can’t be evaluated, rather than let it through.

OPT-IN
04+
Audit log

Every call and every decision, with the policy that made it. On every plan, including free.

WHO · WHAT · WHY
05+
OpenTelemetry export

On paid plans, stream audit events into the observability and security tools you already run.

OTEL
06+
Short retention

Request and response payloads aren’t stored by default. Turn on short retention when you need to debug.

OFF BY DEFAULT
03 · DATA

What we store, and what we don’t.

Stored

Encrypted credentials for each connection; connection metadata such as the app, the scopes granted and when; and audit entries recording which agent acted for which user, in which app, with which scope, and the policy decision.

Not stored by default

The content of requests and responses: the emails your agent sends, the records it reads. You can turn on short retention for debugging, and turn it off again.

Never

Used to train models, sold, or shared with anyone other than the app your user connected. For how connections and policies fit together, see the concepts.

04 · COMPLIANCE

Compliance and hosting.

ITEMSTATUSNOTES
SOC 2 Type IICOMPLIANTReport shared on request, under NDA.
GDPRCOMPLIANTArc0 acts as your processor for your users’ data.
Data processing agreementAVAILABLESigned with any customer that asks.
EU hostingSCALE PLANData hosted and processed in the EU.
Dedicated hostingSCALE PLANA single-tenant deployment in the US or the EU.
Responsible disclosureOPENsecurity@arc0.ai
LAST UPDATED SEPTEMBER 2026
05 · FAQ

Security questions.

Q01

Can Arc0 staff read my users’ tokens?

Credentials are encrypted with per-tenant keys and decrypted only inside the services that execute calls and handle token exports. If you need more isolation, the Scale plan offers dedicated hosting, in the US or the EU.

Q02

Do you store the data my agents read or write?

Not by default. Arc0 stores credentials, connection metadata and audit entries: who acted, in which app, with which scope, and the decision. Request and response bodies are only kept if you turn on retention.

Q03

Do you train models on customer data?

No. Arc0 does not train models, on your data or anyone else’s.

Q04

Are you SOC 2 Type II compliant?

Yes. Arc0 holds a SOC 2 Type II report, which we share on request under NDA as part of your security review.

Q05

Are you GDPR compliant, and do you sign a DPA?

Yes. Arc0 processes your users’ data as your processor under GDPR, and we sign a data processing agreement with every customer that asks. On the Scale plan, data can be hosted and processed in the EU.

Q06

Can we get a dedicated deployment?

Yes. The Scale plan offers dedicated hosting, a single-tenant deployment of Arc0 in the US or the EU, alongside custom retention and volume pricing.

Q07

How do I report a vulnerability?

Email security@arc0.ai with the details and steps to reproduce. We acknowledge reports within two business days and will keep you updated while we fix it.

Get started

Bring us your security review.

New teams get a walkthrough of the architecture with an engineer, and answers to their questionnaire before they connect a single user.