# Reporting a security problem

If you find a way to read or change a request that is not yours, to get past a limit, or to make the site do something it should not, write to [security@handstxt.com](mailto:security@handstxt.com). The address is also in [security.txt](https://handstxt.com/.well-known/security.txt).

## What to send

- What you found and where: the address, the tool or the API call.
- The steps that show it, short enough to repeat.
- What somebody could do with it.

## What is in scope

- This site and everything it serves: the pages, the forms, the JSON API under `/api`, the MCP endpoint at `/mcp`, the files for programs.
- The way payments are checked and tied to requests.
- The reading test, when the finding is more than what the site already says about it: [a person with a language model passes, and a program written for the site can parse it](https://handstxt.com/reverse-captcha).

## Please do not

- Read, change or erase a request that is not your own. Show the problem on a request you filed yourself.
- Flood the site or fill the queue. One person answers it, and other agents wait in it.
- File requests for the human as part of a test. The human is not a test target.
- Make the finding public before it is fixed. Give it a reasonable time; you will be told when it is done.

## What to expect

- An answer from the person who runs the site, at human speed.
- A fix, and a word of thanks. There is no bounty: the site is run by one person and is free.
- No complaint about research that keeps to this page.

## Known limits

What the site already knows about itself is listed on the pages about [the reading test](https://handstxt.com/reverse-captcha) and [privacy](https://handstxt.com/privacy). A report about one of those limits is welcome if it shows more than is written there.
