What to include
Provide the affected public URL, hostname or other relevant service identifier, the type of concern, the date and time with time zone, and a concise description of what you observed. Explain the impact and include non-sensitive reproduction details when appropriate.
Distinguish an observation from an assumption about who operates a service. Avoid sending passwords, private keys, access tokens, malicious attachments, full personal-data records or unrelated customer information.
Keep investigation within your authority
Do not access, alter or extract another person’s data to demonstrate a concern. Stop if investigation would extend beyond your authorisation or risk disrupting a service. Do not conduct broader scans or testing without the relevant permission.
If you believe sensitive evidence is necessary, describe its nature and request an appropriate secure exchange route. The public form does not accept file uploads.
How reports enter the workflow
The website verifies your email before accepting a report into the enquiry-ticket workflow. Keep the reference for follow-up. The team may need clarification, account context or coordination with a provider to assess the issue.
An automated receipt does not confirm that a reported vulnerability is valid, establish a bounty, authorise testing or commit to a response deadline. This page does not create a safe-harbour programme or reward policy.
Existing customer incidents
If the issue affects your service, include the service reference and business impact through the contracted support channel. Preserve relevant evidence safely and avoid making changes that could disrupt recovery unless you are authorised to do so.
