Legal
Subprocessors
Last updated 25 October 2026
These are the third parties that may process data on our behalf when you use MastroSDR. This page is referenced by our Data Processing Addendum.
| Provider | Purpose | Data involved |
|---|---|---|
| Vercel | Hosts and serves the MastroSDR application | Every request to the site or the app, and the IP address it came from. Application data passes through it in transit. |
| Neon | Runs the Postgres database everything is kept in | All application data at rest: accounts, workspaces, prospects, drafts, messages and delivery events. |
| Trigger.dev | Runs the scheduled and background work: queued sends, reply and bounce checks, and list refills | Whatever the job it is running reads or writes, which includes prospects, drafts and message records. |
| Cloudflare | Turnstile, the challenge on the sign-up, sign-in and password reset forms | Your IP address and a browser signal, at the moment you submit one of those three forms. |
| Stripe | Payments and subscription management | Billing contact and payment metadata. Card numbers go directly to Stripe and never reach us. |
| Resend | Delivers the email MastroSDR sends itself: sign-in and account messages, team invitations, reply alerts, booking confirmations, renewal notices for a domain we manage, newsletter confirmations, enquiry and support messages, messages about getting set up, and a copy of your first draft sent to you when you ask for one. Your outreach leaves through your mailbox or our relay, never through it. | The recipient's address and the contents of those messages, which for a booking includes the guest's name and the time they chose, for a reply alert who replied, and for a copy of your first draft the prospect's name and email address. |
| Places, the business directory a search on the Find screen runs against | The words you search for, such as a trade and a town. None of your own prospects are sent to it. | |
| Brave Search or Serper | Finds companies that are not on a map, and looks for the right person when a site names nobody | The search terms, and a company name or domain when the search is about a specific company. |
| Firecrawl | Finds a company's own website when the free search could not, and reads its public pages | A company name and town to search for, and the address of a public company web page to read. |
| MillionVerifier or ZeroBounce | Checks that a mailbox exists before a first email goes to it | The recipient's email address. Nothing else about them, and no message text. |
| treg | Contact discovery and enrichment: finds a published business email address for a company | Company name, company domain, contact name. treg routes each lookup on to whichever data provider answers it, so those companies receive the same three fields. |
Providers you choose
For sending, and for AI once you connect a key, you decide which of these companies processes your data and you contract with them directly.
| Provider | Purpose | Data involved |
|---|---|---|
| Your AI provider | Writes drafts, suggested replies, call briefs and targeting on request, once you connect its key. The assistant's own answers do not use it; a draft the assistant writes for you does. | Your pitch text, and the prospect details, website text and reply for the piece being written |
| Your email provider | Delivers the emails you send | Recipient address, subject and body |
| An assistant you connect | Reads and writes on your behalf when you connect it, such as Claude or ChatGPT | Whatever the permissions you approved allow, which may include prospects and drafts |
| Your CRM | Records replies, bounces and unsubscribes against the contact, on a workspace where a HubSpot connection is switched on. Nothing is sent to a CRM otherwise, and the signed webhook carries the same events to any endpoint you add. | The prospect's email address, contact name and company name, and a note on the contact's timeline describing what happened |
If you connect no email provider, MastroSDR cannot send on your behalf at all, though you can still export drafts and send them yourself.
A sending domain we manage
You can send from your own mailbox, which is the default and involves none of the companies below. You can also have MastroSDR set up a sending domain for you. Mail from that domain leaves through our relay rather than your mailbox, so these three become subprocessors for as long as you use it.
| Provider | Purpose | Data involved |
|---|---|---|
| Amazon Web Services | Relays mail from a sending domain MastroSDR manages, and holds that domain's sending identity | Recipient address, subject and body of every email sent that way. This relay is ours, not yours. |
| Cloudflare | Holds the DNS for a managed sending domain, and routes replies to it back to you | The domain's records, and the sender and contents of any reply that comes back through it. |
| Name.com | Registers a domain bought through the done-for-you setup | The registrant name, address, email and phone that ICANN requires for a registration. |
The domain and its signing key are yours. We publish the records and relay the mail; you can point the domain elsewhere at any time and keep sending from it.
AI on our own account
Some AI work runs through our provider account rather than yours. The assistant always does, whatever key you connect, so what it reads to answer you goes to the provider below. The drafts included with a paid plan do while you draw on that allowance. The sample email on our home page does too, for a visitor who has not signed up.
| Provider | Purpose | Data involved |
|---|---|---|
| Groq | Runs the assistant, and writes the AI drafts included with a paid plan, on MastroSDR's own account | For the assistant: your question and whatever it reads to answer it, which can include prospects, drafts, replies and call notes, whatever key you have connected. For drafts and the other AI work (suggested replies, call briefs, targeting and search): the prospect details, pitch, website text and reply involved, only while the included allowance is in use. Questions typed into the assistant on our website by a visitor who is not signed in go to it too. |
| DeepSeek | Takes over the included drafts and the other AI work when the provider above fails | The same details the provider above would have received for that request, and only during its failure. Never the assistant. |
| DeepSeek (home page sample) | Writes the sample email on our home page for a visitor who has not signed up | The website address or sentence the visitor typed, the text of that website, and the name, website, town and homepage text of the business from our directory the sample is written to. |
Connect your own AI key and drafts, suggested replies, call briefs, targeting and search go through your account instead, from that moment on. Point MastroSDR at a self-hosted or local model and those never leave the machine you name. The assistant stays on ours either way.
Our website, not your workspace
Two analytics providers measure how our website and product are used. Neither receives the contents of a workspace: not prospects, not drafts, not replies, not your pitch. PostHog also counts which screens a signed-in customer opens, by user id and workspace id. Meta's advertising script is not loaded on any signed-in screen at all.
| Provider | Purpose | Data involved |
|---|---|---|
| Meta (Facebook) | Measures our advertising: which ad a visitor arrived from, and whether they went on to create an account | Public marketing pages only, never a signed-in screen. Page views, IP address, browser user agent and its own two cookies, and on a sign-up that did not come from an invitation, a sign-up event and a one-way hash of the email address. Automatic form scraping is switched off. Not loaded for a visitor in the EEA, UK or Switzerland until they allow it, or for any browser that sends Global Privacy Control. |
| PostHog | Product analytics: which screens are used and where people get stuck | Page views and named product events, served through our own domain and sent without their query strings, and for a signed-in customer the user id and workspace id. Session recording, heatmaps and click capture are switched off in our code, so no screen contents, prospect names or draft text are ever captured. Not loaded for a visitor in the EEA, UK or Switzerland until they allow it. |
Changes
We will update this page and notify account owners by email before adding a subprocessor that processes customer personal data.