How we approach security
HumaraMail is still in development, so this page sets out our direction and doesn’t claim anything that isn’t finished. We’ll keep reviewing these decisions as the architecture takes shape.
- Choose established technologies that are actively maintained
- Give the least access practical to people and systems
- Encrypt information in transit using modern standards
- Watch critical systems and look into unusual activity
- Keep dependencies current and review reported vulnerabilities
Protecting accounts
Before public launch, we intend to provide secure sign-in, safe account recovery, abuse monitoring and clear alerts for important account events. The final features will be documented once they’re available.
Looking after data
We plan to restrict access to operational data, hold on to only what’s needed and work with reputable infrastructure providers. Our Privacy Policy covers how this website handles waitlist and enquiry details today.
Report a vulnerability
If you think you’ve found a security issue affecting HumaraMail, email [email protected] with the affected URL or component, steps to reproduce it, the possible impact and a safe way to reach you.
Please don’t access other people’s data, disrupt the service or make the issue public before we’ve had a reasonable chance to investigate.
Reporting misuse?
Our abuse guidance explains what to send.