Privacy policy
Last updated 21 November 2026
The short version. We collect as little as we can. We never store the prompts your agents send or the answers they get back, and we never keep your AI provider keys. We do not sell data, we do not show ads, and we do not use tracking cookies. You can download or delete your data yourself at any time.
This policy applies to everyone, wherever you live. It covers agents.xpenvo.com, the Xpenvo Agents waitlist, accounts and the Xpenvo Agents proxy. Using the service is also covered by our Terms of service. Questions: [email protected].
Who we are
Xpenvo Agents is a service of Xpenvo that sets spending limits for AI agents. In this policy, “we” and “us” means Xpenvo. You can reach us at [email protected] about anything in this policy.
What we collect, and why
| What | Why we need it |
|---|---|
| Waitlist: your email, and if you choose to give them, your company, what you want to solve and how you heard about us | To tell you when you can start, and to decide which teams to invite first. |
| Account: your email address and when you signed in | To sign you in and keep your account secure. |
| Google sign-in: your email address and Google’s account number for you | We ask Google for your email only: not your name, not your picture. We use the email to know who you are. |
| GitHub sign-in: your email, name and profile picture link, as sent by GitHub | GitHub always sends your public profile with your email. We use only your email; our sign-in provider stores what GitHub sends. We ask for nothing more: no repositories, code or organisations. |
| Two-factor sign-in: a secret shared with your authenticator app | To check your app codes. It is held by our sign-in provider, never shown again after set-up. |
| Organisation: its name, members’ emails and roles, invites, budgets, agent key names | To run the organisation you created or joined. |
| Agent request records: time, agent key, budget, provider, model, token counts, cost, whether the request was allowed or blocked and why, and the run, step and end-customer ids your agent chooses to send | To enforce your budgets and rules and show you what your agents spent. Never the text of prompts or answers. Run and customer ids are your own labels; we refuse ids that look like an email address. |
| Loop and approval checks: a keyed one-way fingerprint of a request’s newest message, and of a request waiting for approval | To spot an agent stuck sending the same message again and again, and to make sure an approval is used only for the exact request a person approved. A fingerprint cannot be turned back into the text. Loop fingerprints are deleted after about an hour. |
| Approvals: the request’s model, estimated cost, who approved or denied it and their note | So a person can approve a big request before it is sent. Never the prompt. |
| Alert channels and API tokens: the Slack, Teams or webhook address you add, and a fingerprint of each API token | To send the alerts you chose and let your own tools manage budgets. Webhook signing secrets stay in your organisation’s own database, encrypted at rest by Cloudflare; API tokens are shown once and kept only as a fingerprint. |
| Audit log: who changed what in an organisation, and when | So your team can see and trust every change. |
| Security counters: a one-way fingerprint of your email address, your account id or, for our admin tools, the connecting IP address, with the time of each sign-in code sent or tried | To stop people guessing codes or flooding inboxes. Deleted automatically within 24 hours. |
| Short error logs: a request id and an error type | To find and fix problems. They never contain prompts, answers, keys or email addresses. |
What we never collect or keep
- Prompts and answers. They pass through the proxy to your AI provider (such as OpenAI, Anthropic, Google, Mistral, OpenRouter, Microsoft Azure or Amazon Bedrock) and back. We read only the token counts at the end, to work out the cost.
- Your AI provider keys. Your agent sends its own provider key with each request. We pass it on and forget it. It is never saved and never logged.
- Passwords. There are none. You sign in with an emailed code, or with Google or GitHub.
- Your agent keys in readable form. We keep only a one-way fingerprint. The key is shown to you once.
- Payment card or bank details. The service is free during the beta. When paid plans start, payments are handled by Dodo Payments on its own pages; we never see or store card or bank details.
Cookies and analytics
We use only the cookies needed to keep you signed in: a short-lived sign-in pass, a renewal pass that lasts up to 30 days, and two temporary cookies used while you sign in. Page code cannot read them and they are never used for tracking. That is why there is no cookie banner.
We count visits to our website with Cloudflare Web Analytics, which does not use cookies and does not follow you across other websites. Our fonts are loaded from Fontshare and Google Fonts, which see your browser’s address when they send the font.
Who helps us run the service
We use a small number of providers. Each one gets only what it needs for its job.
| Provider | What it does for us |
|---|---|
| Cloudflare | Hosts the website and runs the proxy. Stores organisations, budgets, agent key fingerprints, request records and audit logs. |
| Supabase | Handles sign-in and two-factor sign-in, and stores the waitlist. Its servers for our project are in the United States. |
| Resend | Sends our emails: sign-in codes, invites, budget alerts, beta access and feedback replies. |
| Google and GitHub | Only if you choose to sign in with them. |
| Dodo Payments | Only once paid plans start (not before 31 March 2027, and with at least 30 days’ notice). It sells the plan to your company as merchant of record and handles payment, tax and invoices under its own privacy policy. We share only your organisation id, the plan, and the billing email you enter on its page. |
| Slack, Microsoft Teams or your webhook | Only if your organisation adds them. Alerts contain budget and key names, amounts and reasons, never prompts or answers. |
| Your AI providers | Your agents’ requests are forwarded to your AI provider (such as OpenAI, Anthropic, Google, Mistral, OpenRouter, Microsoft Azure or Amazon Bedrock), with your own key, under your own agreement with them. We do not add anything about you. |
We do not sell or rent personal data, and we do not share it with advertisers or data brokers. We will disclose data to authorities only when the law requires it, and we will tell you unless the law forbids that.
Where your data is processed
Our providers run servers in many countries, and some of your data is processed in the United States. When data moves between countries, we rely on our providers’ data processing terms, including the Standard Contractual Clauses for data from the European Economic Area, the United Kingdom and Switzerland.
How long we keep it
| Agent request records and Flight Recorder runs | 90 days, then deleted automatically |
| Loop-check fingerprints | About 1 hour, then deleted automatically |
| Approvals | 90 days, then deleted automatically |
| Audit log entries | 1 year, then deleted automatically |
| Account and organisation data | Until you delete your account or the organisation |
| Waitlist entry | Until you ask us to remove it, or until it is no longer needed once you join |
| Expired invites | Deleted 30 days after they expire |
| Security counters | 24 hours at most, then deleted automatically |
Your rights and choices
Wherever you live, you can:
- Get a copy of your data: on your account page, choose Download my data. Organisation owners and admins can export the whole organisation.
- Delete your account: on your account page, choose Delete my account. It removes you from every organisation, deletes organisations where you were the only member, removes your email from audit logs and invites, and deletes your sign-in record.
- Correct your data, object to how we use it, or ask us to limit it: email [email protected].
- Leave the waitlist: email [email protected] and we will remove you.
- Complain to your local data protection authority, if you are not happy with our answer.
We answer requests within 30 days, and we never charge for them. We may ask you to confirm the request from your account’s email address so nobody else can get your data.
When you use Xpenvo Agents for your company
Data inside an organisation (members, budgets, keys and request records) belongs to that organisation. We process it to provide the service to the organisation, following its owner’s and admins’ instructions in the product, under our Data processing terms. If you are a member of someone else’s organisation and want something changed there, you can also ask its owner.
Security
How we protect your data is explained on our Security page. If we ever learn of a breach that affects your personal data, we will tell you and the relevant authorities without undue delay.
Children
Xpenvo Agents is a business service and is not meant for anyone under 16. We do not knowingly collect data from children.
Changes to this policy
If we change this policy, we will update the date at the top. If a change matters for how we use your data, we will email account holders before it takes effect.