House of Hundred

Privacy, simply.

Visitor analytics

House of Hundred counts visits to the studio pages and Rankly to understand how people find the site and what devices, browsers, and operating systems they use. The report groups this information into broad categories. This browser uses random identifiers to estimate visitors, sessions, and returns. The visitor identifier expires after 90 days, and a new session starts after 30 minutes without a page view. We keep the daily traffic summaries for up to 100 days.

When you access an online Rankly room with a known player identity, the administrator can see your game display name, recent room visits with device, browser, and operating system categories, and the rooms associated with that identity. Rankly keeps up to 100 days of visit history. Turning off visitor reports stops collection for both visitor reports on this browser.

The general traffic counts exclude room codes, invitation URLs, Firebase account IDs, rankings, and conversations. The site sends Google Analytics a public studio page address and the referring hostname if you enable it below. Google Analytics uses browser cookies and processes technical information under Google’s privacy policy.

Playing Rankly on one phone

Rankly saves your unfinished game, player names, custom cards, and preferences in this browser so you can return to them. Pass-the-phone games stay on your device. Clearing the site’s browser data removes those saves.

If you choose Save this game on a finished results screen, Rankly keeps a separate copy of the revealed rankings, final scores, and conversations on this browser. This also applies to copies you save from online games. Saved games are not uploaded or synced across devices, and rematches do not erase them. You can update a copy from its finished results screen or delete it under Saved games. The archive holds up to 20 games within a 5 MB limit; clearing browser data removes it.

Unsent answer, reply, and card-question drafts also stay in this browser and follow you between the reveal and reopened conversations. Rankly restores them for up to seven days after your last edit. Draft text is not uploaded before you post it; clearing the site’s browser data removes saved drafts.

A first-party cookie and browser storage remember cards you have seen so future games can show you more variety. This history contains card identifiers, not advertising identifiers, and stays specific to this browser. Clearing the site’s cookies and browser data resets it.

Playing Rankly online

Online play uses an anonymous Firebase identity to keep your place. You don’t need to give us an email address or create a password. Room codes, player names and avatars, rankings, guesses, custom cards, explanations, replies, and posted card-specific questions and answers are stored in Firebase so the game can work across phones.

Other players in your room can see the parts of the game intended to be shared, including revealed results and complete conversations. Revealed rounds can be reopened during play and at the end, and players can add answers or replies later. Room permissions differ: some require membership and invitation confirmation, while others also allow a read-only projector view. Treat codes and invite links as private and play with people you trust.

When the host starts again or returns to setup after a finished online game, Firebase automatically retains that game’s revealed rankings, scores, player identities, custom cards, and latest posted conversations in the room’s history. Original participants who are still room members can reopen this read-only snapshot across devices using the same player identity. Earlier games cannot be edited after that change. New members cannot read games they did not participate in, and reclaiming a name under a new identity does not transfer that access. Access also depends on the room’s current permissions. This shared history is separate from the browser-only Saved games copies described above.

A room keeps up to 20 completed games within an 8 MiB shared history limit, removing older games when needed. Only finished games are added to Past games when a new game starts. Scheduled cleanup moves whole rooms out of active play after 60 days without intentional player activity, with grace for scheduled starts and pending long turns. Archived rooms keep their published results and retained history read-only under the same membership and access rules, and an administrator can restore them. Historical statistics and gameplay identity records remain. Clearing browser data removes local copies and may remove your anonymous identity, but does not delete shared room data.

Opening a room in the foreground or taking a game action records player activity for cleanup. Background room lists, presence signals, and automatic timer moves do not count. Accounts without a current room are separated from the current-player directory; after 60 days without their own activity they are also marked dormant. This does not automatically delete an account, suspend access, or remove a quiet person from an active group. Joining or creating a current room brings an account back into the current directory.

While someone writes an answer or reply online, a short-lived signal can show other room members who is typing in that conversation. The signal uses Firebase and includes no draft text.

After a reveal, you can optionally share Your take: your own ranking of that round’s cards. It is visible to the game’s players, changes no scores, and can be edited while that game remains current. Group insights describe published personal rankings and common choices; predictions about someone else are not treated as your preferences. Insights from earlier games follow the same history access rules as their results.

Rankly keeps first-party operational summaries to understand gameplay and run the service: room and gameplay identity records, game modes, participant counts, published round counts, topic exposure, and counts of conversation activity. The summaries used for platform charts do not contain card text, rankings, guesses, or written conversations. Summary and management records can remain after room content expires. Administrators can review room activity and gameplay identities, pause rooms, and suspend or restore gameplay access. These summaries are not advertising profiles.

While an online room is visible and focused, Rankly also sends Firebase a random tab identifier and a recent activity timestamp to help avoid alerts while you are already viewing that room. This activity signal is treated as inactive after 45 seconds without an update and includes no draft text.

Your browser remembers your player profile and a list of up to 50 rooms, with private group labels, pins, and the last room you opened. Labels and this list stay on this browser and are not shared with other players or synced across devices. Switching rooms keeps your membership and each group’s game progress. Removing a shortcut only removes it from this browser’s list; Leave room removes your place in that group. Clearing browser data removes the list and may also remove the anonymous identity used to return to your rooms.

Unsubmitted online rankings and list matches are kept on this browser for up to seven days so you can switch groups and return to your work. Only your own choices are stored, and they are not submitted to the game until you lock them in. Co-op captains can also share their board with teammates while arranging it. During Whose List matching, Firebase privately tells each player which list is their own; other players cannot read that assignment before the reveal. Rankly also stores game files on your device for faster loading and offline pass-the-phone play.

Optional administrator sign-in uses Google and Firebase Authentication to verify the administrator’s account email. When possible, it links to this browser’s existing player identity; switching to an already-linked account requires confirmation. Other players can continue using anonymous sign-in. Administrator status and room permissions are checked by the server and are not granted by a player name or browser preference.

Rankly’s notification preference starts on, but delivery requires your browser or phone’s permission. While the preference is on, Rankly registers this device automatically if permission is already granted, or asks for approval once when you first create or join a game on a supported device. Your explicit choice to turn notifications off is remembered.

After permission is granted and registration succeeds, Rankly stores a device delivery token with your anonymous player identity in Firebase for your-turn, reveal, and conversation alerts. It does not register devices with undecided or denied permission, or an iPhone or iPad browser tab outside the installed Home Screen app. Notifications use general messages and do not include private rankings, card choices, or written comments. Bursts of activity in a room may be grouped into the latest relevant alert and sent about one to two minutes later. You can turn them off in Rankly’s notification controls or your browser’s settings.

When you create or join an online game, recent card identifiers from this browser help the room avoid repeats for its players. This card history is kept with the room’s private game data and is not shown to other players.

Contact and hosting

If you choose to email us, your email provider sends your message to alex@houseofhundred.com. Please share only the information you want to include in that conversation.

Firebase, our hosting and game service provider, may process technical information to deliver and secure these services. You can read Google’s privacy policy for its practices.

For privacy questions or a request about your online game data, email Alex with the relevant room code. Don’t send passwords or other sensitive information.