Help and feedback
Ask a question, suggest a change, report a bug or reach us in private. Each has its own place.
The forum and the bug tracker are public
Never post an unreported finding, a report draft, an API key, a connection token or a recovery code. To ask about a verdict, describe what happened and leave out the target and the bug.
A question
How to do something, or why a review said what it said. Ask in Q&A
An idea
Something the product should do, or do differently. Post it in Ideas
A bug
Something does the wrong thing. Open a bug report
Your account or a payment
This one is private. Write to support@bountyoperator.com
Ask a question
Q&A is for questions about using Bounty Operator: a review type, a provider or a model, the MCP server, a verdict you do not follow. An answer that settles the question is marked, so the next person finds it.
You need a GitHub account to post. Reading needs none. With no GitHub account, write to support@bountyoperator.com instead.
We keep no files, prompts or results, so nobody here can look your review up. Say which review type you ran, on which provider and model, and what came back.
Suggest a change
Ideas is for what the product should do next: a review type, a check, a platform template, a tool. Say where in a hunt it comes up and what you do today.
Vote on the ideas of others, so the ones most wanted stand out. Releases are posted in Announcements and listed in the changelog.
Report a bug
The bug report form asks where it happened, the version, the steps and what came back. The version is on the changelog; an error message is worth pasting word for word.
A review that reads wrong is not always a bug. If the model missed something or judged it badly, Q&A is the better place, and the guide covers a model that refuses.
Account, payment and refunds
Write to support@bountyoperator.com about sign-in, a lost passkey, a charge or a refund. Email is private; the forum is not.
- A payment or a refund: give the receipt reference, so the subscription can be found. Leave out card numbers, API keys, recovery codes and private reports. The terms say when a refund is due.
- Cancelling: open Account and go to the billing portal. Access runs to the end of the paid week.
- A lost passkey: sign in with your recovery code and add a new passkey. We keep only a hash of the code, so we cannot read it back to you.
A vulnerability in Bounty Operator
A vulnerability in Bounty Operator itself is reported in private: through the report form on GitHub or to security@bountyoperator.com. The security page says what is in scope and how testing is to be done.
Share a win
Wins is for a hole the review caught before a triager did, or a report that paid. Post a finding only when the programme has resolved it and allows it to be told.