Responsible Disclosure
Found a vulnerability? Here is where to send it, and our promise not to come after you.
Draft. This describes how the site actually works, but it has not been through legal review and does not yet meet the disclosure rules of any particular jurisdiction. Do not treat it as the published policy.
Last updated 21 August 2026
If you have found a security problem with this site, we want to hear about it and we will not treat you as an attacker for telling us. This page is the whole process.
How to report
Email security@megaresources.co with enough detail to reproduce it: the URL, the steps, and what you were able to reach. A short proof of concept is more useful than a scanner output.
The machine-readable version of this page is at /.well-known/security.txt, in the RFC 9116 format your tooling expects.
What to expect from us
- An acknowledgement within three working days, from a person.
- An assessment and a rough timeline within ten working days.
- Progress updates while we work on it, rather than silence.
- Credit in the fix note if you want it, and none if you would rather stay anonymous.
We do not pay bounties. We are a small shop and would rather be honest about that up front than imply a reward that never comes.
Safe harbour
If you follow the rules below, we will treat your research as authorised. We will not pursue legal action, we will not report you, and if a third party does, we will say publicly that you were acting with our permission.
The rules
- Give us reasonable time to fix it before telling anyone else. Ninety days is the usual expectation; if it is being actively exploited, say so and we will move faster.
- Do not access, modify or delete data that is not yours. If you stumble into customer data, stop, and tell us what you saw so we can assess the exposure.
- Test against your own account. Use one order, one message — not thousands.
- No denial of service, no social engineering of our staff or suppliers, and no physical attacks.
- Do not use a finding to extort us. A report that arrives with a payment demand is not a disclosure.
Scope
This site and its API. Out of scope: Stripe's checkout, our hosting provider's infrastructure, and anything else belonging to a third party — report those to their own programmes, which are better resourced than ours.
Also out of scope, because we already know: missing security headers with no demonstrated impact, rate limits on non-sensitive endpoints, and reports generated wholesale by an automated scanner without a working proof of concept.
Something here not clear?
Ask us plainly and we will answer plainly — and if the answer shows this page is wrong, we will fix the page.
Write to us