Contact
One address, read regularly. Bug reports, feature requests, advertising questions, and takedown requests all land in the same inbox.
There is no support ticket system and no promise of a reply time — it is a small project — but every message is read.
Before you write
- Bug reports — say what you pasted (or a small piece of it), what you expected, and what happened instead. The exact document that breaks the repair engine is the most useful thing you can send; redact anything sensitive first.
- Feature requests — describe the job you are trying to do, not just the button you want.
- Advertising — mention the page and what you saw. Ad placement and policy questions are handled directly.
- Data removal — nothing is stored server-side, so a document shared through a CurlyBrackit link can be revoked by asking for the link to be taken down; include the link and why.
Please don't send
Real credentials, API keys, or personal records. CurlyBrackit never needs them to reproduce a problem, and email is not where they belong.
For privacy details, see the privacy policy.