Privacy notice

Who we are

CornyBits runs games such as trivia, number bingo and polls at venues. This notice covers this website, the CornyBits management app, the play and display app, and the CornyBits server they all use.

The operator is operator legal name, of registered address. The information officer is name and contact. Legal review will confirm how responsibilities are shared between CornyBits and each venue under the Protection of Personal Information Act and any other law that applies.

What we store

Venues, outlets and billing

• Organisation and outlet names, timezone, language, country, branding (accent colour and logo), game defaults, security settings and the guest retention period.
• The plan, the number of paid outlets, subscription status and the payment provider's transaction references. Card details are handled by the payment provider (payment provider) and are never stored by CornyBits.

Staff

• Name, email address and password. The password is stored only as a one-way hash that cannot be turned back into the password.
• Whether the email address is verified, whether two-step sign-in is on, and organisation and outlet roles.
• Invitations: the email address invited and the role offered.
• Sign-in sessions, with a device label, browser details and IP address, so staff can review and end them.
• An audit record of staff actions: who did what and when, the reason where one is required and, for some actions, the IP address.
• If an outlet is linked to EventSync, EventSync receives the name and email address of the staff member who approved the link, the name of each game's host (or, for a game without a host, of whoever planned it), and the name of the staff member who ends the link in CornyBits.

Game content

• Packs, questions, answers, sources, and uploaded images and audio with their descriptions.

Players who join as guests

• The display name and team name chosen, the game joined, when they joined and when they were last seen.
• Answers and how long each took, captions, quotes and votes sent, the bingo card dealt and any claims, and the score lines that make up the result.
• A rejoin key, so a player can return to the same game after a dropped connection. The key stays on the player's phone, and the server keeps only a hash of it.

Players with an account (optional)

• Email address, display name and the list of games played, with results.
• A marketing preference that is off unless the player turns it on.
• Sign-in uses one-time codes sent by email.
• Any venues the player has chosen to share their details with, whether they want each venue's news and offers, the wording they agreed to, and when they agreed, changed their mind or stopped. See sharing with a venue.

Screens

• Paired screens, their label and when they were paired. The IP address that asked for a pairing code is kept with that code, which is deleted after one day.

EventSync links (only if a venue links an outlet to EventSync)

• The EventSync organisation and account names and identifiers, which outlet the account is linked to, the name of the person who asked for the link in EventSync, the CornyBits staff member who approved it, and when and by whom the link ended. From EventSync, CornyBits receives people's names only, never their email addresses: who asked for the link, who linked a game to an event and who ended the link.
• For a game linked to an EventSync event, that event's identifier, name and start time.
• Signed records of the updates exchanged between the two products. Updates that were sent, cancelled or stopped retrying are deleted after 30 days, except that a player's withdrawal that stopped retrying is kept until it is sent or no longer needed.

Email

• CornyBits sends email for verification, password resets, sign-in codes and invitations, through mail provider.

Sharing with a venue

A venue that also uses EventSync can link its CornyBits outlet to its EventSync account. A player can then choose to share their details with that venue, when they join a game or on the final results. It only happens when a signed-in player with a verified email address ticks the box, at a venue whose outlet is linked. Nothing is pre-ticked, and neither a CornyBits marketing preference nor the venue being linked counts as agreeing. Every player who joins a game at a linked venue is told that the venue sees the names and scores from that game.

What the player agrees to

• To share anything: “Share my name, email and game results with [venue] so they can recognise me.”
• Optional, only when sharing: “Send me news and offers from [venue].”
• Shown with them: “This covers this game and the games you play at [venue] from now on. [venue] keeps its customer records in EventSync. You can stop sharing at any time in your CornyBits profile.”

In each case [venue] is the venue's name. The exact text the player saw is kept with their choice and is what the venue receives as proof, even if the wording or the venue's name changes later.

What the venue receives

• The name and verified email address from the player's CornyBits account.
• Whether the player wants the venue's news and offers.
• The exact wording the player agreed to, and when.
• Which of their games at that venue they played since sharing, including the game in which they shared, with their team, place and points.

What happens in EventSync

• EventSync matches the player to the venue's existing customer with the same email address, or creates a new customer. That customer record is the venue's own data in EventSync, held under the venue's own responsibility.
• The player is only recorded as wanting the venue's news and offers if they ticked that separate box. Turning it off later unsubscribes them from that venue's marketing.
• If the player stops sharing, the venue keeps the customer record but stops receiving new results linked to them, and, if they had agreed to the venue's news and offers, EventSync unsubscribes them from that venue's marketing. EventSync also clears the copy of the name and email it kept for the link.
• If the venue deletes the customer in EventSync, sharing with that venue ends, the player's profile says the venue removed their details, and the customer is not created again unless the player chooses to share again.
• Updates from a venue's link only ever change the records of players who shared with that venue. One venue's link can never change another venue's customers in EventSync.

Games sent to EventSync

• For a linked outlet, CornyBits sends each game's title, times, formats, the host's name (or, for a game without a host, the name of whoever planned it), player and team counts, and final standings with display names. Demo games are never sent, and rehearsals are marked as rehearsals.
• Players who did not share appear in the standings only by their in-game display name, and are not linked to a customer. When guest names are anonymised under the retention rules below, the standings are sent again with the anonymous labels while the outlet is linked. Once a game is no longer covered by an active link, EventSync replaces those names with “Guest” itself within a day.

Stopping

• In their CornyBits profile, under Venues, a player can turn a venue's news and offers off, or stop sharing with it, at any time.
• Deleting the CornyBits player account withdraws every share.
• If the venue's outlet is no longer linked to EventSync, sharing with that venue ends. A choice the player made before then, such as stopping sharing or turning offers off, is still passed on to the EventSync account it was made for. If the player had agreed to the venue's news and offers, the venue may still send them: the player can use the unsubscribe link in its emails or ask the venue, and their profile says so.
• Choices are kept for each EventSync account the venue's outlet has been linked to. If the venue links its outlet to a different EventSync account, the player chooses again there: nothing they agreed to for the earlier account carries over, and a choice they made for the earlier account only ever reaches that account.
• If the venue deletes the customer in EventSync, sharing with that venue ends.
• The profile lists venues the player no longer shares with, and why the sharing ended.

What we do not do

• This website loads no third-party trackers, analytics or advertising scripts, and no fonts or files from other sites.
• Playing never needs an email address. Making a player account never signs anyone up for marketing.
• Player email addresses are never shown on screens or to other players. A venue only receives one when the player chooses to share it with that venue.
• A player's CornyBits marketing preference is kept separate from playing, and never counts as agreeing to a venue's news and offers.
• Answers are judged by fixed rules and by the host, never by AI.

On your device

• This website stores nothing in your browser. Its checkout page, where a venue pays for a plan, opens the payment provider’s checkout, which runs under that provider’s own privacy notice.
• The play app stores a rejoin key for each game you join, so you can return to it, along with the name you last played under and your theme choice.
• If you sign in with your email, the play app keeps a sign-in token on your device (in the phone apps, in the device's secure storage) so you stay signed in until you sign out.
• If you choose “Not now, don't share” when asked whether to share your details with a venue, the play app remembers that for that game so it does not ask you again.
• The management app keeps staff signed in with a secure cookie that scripts cannot read, used only by the CornyBits server.

How long we keep it

• Guest players: once a game has ended and the venue's guest retention period has passed, display names are replaced with an anonymous label and caption text is removed. The period is 180 days unless the venue sets anything from 30 days to three years. Scores stay so results remain correct.
• Sooner on request: venue staff with permission can remove a player's personal details at any time. The scores are kept without the name.
• Player accounts: kept until the player deletes the account. Deleting it also anonymises the player's past games and withdraws every share with a venue. A venue keeps the customer record it already holds in EventSync.
• EventSync link updates: updates CornyBits sent to EventSync, cancelled or stopped retrying are deleted after 30 days. Updates still waiting to be delivered are kept until they are, and so is a player's withdrawal that stopped retrying, until it is sent or no longer needed.
• Codes: player sign-in codes are deleted after one day. Email verification links, password reset links and staff sign-in codes are deleted after seven days. Screen pairing codes are deleted after one day.
• Everything else is kept while the organisation exists, including after a plan expires. What happens after an organisation closes is to be confirmed.

Your choices

• Players with an account can see their game history, export their data, change their display name and marketing preference, and delete the account, all from their player profile. Under Venues in the profile, they can turn a venue's news and offers off or stop sharing with it.
• Guests can ask the host to correct or remove their name, or contact us.
• Staff can change their name and password, turn on two-step sign-in, and see and end their sign-in sessions.
• Venues can correct or remove player records, set the guest retention period and export players and reports. Exporting personal data needs its own permission.
• Requests and questions: hello@cornybits.com (placeholder address).

Security

Each organisation's games, packs and players live in a separate database. Staff, players and screens use separate, short-lived credentials that only work for their own purpose. Answers, hidden quote authors and captions waiting for approval are never sent to phones or screens before they are revealed.

Still to be confirmed

• The operator's legal name, address and information officer.
• Where data is hosted, and the list of service providers that process it.
• The payment and email providers.
• Retention after an organisation closes, and backup retention.
• How requests are verified and answered, and how changes to this notice are announced.

See also the draft terms of use.