Get in touch
Corrections, missing vocabulary, tool bugs, Lab submissions and licensing questions — all welcome.
What to send where
One request: if you are reporting that a tool failed on a particular link, include the link. Almost every download bug comes down to a page shape we have not seen, and without the URL there is nothing to reproduce.
| Subject | Include | Typical reply |
|---|---|---|
| Correction | The page URL and the specific sentence that is wrong | Within a few days; corrections jump the queue |
| Tool bug | Tool name, browser and version, what you did, what happened | Within a week, longer if it needs a rewrite |
| Missing vocabulary | The term and a prompt-ready example of how it is used | Batched into the next reference update |
| Lab submission | Hypothesis, prompt pair, rubric and your score sheet | Reviewed for method, then published with credit |
| Licensing / reuse | What you want to reuse and where | Usually a quick yes with an attribution request |
Message form
This site has no backend and stores nothing you type. The form below assembles your message locally and hands it to your own email program, where you can review it before sending — nothing is transmitted by this page.
Pressing Open in mail app builds a mailto: link from the fields and opens your default mail client. If nothing happens, your browser has no mail handler configured — copy the fields into webmail instead.
Response expectations
- This is a small project maintained in spare hours; replies are measured in days, not minutes.
- Corrections and reproducible bugs get answered first.
- We cannot help with account, billing or generation problems on any AI music service — those need the service's own support.
- We do not accept paid links, sponsored posts or guest articles, and those messages will not get a reply.
- We cannot give legal advice about rights in generated music.
Other routes
If your question is really a documentation question, the answer may already be written. The FAQ hub covers the questions we get most often, troubleshooting covers weak or wrong-sounding results, and the download troubleshooting article covers most failed downloads.
For questions about what this site does with data, the privacy page is the short answer: almost nothing.