Reporting a security issue
Last updated: November 8, 2026
If you think you've found a security issue in MailInApp, please tell us privately. We'd rather hear about it from you than from an attacker, and we treat every report seriously.
How to report
Email [email protected] with "Security" at the start of the subject line. Please include:
- What you found and where: the page, API route, app or plugin, and the account or URL you used.
- Steps to reproduce it, and what an attacker could do with it.
- Any proof of concept, screenshots or request logs that help.
- How you'd like to be credited, if at all.
Please don't report security issues in public places such as social media, app store reviews or the Figma Community page until we've fixed them.
This address is also in our security.txt file.
What happens next
MailInApp is run by a small team at Digitload, and the owner handles every report personally.
- We confirm we've received it. We aim to reply within 3 business days.
- We check it. We work out whether we can reproduce it, how serious it is and who could be affected.
- We contain and fix it. That can mean rotating a credential, turning off the affected feature while we work, and shipping a fix.
- We tell the people affected. If anyone's personal data was exposed, we notify the affected customers directly, along with anyone else we're required to tell.
- We tell you. We let you know when it's fixed and agree with you on when the details can be shared.
What's in scope
- The website and app at mailinapp.com and its subdomains, including the studio, dashboard, live-view and landing pages.
- The public API (
/api/v1) and our MCP server. - The MailInApp mobile app.
- Our integrations: the Figma plugin, the Zapier app, the n8n node and the Shopify app.
- The emails MailInApp builds and sends, and the links and images in them.
Some endpoints that recipients' inboxes call directly, such as poll votes, form posts and open tracking, are public on purpose, because an email can't sign in. Reporting that they accept requests without a login isn't a vulnerability on its own, but showing that they can be used to read or change another account's data is.
What's out of scope
- Denial-of-service attacks, load testing or anything that degrades the service for others.
- Social engineering or phishing of our staff or customers, and physical attacks.
- Spam, or sending email to people who didn't ask for it, through MailInApp.
- Issues in services we use but don't run, such as Google Cloud, Cloudflare, Stripe or Figma. Please report those to them.
- Reports from automated scanners without a demonstrated impact, missing best-practice headers with no exploit, and clickjacking on pages with nothing to click.
Testing in good faith
If you follow this page, we won't take legal action against you or ask anyone else to for your research. In return, please:
- Use only accounts you own or have permission to use, and stop as soon as you reach anyone else's data. Don't view, copy, change or delete more than you need to show the issue.
- Don't send email from MailInApp to anyone who hasn't agreed to receive it.
- Give us reasonable time to fix the issue before you tell anyone else about it.
We don't run a paid bug bounty programme. We're glad to credit you once the issue is fixed, if you'd like that.
Security certifications
MailInApp doesn't hold its own security certification, such as SOC 2 or ISO 27001. It runs on Google Cloud (Firebase), whose infrastructure holds certifications including SOC 2 and ISO 27001. How we handle personal data is described in our Privacy Policy, our Data Processing Addendum and our list of sub-processors.