Security and vulnerability disclosure

Last updated: 20 November 2026

Report a vulnerability

Email customersupport@isthisspam.org with the subject "Security report". Include what you found, where, the steps to reproduce it, and the impact you believe it has. Please do not include other people's personal data in your report. Our machine-readable contact is at /.well-known/security.txt.

What to expect

  • We acknowledge reports within 3 business days.
  • We assess severity and tell you our plan, and we keep you updated until the issue is closed.
  • Target fix or mitigation times from confirmation: critical 7 days, high 14 days, medium 30 days. Low-severity issues are scheduled into normal releases. If a fix will take longer we tell you why.
  • With your permission we credit you once the issue is fixed.

Safe harbour for good-faith research

If you act in good faith, we will not pursue legal action against you for research that follows these rules: test only your own accounts, do not access or change other people's data, do not degrade the service (no denial-of-service or heavy automated scanning), do not use social engineering or physical attacks against our people, and give us reasonable time to fix an issue before you disclose it publicly.

In scope

isthisspam.org and its APIs, our sign-in and account features, and our browser extensions and mobile apps. Reports about third-party services we use should go to those providers.

How we handle incidents

  • We contain the issue, assess what data and which features were affected, fix the cause, and review what happened.
  • If an incident affects personal or sensitive information, we notify affected account holders by email without undue delay, and we notify the Office of the Australian Information Commissioner where the Notifiable Data Breaches scheme under the Privacy Act 1988 (Cth) requires it.
  • If an incident materially affects the reliability of our scam detection, we tell affected account holders what happened and what to do in the meantime.

Dependencies

We use automated dependency monitoring on our code repository and review security updates on a regular schedule, prioritising vulnerabilities in line with the fix times above.

This page describes our process. It is not a guarantee that no vulnerability exists, and it does not replace the independent assessment and validation evidence we may provide to partners on request.