Measure this visit?
Accept allows Google Analytics, Microsoft Clarity and PostHog, including session recording. Reject stops their recording. Cookieless counts and server request logs stay on. What we measure
// security
Found a hole in this site? Tell us and we will fix it. This page says where to send it, what we do with it, and what we will not do to you for sending it.
Email ben@synapsereality.io. We do not publish a PGP key, so describe the problem in plain terms and leave any live credentials out of the message.
What to put in the report:
Please do not put a working exploit chain in a public place before we have fixed it. If you are not sure whether something counts, send it anyway.
If we disagree that something is a problem, we say why. You are free to disagree back, and we would rather have the argument than go quiet.
Report in good faith and stay inside the rules below, and we will treat your testing as authorised. We will not go to a lawyer or to your hosting provider about it, and we will not ask anyone else to.
The rules:
We cannot waive anyone else's rights. If your testing hits a third party's infrastructure, their rules apply to that, not ours.
In scope: synapsereality.io, including the API paths under /api/ and the forms on this site.
Out of scope:
Saving you some time. This is a static site: the pages are HTML files built ahead of time and served from a CDN. There is no CMS, no login, no user account, no payment and no file upload on it.
The only moving part is a small API behind /api/ that takes the forms, runs the audit tool and handles email replies. That is where an interesting bug would be.
We do not run a paid bug bounty. What we can offer is a fast answer, a fix you can check, and public credit if you want it.
/.well-known/security.txt follows RFC 9116 and points back at this page. If it has expired, this page is still the right route, and telling us the file is stale is itself a useful report.