Skip to main content
This page covers email that Boom receives: customers’ replies to emails you sent from Boom, and copies of your support address’s email. For Boom’s security program in general, see our subprocessors list and privacy policy.

Where email goes

  • Region: Boom receives, processes and stores email in the AWS us-east-1 region (United States).
  • Receiving: Amazon SES in us-east-1. SES scans every email for spam and viruses and requires TLS.
  • Raw storage: SES writes the raw email to an Amazon S3 bucket, where it expires after 30 days.
  • Notification: SES tells Boom about each email with a signed message. Boom checks the signature and that it comes from Boom’s own topic, and rejects anything else.
  • Processing: Boom reads the raw email, keeps only what the sender newly wrote as the message text, and stores the message, its attachments and its HTML in your workspace. The full HTML is cleaned on every read (no scripts, forms or remote content unless a person asks to load images).
  • Sending: replies from your team and approved AI drafts go out from your verified domain, through Resend or through Amazon SES in us-east-1. Which one depends on how your domain was connected: domains whose DNS records use boom1._domainkey send through Amazon SES, those with resend._domainkey through Resend. Bounces and complaints come back to Boom as signed notifications, and Boom checks the signature before acting on them.
  • DMARC reports: when the DMARC record Boom suggests ends in rua=mailto:…, mailbox providers that support it send that Boom mailbox a daily aggregate report for your domain: counts of messages sent with your domain’s name and the IP addresses of the servers that sent them, with their SPF and DKIM results. Reports carry no message content or recipient addresses. Leave the rua= part out of your record if you’d rather not receive them through Boom.
  • Queueing: the queue between receiving and processing holds the email’s delivery details and spam verdicts, never the sender’s address or the subject.

How long it’s kept

Open and click tracking

For domains that send through Amazon SES (boom1._domainkey), once Boom has turned tracking on for your workspace, Boom tracks opens and clicks itself, on marketing email only (never on transactional email such as sign-in or order links):
  • Each link points at a tracking address on a Boom mail domain that records the click and forwards the person to the original page. The link’s destination is stored with the email it went out in, so it is erased with that email.
  • To tell a person from a mail privacy proxy or a security scanner, Boom reads the IP address and browser of the request in memory only. Boom does not write them to its database or to its application logs; rate limiting keeps only a keyed one-way code derived from the address, for one minute; it can’t be turned back into the address.
  • The copy of the email in your inbox keeps the original links: opening it there never counts as an open or a click.

Erasure

Send erasure requests to privacy@useboom.ai. Boom completes them within 30 days:
  1. Boom removes every email message from that person, the ones they wrote into other people’s threads, their attachments, and the thread index, in one step. From that moment nothing in Boom can open those files: every read goes through a record that no longer exists.
  2. The stored files themselves are put on a deletion queue. The app’s own storage key has no permission to delete files, by design (least privilege), so a Boom administrator deletes the queued files with separate credentials, every week. Boom is alerted daily while files wait, and escalates any erasure still waiting after 14 days.
  3. Raw copies in the receiving bucket expire with its 30-day rule.
A download link created before the erasure keeps working until it expires, because the file still exists until the queued deletion runs: an hour for links opened from the inbox, and up to 24 hours for links made by journey automations.

Who handles email

From our subprocessors list, these providers handle received email:

What the AI sees

Boom does not use your email to train AI models. AI drafts are written by the AI providers on our subprocessors list. AI drafts are off unless Boom turns them on for your workspace. With them on, for each email the agent sees:
  • only the text the sender newly wrote, not the quoted history below it. Thread history comes from Boom’s own record of the conversation, so nobody can edit a “quoted” message to put words in the agent’s mouth;
  • the text of PDF attachments;
  • whether the sender is verified (below);
  • whether its earlier drafts were sent, edited or discarded;
  • if your workspace has one conversation per email thread, and only when the sender is verified as the conversation’s own customer: the subject, status and last few messages (word for word, shortened) of that same customer’s other email threads, so it can tell when the customer refers to one. Those messages are only emails proven to come from the customer (verified as them, as in the table below) and the replies your workspace actually sent. Never internal notes, drafts, unsent or failed emails, emails from anyone else on the thread, or emails held back as unverified or spam.
Hidden text and invisible characters are removed before the agent reads an email. Images are not sent to the AI. The AI never sends email. It writes a draft that a person on your team approves, edits or discards. Approved replies carry a short line saying they were drafted with AI assistance, which can’t be removed. Apart from reading the same customer’s other email threads as above, the agent can’t use tools that reach other people or other conversations, and its drafts are capped per thread and per workspace each day.

Unverified senders

Anyone can put any address in an email’s From line. Boom judges each email only on the checks its own receiving server ran (SPF, DKIM, DMARC, and ARC from a short list of trusted forwarders), never on headers the sender wrote: Spam is dropped unless the sender’s domain passes DMARC; then it’s shown labelled Marked as spam and automation ignores it. Viruses are dropped. Archives, programs, HTML and SVG attachments are never stored.

Signed reply addresses

Every email Boom sends carries a private reply address for its thread. Each one includes a signature that ties it to your workspace’s thread, so:
  • a reply lands in the right conversation in the right workspace;
  • an address altered or re-signed for another workspace is ignored, and a bad signature is dropped.
The daily check on your support address is signed the same way and expires after 48 hours, so it can’t be faked or replayed. A copy rule only counts as working when that signed check comes back through it.

Who can do what

  • Only organization admins can turn on receiving, set the support address, open Gmail’s confirmation link, send a test email and email the IT instructions. Anyone who can view settings can copy the instructions.
  • Emailed IT instructions are built by Boom from your workspace’s own setup; the person sending them picks only the provider and the recipient, not the text. Replies to that email go to the person who sent it.
  • Only people with permission to reply in the inbox can approve, edit or discard an AI draft; everyone else sees it read-only.
  • Boom never gets access to your mailbox. It only receives the copies your own rule sends.

Email in Boom

Your domain and senders, replies and support address, step by step.

Email setup for your IT team

What to add and how to undo it.

Email troubleshooting

Common problems and fixes.