Skip to content
Sign inGet started
Company pages
Trust & data

Vulnerability disclosure

How to report a security problem in talonlabs.dev, its licence service, or Talon Studio — what is in scope, what we ask of you, what you can expect from us, and our promise not to pursue good-faith research.

Last updated 27 September 2026DRAFT — PENDING COUNSEL REVIEW

How to report

Email security@talonlabs.dev. Tell us what you found, where (the URL, or the product and its version), the steps that reproduce it, what an attacker could do with it, and how to reach you. A proof of concept helps; a working exploit against someone else's data does not.

We do not publish an encryption key yet. If your report needs one, say so in a first message without the details, and we will arrange it. Please do not use the contact form or the support address for a vulnerability.

Scope

In scope
talonlabs.dev and www.talonlabs.dev, including accounts, sign-in and the licence endpoints under /api/license; Talon Studio as released, its container image, the install script and the Helm chart this site serves.
Out of scope
Denial of service and load testing; social engineering or phishing of anyone; physical attacks; the services we use (Vercel, Neon, Resend, Anthropic, Google, GitHub) — report those to them; a self-hosted install whose weakness is only how its operator configured it; scanner output with no demonstrated impact.

What we ask of you

Test against your own account and your own installs.
Do not access, change or delete data that is not yours. If you reach someone else's, stop, tell us what you saw, and do not keep it.
Do not degrade the service for anyone else, and do not send mail to other people through our forms.
Give us a reasonable time to fix the problem before you publish. We aim for 90 days from your report, and will agree a date with you.

What you can expect

Acknowledgement
Within 3 working days.
Assessment
Whether we can reproduce it and how serious we think it is, within 10 working days.
Updates
At least every 30 days until it is fixed.
Fix
Within 90 days for anything we accept, or an agreed date if it needs longer. The fix ships as a new release, with an advisory on the Trust centre.
Credit
In the advisory, under the name you choose, if you want it. We do not run a paid bug bounty.

Safe harbour

If you make a good-faith effort to follow this policy, we will treat your research as authorised. We will not bring or support legal action against you for it, under computer-misuse law or otherwise. For that research, we waive the restriction on probing the site in section 3 of the Terms of Service, and sections 3(c) and 3(d) of the Community Edition Licence (working around licence checks, and reverse engineering) — this policy being our written permission for that research and nothing more. If someone else brings action against you for research that followed this policy, we will make it known that it was authorised.

This covers research into our site and our software, not the services of the providers we use, and it does not cover using what you find for anything but reporting it to us.

WHAT THESE PAGES ARE ABOUT

Talon StudioSelf-hosted detection engineering
Create a Talon Labs accountA free Community key for Talon Studio