1. Our approach
Your inbox holds sensitive customer conversations. We design MilerMail so that access is limited, actions are traceable and data is protected in transit and by our infrastructure providers.
2. Controls
- Encryption in transit (TLS) for connections to MilerMail; encryption at rest provided by our infrastructure providers where available.
- Mailbox credentials (IMAP/SMTP passwords or app passwords) are stored encrypted and used only to sync and send on your behalf; connections to mail servers use TLS/SSL.
- Where you connect Gmail with Google sign-in, we use OAuth — we never see your Google password, and you can revoke access at any time.
- You can disconnect a mailbox at any time, or change its password to cut off access immediately.
- Role-based access, so admins and team members only see what they need.
- Activity logs that record who did what and when.
- Least-privilege access to production systems by our staff.
3. Handling of mailbox data
Humans at MilerMail do not read your email content except with your consent, for security investigation, or as required by law. Where you connect Gmail with Google sign-in, we also follow Google’s API Services User Data Policy, including Limited Use.
4. Incident response
We monitor for abuse and incidents, investigate promptly and notify affected customers without undue delay, in line with the DPA and applicable law.
5. Reporting a vulnerability
If you find a security issue, email security@milermail.com with details. Please give us reasonable time to fix it before public disclosure, and do not access data that is not yours. We appreciate responsible reports and will acknowledge them promptly.
6. Honest limits
No system is perfectly secure. We do not currently claim third-party certifications such as SOC 2 or ISO 27001; if that changes, we will say so here.
