privacy policy

Privacy policy

What MailTrooper stores about you and the people you email, who we share it with, and how to have it removed. It covers mailtrooper.com, the dashboard and the API.

Last updated 18 November 2026

Who this covers

MailTrooper is a transactional email service: you send email through our API or dashboard, and we deliver it and show you what happened to it.

There are two groups of people in this policy. Customers are the people who sign up and send. Recipients are the people our customers email. For the contacts and messages a customer uploads or sends, the customer decides what is sent and to whom, and MailTrooper processes that data on their behalf.

Account data we store

When you create an account and use it, we store:

  • your email address, first and last name, and a username if one is set;
  • your password as a salted argon2id hash, never the password itself (accounts that only use Google or a sign-in code have no password);
  • sign-in tokens and, if you add them, passkeys (we keep the public key only);
  • your settings: sender identities and domains you verify, reply-to address, API keys, webhooks, and your plan and credit balance;
  • if you sign in with Google, the Google account id and email address Google gives us, linked to your account.

Contacts and email content

To send email for you we store what you give us: contacts (email address, name, tags and any fields you add), segments, templates, campaigns, sequences, forms and uploaded images, and each email you send, including its sender, recipient, subject and the data you pass to a template.

We use this only to provide the service to you: building audiences, rendering and delivering messages, showing your logs and analytics, and keeping your sender reputation healthy. We do not sell it, use it for advertising, or read it except to fix a fault, deal with abuse or answer a support request you make.

What we record about recipients

When a recipient opens an email or clicks a link, our tracking records the event for the customer who sent it: the time, the link, the IP address, the browser and device, and an approximate place and network worked out from the IP address. An open also sets a small cookie in the recipient's browser that identifies the message.

Bounces, complaints and unsubscribes are recorded so the address is not emailed again. Public sign-up forms hosted by MailTrooper store the details a visitor submits for the customer who owns the form. Recipients who want their data removed should ask the customer who emailed them; they can also write to us (see Your rights).

Who we share data with

We do not sell personal data. We use these services to run MailTrooper, and each receives only what it needs:

  • Amazon Web Services: Simple Email Service sends the email (message content and addresses), and queue, notification and storage services carry delivery work, bounce and complaint notices, and files.
  • Backblaze B2: stores images and files customers upload.
  • Inkress: processes subscription and card payments. Inkress collects and holds card details; MailTrooper never sees or stores a card number. We exchange your name, email address, plan and payment status with it.
  • Google: only if you choose Sign in with Google. We receive your name, email address and Google account id, and nothing else from your Google account. We do not read your Gmail, contacts, calendar or Drive.
  • An email verification provider (Debounce), only when a customer runs address verification. It receives the address being checked. We also check whether an address has a public Gravatar picture, which sends a one-way hash of the address, not the address.
  • Unsplash: if you search stock photos in the template builder, your search words are sent to Unsplash.

Sign in with Google

Signing in with Google gives us your name, email address and Google account id, and we use them only to create your account or sign you in. We ask for no other Google permissions. Google sign-in is available for Gmail and Google Workspace addresses; other addresses use email and password or a sign-in code.

You can stop using it at any time and sign in another way, or ask us to delete your account. You can also remove MailTrooper from your Google account's third-party connections.

Cookies

We use only the cookies the site needs. We do not use advertising or analytics cookies.

  • mt_session: a signed, HttpOnly cookie that keeps you signed in, for up to 30 days or until you sign out.
  • mt_google: a signed cookie that lasts ten minutes while you sign in with Google, then is removed.
  • mt_theme: remembers light or dark mode.
  • mt_ref: set in a recipient's browser when they open a tracked email, so the opens belong to the right message (see What we record about recipients).

How long we keep data

  • Account data, contacts, templates, campaigns and email history are kept while your account is open, unless you delete them in the dashboard.
  • Campaigns and segments you delete are copied to an internal archive so they can be restored. When we delete your account we delete the archive copies too, where the law requires it.
  • Server request logs hold the method, path, status, account id and timing of each API request. They hold no request bodies, tokens or email addresses, and are deleted after 30 days.
  • Where the law requires it, we delete your account and its data within 30 days of your request.
  • We may keep the minimum we must keep, such as payment records, if the law requires it.

Security

Traffic to MailTrooper uses TLS. Passwords are hashed with argon2id, API keys and sign-in tokens are scoped and can be revoked, stored secrets are never returned by the API, and sessions are HttpOnly and signed. Each account's data is separated from other accounts at the application level, and access to production data is limited to the people who run the service.

No service is perfectly secure. If a breach affects your data, we will tell you without undue delay.

Your rights and deleting your data

You can see and edit most of your data in the dashboard. To get a copy of your data, correct it, or have your account and its data deleted, email admin@fleeksite.com from the address on the account. We may ask you to confirm you control it. We reply within 30 days.

If you are a recipient of someone else's email, you can unsubscribe using the link in the message, or ask us to remove your address from our records.

Children

MailTrooper is for businesses and is not meant for anyone under 16. We do not knowingly collect data from children.

Changes to this policy

If we change this policy in a way that matters, we will update the date at the top and, for significant changes, tell account owners by email or in the dashboard.

Contact

Questions about privacy: admin@fleeksite.com.

Questions? Email admin@fleeksite.com. See also our terms of service.