Choicely Security Acknowledgements
We thank the people who report security issues to us under our Vulnerability Disclosure Policy. When a reporter asks to be credited, we list them here once we have reviewed their report and resolved the issue.
Researchers we thank
No researchers are listed yet. Names appear here after a reported issue has been reviewed and resolved, and only when the reporter has asked to be credited.
How to be credited
- Credit is your choice. Tell us in your report if you would like to be credited publicly, and give the name or alias you want shown. You can add a short description, such as your role, and one link to your LinkedIn or GitHub profile.
- We add your entry after we have reviewed your report and resolved the issue. If several people report the same issue, we credit the first report we received.
- Your report must follow our Vulnerability Disclosure Policy, including its scope and rules of engagement. Out-of-scope findings, such as reports generated solely by automated scanners without demonstrated impact, are not credited.
- We never publish details of the issue, your email address, or anything else from your report.
You can ask us to change or remove your entry at any time by writing to [email protected] from the address you reported from. We may shorten a description, leave out a link that is not a personal LinkedIn or GitHub profile, or decline an entry that is offensive, misleading or names another person or company. Not appearing here does not mean a report was invalid.
A listing is our thank-you, not a reward or an endorsement, and listed researchers are not Choicely employees, contractors or partners. We list names and links with the researcher's consent, as described in our Privacy Policy. Choicely does not currently operate a paid bug bounty program.
Report a vulnerability
Please read our Vulnerability Disclosure Policy before you test, then send your report to [email protected]. Machine-readable contact details are in our security.txt.
Last updated: November 16, 2026