Autonomy with a hard stop.
An agent that works while you sleep must not be able to spend, send or leak without you. Arqivon's approvals fail closed, tokens never reach the model, and every side effect goes through one gate.
→ draft written nothing sent
→ send attempted without approval egress denied
→ you tapped Approve permit opened
→ sent audit event written
How it is kept on a leash.
Approvals fail closed
Sending mail, writing a calendar event, paying, deleting and logging in all wait for your tap. An approval that can't be verified is a no, not a maybe.
The draft shows exactly what will happen, such as the address it goes to, before you decide.
One gate for side effects
Sentinel is the only production door for a Google side effect. Callers open a permit after the approval check, and the egress client refuses the call when the permit is missing or the action is blocked.
Reads that policy allows open their own permit and are still recorded.
The vault
Google tokens are stored in a private vault. They are never sent to the language model, so a prompt can't leak them and a clever message can't ask for them.
Guardian
Links, messages, files and invoices can be checked before you act on them, with a verdict and a list of what couldn't be verified. About Guardian
Official channels only
Chat apps connect through each service's official API. Arqivon never uses unofficial WhatsApp Web clients or scraped inboxes.
Where your data lives, and how it leaves.
Residency, retention, export and erasure are real controls, not promises in a footer.
Residency
A workspace has a region, and the service handling a request has to be in it. A region without a store can't be chosen. Moving a workspace copies its jobs, audit and vault across and removes them from the source.
Retention
Workspaces can set how many days completed work is kept.
Export
Admins can export metadata for the workspace's members and jobs. Exports leave out secrets and message bodies.
Erasure
Delete your Arqivon data from Settings: stored jobs, pairing links and Google tokens in the vault. To remove a waitlist entry, write to us and say so. The privacy policy has the full steps.
Camera and voice
Live frames and voice are used during a session to understand the job. They are not kept as a browsable surveillance log.
No card numbers, even by phone.
Arqivon Line never asks a caller for card numbers, passwords or government IDs. If one is offered, Line interrupts politely and declines.
- Card-like numbers, 13 to 19 digits, are replaced in stored transcripts.
- Caller ID finds records. Line reads back only the last four digits.
- Phone webhooks are signature-checked when a token is set, and unknown numbers are rejected.
What a stored transcript shows.
An example of the stored text.
What we don't do.
Some of this is policy, and some is how the product is built. All of it is in the privacy policy or the terms.
We don't sell your data.
And we don't run ads against your inbox or your chats.
We don't store payment cards.
Arqivon doesn't charge your card, buy tickets, or place calls to restaurants.
We don't send keys to the model.
Vault tokens and card numbers are not sent to Google Gemini. Job text and talk turns are, to route and draft.
Found a security problem? Write to emmanuel.veranyuy@gmail.com with the details and we'll answer.
See it stop before it acts.
Open Arqivon, ask it to write an email, and watch it wait for your tap.