---
title: "Reporting a Vulnerability"
description: "How to report a security issue in Katami, what we promise in return, and our commitment not to pursue researchers acting in good faith."
canonical_url: "https://katami.io/legal/disclosure"
last_updated: "2026-09-24"
---

> Index of every page on this site: [llms.txt](https://katami.io/llms.txt)

Report anything you find to [security@katami.io](mailto:security@katami.io).
This policy is also published at
[/.well-known/security.txt](https://katami.io/.well-known/security.txt), per RFC 9116.

## In scope

- **The Katami app for macOS** — the current release and the current beta.
- **katami.io** and **bespokebyte.io**.
- **The License Manager** — `licenses.bespokebyte.io`.
- **Our API** — `api.bespokebyte.io` and `models.bespokebyte.io`.

## Out of scope

- **Services we use but do not run** — Paddle's checkout and payment pages,
Apple, Resend and Linear. Please report to them directly; Paddle, for one,
runs its own program.
- **Findings with no demonstrated impact** — missing headers or "best
practices", outdated libraries, or scanner output without a working proof of
concept.
- **Denial of service** and volumetric testing of any kind.
- **Social engineering** of us, our customers, or anyone else, and physical
attacks.
- **Email configuration reports** (SPF, DKIM, DMARC) without a demonstrated
spoof that reaches an inbox.
- **Account enumeration** through sign-in. Our sign-in says whether an address
holds a license, deliberately, so a customer who typed the wrong address is
told so.

## Please

- Test only against your own license, your own Macs and your own data.
- Stop as soon as you reach data that is not yours, do not keep it, and tell us.
- Give us a reasonable chance to fix the issue before telling anyone else.
- Include enough detail for us to reproduce it — steps, a proof of concept, and
the versions involved.

## Please do not

- Run automated scanners or brute-forcing tools against production.
- Access, change or delete data that is not yours.
- Degrade the service for anyone else.

## Safe harbor

If you act in good faith under this policy, **we consider your research
authorized, we will not pursue or support legal action against you**, and we
will not ask your employer or anyone else to. If a third party takes action
against you over research that followed this policy, we will make clear that it
was authorized.

If you are unsure whether something is in scope, ask first. A question costs
nothing, and this protection is easier to give in advance than to argue about
afterward.

## What to expect from us

<table>
<thead>
  <tr>
    <th>
      
    </th>
    
    <th>
      
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      Acknowledgment
    </td>
    
    <td>
      within <strong>
        3 working days
      </strong>
    </td>
  </tr>
  
  <tr>
    <td>
      An assessment, with our view of severity
    </td>
    
    <td>
      within <strong>
        10 working days
      </strong>
    </td>
  </tr>
  
  <tr>
    <td>
      Progress updates
    </td>
    
    <td>
      at least every <strong>
        14 days
      </strong>
      
       while it is open
    </td>
  </tr>
  
  <tr>
    <td>
      Fix, or an explanation of why not
    </td>
    
    <td>
      as fast as the severity warrants
    </td>
  </tr>
  
  <tr>
    <td>
      Disclosure
    </td>
    
    <td>
      coordinated with you, normally within <strong>
        90 days
      </strong>
    </td>
  </tr>
</tbody>
</table>

We are a very small team, so those are commitments about communication rather
than a promise that every fix is instant. If we are going to miss one, we will
tell you before it slips rather than afterward.

## Recognition

We do not run a paid bug-bounty program. We credit every reporter who wants
to be named, in the release notes of the fix, and we say plainly what they
found.

## Sitemap

See the full [sitemap](https://katami.io/sitemap.md) for all pages.
