Support


In the app
Section titled “In the app”The Support page, at /support, has two
tabs. Feature requests is the public board: if you want us to build
something, that is where it goes, and other brewers can vote for it. See The
feature-request board. Your conversations is for everything else. Each one is a private thread
between you and us. (Old
/settings#support links still work; they land you on your conversations.)
On Your conversations, pick what it is about, write a line and a message, and send. Our reply shows up in the same thread. Either of us can add to it, and you can close it when you’re done. Replying to a closed thread opens it again.
We email you when there’s a reply, but the email only has a link, not what we wrote. Replying to that email won’t reach us.
You can have five conversations open at once. Close one and you can start another.
Screenshots
Section titled “Screenshots”Attach up to three images per message, on the first message or on any reply. Each can be up to 8 MB, as PNG, JPEG or WebP, which covers what the screenshot key makes on any operating system. We don’t resize them, so the text in the picture stays readable.
They’re private. Only you and Beerwright support can open them. They aren’t public or in the gallery, and a link to one won’t work for anybody else.
An account can store 50 MB of attachments across all its conversations. Past that, your message still sends, but we can’t accept the image.
Deleting your account deletes your screenshots. We keep the conversations themselves with your name and email address removed, because a support thread is often about a refund or something we promised, and we need to keep that. Screenshots aren’t needed for that, so we delete them.
If you can’t sign in, you can’t use the in-app section, but you can still reach us at the address below.
One person reads everything sent to it. There’s no ticket queue and no bot.
Write to it about any of these: a bug, a billing or refund question, a privacy request, or a security disclosure. If what you have is something you would like us to build, put it on the feature-request board instead. It’s public, other brewers can vote for it, and the votes decide what we build next.
What to include
Section titled “What to include”You don’t need to write anything formal, in the app or by email. But these details save us asking:
- A bug — what you did, what happened, and what you expected instead. The recipe name helps; a screenshot of the vitals rail helps more, and in the app you can attach it.
- A number that looks wrong — open the explain popover behind it (every headline figure in the vitals rail has one) and tell us what it says. It names the formula behind the number, which often answers the question straight away. The FAQ may resolve it before you write at all.
- A billing question — email from the address on the account, or say which address it is. A Paddle receipt number helps but is not required.
- A refund — say what you want refunded. The refunds policy is the shorter read.
Things you can answer yourself
Section titled “Things you can answer yourself”- Your subscription, card, invoices or canceling — Settings → Account → Plan → Manage billing opens Paddle’s portal, where you can manage all of that. See Plans, billing and trial codes.
- “Why is my FG so high?” and questions of that shape — the assistant reads your actual recipe and runs the same calculations the app does. ⌘J.
- “Where did my recipes go?” — check the sync indicator in the sidebar first. Guest means the workspace on this device is not the one on your account. Offline explains all five states.
Related
Section titled “Related”- The feature-request board, for asking us to build something.
- FAQ, for the questions that come up most.
- Glossary, for a word one of these pages used without explaining.
Something wrong on this page? Tell us.