Privacy at Rift Dice

Who is responsible

Michal Fuchs, Slovakia, is the controller. Contact: contact@riftdice.com.

What stays in your browser

With Accept, Rift Dice saves settings (including the Animated Roll choices), theme, board view, map visibility, an encoded board, seat names, your last submitted lobby player name, whether you closed the first-board hint and whether keyboard shortcuts are on in local storage. The encoded board includes names and owned champion lists. A Data Dragon version and check time can be saved in session storage. That cache is reusable for six hours and lasts for the browser's page session, which the browser may restore.

Your consent choice, version and date are saved when you choose. Room leader or player tokens and claimed seats are saved without optional consent so you can return to a room. Local storage has no timed expiry. See the fifteen keys and their cleanup rules on Cookies.

The optional browser receipt stores a build digest only after Accept; without Accept, the receipt stays in page memory.

What leaves your browser

Your browser connects to Riot's Data Dragon before you choose consent, to prepare to load images. Image and version requests also reach Riot, including your IP address and browser request information. Riot handles those requests under its own privacy notice. Other game data is served by Rift Dice.

Railway hosts the site in its EU West region in the Netherlands. On the Hobby plan, Railway keeps request logs for seven days. They include your IP address, user agent, request path, time and technical request details. A room request path includes its room ID.

Names and board settings can be included in shared board links. Anyone with a link can read its contents. Anyone with a live room link can see its board and player names. Shared copies can remain after the room ends.

What the server keeps

Live rooms hold board settings, names, owned champion lists, seat claims, access tokens and the creator's IP address in memory. A room ends 2 hours after its last action, or 8 hours after it was made, whichever comes first. The server removes ended rooms within about five minutes. Rooms end when the leader closes them or the server restarts, including each site update.

IP addresses used to limit room creation, actions and room lookups stay in memory with their timestamps for a few minutes after the last request, until the next cleanup, which runs every five minutes. Counts of open live connections per IP address are removed when its last connection closes.

No third-party scripts or ads

Rift Dice loads no third-party scripts and shows no ads. The app sets no cookies. It uses its own usage counter, described below.

Usage counting

Rift Dice counts page visits, reported rolls and room creation to understand site use. These counts do not cover every roll. The counter sets no cookie and does not read browser storage. It runs even with Only necessary.

The server hashes a random salt, the UTC date, your IP address and user agent into a 16-character hexadecimal value. It keeps daily hashes and their last counted roll times in memory to limit duplicate counts. This can link requests within a day and is not a promise of anonymity. The salt and hashes are replaced on the next counting or statistics request after the UTC date changes, or on a restart. They can remain past midnight until that request. They are not saved to disk. Daily totals without IP addresses, user agents or hashes are saved to disk with no automatic deletion period.

Build feedback

If you choose a thumb, we save daily up and down totals for the build. The saved fields are its item and starter IDs, mechanism, champion, role, map mode, direction and evaluation patch. We do not save individual votes, your address, user agent, client token or any hash in the feedback files. We keep the current and previous calendar quarter.

A browser receipt holds a build digest, not a person digest. It limits repeat votes for that build and UTC day. Clearing storage, another browser, concurrent tabs or reloading without Accept can allow another vote. This does not prove one vote per person. The server allows 20 attempts per second and one vote per build per second across all clients. Two people rating the same build in the same second can collide. A busy or unavailable server can refuse a vote.

Why we use data

Room data is used to provide the lobby and short link, which start when you roll after you select Accept, or when you select Share link [GDPR Article 6(1)(b)]. Request logs and IP rate limits serve the legitimate interest of keeping the site working and safe [Article 6(1)(f)]. Usage counting serves the legitimate interest of understanding site use [Article 6(1)(f)]. Saving optional preferences relies on your consent [Article 6(1)(a)]. You can withdraw that consent on Cookies.

Your rights

You can ask for access, correction, erasure or restriction of your personal data. You can object to processing based on legitimate interests. You can withdraw consent at any time without affecting the lawfulness of earlier processing. Write to contact@riftdice.com to make a request. You can complain to the Office for Personal Data Protection of the Slovak Republic or another competent supervisory authority.

How to clear your data

Select Only necessary on Cookies to stop new optional storage writes. Only necessary also keeps your rolls on this device: a room is made only when you select Share link. This does not delete saved values or stop the site from reading them. To remove browser data already saved, clear this site's data in your browser settings. This does not end a live room or remove shared copies. It can remove the token you need to control your room. The room leader can close the room before clearing browser data.

Contact

Contact the operator at contact@riftdice.com for questions or privacy requests.