Security
How we handle what we find out about you
A security test produces exactly the material an attacker would want. Here is how it is protected, and how to tell us if we got something wrong.
Our practices
Your report never sits in a shared inbox
Reports and evidence live in a private store, encrypted at rest, reachable only by the testers on your engagement. Links we send you are unguessable and tied to your request.
Credentials we see are kept out of the deliverable
If a test turns up a password, token or key, it is replaced with a placeholder everywhere a human reads it, and the real value is kept separately so a retest can re-run. We never keep working credentials of yours after the engagement closes.
Evidence has an expiry date
We delete evidence 90 days after the final report unless you ask us in writing to keep it longer. Nothing is kept “just in case”.
Your source stays where it is
If you give us source code for a grey-box review, it is mounted read-only on the tester's machine and never leaves it. Only findings and evidence reach this backend.
This site is built the way we tell customers to build
A strict content security policy, HSTS, no third-party trackers, cookie-free analytics, rate limits on every public endpoint, and the admin area behind authentication and same-origin checks.
Payments never touch our servers
Checkout runs at our payment provider, who acts as merchant of record. We store the fact that an order was paid, not a card.
Found a problem in our service?
Tell us. We would rather hear it from you than from a customer, and we will not threaten anyone who reports in good faith.
Email security@provensecure.io. Include what you did, what you saw, and how we can reproduce it. Our machine-readable contact details are at /.well-known/security.txt.
What you can expect
- We acknowledge your report within two working days.
- We tell you whether we could reproduce it within five working days.
- We keep you updated until it is fixed, and tell you when it ships.
- We credit you by name if you want it, and never without asking.
What we ask of you
- Stay within our own systems: this site and the services it runs on.
- No denial-of-service, no spam, no social engineering of our people or customers.
- Do not access, change or keep anyone else's data. If you reach data that is not yours, stop and tell us what you saw.
- Give us a reasonable chance to fix it before you publish.
We do not run a paid bug bounty. We do say thank you properly.