#Game analytics and privacy

#What you see

The project page shows how your published game is doing: sessions, median load time, errors, and a daily chart. Stage and prod are counted separately, so testing doesn't skew your numbers. The Overview shows a card per published game.

• Today's numbers are live. A session shows up within seconds of someone playing, on the project page and on the Overview card. Earlier days are totalled overnight (UTC days).
• Today (live) on the project page shows today's sessions, plays, median load, average session length and errors for the environment you're looking at. It refreshes every 30 seconds while the page is open. Prod and stage are counted apart: stage plays are under Stage.
• No numbers from a game you published a while ago? If the project page says Republish to start collecting analytics, the live build was made before games sent analytics. Build and publish it again (to stage or prod), and new sessions start counting. Earlier plays of that build can't be recovered.
• One bad event doesn't lose a session. If a game sends something the server can't use, only that event is skipped; the rest of the session still counts.

#What a game sends

A published game reports a few events: loading started (with the device type, screen orientation and the game engine's version) and finished (with the load time), play started, scene changes, errors, and the session ending. Raw events are kept for 90 days, then only daily totals remain.

#What it never collects

• No cookies, and nothing stored on the player's device.
• No IP addresses, user agents or other personal data.
• Each page load gets a random session id that isn't stored or reused.

Because no personal data is kept, games don't show a consent banner.