Here is what this website does, in the order your browser does it: it loads Google Analytics, it may keep a few settings on your device so the dice look the way you left them, and, on the three pages that carry the 3D roller, it fetches the library that draws the dice from a public CDN. That is the whole list. Our Android app is a different piece of software with its own policy, linked at the bottom.
On this page
The short version
- No account. There is no sign-up, no login, and no profile. The dice roller works as soon as you open it.
- No ads. No ad network, no ad script, no advertising profile built from your visit.
- No payment. Everything on this site, and the Android app, is free. We never ask for card details.
- Nothing you type. There is no contact form, no comment box, and no search field anywhere on the site. There is no text field to fill in, so there is nothing typed for us to receive.
- Your rolls stay on your device. The dice are simulated in your own browser. The numbers you roll are never sent to a server.
- One measurement tool. Google Analytics, used in aggregate to see which pages and features get used. Details below.
What Google Analytics measures
Every page of this site loads Google Analytics 4 through Google's gtag.js script, served from www.googletagmanager.com. Our measurement ID is G-BJJ9X4GLZZ. You can see it in this page's source, and you are welcome to check that nothing else is in there.
We use it for one thing: understanding, in aggregate, how the site is used, so we know what to write next and what to fix. Which pages people read, whether anyone ever presses the fullscreen button, whether the game presets get used at all. We do not try to identify individual visitors, and Google Analytics does not tell us who you are.
Alongside the standard page view (page URL, the page that referred you, and basic device, browser and screen information), the site sends a small set of named events when you use the roller:
| Event | What it records |
|---|---|
roll_dice | A roll happened: the number of dice, how many were held, which types were on the table (for example "2d6+1d20"), and the active game preset if there is one. Not the numbers rolled. |
hold_toggle, turn_ended | That a die was tapped to hold it, and that a turn ended under a game's rules. |
game_selected, game_deeplink_arrival, game_rules_click | Which game preset was picked, whether you arrived on a ?game= link, and clicks through to a rules page. |
roller_sound_toggled, roller_fullscreen | Use of the sound and fullscreen buttons. |
dice_manager_opened, dice_type_picked, dice_color_picked | Use of the pencil button and which die type or color was chosen. |
nav_app_click, play_click, qr_card_shown, app_banner_* | Clicks on links to our app page and to Google Play, and whether the install banner or QR card was shown or dismissed. |
dice_engine_failed | The 3D engine did not start, so we can tell how often that happens. |
roll_all_held_noop, roll_must_hold_noop | Roll was pressed but nothing rolled: every die was held, or the game's rules required a set-aside first. |
app_page_install_click, app_page_prompt_accepted, app_page_prompt_dismissed | On the app page, on Android: the install button was tapped, and whether the Play install dialog that opens was accepted or dismissed. |
Google Analytics uses the IP address your browser connects from to work out an approximate location, usually city level. Google states that for visitors in the EU, Switzerland and the UK it does not log or store individual IP addresses at all: the address is used to derive the location and is then discarded. What Google does with the data it processes is set out in Google's privacy policy and in Google's documentation on IP addresses in Analytics.
Prefer not to be counted? Nothing on this site depends on analytics. Every call to it is optional and the roller works the same without it. A tracking blocker, a browser that blocks third-party scripts, or Google's own Analytics opt-out add-on will all stop it, and you will notice no difference.
Cookies
We set no cookies of our own. The site's own preferences use browser storage instead, which is described in the next section.
Google Analytics does set cookies, on this domain, when its script loads. Per Google's own cookie reference the relevant ones are:
| Cookie | Purpose | Expires |
|---|---|---|
_ga | Distinguishes one browser from another so repeat visits are not counted as new people. | 2 years |
_ga_<stream id> | Keeps the session state for this specific Analytics data stream. | 2 years |
You will not see a cookie banner here. That is a description of how the site is built, not a legal opinion on your behalf: the only cookies in play are the two analytics ones above, and blocking them (through your browser's settings, a content blocker, or the opt-out add-on mentioned earlier) costs you nothing on this site.
What the site keeps in your browser
The roller remembers how you left the table, so you do not have to rebuild it every visit. It does that with localStorage, which is a small store inside your own browser. Nothing in it is ever sent to us or to anyone else. It is only read back by the same page on the same device. Clearing your site data removes all of it, and if storage is blocked the site still works, but your settings will not survive a reload.
Three pages carry the roller and so do this remembering: the homepage, the classroom dice roller and the 4d6 drop lowest page. These are the exact keys the site writes:
| Key | What it is for | Written on |
|---|---|---|
dice_count | How many dice are on the table. | The three roller pages |
dice_types_json | Which type each die is (d6, d20, Fudge, and so on). | The three roller pages |
dice_colors_json | Which color each die is. | The three roller pages |
dice_add_type | The die type pre-selected next time you open the add-a-die dialog. | The three roller pages |
dice_add_color | The color pre-selected in that same dialog. | The three roller pages |
dice_recent_colors | Up to ten colors you picked recently, for the "recent" row in the color picker. | The three roller pages |
dice_sound | Whether the rolling sound is on or off. | The three roller pages |
dice_fast_roll | Whether the Fast roll button is switched on, which lands every die at the same moment instead of one after another. | 4d6 drop lowest only |
dice_app_banner_snooze_until | A timestamp: until when the Android install banner should stay hidden after you dismissed it, or after you installed the app from it. | Any page except the app page |
That is the complete list. Every key but the last one belongs to the roller, so content pages such as the dice games guides or dice probability write nothing at all. The only exception is that last key, which any of them can write if you are on Android and dismiss the install bar there.
The Android install prompt
If you open this site on Android, a small bar offering our free app can appear at the bottom of any page except the app page, which is its own install pitch and so never shows the bar. Two things about it:
First, the Install button prefers your browser's own Google Play install dialog, so the install happens over the page instead of sending you somewhere else; where that dialog is not available it opens the Play Store listing instead. Dismissing the bar with the × stores the timestamp described above and keeps it away for fourteen days. Links from this site to Google Play carry a campaign label (the site's domain, the word "website", and which button you pressed) so we can tell in Play Console which pitch works. It contains no identifier for you.
Second, the page asks your browser a question through navigator.getInstalledRelatedApps(): "is the app already installed?" This browser feature can only ever report back about the one app our web app manifest names, the answer never leaves your browser, and we use it for one purpose: to stop pitching an app you already have. To be precise, the app currently declares its matching link only for our Dutch site, dobbelsteen.app, so on this domain that check comes back empty today and the banner shows regardless.
Once you tap through to Google Play, you are on Google's site under Google's terms, and once you install the app, the app's own policy applies.
Other servers your browser contacts
Loading a page always tells the servers involved your IP address and something about your browser. That is how the web works, not a choice this site makes. So here is every host beyond our own that your browser contacts. "The three roller pages" below means the same three named in the previous section: the homepage, the classroom dice roller and the 4d6 drop lowest page.
| Host | What it delivers | Where |
|---|---|---|
www.googletagmanager.com | The Google Analytics script described above. | Every page |
unpkg.com | Three.js, the open-source 3D library that draws and animates the dice. | The three roller pages |
www.gstatic.com | Google's Draco decoder, which unpacks the compressed 3D dice model. | The three roller pages |
play.google.com | The Google Play listing, only if you click a Play link, badge or QR code. | On your click |
Sites we link out to, such as en.wikipedia.org | The sources cited in our game and history articles, and the Google pages linked from this policy. | On your click |
Everything else comes from dice-together.com itself: the stylesheet, the dice models, the rolling sound, the icons and the QR images. There are no web fonts (the site uses the fonts already on your device), no social media embeds, no comment system, no A/B testing tool, no session recorder, and no advertising or affiliate scripts.
The Android app has its own policy
The Dice Together Android app is separate software running on your phone or TV, so it has its own privacy policy, which is the one Google Play links to. It is a different document because it covers different things: the app uses Google's Firebase for analytics and crash reports, which this website does not.
Looking for the app's policy? It lives at privacy.txt. The page you are reading now covers only the website.
Questions, and changes to this page
If something here is unclear, or you think this page does not match what the site does, please tell us. Email dice@itl.dev and we will answer.
If the site starts doing something new, this page gets rewritten to say so; we would rather keep it accurate than keep it broad. Last updated: August 24, 2026.