Bretton · Vulnerability Disclosure

Bretton Vulnerability Disclosure

Vulnerability disclosure

Bretton runs a coordinated vulnerability disclosure program on Hackerone. A dedicated security contact is published.

CompanyFintechRegTechFinancial Crime ComplianceAMLKYCAI AgentsComplianceFinancial-Services
Program: Hackerone

Disclosure Policy

Policy
https://trust.bretton.com/

Security Contact

Contact
privacy@bretton.com

Source

Vulnerability Disclosure

bretton-vulnerability-disclosure.yml Raw ↑ 
generated: '2026-07-18'
method: searched
probe: true
source: https://trust.bretton.com/
policy:
  - https://trust.bretton.com/
contact:
  - privacy@bretton.com
disclosure_channel: >-
  The Bretton trust center publishes a "Report a vulnerability" link that opens a responsible-disclosure
  email to privacy@bretton.com (subject: Vulnerability Report). No public bug-bounty program
  (HackerOne/Bugcrowd/Intigriti) and no /.well-known/security.txt were found.
bug_bounty: null
security_txt: null
evidence:
  - source: https://trust.bretton.com/
    kind: trust-center-disclosure-link
    detail: "Report a vulnerability -> mailto:privacy@bretton.com"

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact 
curl "https://apis.io/api/v1/security/bretton-vulnerability-disclosure"
All security posture 
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.