Legal

Privacy

What AgentiSend stores, why, for how long, and how to get it out or have it deleted.

Draft — not yet reviewed by counsel.

This document says what the product actually does, written by the people who built it. A lawyer has not read it. It is published in this state because a product with no published policy is worse than one with a policy that admits what it is, and it will be replaced by a reviewed version before the first paid contract.

last reviewed 2026-09-17

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.

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).
  • Operational data: one row per authenticated API request (method, route, status, duration, key, IP, user agent), the audit log of account changes, and the webhook delivery attempts.

How long

Messages and their events are kept for 7 days by default and then deleted. 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 constant the purge job runs on.

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.
  • We set no tracking cookies. The console sets one cookie, which is your session.

Getting your data out, or deleted

GET /account/export returns everything we hold on your account as a zip (emails still inside the retention window, suppressions, and domains). DELETE /account closes the account; the data ages out on the retention schedule.

If you are a recipient rather than a customer and you want your address removed, the fastest route is the unsubscribe link in the message; write to [email protected] if there is none, and we will remove you and tell the sender.

Where the data sits

Message data is stored with the product. You pick US or EU per sending domain when you add it; that choice is where mail leaves from, not a second copy of the history. Subprocessors are listed on /subprocessors, with what each one sees.

Contact

[email protected]. Security reports: [email protected] with "Security" in the subject — see /.well-known/security.txt.