Reporting a security problem

If you find a security problem in the Rotulus app, on rotulus.io or in its forms, please tell us privately first. Email support@rotulus.io with "Security" in the subject line. Tell us what you found, how to reproduce it, and which version or page it affects.

What we ask

• Give us a reasonable time to fix the problem before you tell anyone else.
• Test only your own copy of Rotulus and your own data.
• Don't access, change or delete other people's data.
• Don't disrupt the site or its forms: no denial-of-service tests and no automated form submissions.
• Don't use phishing or other social engineering.
• Don't bypass the License Key check, the key lock or the online check, and don't publish ways around them.

What we do

We aim to reply within 24 hours, weekends included, and we tell you when the problem is fixed. We don't pay bug bounties; if you'd like, we credit you by name.

Section 4.3 ("Security research") of the Rotulus End User License Agreement lets you do good-faith security research on the Rotulus app that follows this page, even though its section 4.1(d) otherwise forbids reverse engineering. It does not cover research that bypasses the License Key check, the key lock or the online check, or publishing ways around them.

Beta testers: please report security problems this way before you post about them, and don't publish details that would let someone exploit a problem until it is fixed or 90 days after you told us, whichever comes first.

Last updated 2026-10-12.