PlayAgain

Privacy Policy

Last updated: November 9, 2026

What PlayAgain is

PlayAgain turns a browser into a retro game console and your phone into its controller. Games run entirely in the host's browser. When you play around one screen, our servers only relay small controller messages between your devices. Playing online with a friend works differently: Netplay and link sessions.

Data we process

  • Account (optional): if you sign in with Google we receive your name, e-mail address, and profile picture from your Google account. We use them only to identify you inside PlayAgain. We never see your Google password. Explore: the games you mark as favorites are kept with your account on our server until you clear them in Settings. Whether you have seen Explore's guide is kept with your account too, so it is shown once. What your friends see, and for how long, is under Friends.
  • Realtime session data: when you play around one screen, room codes, player slots, and controller input packets. These are ephemeral — they expire automatically (rooms within hours) and are never written to a permanent database. Playing online with a friend works differently: Netplay and link sessions.
  • Game files: ROMs you load stay on your device or in your own Google Drive. When you add games, each file goes from your browser straight into a PlayAgain folder in your own Google Drive: our server only asks Google to start the upload, with the file's name and size, and the file itself never passes through our servers. PlayAgain never stores or distributes your game files.
  • Usage counts: PlayAgain counts, per day, how many times the console is opened, a game is loaded, a game is added (from a console or from a game's page, and whether it is the account's first), a game starts or fails to start (by console, and a coarse kind of failure such as storage or network), and a phone joins, and whether that phone is an iPhone, an Android phone or something else. When the console warns that it is too slow for a game and suggests a phone, it counts that it did and which choice was made; when a game is picked and no phone can run it, it counts the reason (for example that no phone is connected, or that this browser cannot receive a phone's stream). These counts carry no account, device identifier, room or file information and cannot be traced back to you. Only if you accept analytics cookies (see Cookies), the console also keeps the date of its first visit in your browser's local storage, to count returning visits; only a coarse range (“first visit today”, “within a week”, …) is ever sent. If your browser sends Global Privacy Control or Do Not Track, nothing is counted.
  • Stream quality: while a phone's game plays on another screen, that screen sends a short technical report every thirty seconds for the first ten minutes and every five minutes after: frame rates on both ends, freezes and delays, how the picture was encoded, sent and drawn, and the screen browser's user agent. It names no account, room, game or file, and is kept in our server logs for up to a week. If the screen's browser sends Global Privacy Control or Do Not Track, nothing is sent, unless the page was opened with ?debug=1.
  • Page analytics: we use Vercel Web Analytics to see which pages are visited and where visitors come from. It sets no cookies and reports only aggregate figures.
  • Google Analytics and Microsoft Clarity (only if you accept): see the next section.

Friends

Friends are for signed-in accounts only, and you choose them: someone becomes your friend only when one of you asks and the other accepts. What follows is everything the friends feature keeps, and who can see it.

  • Your friend profile: your Google name and profile picture are kept with your account so that your friends, and people you send a friend request to, see who you are. Someone who played in an online room with you sees only the first name the room already shows them. Your e-mail address is never shown to anyone. Kept while you have an account.
  • Your friend code: eight characters made once for your account, which you share so people can add you. Besides you, it is known to your friends, to anyone you sent a friend request to, and to the screen of a game room your signed-in phone sat in (see Seats in a game room). Nobody gets it from an online room.
  • Friends and requests: who your friends are, and the requests waiting either way. Until a request is accepted, the person who sent it sees only what they asked by: the code they typed or that a game room's seat gave their screen, or the first name an online room showed them; nothing more of yours, and never a code they did not have. A declined request keeps the same person from asking again for 7 days and gives them no code or reference they did not already have. Either of you can remove the friendship at any time; it then goes from both lists.
  • Your games: when your library is read, the titles of your games (each game's console, title and cover name; never a file, a file name, a Google Drive id or a path) are kept so that your friends can look through your library and see the games you have in common. Only accepted friends can see them, and removing a friend stops them at once. Turn off "Friends can see my games" in Settings, under Profile, to delete the list and stop it being kept; turning it on again keeps it from the next time your library is read.
  • Online and playing: while a PlayAgain console you are signed in to is open and on screen, it tells our server every 30 seconds that you are online and which game you are playing. That lasts 60 seconds and is shown to your friends only. No history is kept: no last-seen time and no record of what you played.
  • Invites: an invite to play online goes to the friend you choose, with the game's title and the code of an online room you are in. It lasts 10 minutes, or until the room closes, whichever is first, and only that friend sees it.
  • Seats in a game room: when your phone is signed in and joins a game room as a gamepad, our server notes that your account holds that seat, so the room's screen can show your name if its account is your friend. To anyone else the seat shows only your phone's own nickname, and the screen gets only your friend code, to offer Add friend after the game. The note is removed when your phone leaves the seat, and in any case within 12 hours of the last seat taken in that room.
  • People you played with: after a game room, the screen may offer to add the people who played: by their phone's nickname on a couch, or by the first name an online room showed you. Nothing else of theirs is shown, apart from the friend code a couch seat already gave the screen (see Seats in a game room). The offer for someone met online lasts an hour and can be used once, and never shows their friend code.
  • Removing it: you can remove any friend, decline or take back any request, put away any invite and turn off "Friends can see my games" yourself. Signing a screen out forgets its friends on that screen. To have everything the friends feature keeps deleted with your account, write to us (see Contact).

Netplay and link sessions

Playing online with a friend in another home uses more data than playing around one screen. This section covers Netplay, and link sessions over the link cable or the Wireless Adapter.

  • A room on our servers: while a room exists we store its code, mode, console and the time it was made; each player's account id and first name (a room seats two to four players); a fingerprint of each player's game (its SHA-256); the game titles (which can come from a file's name) and cover addresses; the emulator's build; and whether each player has proved their copy and is connected. A room expires two hours after a player last connected to it, and the note of which room is your latest expires two hours after you made it.
  • Finding your copy: to find your copy of a friend's game, your browser sends us the fingerprints of your games for that console, up to 50 at a time. They are compared with the room's and not kept. A fingerprint is never shown to the other player.
  • Who can see a room: Player 1's first name, game title and cover, and the room's console and mode, are visible to anyone signed in who holds the code. The other players' first names, game titles and covers are visible only to the players in the room.
  • What goes directly between you: inputs, emulator state, Wireless Adapter packets and, in a cable session, each player's in-game save go directly between the players' devices over encrypted WebRTC links, not through our servers. If no direct route can be found, the same encrypted traffic passes through a relay server that cannot read it. Your friend's save is kept only in memory for the session. Emulator state can contain the parts of a game that are in the emulator's memory at that moment; it only goes to a device that has proved it holds the same games.
  • IP addresses: to connect, the browsers in a room swap network details through our servers, which pass them on without keeping them. So each player's IP address reaches every other player's browser in the room while they connect, whichever route they end up on. Each browser also asks Google's public STUN servers for its own public address, and a relay server, when one is used, is run for us by an outside provider and sees the addresses of the players it connects.
  • Saves in a cable session: a cable session's saves go through our servers, so that both players' saves are kept together or not at all. A commit record holds each player's account id, console, cartridge fingerprint and save checksums, and the save each player offered. An offered save is deleted once its point in the session is settled, or else with the record, which is deleted 14 days after the session last wrote to it. A committed save then waits in a queue on our servers until it reaches that player's Drive, and is deleted then. That queue has no time limit: if your Drive cannot be reached, the save waits until a later save read or write gets it there. Your browser also keeps its own copy of each offered save until the room has settled it.
  • Saves in a wireless session: each player's save goes only to that player's own Drive, the same way as when playing alone. It never goes to the other player.
  • Rate limits: we count how often an account makes, looks up, matches or joins rooms, asks for connection details and offers saves. These counters name the account id and are gone within two hours.
  • Error reports: if a session fails or falls out of sync, your browser sends a short report: the step, the emulator, the mode and player seat, the frame, the input delay and round trip, the error's name, message or code, the page address without the room's code, and your browser's user agent. It names no account, room code, file or game, and carries no game or save data. We keep it in server logs and a daily list for up to a week.

Cookies, Google Analytics and Microsoft Clarity

On the landing page we ask whether we may use Google Analytics and Microsoft Clarity. Until you press Accept, neither script is loaded and nothing is sent to Google or Microsoft. Rejecting is as easy as accepting, and the site works the same either way. If your browser sends Global Privacy Control, we treat that as a refusal and do not ask. The console on the big screen and the phone controller never ask; a choice you make on the landing page applies to the console too, and the phone controller never runs either tool.

If you accept, Google Analytics (Google LLC, acting for us) records:

  • which of our pages you view and where you came from (for example a search engine);
  • that you pressed a button that opens the console, that the console opened, that a game was loaded, started, failed to start (with a coarse kind of failure, such as storage or network) or crashed (and on which console, and whether from this device or your Drive), that a phone joined as a controller, and — when the console warned it is too slow for a game, or no phone could run one — that warning, the choice made, or the reason;
  • on the console: whether you signed in (with Google, or with a phone) or went on without an account, and how many games your library holds as a range (none, under ten, ten or more); which console or library game you picked, whether you chose a file from this device (its size only as a range) or from Drive, and what the console found in your Drive (games, none, or a missing permission); roughly how long a game was played (in ranges such as 5–15 minutes); which pause-menu items were pressed (for example Save state or Fast-forward), whether fast-forward, the big-screen mirror or sending to a screen was used, whether cloud saves worked, how many players took part and whether on phones or on gamepads, and the maker of a connected gamepad (for example Xbox or PlayStation); settings switched on or off, fullscreen, the storage panel, and removing downloaded games; on the home screen, which section was opened, that Explore was opened (from its heading or from the empty-library invitation), a console filter or sort chosen there, a favorite added or removed (by console only), the Explore guide closed, the answer on the “Add games to your Drive” sheet, and that games were added (from a console or from a game's page, and whether it was the account's first);
  • your device and browser type and an approximate location (country and city) that Google derives from your IP address; Google Analytics does not store the IP address itself.

It never receives your name, e-mail address, Google account, game files, file names or game titles, exact file sizes, room or screen codes, a gamepad's own id, or anything from your Google Drive. Google signals and advertising personalisation are switched off, so none of it is used for advertising. Google may process this data on servers outside your country, including in the United States. We keep Google Analytics data for 14 months.

If you accept, Microsoft Clarity (Microsoft Corporation, acting for us) records how our web pages — the landing page, the getting-started guide and these legal pages — are used: mouse movement, clicks, taps and scrolling, as heatmaps and as replays of a visit. It never runs on the console, so it never sees room codes, your game library or a game, and never on the phone controller. Text typed into fields is masked before it leaves your browser. Clarity is told that advertising storage is denied. Microsoft may process this data outside your country, including in the United States, and keeps replays for 30 days and heatmap data for 13 months.

You can withdraw your consent at any time — the cookies below are then deleted and both tools stop: .

NameWhat it is forHow longWhen
pa-consentRemembers your answer to the cookie question, on every PlayAgain address: the site, the console and the phone controller (a cookie, and a copy in local storage)12 monthsAlways — necessary
_ga, _ga_<id>Google Analytics: tells visits apart and counts sessions13 monthsOnly if you accept
_clck, _clskMicrosoft Clarity: keeps one visitor id for this site, and joins the pages of one visit into one replaySet by MicrosoftOnly if you accept
CLID, MUID, MR, SM, ANONCHKMicrosoft's own cookies on its domains, which Clarity uses to recognise a browser across sites (Clarity does not use them for advertising)Set by MicrosoftOnly if you accept
pa-first-seenDate of the console's first visit, for counting returning visits (local storage)Until you reject or clear itOnly if you accept
authjs.*, device sessionKeep you signed in, and remember a screen you approvedUntil you sign out or it expiresOnly when you sign in — necessary
Settings and game cacheYour preferences and downloaded games, in this browser's storage; never sent to usUntil you remove themWhen you use the console — necessary
Netplay join code, link save copiesThe code of a room you were invited to (this tab's session storage), and each save your game offers in a cable session (IndexedDB)Until the tab closes, and until the room has settled that saveWhen you play online — necessary

Google Drive access

When you sign in with Google, PlayAgain requests permission to create a PlayAgain folder in your Drive, to read the game files you place inside it, and to keep game saves in the app's own hidden app-data folder. Concretely:

  • What we access: the PlayAgain/ folder the app creates (to list and stream the game files you put there) and the hidden application-data folder (to store your save files). We do not index, list, or open anything else in your Drive.
  • How it's used: game files are streamed directly to the host's browser for play; save files are written so your progress follows you. Game files are never stored on our servers. Save files pass through them on the way to your Drive and are not kept, apart from a cable session's saves, which wait there as described under Netplay and link sessions.
  • Save records: for each game with a cloud save we keep, under your account id and the game's fingerprint, the save's generation number, checksum, time and the device that wrote it, so that an out-of-date device cannot overwrite newer progress. These records have no expiry.
  • Revoking access: you can disconnect PlayAgain at any time at myaccount.google.com/permissions.

Limited Use disclosure

PlayAgain's use and transfer of information received from Google APIs to any other app adheres to the Google API Services User Data Policy, including the Limited Use requirements. In particular: Google user data is used only to provide the features described above; it is never sold, never used for advertising, never transferred to third parties, except that a link cable session you start sends your in-game save to the friend you invited, directly between your two devices, as described under Netplay and link sessions, and never read by humans except with your explicit consent for support, for security purposes, or as required by law.

What we don't do

  • No selling of personal data, and no sharing with third parties beyond what this page describes.
  • No advertising trackers. Google Analytics and Microsoft Clarity run only with your consent, with their advertising features switched off.
  • No storage of controller inputs or gameplay — only the anonymous daily counts above and, for a cable session, the saves described under Netplay and link sessions.

Contact

Questions? Reach us at cxbilen@gmail.com.