Security Response Centre

Effective 30 October 2026 · Version 1.1

Our vulnerability disclosure policy. If you believe you have found a security vulnerability in Porters, we want to hear from you, and we will work with you to understand and fix it. Report to [email protected].

1.Scope

1.1In scope:

  • porters.matmon.tech: the website and customer portal;
  • webmail.matmon.tech: the webmail and its API;
  • the Porters mail servers (IMAP, SMTP, CalDAV and CardDAV) and their configuration;
  • the Porters Mail app for Android (package tech.matmon.porters); and
  • Porters source code, where you have been given access to it.

1.2Out of scope:

  • denial-of-service, load or volumetric testing;
  • social engineering, phishing or physical attacks against our staff, offices or data centre;
  • spam, or sending mail to people who did not agree to receive it;
  • reports from automated scanners without a demonstrated, exploitable impact;
  • missing security headers, cookie flags or TLS settings without a practical attack;
  • self-XSS, clickjacking on pages without sensitive actions, and logout CSRF;
  • rate-limit or brute-force findings that do not bypass a limit;
  • SPF, DKIM or DMARC on domains that do not send mail; and
  • vulnerabilities in third-party services we use, which should go to those vendors.

2.Rules of engagement

2.1When researching, you must:

  • test only against accounts and mailboxes you own, or have the owner's explicit permission to test;
  • stop as soon as you reach other people's data, access only what is needed to demonstrate the issue, and not copy, keep, change or delete it;
  • not degrade the service for others, and not use automated tools that send high volumes of requests;
  • not use a vulnerability beyond confirming it, such as to pivot to other systems; and
  • keep the details confidential until we have fixed the issue and agreed a disclosure date with you.

3.How to report

3.1Email [email protected] with:

  • a description of the vulnerability and its impact;
  • the affected URL, endpoint, app version or component;
  • step-by-step instructions to reproduce it, with any proof-of-concept code, requests or screenshots;
  • the accounts you used for testing; and
  • how you would like to be credited, if at all.

3.2Please write in English, one vulnerability per report. Our machine-readable contact details are in /.well-known/security.txt.

4.What we commit to

StepTarget
Acknowledge your reportWithin 3 business days
Confirm whether it is valid and its severityWithin 10 business days
Fix critical issuesAs fast as possible, typically within 7 days
Fix high-severity issuesWithin 30 days
Fix medium and low-severity issuesWithin 90 days

4.1We will keep you informed of progress, tell you when the issue is fixed, and, with your permission, credit you when we disclose it. If you believe we are not responding, write again with "Follow-up" in the subject.

4.2We aim to disclose fixed vulnerabilities publicly, coordinated with you, within 90 days of your report, or sooner once a fix is deployed.

5.Safe harbour

5.1If you make a good-faith effort to comply with this policy, Matmon Technology considers your research authorised. We will not bring legal action, or ask authorities to act, against you for it, including under the Computer Misuse and Cybercrimes Act, 2018. If a third party brings action over activity that complied with this policy, we will make clear that it was authorised.

5.2This authorisation does not extend to research that breaks the rules in section 2, or to accessing other people's data beyond what is needed to demonstrate a vulnerability. If in doubt, ask us first.

6.Recognition

6.1We do not currently run a paid bug bounty. We are grateful for every valid report and will credit researchers who wish to be named when we disclose the fix.