Responsible Disclosure
If you have found a security flaw, we want to hear about it. This page sets out how to report it and what you can expect in return.
Last updated 18 September 2026 · Operated by Proteen Das (prot.das15@gmail.com)
How to report
Email prot.das15@gmail.com with the subject line “Security report”. Please include:
- A description of the issue and why you believe it is a security problem.
- Clear steps to reproduce it, ideally with a minimal example.
- The affected URL, endpoint or component.
- Any proof-of-concept you used, and your assessment of the impact.
What we ask of you
- Report promptly and give us reasonable time to fix the issue before disclosing it publicly.
- Test only against your own account and your own data.
- Do not access, modify or delete anyone else’s data. If you encounter someone else’s data, stop and tell us.
- Do not run denial-of-service, spam or brute-force testing against the live service.
- Do not use social engineering or physical attacks against the operator or any provider.
What you can expect
- An acknowledgement of your report, normally within five working days.
- An assessment of severity and an indication of the expected fix timeline.
- An update when the fix ships.
- Credit for the finding if you would like it — just say so in your report.
This is a free, individually-operated service, so there is no paid bug bounty. Reports are still genuinely welcome and are taken seriously.
Safe harbour
If you act in good faith within the boundaries above, we will not pursue or support legal action against you for your research, and we will treat your report as an authorised contribution to the security of the service.
Out of scope
- Vulnerabilities in third-party AI providers or connected services — report those to their own security teams.
- Findings that require a compromised device, a malicious browser extension, or physical access to a signed-in machine.
- Missing hardening headers or best-practice suggestions with no demonstrable exploit.
- Self-inflicted issues in a deployment you run yourself with insecure configuration.