Skip to content

OpenGame

Privacy

How OpenGame uses your information, and the choices you have.

The short version

  • You can play without an account. Playing is measured with a first-party identifier in a cookie. We do not use ad networks or track you across unrelated sites.
  • An account needs an email address and a handle. Nobody under 13 may use OpenGame.
  • Published games and their delivered files are public. Drafts and private previews have different access controls. Creators keep their ownership.
  • A game that connects you to other players directly can show them your IP address. That is how direct connections work in every browser.
  • Games you play signed in get your handle, OG number, avatar and outfit, and their leaderboards show your handle. This is part of every account and has no off switch.
  • A game can connect to services its creator chose, such as an AI model or the creator’s game server. Those services see your IP address and the data the game sends them.
  • Most site pages can be recorded as a session replay in PostHog, with what you type masked. Settings, your player passport, uploads and copyright notices are not recorded, and nor is the game. Only a share of visits is recorded, and none from a browser that sends Do Not Track or Global Privacy Control. Read how recording works.
  • We do not run advertising.

Who we are

OpenGame is operated by Vesper Tech, Inc., a Delaware corporation doing business as OpenGame. This policy covers our websites, hosted games, social features, estates, radio, developer tools and related support. We decide how personal data is used for these services and are its controller where that term applies. Questions about anything on this page go to team@opengame.io, which a person reads.

Your account

When you create an account we store:

  • Your email address, to sign you in and to send you the handful of emails listed further down.
  • Your handle, which is public and is the address of your profile, and the OG number issued when you claim it.
  • Your display name, bio, avatar and any links you add. The default avatar is generated from a number. We also store the character appearance, estate layout and public profile content you choose to save.
  • Your country, as a two-letter code, worked out from your connection when you sign in or link an account. Prize eligibility depends on it, and our review team sees it beside your account so they know where people are from. We do not use it to profile you, and it is never shown on your profile or to other players.
  • Your settings: privacy, including whether games can see your OG, social visibility, notifications and optional emails, plus the time zone used for email delivery. We record your choices and, where applicable, when you made them.

Signing in

There are two ways to sign in:

  • An eight-digit code by email. A short-lived code lets you prove access to that address without giving us an email password.
  • Google. We ask Google for your email address and basic profile, meaning your name and profile picture, and nothing else. We do not receive your password, your contacts, your Drive, or anything else in your Google account, and we do not post anything on your behalf. You can revoke our access at any time in your Google account’s security settings.

If you connect X, its permission screen lists the read access it grants. We use the connection to verify and display your X handle, and store the linked X account identifier and verification time. We do not post to X or request your X email. You can disconnect in Settings and revoke access in X.

Playing a game

You can play without an account. OpenGame keeps a random browser identifier in an HttpOnly first-party cookie on opengame.io to recognise repeat visits. PostHog uses a separate identifier in cookie and local storage, described under Analytics. Games receive the game-specific identifiers and, if enabled, profile details described below. The identifier is not used to follow you on other websites.

It does four jobs, all of them ours:

  • Measuring plays and visits to games.
  • Measuring visits to creators’ profiles.
  • Remembering that you liked a game so the heart stays filled.
  • Stopping one person from repeatedly reporting the same game.

Each play we record:

  • Which game and which version of it, and when.
  • How long the tab was visible and focused while you played.
  • Your country and your network operator, worked out from your connection, and keyed hashes of your IP address and its address range, which help us keep the numbers honest. We keep the hashes, not the address.
  • The host that referred you, reddit.com rather than the full link, so creators can see where their players came from.
  • A broad device description from your browser.
  • Random identifiers that join up the records of one play.

If you are signed in, we also keep a player passport for you, with how long each game you play was on screen each day and in how many sessions. Only you see its detailed records. Separately, your social privacy choices control who can see your recent games and played dates, with friends as the default audience. Posting a review also shows that you played that game. You can choose to show your passport totals on your profile. A creator sees totals from these passports for their own games, such as how many signed-in players returned and how long they played. A total is shown only when it covers at least 5 players. These totals cover complete weeks, Monday to Sunday in UTC, so a creator cannot choose dates that overlap. Each week’s totals are worked out once and shown the same way every time after, as Analytics explains. If you turn on audience overlap, a creator can also see how many of their players play another game, counted in groups, without names.

Plays come from the page, not the game. Games can report named events and performance signals through the OpenGame SDK. These are the game’s claims, kept separate from the page’s measurements. Each game receives a stable pseudonym made with a one-way hash scoped to that game. It does not receive your account ID or the browser identifier used by OpenGame, and that identifier alone is different across games. When you are signed in, supported games also receive your handle, OG number, avatar and character appearance. Those public details can identify you across games. On a shared browser, signing in can associate earlier guest scores with the signed-in player.

Your OG in games. When you are signed in, a published game you play gets your handle, your OG number, your avatar’s look and your character’s outfit, and its leaderboard shows your handle next to your scores. The game can show these to other players, and a lobby shares your handle, OG number and avatar with the other players in it. This is the same public profile anyone can see at your handle, and since 12 November 2026 it is shared for every account, with no setting to turn it off. The game never gets your account ID or the browser identifier OpenGame uses. To play without it, play signed out. Private previews of games that have not been reviewed do not get any of this.

Games can ask our location API for your approximate country, for example to select a language or game server. That API does not return your IP address, city or coordinates. Games may also save game progress through our services or on your device.

If a game keeps a leaderboard, we store the score and what the game chooses to display next to the number, and show them publicly on that board. The name next to a score is your handle when you are signed in, and a Guest label otherwise. The game cannot choose it. The scores are the game’s claim. See the jam rules.

Friends and messages

We store your follows, friendships, requests, blocks and privacy choices. You choose who can see your online status, current game, recent games and estate. Your full play history is visible to you. If you are signed in, an estate’s owner who can see your online status can see that you visited, for 90 days. A visit made while you are set to Appear offline is not recorded.

Messages are stored so you and your correspondent can read them across devices. They are not end-to-end encrypted. We check messages for prohibited slurs and unsafe links. Friends messages are sent to TypeSafe’s Jev service for automated safety checks; close-friend messages receive these checks when they contain an outside link. Automated classifications do not create account strikes.

Unsend removes a message from the conversation. We retain its private copy for up to 30 days for safety reports. Deleting a conversation hides your copy; the other person can still read theirs. A report may include up to 50 messages as evidence, including recently unsent messages. Authorized reviewers must record a reason before opening private evidence, and each access is logged. Evidence for an unresolved report may be kept while it is reviewed.

Notification emails contain no private message text. Each email type has a separate preference and unsubscribe link. In-app notifications are removed after 90 days.

Feedback on games

When you leave a note on a game, we store its words, whether it is a bug, an idea or praise, the game and the version you played, when you sent it, the status the creator gives it, and the result of the checks below. We also keep a fingerprint of the words so the same note cannot be sent to one game twice in a day. Only if you tick Attach my device and browser do we store your browser’s user agent and your window size with it.

You can read your notes under Sent. The game’s creator can read the notes delivered to them, with your handle, your avatar and any device details you attached. If you allow it, the creator can message you about a note, and you can turn that off for each note. OpenGame staff who review flags can read notes that are held, refused as abusive or threatening, or reported. They must record a reason before opening a note, and each opening is logged. Notes are never public.

We refuse a note with a link or a prohibited slur before it is stored. Otherwise its words and kind are sent to TypeSafe’s Jev service, which suggests whether to deliver it, hold it for a person to review, or refuse it. A note is held when that check cannot run. While a note is held it shows as sent, and staff deliver or refuse it. A note refused as abusive or threatening is filed as a report against its sender for staff to review; it does not restrict the account by itself.

Notes are kept with the game they were left on. When a creator deletes a note it is gone from their inbox, and you still see it under Sent. Taking a game down does not delete its notes. If you delete your account, your notes stay with the creator without your handle. The email that tells a creator about new notes says how many there are and none of their words.

Who can see your IP address

A game can connect players directly to each other. Making that connection requires each player’s device to tell the others how to reach it, which means the players you connect to can see your IP address. This is how direct connections work in every browser rather than anything specific to OpenGame, but it is easy to be unaware of, so: an IP address is roughly a city and an internet provider, and someone technical can read it out of a connection you are part of. If you would rather strangers did not have it, do not join games that connect you to people you do not know.

Some games use OpenGame’s lobby service to introduce players to each other; the game then connects them directly, as above. A lobby shows the other players in it the identifier the game knows you by, whether you are signed in and the nickname you choose in that room, and, when you are signed in, your handle, OG number and avatar. Connection signalling can include network addresses, and our rate limits count lobby tickets by a keyed hash of your IP address. To run lobbies, the service keeps these in Cloudflare storage:

  • Lobby membership, which records the identifier the game knows you by, whether you are signed in, your room nickname and, when you are signed in, your handle and OG number, and connection reservations. A reservation nobody uses stops holding a place after 2 minutes. These records are deleted within 3 hours of you leaving, except a few connection records from a lobby that empties just then, which stay until that lobby is next used, if it ever is.
  • A keyed hash of your IP address, to limit how many lobbies one address can enter. The lobbies it entered and when are dropped after an hour, but only when that address comes back; the hash itself, and counts of its recent requests, are kept indefinitely.
  • Each room’s host, configuration and host-handoff records, which name the game’s identifiers for the host and for each player who could take over, and the latest checkpoint of the game’s own state, which holds whatever the game put in it. These are kept indefinitely.

A game can send all of a connection through a relay run by Cloudflare. When it does, the other players see the relay’s address rather than yours, and Cloudflare carries that traffic, encrypted. OpenGame does not see it.

In an estate, nobody connects to you directly and nobody there gets your IP address: everything goes through OpenGame’s servers, and voice through Cloudflare’s voice service. Estates lists what the people there do receive.

A game can also connect to services outside OpenGame, such as an AI model you talk to or a server where players find each other. The creator runs those services, or chose the companies that do; we do not. Like any website your browser loads, they see your IP address and the data the game sends them, and their privacy terms cover what they do with it. A game may offer an optional feedback field, but it cannot require an account or email, request passwords, take payments or connect a crypto wallet. Do not put sensitive information into a game. Review and sandboxing do not guarantee that every creator follows the rules.

Estates

An estate is a place on OpenGame that people visit together. The God estate is OpenGame’s own public estate, which puts visitors into separate copies of itself, called lobbies. Unless the owner has limited who may visit, the people in an estate can include signed-out guests.

What everyone there receives

When you visit, everyone else there (in the God estate, everyone in the same lobby as you) receives the following:

  • An identifier for you in that estate. It is the same each time you visit it from your account or, as a guest, from the same browser, so anyone who reads it can tell you have been there before. It is not your account ID.
  • If you are signed in, your handle and a link to your profile. If you are a guest, an automatic name that begins with Guest, and the guest name you chose, if you chose one.
  • Your character’s look.
  • Whether you own the estate and whether you may build in it.
  • Where your character is in the estate, how it is moving and which seat or vehicle it is in.
  • Whether your microphone is on. While it is, everyone there who has confirmed they are 18 or older also receives the name of your voice stream on Cloudflare’s voice service, which their browser needs to play your voice. It does not include your IP address.
  • Your part in a mini game: whether you ask for one, how you answer when someone else does, whether you play or sit out, your role, score and standing, who you tag or hit, and where you aim while firing.

Everyone there also receives any change you make to the sky or the layout, with your identifier. A piece you build in someone else’s estate is saved with a short tag made from your identifier, for as long as the piece stays (in the God estate, until everyone has left that lobby), and people who visit later receive the tag with the piece. If you are signed in, an owner who can see your online status can also see that you visited, as Friends and messages says.

Chat and voice

Estate chat is visible to people in that estate who have confirmed they are 18 or older. We keep at most the latest 50 messages, each with the sender’s identifier, handle and time, and delete each one 5 minutes after it was sent. New arrivals see what is still there. If you are a guest, each chat line we keep carries your automatic Guest name, not the name you chose. People who were there with you may still see your chosen name beside your lines.

Estate voice goes through Cloudflare’s voice service, so nobody connects to you directly. We do not record it, but anyone there can record what they hear or copy what you write in chat.

What we keep

To run estates, we keep these with Cloudflare:

  • If you are signed in, which estates you are in, deleted within 18 minutes of your visit ending.
  • An entry pass each time you are let in, holding your identifier for that estate and, in someone’s own estate, your account ID if you are signed in. Each is deleted when it expires, 12 minutes after it is issued. We also hold your account ID with your connection while you are there. Nobody else in the estate receives it.
  • In the God estate, which lobby you are in, for up to 13 minutes after you are placed in it. If your connection drops, we keep your identifier for 15 seconds so you can rejoin the same lobby.
  • The guest name you chose, for 10 minutes after you last set it, to limit how often you can change it. It is also held with your connection while you are there.
  • While you use estate voice, speaking or only listening, your identifier with your sessions on Cloudflare’s voice service, the name of your voice stream, and the names of the streams you hear. After you leave, they stay until Cloudflare confirms the sessions have closed, and if it does not answer, until a later clean-up succeeds.
  • A count of the chat lines you sent in the last minute, with your identifier, to limit them, deleted the next time someone uses that estate. A count of your voice requests in the last minute, for the same reason, deleted the next time anyone uses voice there, which may be much later.
  • If you change the sky, your identifier, until the owner leaves the estate, or, if the owner is away, until someone next arrives or leaves (in the God estate, until everyone has left that lobby).
  • If you switch how a lobby hears voices, your identifier and the name others see you by, until it is switched again or everyone has left.
  • If you take a seat, your identifier until you leave it.
  • If you ask for a mini game or answer someone’s request, your identifier until shortly after the game starts, or after the request lapses if nobody accepts. If you play, your identifier until shortly after the results are shown.
  • A temporary password we issue your browser for Cloudflare’s voice relay, and how many you have asked for, for at most 5 minutes. It is not your account password.
  • If an owner removes you, a record of that for 30 minutes, so you cannot come straight back.
  • If you lose access because the owner changes who may visit, or because OpenGame restricts your account, a record of that for up to 13 minutes, so an entry pass issued earlier no longer works.
  • If you delete your account, a record of that for one hour, so an entry pass issued before then cannot be used.

The estate servers keep no logs. Cloudflare, which runs them, still logs requests to them, which we describe under What the servers log.

We also keep a keyed hash of your IP address (on IPv6, of its address range) to limit how many people on one network can be joining one estate at the same moment: in storage for up to 12 minutes after you are admitted, and with your connection for as long as you stay. Our rate limits count estate requests by a keyed hash of the same and, if you are signed in, by your account ID. We keep those counts for at least a day. After that, a clean-up that runs now and then as people use OpenGame deletes them.

Uploading a game

Published games are public. The files you upload are served to anyone with the link, from a separate domain reserved for exactly that. Alongside the bundle we store what you tell us about it, and what our checks find:

  • Your submission: title, description, cover art, screenshots, the track you entered, and the version history of every build you upload.
  • Validation output. We run your game in a sandbox: screenshots at five window sizes, a short capture, frame rate, memory, and a log of every network request it attempted. Reviewers see all of it.
  • Your attestations. When you tick “I own the rights to this” and the others, we record each one separately with a timestamp, the exact text you agreed to, your browser’s user agent, and a hash of your IP address rather than the address itself. These exist for one purpose: if a rights holder complains, or a result is disputed, we can show what was claimed and when.
  • Review decisions: who decided what, when, and why. This log is append-only and is not deleted with your account.

Connected tools

When you use our CLI, API or MCP tools, we store the authorized account, credential metadata and activity needed to run those requests. A connected agent can read or change the material its permissions allow. The agent service you choose may receive that material under its own privacy policy. You can revoke OpenGame credentials in Settings. Revocation cannot remove copies already received by another service. GitHub import fetches public repositories without connecting your GitHub account; private repositories are not supported by that import. We retain repository, commit and build metadata. Build services can contact dependency registries and other hosts during a build.

Anyone can send a copyright notice about a game, with or without an account, in the ways our copyright page describes. What happens to the details in one:

  • If you send a notice, we keep everything in it: your name, address, phone, email, the work and your signature. The creator of the game sees who claims the rights and what you say was copied. They see your email only if you tick the box that allows it, and never your phone or address. We confirm your email with a one-time code, which leaves an unused account row behind, the same as asking for a sign-in code and never finishing.
  • If you send a counter-notice, the law has us send it, in full, to the person who sent the notice. That includes your legal name, address, phone and email. The counter page says so before you start.
  • Both are kept for 3 years after the notice closes, as a record of a legal claim, including after either account is deleted. Staff can read them, and so can a court that asks.

We record an IP-address hash and browser information with a filing. To assess a verified work-email sender, we may check the domain through public registration records, DNS and automated web research. That check uses the domain, not your notice or full email address. We store its assessment and sources for review.

Analytics

We use PostHog for analytics on the site and ClickHouse for analytics on games. Both are described below.

We use PostHog to understand how the site is used, served through our own domain. It uses a random browser identifier. We do not send it your account ID or email address, or link that identifier to your account with PostHog’s identify feature.

  • Named events only. Automatic capture of every click is turned off; we send page visits, campaign attribution, which part of the site a page belongs to, and a defined list of events such as a play starting, a sign-in code being sent, a game being published, or how long an estate visit or a radio listen lasted. An event holds names, counts and durations, not what you type.
  • Account activity. After a successful sign-in, we record when your account was last active, at most once per UTC day. A new account can produce one signup event under the browser’s existing analytics identifier.
  • Events our servers send. When a play is counted or refused, and when a sign-in code is accepted, our server sends that event under the browser’s existing analytics identifier, and sends nothing if the browser has none. When a game is published or entered in the jam, our server records it with the game and how it was deployed, and nothing about a person.
  • Do Not Track and Global Privacy Control. If your browser sends either signal, we do not load PostHog, and our servers send PostHog no events for that browser either.
  • Session recording can run on most of the site, including the page around a game, signing in and claiming a handle. A share of visits is recorded, not every visit. Inputs and marked private text are masked. We do not record your settings, your player passport, your uploads, jam entries and release certification, your game’s analytics and audience pages, copyright notices and counter-notices, estates, password-protected decks or preview pages. The game runs in a frame on a separate domain; its contents are outside the page recording. Project settings can disable recording.
  • Errors are captured here too, so a crash reaches us without a separate tool.

Games do not send anything to our PostHog project. Creators can use the OpenGame SDK to report named game events, such as a level being completed, with a limited set of properties. We treat these as the game’s claims.

We also run a separate game analytics system using ClickHouse hosted on Amazon Web Services and an archive in Cloudflare storage. It measures game discovery, play sessions and SDK events using identifiers scoped to each game, and does not receive account IDs or IP addresses. It also records each counted visit to a creator’s profile, with the profile, the minute, and whether the visit came from OpenGame, another site or neither. Nothing in that record identifies the visitor. These records are kept for 90 days, including after the creator closes their account.

On a game’s page we record how long the game took to load, and whether you muted it, paused it, made it fullscreen or left it idle. In the gallery, the jam and on profiles, we record a game’s card as seen.

Creators receive aggregate reports, and preview events are available only to the game’s creator. Sensitive breakdowns require at least 5 players, and within one report, additional groups are hidden where its totals could reveal a smaller group. Some weekly figures from this system are shown to everyone; What is public lists them.

Creator figures cover complete weeks, Monday to Sunday in UTC, and so do the passport totals above, so no two reports share a day. The first report a creator opens for a week is saved and shown again on later visits. Once part of that week is over 90 days old, it is shown without the per-player figures. A new view of that week, such as one with a funnel, is checked against every view of it already shown. Creators cannot narrow a week to one country, device or source; those are rows inside the week’s report, under the same minimum. A figure that would reveal a smaller group is hidden. Hiding a figure still says a little: about one yes or no for each figure, each time a new view is shown.

Aggregate history is kept indefinitely: minute buckets, counts of plays and events, playtime, numeric summaries and event order. These records include sets of hashed game pseudonyms. Every aggregate row also stores the random identifier of its play session. Lists of player pseudonyms, including those behind property breakdowns, are deleted after 90 days along with raw history. Returning players, retention, session length milestones, event and property breakdowns and funnels therefore cover the last 90 days only. The full event payload and exact event timestamp also expire with raw history. Someone who already has a pseudonym can test whether a hashed set contains it, and a session identifier can be looked up in our play records, so both remain personal data. When you erase your history, we use the sets to find the entries with your pseudonyms and delete them. Reports shown to creators contain grouped results without the pseudonyms.

When you erase your play history in your passport settings, or delete your account, we queue removal from the game analytics system and its archive of public events and aggregate history recorded up to that moment under your account’s pseudonyms. This also covers guest activity from browsers you played on while signed in. Removal runs in the background and retries failures. Figures creators have already been shown remain as grouped counts without pseudonyms.

Some copies are outside this erasure process. Until November 2026, named game events were also copied to Cloudflare Analytics Engine; those copies remain for its three-month retention period, until February 2027 at the latest. Private-preview events expire after 7 days. Warehouse backups are not removed by this process. Restoring a backup or rerunning an operator backfill can bring erased rows back until the recorded erasure requests are applied again. Contact us about these copies when making an erasure request; we do not promise immediate removal from every system.

Where a creator allows their game to be embedded on another site, the embedded player uses a separate anonymous identifier without reading your OpenGame account or browser cookie. These visits are not added to your player passport.

Email

Mail is sent through Resend. Service emails include requested sign-in codes, welcome messages, submission and release decisions, copyright notices, safety notices and account communications. These may be needed to run your account or meet legal duties. Optional categories, such as friend and follow updates, feedback on your games, analytics reports and announcements, have their own preferences and unsubscribe links.

We log what we sent, to which address, and whether it was delivered, bounced or reported as spam, so that “I never got the email” is a question we can answer.

What the servers log

Our hosting and network providers log requests, including IP addresses and user agents, to serve pages, apply rate limits and block attacks. We use Cloudflare Turnstile during protected email-verification flows, including sign-in and copyright notices, to limit automated abuse. Cloudflare receives browser and connection signals to perform these checks.

Who else sees your data

The services below process data to run OpenGame.

For jam winners, to deliver a sponsor’s prize we give that sponsor the winner’s name, handle and email address, and to pay any prize we collect proof of eligibility, a tax form and payment details, which we keep for as long as tax law requires. The official rules say when.

ServiceWhat it handles
SupabaseAccounts, sign-in, and the database behind everything
VercelServing opengame.io
CloudflareDNS, the network in front of the site, game file storage, the lobby service and relay, estates’ rooms and voice, bot checks, and the game analytics archive in R2 storage
ModalBuild and validation sandboxes
PostHogProduct analytics, recordings of site pages outside settings and uploads, error tracking
ResendSending email and reporting what happened to it
Amazon Web ServicesOff-site backups and the ClickHouse game analytics warehouse. The warehouse holds game events with game-scoped player and session pseudonyms, country and device type. No account IDs or IP addresses
Google and XGoogle sign-in and optional X account linking, when you choose them
AI model and web research servicesAutomated research on the sender’s domain for copyright notices
TypeSafe (Jev)Automated safety checks on social messages and on feedback notes, as described above

We may also disclose relevant data to professional advisers and authorities to meet legal obligations, protect people, investigate misuse or establish or defend legal claims. A merger, financing, acquisition or transfer of the service may involve access to relevant records, subject to applicable privacy duties. We do not use your information for cross-context behavioural advertising. Public posts, games and profile details can be copied by people outside OpenGame; their copies are outside our control.

What is public

Anyone can see these, signed in or not:

  • Your profile: handle, display name, avatar, bio and links.
  • Your friend count, and your follower count once you have at least 10 followers. How many people you follow is shown the same way, once it is at least 10. Who your friends and followers are, and who you follow, is shown only to you.
  • Your published games, with their visit and play counts. A game’s page shows its likes once it has more than 100, and your profile shows your games’ total likes once the total is more than 100. On your profile, each game’s likes and your games’ total playtime are shown only to you.
  • Your player passport totals, if you choose to show them: games played, time played, days played and your best streak, counted from the date shown with them. The games in your passport are not shown, though a review you post shows that you played that game.
  • Player reviews you post: your handle, whether you recommend the game, what you wrote, when you posted it and last edited it, and a wide band of your recorded playtime on that game when you first posted, never the exact time. Deleting a review takes it down. Erasing your play history removes the band and leaves the review up.
  • Leaderboard entries. On a game with a leaderboard, your score, the name next to it and anything the game shows next to the score. The name is your handle when you are signed in, and a Guest label otherwise.
  • Achievement counts: how many players unlocked each of a game’s achievements and what share of players that is, shown only when at least 5 players unlocked it and at least 5 did not, or everybody did.
  • Weekly activity for groups of players, without names. Published games’ plays, players, recorded time per player and next-day return for the last full UTC week are published as data at /api/v1/analytics/public, with each game’s total recorded time and the trending score built from those figures. Figures drawn from fewer than 5 players are withheld.

Your email address, your country and your draft submissions are not public.

Cookies and local storage

Our sites use cookies and browser storage for:

  • Sign-in sessions, security checks and access to password-protected pages or private previews.
  • The first-party play identifier and separate PostHog analytics identifier described above.
  • Theme, sound, radio, cursor and other device preferences.
  • Saved form progress, which can include the email address you entered.
  • A short-lived pass on copyright pages after email verification, lasting 60 minutes.

We do not set advertising cookies. Games on the separate game domain cannot read the site’s account cookies; games can keep their own progress on your device. You can clear or block cookies and local storage in your browser. This can sign you out, remove saved preferences or progress and prevent some features working. The site does not offer a separate analytics-consent switch. Browser tracking protection can block analytics requests.

How long we keep things

WhatHow long
Uploaded archives awaiting validationScheduled for deletion after 30 days unless retained for a live version or legal hold
Builds never attached to a submissionLegacy uploads expire after 48 hours. Platform cleanup keeps the newest 10 ready releases; older releases are eligible only when no publication, submission, active operation or legal hold protects them. Failed or expired deploys become eligible after 24 hours; rejected submissions use 30 days
Published game filesKept for as long as any live or judged version needs them, because jam entries are meant to stay playable
Feedback notes on gamesKept with the game they were left on, including after it is taken down. A note whose author deletes their account stays without the author’s handle
Account and profileUntil you delete it
Player reviewsDeleting a review takes it down for everyone, but its text, recommendation and times stay stored with your account. A review someone reported is also kept with that report. Deleting your account takes all your reviews down.
Play recordsNo automatic age-based expiry is set for these records. They can remain while the game and its history are stored. Each record holds the game, version and time, how long you played, your account ID if you were signed in, the browser identifier, random identifiers that join up the play, the site that referred you, a broad device description, your country, your network operator, and keyed hashes of your IP address and its address range. Account deletion does not by itself establish that every historical account reference is erased; we assess these records as part of an erasure request.
Player passportUntil you delete your play history in your passport settings, or delete your account. Hiding the passport from your profile does not delete it. Turning off audience overlap takes you out of creators’ overlap counts.
Game analytics events in ClickHouseRaw events: 90 days. Preview events: 7 days. Aggregate counts are kept, including the sets of hashed pseudonyms used to count players. Lists of pseudonyms are deleted after 90 days. Your public events and aggregate history are deleted sooner when you erase your play history or delete your account; preview events are left to expire.
Game analytics archive in Cloudflare R2At most 13 months from when each event happened. Preview events: 7 days. Your public events are removed sooner when you erase your play history or delete your account.
Named game events copied to Cloudflare Analytics Engine before November 2026Three months from when each was recorded, set by Cloudflare, so all are gone by February 2027. Nothing new is copied there. Not removed when you erase your play history or delete your account.
Game analytics events waiting to be sent to the warehouse7 days after delivery. Undelivered events are deleted after 90 days.
A creator profile visit’s keyed hashKept for at least 30 minutes, then deleted when later visits arrive
A game page load’s keyed hashesKept for four hours, then deleted when later visits arrive
LikesUntil you remove them or delete your account
PostHog events and session recordingsRetention is controlled separately in PostHog. No fixed period is stated here for those records; the game analytics periods above do not apply. Contact us for the retention applicable to your data or to request erasure.
Copyright notices and counter-notices3 years after the notice closes, including after an account is deleted
Attestations, review decisions and the audit logRetained for safety, disputes and legal claims, including after account deletion; no automatic age-based expiry is set

Deletion does not recall material already sent to a provider. Provider copies follow that provider’s retention rules. Ordinary messages remain until removed under the rules in Friends and messages; both-sided conversation deletion also uses the safety-retention window. Estate chat is removed 5 minutes after it is sent. Research-choice and blocking records may remain to honour those choices and address disputes.

Backups and cached copies can outlast removal from the active service. We do not promise immediate deletion from every backup or another person’s device. The periods above describe configured cleanup rules, rather than a guarantee that every physical copy disappears at the same instant.

One exception cuts across all of it: anything subject to a legal notice or an open investigation is held until that is resolved, so evidence is not destroyed by a timer.

Deleting your account, and getting a copy

You can change your email or delete your account in Account settings. Email team@opengame.io to request a copy, another correction, or help with deletion. Use the account’s email if you can. We may ask for information needed to verify the request and protect someone else’s data.

  • A copy. We send you what we hold about you in a machine-readable file.
  • Deletion. We close the account and remove or de-identify its public profile and personal data that no longer needs to be retained. Social cleanup removes friendships and follows and takes your sent messages out of conversations, subject to the temporary safety copy described above. Blocking records and unresolved reports can remain. You can erase passport history separately without closing your account. Account deletion also queues game analytics erasure, with the limits described under Analytics.
  • Your games. Account deletion withdraws all your games from OpenGame. Links and embeds stop working. File removal and cleanup across our services can take longer than closing the account; interrupted work is retried. Copies needed for a legal hold or a frozen judging version are retained.
  • Your handle becomes free. Once your account is deleted, anyone can claim it, including you on a new account. Your games do not go with it.
  • What survives. Attestations, review decisions, audit records and, if you won something, the result. Those are evidence about what happened, and deleting them would defeat their purpose. If your account was suspended or banned when you deleted it, we also keep a one-way hash of its email address and of each sign-in account linked to it, with the reason and the date, so the suspension still applies to a new account. We never keep the address itself, and the hash is removed if the suspension is lifted.

We respond within the period required by the law that applies to your request. Under EU or UK data-protection law this is normally one month; a complex request may allow a further two months, with an explanation in the first month. Under the California Consumer Privacy Act, covered access, correction and deletion requests normally have a 45-day response period, extendable by a further 45 days with notice. A legally shorter period takes priority. If we cannot fulfil a request, we explain the reason and any available complaint or appeal route.

Where your data is

OpenGame’s operator is a US corporation. Our database and backups use US infrastructure; hosting, network and compute providers can process data in other countries. Those countries may give data different protections from the country where you live. We have not confirmed that our provider arrangements include Standard Contractual Clauses, the UK addendum or another applicable safeguard for these transfers. We do not claim that OpenGame is certified under the EU-US Data Privacy Framework. Contact us for the provider and transfer arrangements relevant to your data. Using the service does not waive a transfer protection the law gives you.

Why we use data

Where EU or UK data-protection law applies, the purposes and legal grounds are:

  • Providing the services you request: account access, hosting, game saves and communications, as needed to perform our agreement with you or take steps you request before it.
  • Running and protecting OpenGame: security, abuse prevention, debugging, service measurement and support, based on our legitimate interests in a reliable service, subject to your rights and any consent required by law. A legitimate interest does not replace consent where consent is required for device storage or tracking.
  • Your optional choices: optional marketing on consent, which you can withdraw. Withdrawing consent does not make earlier lawful processing unlawful.
  • Legal duties and claims: handling valid notices, tax requirements and lawful requests on the applicable legal obligation, and keeping proportionate evidence for establishing, exercising or defending legal claims.

An email address is needed for an account; publication requires the game files and rights confirmations; an optional generation request requires its input. Optional profile details are not conditions of access. Automated checks can block a request, flag content or affect publication. A person can review a disputed moderation or account decision if you contact us.

Your rights

Depending on your location and the law’s application to OpenGame, you may request access, correction, deletion or a portable copy, restrict processing, object to processing based on legitimate interests, and withdraw consent. You may complain to your local data-protection authority, including in the EEA or UK. You do not have to contact us first. These rights have exceptions, such as protecting another person’s privacy or retaining evidence for a legal claim.

California and other US state laws can provide rights to know the categories and specific information collected, its sources, purposes and recipients, to correct or delete it, and to opt out of sale, targeted advertising or certain profiling. The sections above describe our categories and recipients. We do not use data for targeted advertising. An authorized agent may send a request with proof of authority. We may verify the person represented. Contact us to appeal a refusal where state law provides that right. We will not penalize you for exercising a privacy right.

A browser’s Do Not Track or Global Privacy Control signal turns off PostHog analytics and session recording for that browser, as described under Analytics. It does not change the records the service needs to run, such as play records, account activity and game analytics. Email us if you need help exercising an applicable opt-out. We do not claim that the absence of an advertising business removes other legal duties that may apply to disclosure of personal data.

Age

Nobody under 13 may use OpenGame, and we do not direct the service to children under 13. Anyone under 18 needs a parent or guardian to agree to our terms first. We record when you accept our terms, which is when you sign in. Jam entrants must be 18 or older, and estates ask for confirmation that you are 18 or older before their chat and voice. If you believe a child under 13 has provided personal information, contact us so we can investigate and remove it as required.

Changes

When this changes materially we will say so on the site and update the date below. We will give any additional notice or obtain consent where the law requires it. Submission records retain the terms and rules version accepted at the time.

Contact

team@opengame.io. Privacy questions, deletion requests and complaints all go to the same place. You may also write to Vesper Tech, Inc., 1111B S Governors Ave #56688, Dover, DE 19904, United States. Mark the correspondence “Privacy”.

Last updated 18 November 2026.