REPORT A PROBLEM / SUGGEST AN IMPROVEMENT
Tell us where Rightly needs to be better.
Early beta only becomes useful when failure is visible. Report a bug, confusing behavior, feature request, or something that worked especially well.
Please protect yourself
Do not include passwords, authentication codes, card or bank data, private keys, confidential client records, protected Rightly governance material, canonical prompts, source instructions, or master packages. Crop or redact screenshots before uploading them.
How reports are handled
Each accepted report is assigned a private unique ID and stored for triage with its timestamp, category, severity, reproducibility, affected version, status, owner, disposition, follow-up permission, and closure evidence. A fix is not treated as resolved until it has independent verification; otherwise it remains fixed pending verification.
Critical and high-impact reports are reviewed promptly. Repeated patterns are reviewed regularly. Rightly is not an emergency service and does not promise continuous monitoring or a guaranteed response time.
Send a report
Give concrete steps and impact where you can. A successful submission means the site accepted the report; it does not by itself prove mailbox delivery or guarantee follow-up.