Legal
Privacy Policy
Last updated: November 15, 2026
This Privacy Policy describes how Sponge Labs LLC ("MailStream," "we," "us") collects, uses, discloses, and protects information in connection with the MailStream websites, applications, APIs, and related services (the "Service"). By using the Service, you agree to this Policy together with our Terms of Service.
1. Scope
This Policy applies to visitors to our marketing sites, registered users, API consumers, and anyone who otherwise interacts with us in relation to the Service. If you are a customer processing personal data on behalf of others (for example your end customers or employees), our Data Processing Addendum may also apply.
2. Information we collect
- Account and billing data: name, company, email, phone, billing address, payment-related metadata (card type and last digits when processed by a payment provider).
- Service usage and diagnostics: log data, IP address, device and browser type, approximate location derived from IP, timestamps, pages viewed, API request metadata, error reports, and security signals.
- Customer content for fulfillment: mailing lists, recipient names and addresses, creative assets, job settings, and messages you submit to produce and deliver mail. This often includes personal data about recipients you choose to mail.
- Communications: content of emails, chat, or support tickets you send us.
- Referrals and integrations: information from connected tools when you authorize integrations (for example CRM or automation platforms).
- Calls to tracking numbers: see section 11.
- Scans of tracked QR codes: see section 12.
3. How we use information
We use information to:
- Provide, operate, secure, and improve the Service;
- Process payments and fulfill print and postal orders;
- Verify addresses and comply with postal and carrier requirements;
- Provide support and respond to requests;
- Send service-related notices and, where permitted, marketing (you may opt out of marketing);
- Detect, prevent, and investigate fraud, abuse, and security incidents;
- Comply with legal obligations and enforce our agreements;
- Analyze usage in aggregate or de-identified form.
4. Legal bases (EEA, UK, and similar jurisdictions)
Where GDPR or UK GDPR applies, we rely on one or more of: performance of a contract; legitimate interests (for example securing the Service, understanding product usage, and direct marketing to business contacts where appropriate); consent where required; and legal obligation. You may object to processing based on legitimate interests as described below.
5. How we share information
We share information with:
- Service providers and subprocessors who assist with hosting, printing, postage, presort, address verification, analytics, customer support, email delivery, and payment processing, bound by confidentiality and data-processing terms where applicable;
- Telephone carriers that connect calls and hold recordings until we copy them;
- Google, which checks the links our customers set for QR codes (it receives the link, never anything about the person who scans);
- Carriers and postal authorities as required to deliver mail;
- Professional advisors (lawyers, accountants) under confidentiality;
- Authorities when required by law, legal process, or to protect rights, safety, and security.
We may disclose or transfer information in connection with a merger, acquisition, financing, or sale of assets, subject to standard confidentiality arrangements.
6. International transfers
We may process information in the United States and other countries where we or our subprocessors operate. Where required, we use appropriate safeguards (for example standard contractual clauses approved by relevant regulators) for cross-border transfers.
7. Retention
We retain information for as long as needed to provide the Service, comply with law, resolve disputes, and enforce agreements. Fulfillment records may be retained for accounting, postal compliance, and dispute resolution. Marketing preferences are honored until you change them.
Call records and recordings: see section 11. QR scan records: see section 12.
8. Security
We implement administrative, technical, and organizational measures designed to protect information against unauthorized access, loss, or alteration. No method of transmission over the Internet is completely secure.
9. Your choices and rights
Depending on your location, you may have rights to access, correct, delete, restrict, or object to certain processing, or to data portability. You may also withdraw consent where processing is consent-based. To exercise rights, contact hello@mailstream.app. We will respond in line with applicable law. You may lodge a complaint with your local supervisory authority.
Marketing emails include an unsubscribe link. Service-related messages may continue where necessary.
10. Text messages (SMS)
If you check the SMS consent box on one of our forms or in the MailStream app, turn on text notifications in your account settings, tell a member of our team that we may text you, or text us first, we may send you text messages about the status of your mail campaigns and orders, account notifications, and replies to your inquiries. Consent is not a condition of purchase. Message frequency varies. Message and data rates may apply. Reply STOP to opt out at any time and HELP for help. Full program terms are in our Mobile Messaging Terms.
Mobile information, including phone numbers and SMS consent, will not be shared with or sold to third parties or affiliates for marketing or promotional purposes. All the categories above exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties. We share it only with the service providers that deliver our text messages, and only so they can deliver them.
10.1 Touch by Mailstream text messages
Touch by Mailstream, our phone app at touch.mailstream.app, also sends text messages. If you enter your mobile number there and tap "Text me a code", we may text you sign-in codes, updates about cards you send, reminders you set, and notices about adding credits. Consent is not a condition of any purchase. Message frequency varies. Message and data rates may apply. Reply STOP to stop and HELP for help. Mobile numbers and text message consent collected through Touch by Mailstream are not sold to, or shared with, third parties or affiliates for their marketing. The program terms are in section 11 of our Mobile Messaging Terms.
11. Calls to tracking numbers
11.1 What we collect when someone calls
When someone calls one of your tracking numbers, we keep the caller's phone number (unless they withhold it), the number they called, when the call came in, whether it was answered, how long the call lasted and how long the conversation lasted. We show the city of the caller's area code next to their number. We do not look up where the caller actually is. If recording is on, we keep a recording of the call. If the number is paused, we keep any voicemail the caller leaves. You and your team can add an outcome and a note to each call.
11.2 We handle it for you
We handle caller information on your behalf, to provide call tracking to you. You decide how it is used, and our Data Processing Addendum covers it. We use it only to run call tracking for your account, to support you, and to keep numbers from being misused.
11.3 Kept apart for each customer
Each customer sees only the calls to its own numbers. We never combine one customer's callers with another's. Even whether someone is calling for the first time is worked out inside your account only.
11.4 The recording notice
When recording is on, every caller hears "This call may be recorded." before the call connects, and no call is recorded without it. When recording is off, the notice does not play and calls are not recorded. A voicemail left on a paused number is kept whatever the setting, because the caller chooses to leave it.
11.5 Where recordings are kept, and who can play them
When a call ends, we copy its recording to our own private storage, then delete it from our carrier. In the app, only signed-in members of your account can play a recording, through a link that stops working shortly after the recording's length. Recordings are not in the Calls export, the API or webhooks. A voicemail left on a paused number is attached to the next morning's calls email (11.7) while that email has room for it, up to 5 MB of voicemails an email, newest first; a voicemail that does not fit is named in the email and stays in your account.
11.6 How long we keep it, and deleting it
We keep call records and recordings until you delete them or your account is deleted. Any member of your account can delete a recording at any time. It is removed from our storage at once and cannot be restored, and the call's record stays. A voicemail already sent with a calls email stays in the mailboxes it reached. When an account is deleted, we delete its call records and recordings. A number that ends keeps its call history in your account.
11.7 Who gets caller details
Caller details go to the people and systems you choose. On each morning after a day with calls, we send one calls email to every address on a number's missed-call list and, while your account's Daily Email setting is on, to your account's admins (or its owner if it has none). People on your own team who are on a list get it only while that setting is on; addresses outside your account get it whatever the setting, and can turn it off from the email itself, which takes them off every number's list in your account. On a morning after a day with QR scans, your account's admins (or its owner if it has none) also get that day's QR scan counts by mailing in the same email, while the Daily Email setting is on, whether or not you use call tracking. The email gives the number of QR scans and pieces scanned for each mailing; it does not list who scanned. Other people on a number's missed-call list get the calls only. The email lists each missed call of the day before: the caller's number and city, the time, the number called and the campaign, with any voicemail attached. Past 100 missed calls it attaches the full list as a spreadsheet, without your outcomes and notes. Anyone on your account who downloads the Calls export gets caller details, and so do your own systems if you use our API or webhooks (the caller's number, times, outcome and note, never the recording). Our telephone carrier connects every call and holds each recording until we copy it, and our email provider delivers the emails.
11.8 Our team
Our team can see a number's call records to support you, to run the monthly minutes limit and to review numbers for misuse. When our team signs in to your account to help you, they see what you see.
11.9 Requests from callers
Someone who called you and wants their recording or details deleted should ask you. You can delete a recording yourself in the app. For anything else, contact us and we will help, as our Data Processing Addendum sets out.
12. QR code scans
12.1 What a QR scan records
When someone scans a tracked QR code on mail we printed for a customer, we record the time; what the scan was shown (the customer's page, a Call, Text or Save contact page, or one of the notice pages in our Terms); whether it looked like a person or an automated link preview; the type of device, its operating system and browser; a one-way scrambled copy of the browser's description of itself; the name of the website or app that opened the link, never the full address of that page; two technical details of the request that help tell people from automated previews; and the country, when available. Each record is tied to the mailpiece the code was printed on. Scans of the sample code on a proof are not recorded.
12.2 Who a scan points to
A scan record holds no IP address, name, phone number, email address or cookie, so it does not say who scanned. Because each code is printed on one mailpiece, the business that sent it learns that the code on the piece mailed to a given person on its list was scanned, how many times, and when. Anyone holding that piece could be the one who scanned it.
12.3 We handle scans for our customers
We record and report scans on behalf of the business that sent the mail, as its service provider, under our Data Processing Addendum. We do not sell scan records or share them for advertising. We do not combine one customer's scans with another's, except to spot fraud and automated abuse across our service.
12.4 Who sees scan data
People on the sending business's account see its QR scans on the campaign page and the dashboard, on every plan, and can download who scanned: the recipient's name and address from their own list, the number of scans, the first and last scan, and the link opened. The account's admins (or its owner) also get each day's QR scan counts by mailing in the morning email; the email does not list who scanned. Our team sees each code's link, its safety checks and its count of scans, to support the customer and keep our short link domain safe, and sees what the customer sees when signed in to their account to help them.
12.5 How long we keep it
We keep each scan record for 24 months. Each code's running totals stay with the campaign. Deleting an account does not delete its scan records: codes already printed keep answering, with a page saying the link is no longer active, and their records follow the same 24 months.
12.6 The links site, and blocked requests
Tracked codes open links on mstrack.link, which we run. Its pages set no cookies and load nothing from other sites. We use a request's IP address only to limit abuse, through a scrambled key that cannot be turned back into the address once that day is over, and we do not store it with the scan. If we block a request, because one address sent more than 60 requests in a minute or asked for a page the site does not serve, we keep that request's IP address for 7 days, for security, and then delete it.
12.7 Checking links with Google
To keep people who scan safe, we check the web links our customers set against Google Web Risk's list of unsafe sites, when a link is set and again later. Google receives the link, never anything about a person who scans: at most the page's address without the part after "?", and only the site's address for links that come from a customer's mailing list. A scan itself sends nothing to Google.
12.8 Reports and requests about scans
Anyone can report a code at mstrack.link/report. We keep what the report says, and an email address only if the person gives one, to look into it. Someone who wants the scan records of a piece mailed to them deleted should ask the business that mailed it; contact us and we will help, as our Data Processing Addendum sets out.
13. Cookies and similar technologies
We and our partners may use cookies, pixels, and local storage for essential operation, preferences, analytics, and (where allowed) advertising. You can control cookies through your browser settings; some features may not work if cookies are disabled.
14. Children
The Service is not directed to children under 16, and we do not knowingly collect personal information from children. Contact us if you believe we have collected a child's information in error.
15. U.S. state privacy notices
Residents of certain U.S. states may have additional rights regarding personal information under local laws (for example access, deletion, correction, opt-out of sale or sharing, and appeal). We do not "sell" personal information in the conventional sense of exchanging data for money; we may use cookies or pixels that constitute "sharing" for cross-context behavioral advertising under some laws where you can opt out via browser controls and industry tools. To submit a request, email hello@mailstream.app with your state of residence and a description of your request. We will verify your identity before responding.
16. Changes to this Policy
We may update this Policy from time to time. We will post the revised version here and update the "Last updated" date. Where changes are material, we will provide additional notice as appropriate.
Privacy inquiries: hello@mailstream.app.