Rally Point - Privacy Policy
Rally Point is made by one person. This policy describes exactly what the game sends, when it sends it, and who can see it. It describes the game as it actually behaves - not a generic template - and it is kept in step with the code.
Who is responsible
Hugh Shelton, sole developer of Rally Point, is the data controller for the personal data described here. Contact: support@rallypointgame.com.
The short version
- There are no ads, no advertising identifiers, no third-party analytics SDKs, and no tracking of any kind inside the game or on this page.
- Nothing is ever sold, rented, or shared with advertisers or data brokers.
- Three things can leave your machine: a bug report you send, an automatic crash report, and - if you play the online cup - your Steam name and Steam ID.
- Everything else the game measures is anonymous and aggregate, and goes only to Steam.
1. Bug reports you send
The game has a "Report a Bug" form in the settings/pause menu and on the game-over screen. It transmits only when you fill it in and press send. If you never use the form, it never sends anything.
When you do press send, the report contains:
- Your message - the text you typed - and the category you chose (Crash, Stuck / Hang, Visual, Balance / Design, Co-op, Suggestion / Idea, General Feedback, or Other).
- Your Steam display name (your persona name, as shown to your friends), so a reply is possible. Your numeric Steam ID is not included; it was removed from bug reports on 9 August 2026.
- Build and system information: the game version, your operating system (Windows, macOS, Linux, or Steam Deck), and your local date and time.
- The state of your run: the current game state and room, act, campaign progress, the run's random seed, which hero you picked, endless loop and ascension level, coins, hit points, and your full deck as a list of card IDs.
- Your game settings: window mode, vsync, screen shake, hover tips, and music and effects volume.
- Performance figures: current and real frame rate.
- Co-op session details, if you are in a co-op or versus session: the session ID, your slot, the number of players, the peer ID, and the internal turn counter.
- Diagnostic log tails - up to about 256 KB from the end of each of the game's error log and network logs.
About those logs. They are freeform diagnostic text written by the game as it runs - error messages, stack traces, and networking events. They are not a structured or filtered dataset, and they are the part of a report we can least precisely describe in advance. They are not designed to contain personal information and in normal play they do not, but because they are freeform we cannot promise that a stray file path (which on Windows usually contains your account name) or a co-op peer identifier never appears in one. If that concerns you, do not send a bug report; nothing else in the game attaches them.
Where a bug report goes
The report is sent over HTTPS to a relay we run on Cloudflare Workers, which forwards it - unchanged - into a private Discord channel that only the developer reads. The relay exists so that the credential for that channel is not shipped inside the game. Reports are not published, and they are not visible to other players.
2. Automatic crash reports
This one is not player-initiated, and we want to be plain about that. If the game crashes, it writes a report to your disk as it closes, and the next time you launch the game that report is uploaded automatically, without asking you. A crash cannot upload itself - by the time the handler runs there is nothing left to send with - so the report has to wait for the next launch. The crash dialog itself tells you this at the moment it happens.
An automatic crash report contains the same snapshot listed in section 1 above (including your Steam display name and run state), plus the error message and the stack trace of the crash, plus the tail of the error log. It contains no typed message, because you were not asked for one. It goes to the same relay and the same private Discord channel.
Delivery is attempted at most three times; after that the report is deleted from your machine unsent.
There is currently no setting that turns automatic crash reporting off. We
would rather say so than list an option that does not exist. What you can do is delete the report
before it is sent: it sits on your own machine as crash_pending.txt in
%LOCALAPPDATA%\rtt\ between the crash and your next launch, and deleting that file
stops it going anywhere. You can also write to us and we will delete any report we have already
received.
3. The online cup (Skirmish Cup)
Rally Point includes a recurring online tournament. Its results are shared through a second Cloudflare service we run. If you enter a cup, the game sends:
- Your Steam display name;
- Your numeric Steam ID, used as the stable key for your row so your result updates rather than duplicating (if you are playing without Steam, a random local ID is generated and used instead);
- your results for that event: placement, field size, wins, losses, round, and the game build number.
Your Steam display name is published publicly. Cup standings are served as a public web page so they can be shared in the community Discord. Anyone with the link can see the names and results of everyone in that event. Your numeric Steam ID is stored but is not shown on the public page.
This data is stored in a Cloudflare D1 database. The online cup is active by default in the full game. It is disabled entirely in the demo build, which never contacts the cup service. If you do not want to appear in the standings, do not enter a cup - and if you already have, contact us and we will remove your rows.
4. Anonymous game statistics
Rally Point records aggregate gameplay statistics - things like how often a card is played, or how many players reach a given act - through Steam's own global stats system.
These are counters only. No account link, no name, no identifier, and no IP address is attached to them, and they are not sent to any server of ours. We can read only the global sum across all players; we cannot see an individual player's contribution. Even measurements that would normally require identifying you, such as whether a player returns a week after installing, are worked out on your own machine and reported as a single anonymous "+1" to a global counter.
Because this pipeline contains no personal data, there is nothing here to opt out of, request, or delete. An earlier telemetry system that did transmit account identities has been removed from the game entirely - it has no address to send to and no code to send with.
5. Multiplayer
Co-op and versus matches are carried over Steam's peer-to-peer networking. To play together, your Steam ID and display name are necessarily visible to the player you are matched with, in the same way they are in any Steam multiplayer game. This is handled by Steam, not by us, and is covered by Valve's Privacy Policy. We do not operate a game server and do not record your matches.
6. Why we collect this, and our lawful basis
Under the UK GDPR and EU GDPR, we rely on:
- Legitimate interests (Article 6(1)(f)) for bug reports and crash reports. The interest is diagnosing and fixing faults in the game, and being able to reply to the person who reported one. We have limited the data to what a diagnosis actually needs - which is why the numeric Steam ID was removed from bug reports - and reports are read only by the developer.
- Performance of a contract / your request (Article 6(1)(b)) for the online cup. Entering a shared competition and appearing in its standings is the service you asked for; it cannot be provided without publishing a result under a name.
The anonymous Steam statistics in section 4 are not personal data, so no lawful basis is required for them.
7. Who else can see it
We do not sell, rent, or share your data with advertisers, data brokers, or any third party for their own purposes. The only other parties involved are the services that carry or store the data on our behalf:
- Cloudflare - hosts the relay, the cup service and its database, and this page. As with any web request, Cloudflare processes connection metadata including your IP address in order to deliver the request.
- Discord - hosts the private channel that bug and crash reports are delivered into.
- Valve / Steam - provides the display name, the statistics system, and the multiplayer networking.
We may also disclose data where we are legally required to. Our services are hosted on infrastructure that may process data outside your country, including in the United States.
8. How long it is kept
- Bug reports and automatic crash reports: deleted within 12 months of being received.
- Online cup entries: your name, ID, and results for an event are deleted within 90 days of that event finishing.
- Anonymous Steam statistics: retained indefinitely as aggregate counters, since they contain no personal data and cannot be traced to anyone.
9. Your rights, and how to exercise them
If you are in the UK, the EU, or another region with comparable law, you have the right to ask for a copy of the personal data we hold about you, to have it corrected or deleted, to restrict or object to our processing of it, and to complain to your data protection authority (in the UK, the ICO).
There is no deletion button inside the game. Rally Point currently has no in-product way to review or erase what you have sent. Requests are handled by hand, by email. We would rather say that plainly than imply a self-service flow that does not exist.
Email support@rallypointgame.com and tell us your Steam display name, and roughly when you sent the report or played the cup. That is enough for us to find and delete it. We will respond within 30 days. We do not ask you to prove your identity with documents; if a request is ambiguous we will ask a follow-up question rather than act on the wrong data.
10. Children
Rally Point is not directed at children and we do not knowingly collect personal data from them. Steam requires its users to be at least 13 years old, and the game is distributed only through Steam. If you believe a child has sent us a bug report, contact us and we will delete it.
11. Changes to this policy
If what the game collects changes, this page changes with it, and the date at the top is updated. Material changes will be noted in the game's Steam news posts. This page is the current version; there is no archive of previous ones.