Security
If you find something, tell us. We will not threaten you for it.
Reporting a vulnerability
Email security@proxycrunch.com with enough detail to reproduce. We aim to acknowledge within one working day. We will not pursue legal action against good-faith research that avoids privacy violations and service degradation.
How the site is built
- Every table enforces row-level security in the database. Authorisation is not a UI concern here — an unpublished listing is unreachable even with a crafted API request.
- Public write paths are narrow and constrained: counters go through single-purpose functions that cannot touch anything else, and submissions cannot self-approve.
- Outbound redirects accept only http(s) targets.
- Credentials that can bypass row-level security never run in a public path.