Privacy statement
Last updated: 18 November 2026
AgentInbox gives your AI agent its own email address. To do that, we store your email address, the addresses you create, and the mail your agent sends and receives. We use this data to run the service, to take care of payments through Stripe, and to keep the service safe. For the mail in an inbox we work for you: you decide what your agent does with it. We encrypt stored mail, but our service holds the keys, so it is not end-to-end encryption. Our servers are in Germany. On this website, Google Analytics runs only after you agree, if you are in Europe. This statement explains all of this in detail, and tells you how to use your rights.
1. Who we are
AgentInbox is a service of Datapad, a business established in the Netherlands. Datapad is the controller of the personal data in this statement, except for the mail in an inbox (see section 3).
- Chamber of Commerce (KvK) number: 34284576
- VAT number: NL818546839B01
- Email: hello@agentinbox.im
We have not appointed a data protection officer. For any question about your data, write to the address above.
In this statement, "we" means Datapad. "You" means the person who signs in to the dashboard and creates addresses: the owner of the agent. This statement covers the website agentinbox.im, the dashboard at app.agentinbox.im, the API and MCP server at api.agentinbox.im, and our mail servers.
2. Which data we process, and why
| Data | Why | Legal basis (GDPR) |
|---|---|---|
| Your email address. When you sign in, we store a sign-in link and a session, each as a hash, with your email address and an expiry time. | To let you sign in without a password and to send you the sign-in link. | Contract (article 6(1)(b)) |
| Your agents and addresses: the agent name you choose, the address, its domain, its status, the billing period, the dates, and a hash of the API key. For apps you connect over OAuth: the name the app gave itself, its return addresses and which address it may use. | To provide the service: to create the address, to let your agent use it with its key, and to show it to you in the dashboard. | Contract |
| Payment records: the IDs of your customer record, subscription and invoices at Stripe, their status and dates, and payment links. We give Stripe your email address and our IDs of the agent and the inbox. We do not receive or store card details. | To start and follow your subscription, and to make an address active or suspend it when a payment succeeds or fails. | Contract; legal obligation (article 6(1)(c)) for the business records we must keep |
| The mail in an inbox: messages, attachments, recipients, delivery status, webhooks and the events sent to them, and the list of addresses we no longer send to (see section 3). | To send and receive mail for your agent. | We process it for you (see section 3). For you as our customer: contract |
| Security data: IP addresses and email addresses in counters that limit how often sign-in links can be asked for, addresses can be created and apps can register. Server logs (see below). | To keep the service safe, to stop abuse and spam, and to find and fix faults. | Legitimate interest (article 6(1)(f)) |
| Mail you send us at hello@agentinbox.im: your address and what you write. | To answer you. | Contract, or legitimate interest if you are not a customer |
| Visits to agentinbox.im: our web server log (see below), and Google Analytics (see section 9). | To run the website and to see how it is used. | Log: legitimate interest. Analytics: consent (article 6(1)(a)) for visitors in Europe; legitimate interest elsewhere |
Server logs. Our servers write logs. They hold, among other things:
- requests to the website, the dashboard and the API, with the time, the IP address, the page or endpoint and the browser's description of itself;
- actions in the dashboard, such as creating or deleting an address or making a new key, with your email address;
- each delivery attempt of mail your agent sends, with the recipient's address;
- incoming mail that we refuse, for example for a virus or spam, with the sender's address and the IP address of the server that sent it.
We use them only to run the service, to deal with abuse and to find faults. We do not use your data, or the mail in your inbox, for advertising. We do not make automated decisions about you that have legal effects. The spam and virus checks are automatic, but they only decide how a message is handled.
3. Mail in an inbox
The mail your agent sends and receives can hold personal data of other people: senders, recipients, and anyone named in a message. For this mail, you decide what happens: your agent chooses what to send, to whom, and what to do with what it receives. We process this mail for you and on your instructions, as your processor under the GDPR. The data processing section of our terms sets out what we promise you about it.
This means:
- You are responsible for the mail your agent sends and receives, and for the personal data of other people in it. If you need a legal basis to process it, you need to have one.
- We use this mail only to provide the service: to receive it, check it for spam and viruses, store it, give it to your agent, and deliver what your agent sends.
- If someone whose data is in your agent's mail asks us about it, we send them to you, and we help you answer.
For each message we store: the sender, the recipients (To, Cc, and Bcc for mail your agent sends), the subject, the text and HTML body, the attachments with their names, types and sizes, the whole raw message, the Message-ID and threading headers, the times it arrived, was sent and was marked read, and for incoming mail the results of the SPF, DKIM, DMARC and spam checks. For mail your agent sends, we store each recipient's delivery status, the number of attempts and the last error. When a recipient's mail server refuses an address for good, we put that address on a list and do not send to it again.
When mail arrives, we check it for spam with Rspamd and for viruses with ClamAV. Both run on our own servers. Mail with a virus is refused. Mail the spam filter rejects is refused too. Other spam is stored and marked as spam.
4. Who can see your data
- You see your own agents, addresses and mail in the dashboard. Other customers cannot see them.
- Your agent, and anyone else who has its API key, can read and send all mail of its address. So can an app you connect over OAuth, until you revoke it.
- Our operators, the people at Datapad who run the service, can see all data of every customer in the dashboard. This includes the content of mail: messages, attachments and raw messages. They open mail only when that is needed to run the service: to help you when you ask, to deal with abuse or to fix a fault.
Webhook signing secrets are never shown in the dashboard, not even to operators. API keys are stored only as a hash, so nobody can see them after they were shown to you once.
5. Encryption and security
We encrypt the content of stored mail with AES-256-GCM before it goes into our database. The keys are not kept in the database. Encrypted are: the subject, the text and HTML bodies, the From, To and Cc addresses, attachment file names, the raw message and the attachments, the recipient and last error of each delivery (so Bcc recipients too), the addresses on the list of addresses we no longer send to, and webhook signing secrets.
Not encrypted are: your email address, agent names, inbox addresses, payment records, webhook URLs, Message-IDs and threading headers, times, the results of the spam and authentication checks, attachment types and sizes, and delivery statuses.
This is not end-to-end encryption. Our service holds the keys and decrypts the mail when your agent, you or an operator reads it. The encryption protects mail against someone who gets a copy of the database or a backup without the keys.
Other measures:
- The website, the dashboard and the API are served only over HTTPS.
- API keys, sign-in links, sessions and OAuth tokens are stored only as hashes.
- Mail between our servers and other mail servers is encrypted with TLS when the other server supports it. Not every mail server does; then mail travels without encryption, as is normal for email.
- HTML mail is shown in the dashboard in a closed frame that runs no scripts and loads nothing from the internet, so tracking pixels do not load.
6. Who receives data
- IONOS hosts our servers and our database, in Germany. It processes data for us, under a contract.
- Stripe sells the subscription and takes the payment, as the seller (merchant of record, Stripe Managed Payments). We give it your email address and our IDs of the agent and inbox; you give it your payment details at its checkout. Stripe decides itself how it uses that data, and its own privacy policy applies.
- Google receives data about your visits to agentinbox.im through Google Analytics, if it loads (see section 9). It does not run in the dashboard or the API.
- Recipients' mail servers receive the mail your agent sends, and the mail servers of the person signing in receive our sign-in mail. That is how email works.
- Your webhook URLs, which your agent chooses, receive an event for each new message, with the sender and the subject.
- Blocklists: to check incoming mail for spam, Rspamd looks up public blocklists over DNS. Those lookups contain the IP address of the server that sent the mail and domain names that appear in it, such as in links.
Our DNS is at Cloudflare. It answers lookups of our domain names. It does not carry your visits, your mail or other data. We do not sell your data. We give data to authorities only when the law requires us to.
7. Where your data is stored
Our servers and our database are at IONOS in Germany. Stored mail stays in the EU.
Some data leaves the EU:
- Google and Stripe may process data in the United States. They state that they use safeguards that the GDPR allows for this, such as the EU-US Data Privacy Framework or the European Commission's standard contractual clauses.
- Mail your agent sends goes to the recipient's mail server, wherever that is. Events go to the webhook URLs your agent chooses. That is part of what you ask the service to do.
8. How long we keep data
| Data | How long |
|---|---|
| Mail in an inbox, with its deliveries, webhooks and webhook events | While the inbox exists. The mail and the address of an inbox are deleted 7 days after its subscription ends. |
| An address that is not paid | Deleted 2 days after it was created, with its API key, its webhooks and its payment records. |
| Your email address, agents and addresses | While you have an agent with us. |
| Records of subscriptions and payments | As long as Dutch law requires us to keep business records. |
| Sign-in links | 15 minutes, or until used. |
| Sessions | 7 days after you sign in, or until you sign out. |
| Counters for rate limits, with IP or email addresses | Until the time window they count in ends (15 minutes to 24 hours). |
| OAuth | Codes 2 minutes, access tokens 1 hour, refresh tokens 90 days. A connection stays until you revoke it or the address is deleted. An app that registered but was never allowed by an owner is removed after 7 days. |
| Addresses we no longer send to | Until an operator removes them from the list. |
| Server logs | The logs have a fixed maximum size. When they are full, the oldest entries are deleted. |
Expired sign-in links, sessions, counters and OAuth tokens are removed by a job that runs every hour, so they can stay up to an hour longer than the times above.
9. Cookies and local storage
The dashboard has no analytics. It sets only the cookies it needs to work. On the website agentinbox.im, Google Analytics runs through Google Tag Manager. If your browser shows a time zone in Europe, or no time zone at all, we ask you first, and nothing from Google loads until you accept. Elsewhere, it loads at once. Google's advertising features are turned off.
| Name | Where | Purpose | Lifetime |
|---|---|---|---|
__Host-session (cookie) | app.agentinbox.im | Keeps you signed in to the dashboard. | 7 days after you sign in, or until you sign out |
__Host-oauth_return (cookie) | app.agentinbox.im | Only when you connect an app over OAuth and are not signed in yet: remembers the app's request while you sign in. | 30 minutes |
cookie-consent (local storage) | agentinbox.im | Remembers whether you accepted or declined Google Analytics. It is not a cookie and is not sent to us. | Until you clear your browser's site data |
_ga (cookie) | agentinbox.im, set by Google Analytics | Tells one visitor from another. | 2 years (Google's default) |
_ga_ followed by an ID (cookie) | agentinbox.im, set by Google Analytics | Keeps the state of a visit. | 2 years (Google's default) |
If you are in Europe, you can change your choice at any time with "Cookie settings" at the bottom of each page of the website. If you decline after you accepted, the page reloads without Google Analytics. Cookies it set before stay in your browser until they expire or you delete them.
10. Your rights
Under the GDPR you have the right to:
- see the personal data we have about you, and get a copy;
- have it corrected if it is wrong;
- have it deleted;
- have its use limited;
- get it in a format a computer can read, to take it elsewhere;
- object to processing we do for our legitimate interest;
- withdraw your consent for analytics at any time, with "Cookie settings".
To use a right, write to hello@agentinbox.im. We may ask you to show that the data is yours, for example by writing from the email address you sign in with. We answer within one month. Some rights have limits: for example, we cannot delete the business records the law requires us to keep.
Your agent can already download every message of its inbox, raw, through the API.
If you think we handle your data wrongly, please tell us first. You also have the right to complain to the Dutch Data Protection Authority, the Autoriteit Persoonsgegevens, or to the data protection authority of the EU country where you live or work.
11. Changes to this statement
When we change this statement, we put the new version on this page with a new date. If a change matters to customers, we also tell you by email before it applies.