Bloodtide is an indie browser game served at bloodtide.io. This page explains what data the site collects, why, where it lives, and what rights you have over it. The site is operated as a hobby project by an individual based in the Netherlands. Contact for privacy matters: [contact email TBD].
When you finish a run and a score is submitted, the following fields are sent to our database:
These rows are public by design — the leaderboard is a public log book. We do not collect your IP address alongside leaderboard rows, and we do not link captain names to people.
The site uses Cloudflare Web Analytics, which is cookieless and does not track individual visitors across sites. It records aggregate counts of page views and basic referrers, with no personally identifying information. You can opt out from the privacy settings panel inside the game.
Game settings (audio volumes, control bindings, captain name draft, tutorial-completed flag) live in your browser's localStorage. They never leave your device unless you explicitly submit a score.
Our processing of your captain name and run statistics is grounded in legitimate interest: the leaderboard is a core part of an arcade-style game and players who post a score are consenting to public display by the act of submitting. You can request erasure at any time (see "Your rights" below).
Cloudflare Web Analytics relies on the legitimate interest of understanding traffic without identifying users; it sets no cookies and stores no individual records. You may still opt out.
Under the GDPR, you have the right to:
Send any of these requests to [contact email TBD]. Because we hold very little data per captain, we can usually action requests within a few days. We may ask for the captain name(s) you used and a rough time window so we can find the right rows.
Bloodtide is not directed at users under 16 and we do not knowingly collect data from minors. If you are a parent or guardian and believe your child has submitted a score you would like erased, contact us and we will remove the relevant rows.
Each provider has their own privacy practices, which apply to the data they handle on our behalf as data processors.
Material changes will be reflected in the "last updated" date at the top of this page and listed in the changelog below. Trivial edits (typos, clarifications) may be made silently.