Privacy

Who this covers

Two different sets of people appear in this product, and they are treated differently.

You, the account holder. You gave us an email address to sign in with, and everything you do in the console or through the API is attributed to your account.

Your recipients. They never signed up for anything with us. We hold their addresses because you asked us to send them mail. We do not build a profile on them, we do not sell or share their addresses, and we do not use them to train anything.

Who is responsible

Legal entity: AgentiSend (agentisend.com), reachable at hello@agentisend.com

We are the controller for your own account data — the contract with you is why we process it: the sign-in, billing and support you asked for. For the message data you send through us, we act only as a processor, on your instructions (see /dpa for what that split means), with a legitimate interest in keeping the sending infrastructure secure and working for every customer — screening abuse, stopping loops, and keeping deliverability high for everyone sending through it.

If you believe we are handling your data wrong, write to hello@agentisend.com. You may also complain to your own country's data protection authority; this is a right EU, EEA, UK and Swiss residents have regardless of where we are.

What we store

• Account data: your sign-in email, account name, API keys (hashed — the plaintext is shown once at creation and never again), team members, and the settings you choose.
• Message data: the messages you send — envelope, headers, subject, and body — plus the delivery events they produce (accepted, delivered, bounced, complained, opened or clicked if you turned tracking on).
• Audience: the contacts you store, with their properties and topic answers, and how each one agreed to hear from you when you told us that (a signup form, an import, or however you recorded it).
• Received mail: not open to customers yet, so nothing is stored under this category today. When it opens, mail sent to your own domain will be stored the same way message data is.
• Reports about your domains: the DMARC and mailbox-provider feedback reports that name mail sent using your domains.
• Support: your support requests and any files you attach to them; an attachment is deleted 30 days after you upload it.
• Sign-up source: the campaign tags, referring site and first page of your first visit, the same for your most recent visit before you signed up, the click id a Google or Meta ad adds to the address when you arrived from one, and the campaign of your most recent visit when you first bought a plan. Attached to your account, so we can tell which campaign earned the sign-up and the sale.
• Operational data: one row per authenticated API request (method, route, status, duration, key, IP, user agent), the audit log of account changes (with the IP address and browser of whoever made each change), and the webhook delivery attempts.

How long

Messages and their events are kept for the number of days on your plan, then deleted: Free keeps 7 days, Starter 30, Pro 90, Scale 180. A purge is a delete, not an archive: the rows are removed, and nothing is copied somewhere quieter first. /retention.json states the current numbers in machine-readable form, generated from the tier table the purge job reads, and /policy/retention says which other stores follow the same window and which do not.

Account data — the account itself, your team, your domains, your contacts, your templates — is kept while the account is open. /policy/retention says exactly what happens to it, and when, once you close the account.

What we do not do

• We do not sell data, and we have no advertising business to sell it to.
• We do not train models on your message content.
• We do not read message bodies except when an automated abuse check flags one, or when you ask us to look at a specific message to debug a delivery problem.
• This site sets two cookies before you sign in. The first remembers which campaign or referring link brought you here on your first visit and never changes. The second remembers the most recent one and is replaced each time you arrive from a campaign, an ad or another site. When you arrive from a Google or Meta ad, they also keep the click id that ad put in the address (gclid or fbclid). We read them when you create an account and when you buy a plan, and nowhere else. The console sets two more: your session, and a flag that tells our pages you are signed in. None of the four is sent to Google, Meta or anyone else, and no page here loads a script from an ad network.

Getting your data out, or deleted

GET /account/export returns a zip of every store on your account: messages still inside the retention window with their full body, delivery events, mail you received, your contacts with their properties, templates, topics, segments, broadcasts, automations, webhooks (without the signing secret), this account's own suppressions, domains, support requests (an operator's internal notes stay out), the audit log, and the team, with a manifest that counts every file.

DELETE /account closes the account: your keys stop working immediately. Messages and their events keep ageing out on your plan's window; closing the account does not change that. We are still building the automation that also erases the rest of a closed account (contacts, templates, webhooks, the team, the audit log) on a schedule; until it ships, write to hello@agentisend.com and say you have closed the account, and we remove the rest by hand and confirm it.

If you are a recipient rather than a customer, the unsubscribe link in the message stops that sender. To have your address removed from our systems, write to hello@agentisend.com; we tell the sender, who decides about their own records, and we delete or redact the copies we hold within 30 days and confirm.

Where the data sits

All data is stored and processed in the United States (Hillsboro, Oregon), and outbound mail leaves from US servers for every domain, whichever region you picked when you added it. The region on a domain is recorded for a planned EU sending path; it does not change where anything is stored or sent from today, and this page will say so the day it does. Subprocessors are listed on /subprocessors, with what each one sees and where.

Contact

hello@agentisend.com. Security reports: hello@agentisend.com with "Security" in the subject — see /.well-known/security.txt.