KUMODeck

Privacy policy

This policy explains what personal data KUMODeck collects, why, who it goes to, and how long it is kept. KUMODeck is operated by the KUMODeck operator ("we"). Questions and requests: [email protected].

Effective date: 2026-11-16

Who this covers#

  • Creators: people who sign up for KUMODeck to build and host their apps. We decide how this data is used.
  • Users of creators' apps: people who use an app or game built on KUMODeck, or play a game that uses KUMODeck Analytics. The creator decides what their app or game collects and is responsible for it; we store and process that data on the creator's behalf and only to run the service for them. See "Data in creators' apps" below.
  • Players with a KUMODeck account: people who use "Sign in with KUMODeck" to sign in to games and apps built on KUMODeck. The account itself is ours, and we decide how its data is used. See "KUMODeck accounts for players" below.

What we collect from creators#

DataWhere it comes fromWhy
Email address, display name, password (stored only as a one-way hash)You, when you sign upYour account and sign-in
Email address, name and account ID from Google or GitHubThe provider, if you sign in with itSign-in. We do not keep your profile picture
Passkey public key and labelYour device, if you add a passkeySign-in
Sign-in sessions (stored as a hash, 30 days)Created when you sign inKeeping you signed in
Projects, deployed files, settings and a record of account actionsYou and your AI agent or CLIRunning your projects; security and support
Usage amounts per project and dayMeasured by the serviceUsage fees
Prepaid balance, top-ups, invite credit, and the Stripe IDs of a saved cardYou and StripeBilling. Card numbers go directly to Stripe and never reach us
Request logs: IP address, browser user agent, the page or API called, timeYour browser, CLI or AI agentSecurity, abuse prevention and fixing errors

We use your email only for messages about your account and service: email verification, password reset, security notices (for example a new sign-in method or a connected AI agent), changes to your projects, and low-balance notices. We do not send creators marketing email.

KUMODeck accounts for players#

A KUMODeck account lets you sign in to many games with one account. A game never gets your email address or your account itself: it gets only an ID made just for that game and your display name. Each game gets a different ID, so games cannot use it to match you up with each other.

DataWhere it comes fromWhy
Email address (optional)You, when you sign in with an email link or code, or the sign-in service belowSigning in by email. We send it only sign-in emails. An account made with X has no email address, and you can remove the email address later
How you sign in: email link, Google, Apple, X or Discord, and the account ID each service gives usYou and the service you chooseSign-in
Display nameThe sign-in service (Google, Apple or Discord; not X), or youShown to the games you connect. You can change it
An ID for each game you connectMade by us at randomThe game knows you by this ID only
The list of games you connected, when you connected them and last used themCreated when you connect a gameShowing it on your account page, so you can disconnect a game
Sign-in records: when you last signed in, sign-in sessions (stored as a hash, 30 days)Created when you sign inKeeping you signed in; security
When you ask for a sign-in email: the kind of device and browser and an approximate place, worked out from your browser and IP address (for example "Chrome on Windows, near Seattle, US")Your browserWritten in the email so you can tell whether you asked for it. We do not keep the IP address itself, and this is deleted after about a day
Request logs: IP address, browser user agent, the page called, timeYour browserSecurity and abuse prevention (about 7 days, as for every request)

What we receive from each sign-in service, only if you choose it:

  • Google: your Google account ID, name and email address (and whether Google has verified it). Google also sends a link to your profile picture; we do not keep it.
  • Apple: your Apple account ID, email address (this may be a private relay address from Apple) and, the first time, your name.
  • X: your X account ID. X also sends your username, name and profile picture link; we do not keep them for your KUMODeck account, and X does not give us your email address. We only read your profile; we never post.
  • Discord: your Discord account ID, username and email address (only if Discord has verified it).

We use what we get from these services only to sign you in and run your account. We do not use it for advertising or to train AI models, and we do not trade or rent it. KUMODeck's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. This also applies to creators who sign in with Google.

When you connect a game, that game's creator gets your ID for that game and your display name, and what you then do in the game is data in that creator's app (see "Data in creators' apps"). The game can use your sign-in, but it cannot see or change your KUMODeck account.

Deleting: on your KUMODeck account page you can disconnect a game (it signs you out of that game on every device), remove a way to sign in (the last one stays), and delete your account. You can also remove a game from your list of games: this hides it and erases its last sign-in date, without signing you out, and it shows up again the next time you sign in to it. Deleting the account removes it, its sign-in methods and its game list, and removes KUMODeck sign-in from your games. Your data inside each game stays with that game; ask the game, or use its delete option, to remove it. You can also email [email protected].

Who we share it with#

We do not trade or rent personal data. We share it only with the service providers that run KUMODeck for us, and only what each one needs:

ProviderWhat it doesLocation
CloudflareHosting, compute, file storage, request logs, relaying realtime and voice trafficWorldwide
NeonMain databaseUnited States (AWS us-east-1)
ResendSending account emailsUnited States
StripePrepaid top-ups and saved cardsUnited States and others
Amazon Web Services (SES)Sending KUMODeck news to people who asked for itUnited States (us-east-1)
Google, GitHubCreators' sign-in, only if you choose itUnited States
Google, Apple, X, DiscordSign-in to a KUMODeck account, only if you choose itUnited States
Google FontsFonts on this site and the dashboard (your browser asks Google for them, which shows Google your IP address)Worldwide

When a creator added a game to KUMODeck Analytics from another platform they build with, we send that platform the game's numbers (totals only, with no marks or IDs) so it can show them to the creator.

Your data may therefore be stored and processed outside your country, including in the United States. We may also disclose data when the law requires it.

How long we keep it#

DataHow long
Account dataUntil you close the account. After closing, the account is anonymised (email, name, sign-in methods and passkeys removed) once no balance remains
Billing and ledger recordsAs long as accounting and tax law require (up to 7 years)
Sign-in sessions30 days, or until you sign out
KUMODeck accounts for playersUntil you delete the account. A disconnected game is kept on the list (marked as disconnected) so that you come back as the same player if you connect it again
Sign-in emails for players (link, code, device and place)The link and code stop working after 10 minutes; the record is deleted after about a day
Play measurement in creators' games (KUMODeck Analytics)The mark that tells people apart: 3 days. The daily rows made from the random ID in the browser: 31 days after the day of play. The record of each run: 90 days, with its country and device. Its region, operating system, browser, language, screen size, referring site, utm values and visit ID: 3 days. Daily totals split by country, region, device, operating system, browser, language, screen size, referring site and utm value: 13 months. Other daily totals: kept for the creator's reports (they hold no marks or IDs)
Request logs and Functions logsAbout 7 days
Database backupsUp to 30 days

Your choices and rights#

  • Users of creators' apps can download or delete their own data where the app offers it (the API is GET /v1/players/me/export and DELETE /v1/players/me), and creators can do the same for any of their users from the dashboard or their server. Deletion is permanent; records needed for accounting are anonymised and kept.
  • Players with a KUMODeck account can delete it, disconnect games and change their display name on their KUMODeck account page. For a copy of your account data, email [email protected].
  • Creators can close their account from the dashboard after deleting their projects. To get a copy of your account data, or to correct or delete it, email [email protected].
  • Depending on where you live, you may have further rights (for example to object or to complain to a data protection authority). Contact us and we will answer within the time the law requires.

Cookies and browser storage#

There is no analytics or tracking on this site, the dashboard or the CLI, and no advertising cookies. KUMODeck Analytics measures play in creators' own games, not visits to this site, and the two random IDs it uses (_pt_pid and _pt_ses) are stored on the creator's game page, not on this site; see "Data in creators' apps".

  • This site stores only your light / dark theme choice in your browser.
  • The dashboard keeps your session, your last sign-in method and your language in browser storage.
  • Signing in from an AI agent sets two short-lived cookies (10 minutes) for the sign-in step only.
  • The KUMODeck account page sets two cookies, only for signing in: your session there (30 days) and a random ID for your browser (1 year), used to check that each sign-in step finishes in the browser that started it.

Data in creators' apps#

When a creator uses KUMODeck, data about their users is stored by KUMODeck: accounts (display name, email and sign-in identities from email, Google, Discord, Apple, X or KUMODeck; passwords only as a hash), saves and app data, uploaded files, and the creator's own databases and storage. Realtime and voice traffic is relayed and not recorded.

The creator decides what to collect and must tell their users in their own privacy policy. We use this data only to provide the service to the creator, do not use it for our own purposes, and help creators answer their users' requests with the export and delete tools above. If you use an app built on KUMODeck, contact the app's creator first; if you cannot reach them, contact us.

Play measurement in creators' games (KUMODeck Analytics): a creator can add one line (p.js) to a web game they host on their own site, to see how many people play it and for how long. This is data in the creator's app: the creator chooses to measure and should tell their players in their own privacy policy. We use it only to show the creator their numbers (directly, or through another platform the creator builds the game with, when the game was added from that platform) and to run and protect the service.

  • What the game page sends: when a run starts, every 5 seconds while it changes, and when it ends: the time played while the tab was visible and in use, the number of inputs (a count only, not which keys or where), retries, how far the player got, and the names and counts of events the creator chose to send (for example enemy_defeated). At the start it also sends whether the browser reports itself as automated, the browser's language setting (for example ja-JP), the screen width in one of three sizes (up to 480, up to 1024, or wider, in pixels), the host name of the site the player came from (only the host name, such as example.com; (direct) when there is none and (internal) when it is the game's own site), the utm_source, utm_medium and utm_campaign values in the page address, and the visit ID below. When the page opens, it sends the language, screen size, site the player came from and utm values again; we do not keep them from that request. Each request carries the game's site address (origin).
  • What it does not do: the line sets no cookies and sends no names, email addresses or account IDs from the game.
  • Telling people apart within a day: from the IP address and browser user agent we make a mark with a key that changes every day (UTC), so marks from different days cannot be matched. We do not keep the IP address or user agent with the run, and we erase the mark after 3 days. The mark is also compared with the creator's own mark, so the creator's test runs are not counted.
  • Where and what people play on: when a run starts, we note the country (the country code Cloudflare attaches to each request, worked out from the IP address), the region (Cloudflare's region code, such as a state or prefecture), the kind of device (mobile, tablet, desktop or other), and the operating system and browser with their main version only (for example iOS 18 and Safari 18), worked out from the browser user agent. We do not keep the IP address or the user agent itself. A utm value is cut to 100 characters, and one that looks like an email address, a long number (10 digits or more) or a web address with parameters is replaced with "(dropped)" before it is kept. We do not use any of this to decide whether a run counts.
  • What is not counted as people: runs from automated browsers and from connections that come from data centers.
  • A random ID in the browser: to count how many different people play over several days and how many come back, the line stores one random number (32 hexadecimal characters, made in the browser, meaning nothing on its own) in the browser storage of the game's page (localStorage, under the name _pt_pid) and sends it when a run starts. Each site has its own storage, so the same person gets a different number on another site. If the browser does not allow this storage (for example in some private windows), nothing is stored or sent and the run is measured as before. A player can remove the number by clearing that site's data in their browser; they then look like a new person.
  • What we do with the ID: we do not keep the number itself. We keep only a value made from it with a fixed secret key, separately for each game, so the values for two games cannot be matched. That value is kept in one row for each day the person started a run, with no IP address, user agent, site address or the mark above, and apart from the record of each run. We erase each row 31 days after that day. After that, only daily counts remain: how many people were new, how many came back 1, 7 and 30 days later, and how many runs carried the number. Runs from automated browsers, from connections that come from data centers and the creator's own runs are left out. Because anyone can change the number, we do not use it to count runs, to bill, or to check for fraud.
  • A visit ID in the browser: to count visits (a stretch of play with no more than 30 minutes without activity), the line stores a second random number (32 hexadecimal characters, made in the browser) in the same browser storage, under the name _pt_ses, together with the time of the last activity and whether a run has started in that visit. After 30 minutes without activity it makes a new number. It is separate from _pt_pid and sent when a run starts. If the browser does not allow this storage, nothing is stored or sent. A player can remove it by clearing that site's data.
  • What we keep: the record of each run (the numbers above, the site address, the time, the country and the device) for 90 days. Its region, operating system, browser, language, screen size, referring site, utm values and visit ID are erased from it after 3 days. Daily totals split by each of country, region, device, operating system, browser, language, screen size, referring site and each utm value (runs, counted runs, visits, visit time and play time for each value) are kept for 13 months; each day, values outside the 200 largest for a game are merged into "(other)". They hold no marks or IDs and are not combined with each other. Other daily totals (runs, play time, people per day, most playing at once, and the counts from the random ID above) also hold no marks or IDs. The requests also appear in the request logs (about 7 days), like every request.

KUMODeck news: some apps show a box to get news from KUMODeck. If an adult ticks it and confirms by email, we keep the email address and a record of that consent to send our news. Every message has a link to stop it.

Changes#

We will post changes on this page and update the effective date. For significant changes we will also tell creators by email.