Report a vulnerability
If you believe you found a security problem in zmle, please tell us privately so we can fix it before anyone is harmed.
Rules for reporting
- Report privately through the form below or by email to the address in our security.txt file. Do not share details publicly until we confirm that the problem is fixed.
- Test only with accounts and workspaces that you own. Do not access, change or delete other people's data, and stop as soon as you reach data that is not yours.
- No denial-of-service tests, spam, social engineering of our staff or customers, and no physical attacks.
- We confirm that we received your report, keep you informed, and tell you when the problem is fixed.
In scope
- The website zmle.com and the sign-up
- Workspaces on addresses like name.zmle.com and their admin
- The public API v1 (api.zmle.com) and webhooks
- The control center (control.zmle.com) and the connector for own hosting
- zmle's own Business office (office.zmle.com), which runs on the same platform
Out of scope
- Websites and content that customers run on their own servers, unless the problem is in zmle itself
- Reports from automated scanners without a demonstrated impact
- Missing best-practice settings without a working attack
- Services of other companies that we use (for example payment or email providers) — please report to them directly
Our safe-harbor terms for good-faith research are under legal review and will be published on this page. Until then, please follow the rules above, and ask us first if you are unsure whether a test is allowed.
What you can expect
We acknowledge your report within 3 business days and triage it — confirm it, rate its severity and plan the fix — within 10 business days. Until it is resolved we update you at least every 14 days, and we agree a disclosure date with you.
Rewards
We do not pay money for reports yet. With your permission we thank you by name in the hall of fame below. If we start a paid bounty program, we will announce it on this page first.
Hall of fame
With their permission, we thank the researchers whose reports made zmle safer.
No entries yet — the first valid report could be yours.
Prefer email? Write to security@zmle.com. security.txt