Privacy
This page says what Dispersed 3D counts, what it keeps on your own device, and what it sends to our server. It is written from the game’s code, and a build check fails if the two drift apart.
The short version. No account. No cookies. No ads. No analytics service. No third-party scripts. The game counts a few anonymous moments, and none of them can tell one visitor from another.
The anonymous counts
We want to know where people give up, so the game counts a few moments. Each count is one small request for a file the page already asks for, data/starlink.json, with four things added to the address:
m=is a word for what happened.s=is the source. It is theutm_source,viaorfromtag on the link you opened. If there is none, it is the site you came from (the host only, never the path or the query). If there is none of that, it is the worddirect.t=is the time since the page started loading, rounded to a tenth of a second.d=is one letter:pfor a phone-sized screen,dfor a desk-sized one. No screen size is sent.
The words are:
load ready tapfirst tapplay tapother auto cardpick welcomeclose roll wheel wheel30 made camp night2 out callshown callpick callreveal ndoffer ndcard spot spotgo take rate arrive alive camptap pad view trip4 watch share
They mean things like: the title’s button turned on, you tapped a title button, the truck first moved, you made your first camp, you slept your first night. spot and spotgo mean a link to a spot opened on its ground, and then the Drive to tonight’s camp button tapped. take means a person ended a self drive (the Stop button, or a key or the stick), rate that the speed button was used, and arrive that a drive reached its camp. alive that a real touch, click or key reached the title before the game began, camptap that a person pressed Camp at a camp for the first time, pad that a game pad was connected, view that a person changed the camera, and trip4 that a person tapped the first morning’s Start the four-night trip button. watch and share mean a replay link or a share link opened.
- Each word is sent once per page load, and only after the thing really happened.
loadis sent only from a device that has nothing of ours stored yet.- There is no ID and no cookie. Nothing the game adds to the request tells one visitor from another. Our server log does hold the usual IP address for the request (see “Server logs” below), and the counts do not use it to tell visitors apart. The game does not read the answer.
- Only live visitors send them. Automated browsers, crawlers and link previews do not.
- They are not sent in a challenge, an AI seat, a replay, a trip link or a camp share link. The one exception is a single
watchorshareword when a replay link or a share link opens, and never beside a trip link or an AI seat.
What stays on your device
The game keeps some things in your browser’s own storage. They stay on your device. The game does not send them to us.
- Your settings: sound, names on the map, the driving aids and similar switches.
- The view you last used, and the rig you picked (truck or van).
- The last forest you played, which forests you have opened, and which nights you camped.
- A small picture of each night you camped, for your Season Book. The game keeps at most 30.
- Which daily games you finished.
- Which one-time tips you have already been shown, so each is said once.
- Which forests you saved for offline play, and the files saved with them.
- For a challenge trip: the trip code and its private edit key, and the bot name, model and “plays for” words you typed.
A visit from a share link keeps nothing on your device. You can clear all of this in your browser’s site settings.
What goes to our server
- The page and its files. Like any web page, this one asks our server for files. See “Server logs” below.
- The count of other players. Once a night at camp, the game asks our server how many other people camped at that spot. It sends the forest’s name and no credentials, and gets back a number. It does not ask in a challenge or a share link visit.
- Sharing a link. The Share and Copy buttons use your phone’s share sheet or your clipboard. The link goes where you send it. It does not pass through our server.
- Challenge trips and the AI leaderboard. These are for people and AI assistants who play a set challenge. A trip is saved on our server as its list of moves, with the challenge, the game build and the names you typed. You get a trip code and a private edit key. We keep only a scrambled copy of the key. The service stores no IP address. When you press Submit, your run goes to the leaderboard to be checked by hand.
- An AI seat. If you let an AI play through a seat, the seat holds the turns and moves in the server’s memory and writes nothing to disk. A seat ends after 2 hours with no new turn or move, and always after 6 hours. The server allows 300 open seats at once, and 10 new seats an hour from one address. To enforce that, it keeps each address only as a scrambled value, with a new random key each time the service starts, and only as long as the limit needs. The seat service writes no request log.
Server logs
Our web server keeps an ordinary access log. For each request it records the time, the file asked for, your IP address and your browser’s name. That is how the anonymous counts above are read: from the requests for data/starlink.json. The counting script scrambles IP addresses with a random key it throws away when it finishes, and prints none.
Trackers and third parties
The game loads no analytics, no ads and no third-party scripts. Every script and file comes from our own site. The weather and the other live data are fetched by our server and saved there, so your browser never asks those agencies directly.
Credits
Road miles to town are from © OpenStreetMap contributors. Every other source and its license is on the sources page.