SECURITY · LAST UPDATED SEP 06, 2026
Found a security problem?
There is a clear reporting route, and no need to test destructively.
What to include
Please include the affected URL or component, the behavior you observed, reasonable reproduction steps and the potential impact. Screenshots are useful when they do not contain third-party personal data.
Testing boundaries
Please do not disrupt service, access data you do not own, attempt social engineering, send spam, or create avoidable costs. A report does not imply a bug bounty or payment promise.
Payment boundary
This site does not collect card details. The primary payment action opens the project’s Ko-fi checkout, where payment processing is handled outside this site.