What to include
- The affected URL or script file ID.
- What happened and when, including the time zone.
- Expected behavior and the steps that reproduce the issue.
- Redacted screenshots or logs and a way to contact you.
Where to send it
Include the affected URL or script file ID, a short description, timestamps, and redacted evidence. Never include passwords, full license keys, OAuth tokens, or private script source.
A public support inbox has not yet been configured. Contact the operator through the channel where you obtained your account; this page does not submit a report.
Security reports
For a suspected service vulnerability, use an isolated test account and stop after demonstrating the issue. Do not access another customer’s source or data. Send the minimum reproducible example privately to the operator.
Other issues
License access problems belong with the script owner. Copyright concerns have a separate copyright reporting guide. For immediate danger, use local emergency channels rather than a product support report.
Lua