MailPier Inbox Privacy Policy
Solutions Group Unlimited, LLC · Last updated November 13, 2026
This policy explains what information Solutions Group Unlimited, LLC ("SGU", "we", "us") collects when you use MailPier Inbox at app.mailpier.io and api.mailpier.io, what we use it for, and who else sees it. We do not sell personal information. SGU's website and desktop software are covered by the SGU privacy policy.
MailPier Inbox gives teams ("workspaces") email addresses that receive the test mail their own systems send. It is meant for test data only (see the Terms of Service).
Mail sent to MailPier Inbox addresses
Mail sent to a workspace's addresses is received by MailPier, SGU's own mail receiver, on SGU's servers; it is not passed to another mail provider. For each message we store:
- the whole message as it arrived: headers, sender and recipient addresses, subject, text, HTML and attachments;
- the sending server's IP address and the time it arrived;
- the results of our own checks of the message: whether it passes SPF, DKIM and DMARC, and a spam score.
When you open a message, we also pick out its links and one-time codes so you can use them in your tests, and work out its email check report (sender authentication, content, links, headers); these are worked out from the stored message and not kept separately.
To tell you when an email differs from the previous one of the same kind (template change detection), we keep a masked copy
of the most recent email of each template: its text with names, email addresses, codes, numbers, dates and links' variable
parts replaced by placeholders such as {name} and {code}, the masked link and image addresses, and
the attachment types. It holds no addresses or codes and is not deleted with the mail; we keep it for at most 500 templates
per environment (the least recently seen goes first) and delete it with the environment.
When you press Check links (or call the link check API), our servers request each web link of that message
(at most 50, without cookies or credentials, as MailPierInbox-LinkCheck/1.0), so the linked sites see a request
from our servers. Internal and private addresses are never contacted. We count the checks per account to apply the hourly
limit and keep the result for about an hour.
Messages are permanently deleted when the environment's retention period ends: at most 12 hours, or 24 hours on the Business plan, after they arrived (a message sent to several environments is kept until the longest of their retention times ends). We check for expired messages every 5 minutes, so messages are deleted within about 5 minutes after their retention period ends, and a shorter retention time also deletes older messages within minutes. Workspace members can delete messages sooner in the web inbox or through the API. Mail to an address no workspace owns, or to a workspace over its monthly quota, is refused and not stored.
For this mail we act on behalf of the workspace: the workspace decides what its systems send to its addresses. The mail domains are shared by all workspaces and run by SGU, so our staff can see this mail while running, securing and supporting the service and when looking into abuse. Only the workspace's own members and API keys can read it through MailPier Inbox; there are no public inboxes.
What we store about workspaces and their users
- Workspaces: name and short name (used in the addresses), plan, status, monthly quota, retention time, enabled mail domains, when it was created and the email address of the person who created it. For a trial or a paid plan also when the trial ends and the subscription's status, plan, paid-through date and whether it cancels at the end of the period (no card or payment details: those stay with Stripe). When its last member signed in and when it last received mail (to close unused Free accounts), and, while it is being deleted, when that was asked for, by an admin or for inactivity, and when it will be deleted.
- Own domains (Team and Business plans): the domain name, its verification code, its status, when it was added, checked and verified, what the last DNS check found, and the email address of the person who added it. We look up the domain's public DNS records to check it.
- Members: email address, role (owner or member), when you were added and when you last signed in. Workspace owners add members by their email address.
- Sign-in codes: we email you a one-time code that expires after 15 minutes. We store only a salted hash of it (never the code itself), with your email address, the number of tries and the IP address that asked for it. These records are deleted about a day after they expire.
- Sign in with Microsoft or Google (when offered): Microsoft or Google tells us your email address (and name), and that it has confirmed the address. We use only the email address, to find your workspace; we keep nothing else from them (no tokens, no profile). If you are creating an account, a cookie holds the confirmed address for up to 15 minutes until you finish.
- API keys: the key's name, its first 12 characters and a SHA-256 hash of the whole key (never the key itself), who created it and when, when it was last used and when it was revoked.
- Usage: the number of messages each workspace received per month, to apply its quota, and the times of link checks in the last hour (in the current month on the Free plan), to apply their limit.
- Mail templates: per environment, the masked copy of the latest email of each template described above, when it was first and last seen, how many were seen, and the masked differences of its last 20 emails.
- Audit log: sign-ins and changes made in a workspace (for example adding a member, saving settings, creating or revoking a key), with the email address of the person who made them. Keys appear in it only by their first characters.
This information and the mail above are kept in SQL Server databases on servers that SGU operates in its own data centers in the United States.
Email we send
We send email through Microsoft Azure Communication Services: sign-in codes, and to an account's admins the emails about the account itself (the confirmation of a deletion with its undo link, the notice when it has been deleted, and the warnings before an unused Free account is closed). We do not send marketing email from MailPier Inbox.
Cookies
MailPier Inbox uses only the cookies it needs to work:
mpp_sessionkeeps you signed in to the web inbox. It is encrypted.lb_mailpierportalkeeps your visit on the same server.- A security cookie protects forms against cross-site requests.
We do not use analytics or advertising cookies, and our pages load nothing from other websites. Remote images in a test message are blocked unless you choose to load them for that message; if you do, your browser contacts the servers named in the message, which can see your IP address and that the message was opened.
Server logs
Our servers record technical details of requests and errors, such as IP addresses and the pages and API calls requested. The mail receiver records, for each delivery attempt, the sending server's IP address, the recipient addresses, the size of the message and whether it was accepted or refused. Sign-in codes and API keys are never written to the logs. These logs are kept on our servers for up to 31 days.
Who we share information with
- Your workspace: the members of a workspace see its mail, its members' email addresses, its API key names and its audit log.
- Microsoft delivers our sign-in emails (Azure Communication Services), so it receives your email address and the email's content. If you choose "Sign in with Microsoft" or "Sign in with Google", that provider learns that you signed in to MailPier Inbox (under its own privacy terms). Microsoft Azure Traffic Manager and Cloudflare answer the DNS lookups for our domains; they see those lookups, not your mail or your use of the service.
- Stripe processes payments for paid plans through Solutions Group Unlimited's billing service. When an account admin starts a subscription, we send the account's ID and name, the chosen plan and the admin's email address to that service, which opens the Stripe checkout. When an admin switches the account to another plan, we send the account's ID and the new plan. Card details go straight to Stripe and are never seen or stored by us.
- Destinations you add for notifications (a Slack, Microsoft Teams, Discord or Google Chat channel, PagerDuty, your own webhook): when an account admin adds one, the events it chose are sent there and kept under that service's terms. A notification carries the masked subject, the sender's and "intended for" domains, sizes, counts and a link into MailPier Inbox, never a full email address, a message body, a code or a link from the mail. The webhook addresses and keys are stored encrypted by Solutions Group Unlimited's notification service and its delivery log is kept 30 days.
These providers may use the information only to provide their services. We may also disclose information if the law requires it, or to deal with abuse of the service.
How long we keep it
Mail, sign-in code records and logs are deleted as described above. Account, environment, member, API key, usage and audit records are kept while the account exists.
Deleting an account. When an account admin deletes the account (on main's Settings page), mail to it is refused at once and nobody can sign in to it; its records are kept for 7 days so that an account admin can undo the deletion. After those 7 days its mail and all of its records (environments, members, API keys, SMTP passwords, routing rules, own domains, notification destinations, templates, usage and audit records) are permanently deleted, usually within an hour; its notification destinations are deleted from our notification service as well. We keep only a record that the account existed, without personal data: its ID and short name, when the deletion was asked for and done, and whether an admin or the inactivity rule below did it. Its short name stays reserved for 90 days. Billing records (Stripe invoices and tax records) are kept by Stripe and Solutions Group Unlimited's billing service as the law requires.
Unused Free accounts. A Free account that nobody signs in to and that receives no mail for 12 months is closed and then deleted in the same way. We email its account admins 30 days and again 7 days before; any sign-in or any mail it receives keeps it open.
Deleting your login. When you delete your login (on the "Your login" page), we remove you from every environment and delete your sign-in codes and your sign-in records at once. The audit logs of the accounts you were in keep the changes you made there (with your email address) for as long as those accounts exist.
Apart from this, we keep information only where we must for legal, tax, accounting or security reasons.
Your choices
- Workspace owners can remove members, revoke API keys and delete mail at any time.
- Account admins can delete their account on main's Settings page (with 7 days to undo it). Anyone can leave an environment or an account, or delete their own login, on the "Your login" page.
- You can ask us to see, correct or delete your information. If you are not a workspace member but your information is in mail a workspace received, you can ask the company that runs that workspace, or us.
- For any other request about your information, email us at the address below.
MailPier Inbox is a business service and is not directed at children under 13.
Security
Connections to MailPier Inbox use HTTPS. Sign-in codes and API keys are stored only as hashes, one workspace cannot read another workspace's mail, and message HTML is cleaned and shown in a locked-down frame that cannot run scripts.
Changes
If we change this policy we will update the date at the top of this page.
Contact
Solutions Group Unlimited, LLC
Email: support@solutionsgroupunlimited.com