01
Authorization remains mandatory
Nothing published on this website grants permission to test, scan, probe, exploit or otherwise interact with No Breach systems outside their normal intended use.
Website security
Security starts with clear boundaries.
Information about responsible contact, public website security expectations and the limits of authorization.
Principles
Clear security expectations for the public website.
02
Sensitive information stays out of public forms
Passwords, tokens, private keys, customer information and confidential infrastructure details should not be submitted through public website interfaces.
03
Suspected website issues can be reported responsibly
If you believe the public No Breach website exposes a security issue, use the official contact channel and provide only the information necessary to explain the concern.
Responsible contact
No Breach does not publish a public bug bounty program through this website.
The existence of a security.txt file, a security page or a public contact channel does not constitute authorization to scan, probe or exploit No Breach systems.
If you believe you have encountered a security issue while using the public website normally, contact No Breach through its official channel before disclosing sensitive technical information publicly.
Public security.txt
Machine-readable security contact information is available under the standard well-known path.
Security contact
Report concerns without sending credentials or confidential data.
Use the public contact channel for an initial message. Sensitive technical material should only be exchanged after an appropriate communication path is established.