Contact BoardRepo

General questions and feedback

[email protected]. Bug reports, a board that rendered wrong, a format you want supported, a feature you need, or a question the FAQ did not answer. If a specific board is involved, send the link: a public or private-link URL lets us open exactly what you are looking at, which usually turns a day of back-and-forth into one reply.

Security

[email protected] for anything that looks like a vulnerability: access to a board you should not be able to reach, a way around a private link or password, or something in an upload that escapes the sandbox it is processed in. Tell us what you did, what you expected, and what happened. The disclosure policy is on the security page, and the machine-readable version is at /.well-known/security.txt.

Please do not open a public issue for a vulnerability before it is fixed.

Privacy and your data

[email protected] to copy, correct, export or delete personal data, or to ask what is held about you. The privacy policy covers what is collected and why.

Takedowns and licensing

[email protected], with the board URL and what the problem is. Part of the library was imported from public GitHub repositories, so if a board of yours is here and you would rather it were not, say so and it comes down. If it is yours and you want to keep it, you can claim it instead and take over the page.

Building against BoardRepo

Connecting an assistant, reading boards from code, or wiring up the MCP server: start with the developer and agent docs. If you want something the read surface does not offer yet, email [email protected] and say what you would build with it. That is what decides what gets built next.