Last updated: November 15, 2026
If you think you've found a security problem in Morse, please tell us. This page explains how to report it and what to expect from us.
How to report
Email hello@trymorse.ai with "Security" in the subject. Tell us what you found, where, and the steps to reproduce it, with any proof of concept, screenshots, or requests that help. Please write in English.
What we ask of you
- Use your own account. Test only with accounts you own or have permission to use, and never open, change, or delete anyone else's data.
- Keep it quiet until it's fixed. Give us a reasonable time to fix the problem before you share it with anyone else.
- Don't disrupt the service. No denial-of-service, spam, or automated testing that slows Morse down for others, and no phishing or social engineering of our team or users.
- Stop when you've shown it. If you reach data that isn't yours, stop there, don't keep a copy, and tell us in your report.
What you can expect
- We'll reply to say we got your report, and keep you posted while we look into it.
- We'll tell you when it's fixed, and, if you'd like, credit you by name when we write about it.
- We won't take legal action against research done in good faith that follows this page.
Morse doesn't run a bug bounty, and we don't pay for reports.
Machine-readable contact
The same contact is published at /.well-known/security.txt, in the format RFC 9116 sets out.