This page is linked from inside the game, under Settings → Send Feedback. It covers where to send things and what to include.
Rushmark is made by one person. Everything sent here is read, and most of it is replied to, but not always quickly.
In short
- The most useful thing you can send is not a bug. It is “this section feels unfair” or “I wish the game did this instead”.
- Bugs are better posted publicly on Steam, where other players can confirm them and the answer stays findable.
- Anything with your purchase, your account or your personal details should come by email instead.
- Settings → Copy Diagnostics puts your version, platform and renderer on the clipboard. Paste it in. It saves a round of questions.
1. What is most worth sending
Crashes and broken things matter, but they are also the easiest to find without help — a crash on Android is reported automatically, and anything that stops the game outright tends to get found fast.
What is genuinely hard to discover from the outside is how the game feels:
- A section that seems unfair, or that you cleared without understanding why.
- A rule you had to work out for yourself that the game should have told you.
- A control, menu or screen that fought you.
- Something you expected the game to do that it does not.
- A time or a score that looked wrong.
None of that needs a reproduction case or a technical description. “Course 7 section 3 feels like a coin flip” is a complete and useful report.
2. Where to send it
Steam — public, and better for bugs
The Rushmark Community Hub is the right place for anything other players might also be hitting. A public thread means someone else can confirm it, the answer stays searchable, and ten people do not each report the same thing separately.
It is public, so post nothing there you would not want indexed.
Email — private, and for everything else
Use this for anything involving your purchase, your account, your personal details, or simply anything you would rather not post in public. On Android, Settings → Send Feedback opens your mail app with this address and your diagnostics already filled in.
Google Play reviews
Reviews are read and replied to, but they are a poor place to work a problem — there is no thread, and the reply is public. If you want something actually fixed, one of the two routes above will get further.
3. What to include
Press Settings → Copy Diagnostics and paste the result into your message. It looks like this:
Rushmark 0.9.27
Windows 10.0.26200
renderer: NVIDIA GeForce RTX 3060
backend: SteamManager
season: 1 stats: _prerelease
screen: 1920x1080
at: course_6
It deliberately contains nothing that identifies you. No account ID, no display name, no email address, and no file paths — a file path would carry your computer’s user name, and this block is built to be safe to paste into a public forum.
Beyond that, the useful things are what you expected to happen, what happened instead, and whether it happens every time.
4. Crashes
On Android, crashes are reported automatically. Google Play collects them with the technical detail already attached, so you do not need to do anything — though it is still worth saying what you were doing when it happened, because that part is not collected.
On Steam, nothing is collected automatically. A crash is worth reporting, with the diagnostics block above.
5. Purchases and refunds
Rushmark never handles your payment details, so refunds are not ours to issue:
- Steam — use Steam’s own refund request, under Help in the Steam client.
- Google Play — use Google’s refund process through the Play Store.
If a purchase went through and the game has not unlocked, that one is ours. Email us. On Android, Settings → Unlock the Full Game also restores a purchase Google already knows about.
6. Your data
What the game stores, who can see it and how long it is kept is set out in the Privacy Policy. You can delete everything from inside the game, or see Deleting your account.
Privacy questions specifically, including anything under POPIA or the GDPR, go to info@beyondbounds.co.za rather than the address above.