Contact
Contact & feedback
A small team builds this. Mail reaches a person, and corrections to our content are the most useful thing you can send.
General, content corrections, and data requests
- A question or recommendation is wrong or out of date. Tell us which one and why — every published item names its sources, so point at the source that contradicts it.
- A score felt wrong. Say which assessment and what you expected. Scoring is deterministic, so a disagreement is usually about a rule, and rules can change.
- Data requests — export, account deletion, or removing evidence files. These are not self-serve yet, so a human handles them; see the privacy policy.
Security reports
If you believe you have found a vulnerability, please tell us before telling anyone else, and give us a reasonable window to fix it. Include what you did, what happened, and what you expected. Please do not run automated scans against the live service, access other people's data, or degrade the service while testing — we would rather hear about a theoretical issue than clean up after a demonstrated one.
We do not currently run a paid bug-bounty programme, and we will not pretend otherwise. We will credit you if you want the credit.
Feedback inside the product
On a results page you can mark whether the score felt fair and whether each suggested fix was relevant. Those signals carry no free text — just the verdict and which item it referred to — and they go straight into how we prioritize content work.