Last updated:
PhishClean is a security product, so we want to hear about any security problem in it. This page explains how to report one, what we promise in return, and how the extension, API and data are protected.
Please include the product and version (extension, website, API, MCP server or desktop agent), steps to reproduce, and what an attacker could do with it. We aim to reply within 7 days. We will tell you when a fix ships and credit you in the release notes, unless you would rather not be named. We do not pay bounties at the moment.
Our machine-readable contact file is at /.well-known/security.txt.
/api/) and the remote MCP server (/mcp).phishclean-mcp npm package and the PhishClean desktop agent.Examples we especially want: a web page that can read, change or switch off the extension's settings or licence; the extension sending data anywhere not listed in its public network table; script injection through a warning, popup or options page; access to another customer's licence, account or organisation data.
If you act in good faith under this policy, we will not take legal action against you or ask anyone else to. Good faith means you test only against your own accounts and installs, stop as soon as you reach anyone else's data and do not keep it, avoid harming the service or its users, and give us reasonable time to fix the problem before you publish (we suggest 90 days, and we will work with you on the date).
| Area | What we do |
|---|---|
| Detection | All checks run inside your browser. Addresses you visit and page content are not sent to us. The extension source is public so this can be checked, and its README lists every network request it can make. |
| Updates | The extension updates only through the Chrome, Edge and Firefox stores, and it loads no remote code. |
| Data we hold | A random install ID, licence status, extension version and check-in counts. For accounts, an email address. The privacy policy lists everything. |
| Infrastructure | Website and API on Vercel; database on Supabase (Postgres), with row-level security on every table; DNS and proxy through Cloudflare. All traffic uses HTTPS with HSTS. Payments are handled by Dodo Payments, so card numbers never reach us. |
| Development | Automated tests run on every change. The public repositories run OpenSSF Scorecard and Dependabot. |
| Accuracy | Detection and false-alarm rates are measured every day on live pages and published on the transparency page. |
PhishClean does not hold ISO 27001 or SOC 2 certification. We would rather say so than show a badge we have not earned. Instead, you can read the extension's source, check its network requests and see our measured detection numbers. Business customers can ask for our security questionnaire answers and data processing agreement through the contact form.