Privacy policy

Two kinds of people

Developers: people who sign in on this site and connect their game. Players: people who play a game whose developer added our analytics. Most players never visit this site, and many of them are children — so we collect as little as we can about them and never in readable form when it identifies them.

Developers: your account

A guest account is a random id kept in a cookie for 60 days. If you sign in with Google, we keep your name, email address, profile picture link, Google account id and the sign-in tokens Google returns. If you sign in with an email link, we keep your email address. For each signed-in session we keep the IP address and browser name (user agent) it started from, to keep accounts safe; sessions end after 60 days without use.

We keep a log of important actions (for example, who opened a game's player list, who deleted a game) so a team can see what happened. The log never holds players' names.

Players: what a game sends us

Our open-source SDK runs on the game's server, not on the player's device; its client part passes that server counts of how the game's own interface is used — never chat or what a player types. It sends: a pseudonym for each player (a code made with a key only the developer has — we cannot turn it back into a Roblox account); session start and end; whether the player is new, has Premium, and how they came (a friend, a link, a teleport); country and device type as Roblox reports them; purchases (item and price); changes of the game's own stats (the stat's name and by how much); steps the developer marks (for example, “finished the tutorial”) and key moments the SDK notices (equipping an item, changing team, a game attribute changing, a death); where on the map players walk, die and leave (cells of 16 studs, and for deaths and exits the point inside the cell to a tenth of a stud); frame rate and memory of devices and servers; how the game's menus and buttons are used (counts, paths made of the game's own element names, the text of buttons and the hints of input fields, and window layouts — position, size and colour of elements); names of players on the same server are taken out of all of it, and label texts and anything inside lists are not sent at all; server errors, with player names removed from object paths.

The player's Roblox UserId, user name and display name are encrypted on the game server with the developer's key before they are sent. We store only the encrypted text; the names are shown only in the developer's own browser.

We do not receive chat messages, passwords or payment details. We do not link a player across different games: each game has its own pseudonyms and its own key.

Who sees game data

Only the team of that game: owners and members see the player list; viewers see totals. In alerts sent to Discord or Telegram we send numbers only, never a player. Our team can technically reach the database to run the service, but player names stay encrypted there.

What we never do

We do not sell data. We do not show ads. We do not train AI models on players' data. We do not use data from Roblox's APIs to assess Roblox's own usage or business. We do not share a game's data with anyone outside its team, except the service providers below.

Service providers

Vercel (this site), Cloudflare (receiving data from games), Neon (database), Google (sign-in), Resend (sign-in emails), Roblox (only if a developer connects their Roblox account to import official numbers), Discord and Telegram (only alerts a developer turns on). They process data only to run their part of the service.

How long we keep it

Raw events: about 90 days (they are removed once their day is safely counted in the daily totals). Window layouts: until a window is not seen for 90 days. Daily totals, per-player totals, encrypted player names, interface counts and map heat: as long as the game stays connected, unless a player is erased sooner (interface counts and heat hold no player, so erasing a player does not change them). The record of important actions: kept to keep accounts safe, without players' names; when a player is erased, records of who opened that player's profile lose the player's code. When a developer deletes a game, everything it collected is deleted at once; our database provider keeps short-lived recovery copies for a limited time set by that provider.

Deleting data

Players: ask the game's developer, or use Roblox's own data request — Roblox then sends the developer a Right to Erasure request, and the developer erases the player in Settings → Erase a player. That deletes the player's events, encrypted name and totals for that game.

Developers: delete a game in its Settings. To delete your account, write to baseplatetools@gmail.com from the address you signed in with.

Changes and contact

This is a beta, and this policy will change as the product does; the date at the top says when. Questions: baseplatetools@gmail.com.