Beaver

Privacy Policy

Version: 2026-11-09

This Privacy Policy explains how Beaver ("we", "us", "our") collects, uses and protects your personal data when you use the Beaver mobile app or our website, www.beavergames.co.uk. We are committed to protecting your privacy and complying with the UK General Data Protection Regulation (UK GDPR).

1. Who we are

Beaver is an outdoor game app published by William James Varcoe, Ballards Barn, Westerham Road, Oxted, RH8 0SL, United Kingdom, which is the data controller for your personal data. If you have any questions about this policy or your personal data, please contact us at will@beavergames.co.uk.

2. What data we collect

We collect the following personal data when you use the app:

  • Account information: your display name and email address, provided when you create an account.
  • Sign-in: if you sign in with Google, Microsoft or Apple, we receive your name and email from them (Apple may give us a private relay address).
  • Location data: your GPS position while the app is in use. It is used to check that you are at a checkpoint and to show your team's position (the team pin: one teammate's precise position, sent while Beaver is open on that phone). The team pin is stored and shown to the game's organiser and to Beaver's team; other players in your game see it only when the game's items allow it. While a game is running, our server also keeps the team pin as your team's route, for the game replay (section 11).
  • Photos: images you submit as part of checkpoint completions or side quest submissions, and photos you add to your team's profile or to a checkpoint you create with an item. They are kept in our cloud storage and reviewed by the organiser of your game and the Beaver team. Players on other teams in your game can see the photos you send unless you keep a photo private, and a photo you have not kept private may also be shown after the game (section 11).
  • Practice mode: when you start a practice run, your position is used to place practice checkpoints near you, and is sent to Mapbox (our map provider) to find public paths and places nearby. Your practice checkpoints, answers and points are visible only to you and are deleted when you finish, after two hours, or when your game starts. Photos you take in practice stay on your phone. We keep the times you started and ended practice for two days, to apply the daily limit.
  • Out-of-bounds areas: in a game that has them, your phone compares your location with the areas on the phone itself. If you stay inside one, your phone sends the area, the time, how deep you were and where you entered to the Beaver team. It also says whether the phone reported the location as a mock (fake) location and the best accuracy of the location signal, and our server marks a record that looks doubtful (for example an entry far from the area's edge, or a very shallow one). Our server also compares your team's position with the same areas, and records the same thing, with the account of the player whose phone sent the position, when a team stays outside the play area or inside a no-go area for longer than the area's grace period (20 seconds today). The server also keeps a short list of the team's positions that were outside the areas (the game, the team, the area, the time, the position and how far outside), so the Beaver team can see where a team went. We keep the place of entry for 90 days after the game and the list of positions for 14 days, and we delete the place of entry at once if you delete your account; we keep the rest with the game record. We use it to keep players safe and to apply the game's rules, and for nothing else. If you delete your account it is no longer linked to you.
  • Chat messages and text answers: the messages you send in your game's chat and your text answers to quests. Also, if you use them, your notes and mentions in chat, and the messages you send to another team while the Beaver team has that feature switched on (section 11). On a quiz that limits how many guesses a team may make, the wrong answers a team types are saved too, up to 120 characters each, against the team and not against you.
  • Device push token: a unique identifier used to send you in-app notifications about your game activity (for example submission approvals, messages and announcements: see section 11). We do not use this for marketing.
  • Game activity: your in-game actions, scores, and team membership within a game session. During a game this includes which team is alone in first place and for how long, and which team held which item (section 11).
  • Clock checks: while you are a player in a game, your phone's clock readings and some technical details of the app, so that breaks happen at the same moment for everyone (section 11).
  • Feedback you send us: what you write, with a short technical report, if you choose to send feedback (section 11).
  • When you last opened the app: current versions of the app no longer record the time you last opened it; only older versions did, so a time may still be held for you from then. Nothing uses what was stored, and we plan to delete it.
  • Purchase records: when event codes are on sale on our website, a purchase leaves a record that holds the payer's email and the Stripe payment reference, and it is linked to your account when you redeem its code in the app. Codes given as comps or to reviewers create the same record, without a payment.

When you use our website, we also collect:

  • Website purchases: only when event codes are on sale on our website: see section 6.
  • Contact form: the name, email, organisation and message you send, delivered to us by email.
  • Event bookings: the details you give when you book a place at an event on our website: see section 7.
  • The Beaver Community: if you choose to join, your email address and name, here or in the app: see section 8.
  • The feedback questionnaire: if you fill in the anonymous questionnaire on our website after a game (/feedback), we keep your answers (the written ones, and the questions about you such as an age group), the version of the questions, the date you sent them (not the time) and, if the link you used had one, a tag for the event. No name, email address or IP address is stored with them, and the form asks you not to put names or contact details in the text boxes, but anything you type is kept exactly as you wrote it. The address your visit comes from is used only in the memory of our website's server, to limit how many answers one connection can send in ten minutes; our website host's ordinary request logs still hold it, as for any page (section 5). Until you send the answers, a draft is kept in your browser's session storage; it is removed when you send them and ignored once it is six hours old. The answers are stored with Supabase and read by the people at Beaver Games who have administrator access to our database, which includes the AI assistant named in section 5. There is no automatic deletion: we keep them until we delete them.
  • One cookie: set only when event codes are on sale on our website and you start a payment: see section 9.
  • Visitor statistics: counts of the pages people look at on our website, kept under a daily code that stands in for you, not your name: see section 10.

3. How we use your data

We use your data to operate the Beaver game platform and the events you book, and, only if you join The Beaver Community, to tell you about other events:

  • To create and manage your account
  • To verify checkpoint and quest completions
  • To display live scores and activity to other players in your game session
  • To send you notifications about your game activity
  • To show your team's position to the organiser of your game and to Beaver's team, and to other players when your team holds 'visible to all' or theirs holds 'see all players'. A team holding 'hidden location' is not shown to other players during the game; its position is still sent and stored, and the organiser still sees it.
  • To check, from your team's position, whether a team is outside the play area or inside a no-go area, and to tell the game's organisers
  • To show photos you have not kept private to the other players in your game, and afterwards in the game's photo gallery and, where it includes them, in the game's replay (section 11)
  • To make the end-of-game replay of the event from the routes teams walked, so the people who took part can watch it (section 11)
  • To keep breaks and game timers the same for everyone, and to tell a team if a phone's clock was moved (section 11)
  • To show which team is in front and for how long, and which team picked up an item, and to tell teams when an item is picked up (section 11)
  • To let players write to each other, to send notifications about messages and announcements, and to let an organiser write to the whole game (section 11)
  • To fix problems you tell us about (section 11)
  • To deliver event codes, when they are on sale on our website, and to answer messages sent through our contact form
  • To take your booking for an event on our website, keep your place, tell you about the event and email you about your booking (see section 7)
  • To email you news of other Beaver Games events, only if you have chosen to join The Beaver Community (see section 8)
  • To read the answers to the anonymous questionnaire on our website, so we can see how an event went and improve it (see section 2)
  • To count visits to our website and see where they come from, without your name or email address (see section 10)

We do not use your data for advertising, profiling, or any purpose unrelated to the game. The exceptions are The Beaver Community, which you choose to join and can leave at any time (section 8), and the visitor statistics for our website, which we use only to understand how many people visit and where they come from (section 10).

4. Legal basis for processing

We process your personal data on the basis of contract performance: processing is necessary to provide you with the Beaver game service you have signed up for, and to supply an event code you have paid for. Location sharing features rely on your consent, which you can withdraw at any time through your device settings. For event bookings, we use your details to take and run your booking, and we ask for your consent (the tick box on the booking form) for anything you tell us about health or access needs in the notes box. The Beaver Community (section 8) is based only on your consent, given by ticking a box that is never ticked for you. Counting visits to our website (section 10) is based on our legitimate interests in understanding how the website is used and improving it. We keep it to what that needs: no name, email address or IP address is stored with it, and you can object to it (section 10). We keep purchase records because the law requires us to keep accounting records (legal obligation).

For the things described in section 11 we rely on our legitimate interests: in running a fair and safe game (clock checks, the who-is-in-front record, the item history and the out-of-bounds checks), in showing an event back to the people who took part (the team route, the photos and the replay), in letting players talk to each other and be notified (messages, announcements and notifications) and in finding and fixing problems (feedback). Where a photo is shown beyond the game, you can choose to keep it private (section 11).

5. Third parties

We use the following trusted third-party services to operate the app and the website:

  • Supabase (supabase.com): secure cloud database and file storage for your account data, game data, submitted photos, event bookings, and the website visitor statistics (section 10), including the request that makes the visitor code. Servers are located in the European Union (Ireland).
  • Expo / EAS (expo.dev): app infrastructure and push notification delivery. A notification passes through Expo to your phone's maker (Apple or Google), and it contains the text shown on your lock screen (section 11).
  • Mapbox (mapbox.com): map rendering. Apart from practice mode (section 2), Mapbox does not receive your location from the app: it is used on your device to check proximity to checkpoints, and the map's telemetry is switched off. In practice mode your position is sent to Mapbox to find public paths and places nearby. The game replay page (section 11) loads its map from Mapbox, so the browser on the screen that shows it contacts Mapbox and sends its IP address. Mapbox's map library on that page also sends anonymous usage events to Mapbox and keeps an anonymous identifier in that browser's local storage (not a cookie). We cannot switch that off completely.
  • Google, Microsoft and Apple: sign-in providers, if you choose to sign in with one of them.
  • Shotstack (shotstack.io): makes the end-of-game highlight video, if the game's host asks for one. It receives the approved quest photos that players have not kept private, with team names and quest titles. A photo that is private when the video is made is not sent to it. If a video is made, the players of the game can watch it from the game-over screen, at a web address on our video provider's site that anyone who has the address can open. When you delete your account: Game highlight videos that show your photos are removed from the app straight away (the host can make a new one without them). Our video provider deletes its copies within 24 hours, or within 7 days if we have to finish the deletion by hand.
  • Anthropic (anthropic.com): makes Claude, an AI assistant that the Beaver team uses, with access to our database tools, to run and look after the service, which includes reading and sorting the feedback you send us and the list of The Beaver Community.
  • Stripe (stripe.com): payments, when event codes are on sale on our website. It then receives your email and the purchase when you buy an event on our website (see section 6). The app takes no payments.
  • Resend (resend.com): sends the emails about event bookings (your confirmation, any waiting-list or cancellation email, and a notice to our team), our contact-form emails and, when event codes are on sale on our website, the email that delivers an event code. It receives the recipient's address and the message.
  • Vercel (vercel.com): hosts our website and keeps request logs (IP address and the page requested) for up to 30 days. When event codes are on sale, the address of an event-code page (/redeem/…) will therefore appear in those logs, and the requests that count visits to our website (section 10) do already. The same holds for the game replay page, if we host it on our website.
  • WhatsApp (whatsapp.com, owned by Meta): used for the WhatsApp group of an event you have booked. It receives the phone numbers of the people we add to the group, and the other people in the group can see who is in it (section 7).
  • OpenStreetMap, YouTube and Vimeo (on our website only): the small street maps on the photo gallery page (/photos) and on event pages load their map pictures from openstreetmap.org, which therefore receives the visitor's IP address and the map area being shown. An event page that has a video may load it from YouTube (its no-cookie address, youtube-nocookie.com) or from Vimeo (with its do-not-track setting on), which then receive the visitor's IP address, as any site a browser contacts does.

We do not sell, rent, or share your personal data with any other third parties.

The database is hosted in the European Union (Ireland). Some of the providers listed above are based in, or handle data in, the United States or other countries outside the UK. Where they do, they rely on safeguards the law allows (for example the UK-US data bridge or standard contractual clauses), as described in their own terms.

6. Buying an event on our website

This section applies when event codes are on sale on our website.

  • Our website sends Stripe no personal data. Stripe collects the cardholder's name, billing address, email address and card details on its own payment page.
  • Stripe returns the email address to us, and we store it on the event-code record for six years after the end of the tax year in which the purchase was made. The name and billing address stay with Stripe: our systems receive them from Stripe with the payment confirmation, but store only the email address. Our website never reads them, although the payment key it uses to start a checkout could.
  • We send Stripe the event, the price and internal reference numbers.
  • The email that delivers your code repeats the order details: the price and payment date, the VAT line, what the code works with and how long it lasts, the terms version, the refund summary, and our name and address. You keep it, and Resend keeps it for its own retention period. If it cannot be delivered, we send you the same text from our support address.

7. Booking an event on our website

You can book a place at an event on our events page. Here is what that involves.

  • What we collect: your name, email address and phone number (the phone number is optional unless the form says it is required), how many people and how many teams you are booking, the names and phone numbers of the other people in your party, and any notes you add. We use the phone numbers to add everyone in your party to the WhatsApp group for the event.
  • Why: to take your booking, keep or release your place, email you your confirmation, tell you about the event, and run it on the day.
  • Who sees it: the Beaver Games team; Resend, our email provider, which sends your booking emails; and WhatsApp (owned by Meta), which receives the phone numbers of the people we add to the event's WhatsApp group. The other people in that group can see who is in it. Your booking is stored with Supabase (section 5). We do not sell it.
  • Your private booking link: your confirmation email has a private link that lets you see or cancel your booking. Anyone who has the link can do that, so keep it to yourself.
  • Other people: if you give the names of other people, please check with them first that they are happy for you to do so. We use their names only to run the event.
  • Notes: the notes box is optional. If you tell us about health or access needs, we use it only to make the event work for you, and you can leave it blank.
  • How long we keep it: we keep your booking details until 12 months after the event, and then erase them automatically. This includes bookings that were cancelled.
  • Asking for it to be removed sooner: email will@beavergames.co.uk and we will erase your booking details.

8. The Beaver Community (optional)

When you create an account in the app, and when you book an event on our website, we ask whether you would like to join The Beaver Community. It is optional, the box is not ticked for you, and your account or booking does not depend on your answer.

  • What it is: if you join, we email you news of other Beaver Games events, which you can share with friends and family. We do not send you anything else through it, and we do not sell your details or pass them on.
  • How you join: ticking the box is all you need to do. You are added to the list as soon as you tick it, and we do not email you a link to confirm. Your booking confirmation email says that you are in and has an unsubscribe link; in the app, the switch in Profile shows it. If you ticked the box on our website before 10 November 2026 and never pressed the confirm link we emailed you, you were not added, and that request is deleted after 30 days.
  • What we keep: your email address and name, when and where you joined (the app, or which event you were booking), and which version of the question you saw.
  • Why we may do this: only because you said yes. Your consent is the legal basis, and you can withdraw it at any time.
  • How to leave: use the unsubscribe link in any Community email or in your booking confirmation, or switch it off in the app (Profile → The Beaver Community). It takes effect at once, and we delete your name.
  • Who sees it: the Beaver Games team, and Resend, the email service we use when we send you an email (section 5). The list is stored with Supabase (section 5). It is read with the same database tools as feedback (section 11), including the AI assistant named in section 5.
  • How long we keep it: until you leave. If you joined in the app, your record is deleted when you delete your Beaver account; if you joined on our website, use the unsubscribe link or email us. After you leave we clear your name and keep the rest of the record as a record that you asked not to hear from us, so that we respect that (our legitimate interest): your email address, when you joined (and when you confirmed, if you did so by a link we emailed you before 10 November 2026), where you joined (the app, or which event you were booking), which version of the question you saw, the date you left and how (in the app, or by the link in an email), the random code behind the unsubscribe link (and behind any confirm link we emailed you) and, if you joined in the app, your account number. Email us if you want that erased as well.
  • If someone used your address: anyone can type an address into a form, and we do not check that it is yours before adding it. If you did not ask to join, use the unsubscribe link in your booking confirmation email and you will not hear from us, or email will@beavergames.co.uk and we will remove it.

9. Cookies

Our website sets no cookie for visitors today. When event codes are on sale on our website it will set one, and only when you start a payment. It is strictly necessary: it lets the thank-you page show your event code to you and nobody else. It expires after 24 hours. Booking an event sets no cookie. A separate sign-in cookie is set only for our own team when they sign in to the private admin page; it is never set for visitors. We use no analytics or advertising cookies, and our visitor statistics (section 10) use no cookies or similar storage at all. Two pages keep a little in your browser's session storage while you use them, which is emptied when you close the tab: the photo gallery keeps the code you entered, and the questionnaire keeps a draft of your answers (section 2). The events page keeps your choice of calendar or list view in your browser's local storage, which stays until you clear it.

10. Website visitor statistics

We count visits to the pages of our own website, so we can see how many people come, which pages they look at and where they come from. We use no cookies or browser storage for this, and we store no name, email address or IP address with it. The records are still personal data, because each carries a code that stands in for you for a day, so this section says exactly what happens.

  • What runs on your device: a small script on our pages sends the page address and the website you came from to our own server when a page loads. It reads nothing stored on your device and puts nothing there, so we do not show a cookie banner for it.
  • What we record: for each page you look at, the page address (without anything after a question mark, and without the private part of a booking link), whether it was the first page of your visit, the website, search engine or campaign tag in the link that sent you to us, the kind of device (phone, tablet or computer), your browser and operating system in broad terms, your country (our website host works it out from your IP address, and we keep only the country), the time of the view, and a short code.
  • How the code is made: so that we can count a visitor once a day, our database makes the code from your IP address and browser details mixed with a random value (a "salt") that is made fresh every UK day. The IP address and browser details are not stored in our database. They are sent from our website to our database provider, Supabase, in the request that makes the code. Our website host, Vercel, also keeps ordinary request logs that include these requests, for up to 30 days. Those logs do hold your IP address, so a record here could be matched with one of them by its time while they last.
  • A pseudonym, not anonymous: while a day's random value still exists, someone with access to our database who already held a list of possible IP addresses could in theory match a code back to an address. So we treat the codes as personal data and protect them with the same access controls as our other data. We delete each day's random value when it is about two days old, after which the code can no longer be recreated from an address. Database backups kept by our provider can hold a copy for a short time longer (section 12).
  • Who is not counted: our own team while signed in to the admin pages, robots and link-preview programs, and anyone whose browser sends a Do Not Track or Global Privacy Control signal, which we respect.
  • Why we may do this: our legitimate interests in understanding how the website is used and improving it. We use the records only to understand how many people visit and where they come from.
  • Who sees it: the Beaver Games team, on a private admin page. The records are stored with Supabase (section 5). We do not share them with anyone else, and no advertising or analytics service receives them.
  • How to object: email will@beavergames.co.uk (section 13). We cannot pick out your records from a code alone, so the simplest way to avoid being counted is to switch on Do Not Track or Global Privacy Control in your browser: our script then sends nothing.
  • How long we keep it: page view records are deleted automatically after 400 days (a little over 13 months). A job that runs every day does this and deletes the old random values.

11. What the app saves during and after a game

This section describes what the app and our server keep while a game is waiting to start, running or finished, beyond the basics in section 2. Where it says "the Beaver team" it means the people at Beaver Games who run the service. Where it says "the organiser" it means the person running your game, and the Beaver team members connected to it.

Game replay (your team's route)

While a game is running, our server saves where your team is, so that after the game the organiser or the Beaver team may play a map replay of the event for the people who took part.

  • What we collect: the position of your team's pin (the position one phone per team sends, about every 20 seconds, only while Beaver is open on that phone), with the time and your team. The time is our server's clock, not your phone's. It is saved against your team and not against your account: it holds no name and no account number. If the phone has no signal, nothing is saved for that time. In a team of one, the route is yours. Nothing is saved in practice games or in a game that is not running, and an organiser's phone is not recorded.
  • What the replay shows: team names and colours, where each team went, the checkpoints, steals and item moments, the distance each team covered and, unless the game hides its scores, the scores and when the lead changed (only the Beaver team can put hidden scores on a replay). A game that hides its scores still shows the points of single moments on its replay, such as a checkpoint or the size of a steal, but no totals and no lead changes. It may include photos teams took at checkpoints and for quests, but not those they have kept private. It never shows player names, chat messages, quest answers, out-of-bounds records or anyone's account details. By default a route is drawn cut off at the edge of the play area, so a screen does not show where a team stepped outside it. A team that was hidden on the map from other teams during the game (hidden location) is shown in the replay once the game is over.
  • Where it is shown: when a replay is played, it is shown on a screen at the event (a television, a projector or a laptop), from a private, view-only link that an organiser or the Beaver team makes after the game has finished. Anyone who holds the link can watch that game's replay until the link stops working: after 12 hours unless a different time between 1 and 24 hours was chosen, or sooner if it is switched off. The Beaver team can switch off every replay at once. We store only a one-way fingerprint of the link, never the link itself, and we count how many times and when it was last opened. The replay page loads its map from Mapbox and the photos from Supabase, so the browser on the screen contacts them (section 5).
  • Leaving your team out: any member of a team can leave the whole team out of the replay in the app (Profile, then Game replay, or on the notice the app shows once). That stops the recording for the team, deletes the route already saved for it at once, and leaves the team out of every replay from then on. You can also ask us to do this by email: write to will@beavergames.co.uk and we will leave your team out and delete its saved route. The Beaver team can switch the recording off for a game. A route that has been deleted does not come back if a team is included again.
  • How long we keep it: we delete the saved route 90 days after the game ends, or at once if your team leaves itself out. A record of each replay link (when it was made and by which organiser, when it expires, how many times it was opened) is deleted 30 days after the link stopped working, at the earliest: the clean-up runs only when the next replay link is made, so a record can stay longer. It is also deleted with the game.

Photos you send

  • Who can see a photo: the organiser of your game and the Beaver team, who can see every photo you send to check that points are fair and to keep the game safe; your own team; and the other players in your game: a checkpoint photo as soon as you send it, and a side quest photo once it has been approved.
  • After the game: unless you keep a photo private, it may also be shown after the game: in the game's replay on a screen at the event (above), in the photo gallery of the finished game on our website, which anyone who holds one of that game's codes (the codes players join the game with) can open, and, if the game's host makes one, in a highlights video made with our video provider (section 5).
  • Your choice: when you send a checkpoint or quest photo you can switch off "Share this photo with the game". The switch is on unless you turn it off. A photo you keep private is left out of other teams' galleries in the app, the replay, the photo gallery and any highlights video, and is shown in the app only to your team, the organiser of your game and the Beaver team. You can change your mind afterwards from the photo, if you have a signal. Anyone on your team can change the setting for a photo your team has sent, in either direction, and the most recent change counts, so a teammate can make a photo you kept private shared again. This works only while that game is still open in your app: once you have left the game, the setting can no longer be changed in the app. If you want it changed after that, email will@beavergames.co.uk and we will consider your request. The app remembers your last choice on that phone. The choice covers checkpoint and quest photos. It does not cover your team's picture or the photo of a checkpoint you create with an item. An organiser can make a photo private, but cannot make a private photo public.
  • What "private" does not mean: the organiser of your game and the Beaver team can always see every photo. Your points, the fact that your team completed the checkpoint, and any note you wrote stay visible. Photos are kept in a public storage area: anyone with Beaver's public app key can list the files in it and open them without signing in, so "private" is a setting that the app, the replay, the photo gallery and any highlights video obey; it is not a lock, and the file of a private photo is not secret. Photos sent before this feature existed were never marked private and stay shared. An older version of the app can still show another team's private photo to the person using it. A copy someone has already saved or screenshotted, or a highlights video made before you changed your mind, is not taken back (the host can make a new video without it).
  • How the choice is saved: if you choose private before the photo has reached us, we save a short note with your account, whether it is a checkpoint or quest photo, the photo's reference number and "private", so that the photo arrives marked private. It is removed when the photo arrives. If the photo never arrives, the note is removed after about 30 days, but only when someone next saves a privacy choice for a photo that has not reached us yet, so it can stay longer.
  • How long we keep it: a photo is kept until you delete your account, when we delete every photo you uploaded, including private ones, or until the Beaver team removes it. We do not delete photos automatically after a game.

Clock checks and breaks

Some games have scheduled breaks, and an organiser can call a break at any time. So that a break starts and ends at the same moment for everyone, and so a team can be told if a phone's clock was changed, the app checks its clock against ours.

  • What we collect: about every one to two minutes while a game is running (every two minutes before it starts, and every three to five minutes when nothing is happening), while Beaver is open on your screen with a signal and you are a player in a game that is waiting to start or running: your phone's clock reading and ours, how long the round trip took, a second clock reading that counts only while the phone is awake, the app's version number, which version of the game's break plan your phone holds, whether you are in a break, whether the app is in front, a random code that identifies your installation of the app, your team, and a note if the clock looked wrong. If your phone's clock is changed we also record when, by how much and whether it was put back. If you press and hold "Screen stuck?" to end a scheduled break on your own phone, we record that, with the random code that identifies your installation of the app and your team. When an organiser sets or calls a break, we record who did it and when. This is linked to your account and the game. We keep the readings of at most five installations of the app for one account in one game.
  • When it does not happen: in practice games, on an organiser's phone, when the phone is offline or Beaver is in the background. It sends no location, photos or messages.
  • Why: so that scheduled and called breaks happen at the same time for everyone, and so that a clock change that looks like a fault or like cheating can be seen. A clock change only ever produces a warning. Neither the app nor our server refuses, takes away or locks anything because a clock reading looks wrong. What an organiser decides after a warning is covered by our Terms of Service (section 3.5).
  • Who sees it: our server uses the readings and does not show them to anyone. When a clock change is detected, the game's organisers and the Beaver team can see the team, your display name, the size of the change and when it happened, and an organiser can add a note when they review it. Your phone is told how far its clock moved, and your teammates are told only that a phone on the team had its clock adjusted. A record of a "Screen stuck?" press goes in the game's break log, which the organiser and the Beaver team can read, with your display name and team.
  • How long we keep it: your latest clock reading is deleted 14 days after it was last updated. Records of clock changes, of breaks and of "Screen stuck?" presses are deleted after 90 days. All of it is deleted with the game. The clean-up runs as the app is used, not on a timetable, so a record can stay a little past its date until the next game is played. If you delete your account your clock reading is deleted at once, and the other records stay, no longer linked to your account, until their 90 days end. A record of a clock change or of a "Screen stuck?" press still holds the random code that identifies your installation of the app, and the team, until then.

Which team is in front

During a game our server keeps a record of when one team was alone in first place and for how long (the team, when it went in front and when it stopped). It names a team, never a player. It is shown to the players of the game on the scoreboard and team pages unless the game hides its scores. It is kept with the game and deleted when the game is deleted; we do not delete it automatically before that.

Item history

During a game our server keeps a short log of who holds each item.

  • What we collect: each time a team picks an item up, puts it down, passes it on or swaps it, or an organiser moves it or its hold time runs out: the game, the item, the team and the time, and for a pick-up or a put-down the place where the item lay or was put down. It records the team, not the player.
  • Why: so the game can tell other teams when an item is picked up, and so the replay can show it. Practice games and games that have not started are not logged.
  • Who sees it: the Beaver team. No screen in the app shows the log. Teams see only the pick-up notification, which names the team and the item (for items that hide their holder it says "a team").
  • How long we keep it: entries older than 90 days are deleted, and entries are deleted with the game. The clean-up runs as the app is used, so an entry can stay a little past its date.

Chat, messages between teams, announcements and notifications

  • Game chat and team chat: the game chat is shown to every player in the game, and the team chat to your team. You can mention a player or a team; we keep who was mentioned. We keep when you last read each chat and whether you muted it. Any message can be reported to the Beaver team, who then see the reported message and the sender's last ten chat messages in that game. Chat messages are kept with the game until it is deleted; we do not delete them automatically before that.
  • Messages between teams: the Beaver team switches this feature on and off for the whole service, and at the date of this version it is switched off. While it is on, a player can send a private message to another team in the same game. We keep the message (up to 500 characters), your display name, your team, the time, and, if you started it from an item, which item; and for each conversation when you last read it and whether you muted it. Every current member of the two teams in the conversation can read it, and nobody on other teams. The Beaver team does not read these as a matter of routine: it can read a message that someone reports, together with the last ten messages of that conversation, and it can switch messages off for a game or a team (for example for a game that has players under 18). The messages are stored in our database like the rest of the game's data, so the people at Beaver Games who have administrator access to it could technically read them. Any player in a conversation can report a message, mute it, block a player or close the conversation. Messages are not available in practice games. Conversations close for reading and sending 6 hours after the game ends. The messages stay until the game is deleted; we do not delete them automatically before that. If you delete your account, the words of your messages are replaced with "Message deleted" and your name with "Deleted user"; messages sent by the other team stay.
  • Announcements: an organiser can send one message to everyone in the game. It appears in the game chat marked "The Beaver team" and as a notification from "the Beaver team" that shows its first 120 characters. It does not follow your mute settings.
  • Notifications: the app sends notifications to your phone's push token through Expo (section 5) about your game: for example that an item has been picked up ("Team X picked up Item Y", or "A team picked up Item Y" for items that hide their holder), a game starting or ending, a break being called or ending, a mention or message in the chat (the lock screen shows the sender's name and the first 80 characters), a message from another team while that feature is on (the lock screen shows the sender's team and "New message", not the text, unless the Beaver team switches on previews, when it shows the first 80 characters), an announcement, and a note that a phone on your team had its clock adjusted. For item pick-ups, breaks, messages between teams, announcements and clock notes, a notification is sent to a phone only if every account that has used that phone is meant to receive it, so that a shared phone does not show one team's news to another team's player. A notification sent to a team about its points, a steal, an achievement, an item, the game starting or ending, or an out-of-bounds decision is also saved in the app's notification inbox, where your team can read it again: its title and text, saved against your team and not your account. These stay until the game is deleted; we do not delete them automatically before that.

Feedback you send us

If you send feedback from the app, this is what we keep.

  • What we collect: what you write (up to 2,000 characters), the type you choose (something broken, an idea or a question), the time, your account, and whether you are a player or an organiser. Our admin screen shows your display name next to it.
  • The technical report: when you press send, the app also attaches a short report so we can see what went wrong: the screen you were on and the last few you visited; your game and team, and whether it was a practice game; recent app errors and the app's recent calls to our servers (with ids hidden); your connection and how many items are waiting to upload; whether location and notifications are switched on and how accurate the phone's location signal was; and your app version, your phone's system version, screen size, language, time zone and free storage (on Android also the phone's make and model). The app lists this next to the send button, and sends nothing until you press send.
  • What we do not collect: where you are (no GPS position), your photos, your chat messages or screenshots.
  • Please take care: what you write can be anything you choose to type, so please do not put other people's phone numbers, addresses or passwords in it. The report is cleaned automatically to remove obvious personal data such as email addresses, sign-in tokens, ids, file paths and IP addresses, but that cleaning cannot recognise names, postcodes, phone numbers or street addresses that might appear in an error message.
  • Why: to find and fix problems and to improve the app. Feedback is not for emergencies or for reporting another player: use Report in the app, and call 999 if someone is in danger.
  • Who sees it: the people at Beaver Games who have administrator access, in the app's admin screen and in our database tools, which include the AI assistant named in section 5. Other players never see it.
  • How long we keep it: we delete feedback 90 days after we have dealt with it, and in any case 12 months after you sent it, with a clean-up that runs every night. We delete it at once if you delete your account (backups can hold a copy for up to 7 days: see section 12).

12. How long we keep your data

Your account data and game history are kept for as long as your account is active.

You can delete your account in the app at any time (Profile → Delete account); in the app, deletion is immediate. You can also email will@beavergames.co.uk from the address you signed up with, and we will act on an emailed request within 30 days. The full details are on our page Delete your Beaver account.

What we delete:

  • your account and sign-in: email, password, and any Google, Microsoft or Apple sign-in link;
  • your name and profile;
  • your place in every game;
  • your notification token;
  • your Beaver Community record (your email address, name and when you joined), if you joined in the app (a record made on our website goes when you use its unsubscribe link or email us);
  • every photo you uploaded: checkpoint and quest photos, team photos you added, and photos for checkpoints you created with an item, including photos you kept private;
  • the words of your chat messages, your messages to other teams, notes and quest answers;
  • feedback you sent us from the app, with its technical report;
  • your phone's latest clock reading for each game, and your chat read and mute settings;
  • any note saved about a photo you chose to keep private;
  • the place where you entered an out-of-bounds area, if you did;
  • a note you wrote with a report you made, and the stored copy of anything hidden after a report about you;
  • the fingerprints of your email address that our sign-in screen keeps to stop abuse (at the latest within 7 days).

What we keep, without your name, and why:

  • the points and results your team earned, and which checkpoints and quests your team completed, so other players' scores don't change (game integrity);
  • records that an item was used, so it can't be reused (game integrity);
  • the record of which team was in front and for how long, and the log of which team held which item, which name teams and not accounts;
  • a record of an out-of-bounds visit (the area, the time and how deep), without the place where you entered it;
  • your team's last position on the map and when it was sent, which may hold the random code that identifies the installation of the app that sent it, and which stays until the game is deleted;
  • the wrong answers a team typed on a quiz that limits guesses (up to 120 characters each), saved against the team and not against you;
  • reports made through the Report button, and the report that blocking a player also files, with the reason "blocked" (what was reported, the reason and what the Beaver team did about it), which no longer point to your account;
  • purchase records we must keep for accounting, for six years after the end of the tax year in which the purchase was made: what was bought, the price, the payment reference and, if you bought on our website, the email address you paid with (legal obligation).

None of these are linked to your Beaver account after deletion. Some belong to your team, though, and could still point to you if your team is only you, or if its name is your name: your team's results, its last position on the map, the wrong answers it typed on a quiz, and the installation code on a clock-change or "Screen stuck?" record. The email address on a purchase you made on our website also stays.

Sign-in lookups: when you type an email on the sign-in screen we keep a one-way fingerprint of it, never the address, to stop abuse. It is deleted when you delete your account (at the latest within 7 days). Otherwise it is deleted two days after the lookup at the earliest; the clean-up runs only when someone uses the sign-in screen, so after a quiet spell a fingerprint can stay longer.

Kept for a limited time, then deleted automatically:

  • Our hosting provider keeps security logs of sign-ins and requests (account id, email address, IP address, approximate location from the IP address, and device and browser details) for up to 90 days, then deletes them automatically.
  • Our website host keeps request logs (IP address and the page requested) for up to 30 days. The address of a private booking link (/events/booking/…) therefore appears in those logs.
  • Our hosting provider's daily database backups are kept for 7 days, so deleted data can remain in a backup until it expires.
  • Website visitor statistics (section 10): page view records are deleted after 400 days, and the random value behind each day's visitor code when it is about two days old. A database backup can hold a copy for the period in the line above.
  • Game highlight videos that show your photos are removed from the app straight away (the host can make a new one without them). Our video provider deletes its copies within 24 hours, or within 7 days if we have to finish the deletion by hand.
  • Your team's saved route for the game replay: 90 days after the game ends, or at once if your team leaves itself out. It is saved against your team, not your account. The record of a replay link: 30 days after the link stopped working, at the earliest. The clean-up runs only when the next replay link is made, so a record can stay longer; it is also deleted with the game.
  • The place where a team entered an out-of-bounds area: 90 days after the game. The list of a team's positions outside the areas: 14 days.
  • Your phone's latest clock reading: 14 days after it was last updated. Records of a clock change, of a break or of a "Screen stuck?" press in a game: 90 days after they were made (they are no longer linked to your account if you delete it; a clock-change record or a "Screen stuck?" record still holds the random code that identifies the installation of the app, and the team).
  • The log of which team held which item: 90 days after it was written (it names your team, not you).
  • Feedback you sent: 90 days after we dealt with it, and 12 months at most.
  • A note saved about a photo you chose to keep private, before the photo reached us: until the photo arrives, or about 30 days. The clean-up runs only when someone next saves a privacy choice for a photo that has not reached us yet, so the note can stay longer.
  • The clean-up of the clock, break and item records runs as the app is used, not on a timetable, so after a quiet spell a record can stay a little longer than its number of days, until the next game is played.

Kept with no automatic deletion: the game chat, messages between teams, the record of which team was in front, scores, the notifications saved in your team's app inbox (title and text), your team's last position on the map and the wrong answers typed on a quiz that limits guesses stay until the game is deleted (and, for the words of your own messages, until you delete your account). Reports made through the Report button, and the answers to the website questionnaire (section 2), have no automatic deletion. Photos stay until you delete your account or the Beaver team removes them.

13. Your rights (UK GDPR)

Under UK GDPR, you have the right to:

  • Access: request a copy of the personal data we hold about you
  • Rectification: ask us to correct inaccurate data
  • Erasure: ask us to delete your personal data
  • Restriction: ask us to limit how we use your data
  • Portability: request your data in a portable format
  • Object: object to our processing of your data, including the visitor statistics in section 10

To exercise any of these rights, please contact us at will@beavergames.co.uk. We will respond within 30 days.

You also have the right to lodge a complaint with the Information Commissioner's Office (ICO) at ico.org.uk.

14. Data security

We take reasonable technical and organisational measures to protect your data, including encrypted data transmission (HTTPS), cloud storage with access controls on our database tables (the photo files are in a public storage area: see section 11), and restricted access to personal data. The tables that hold your team's route, your clock readings, your feedback, the item log and the who-is-in-front record cannot be read directly from the app by players: they are reached only through our own server functions.

15. Children

Beaver is intended for players aged 13 and over. We do not knowingly collect personal data from children under 13. If you believe a child under 13 has provided us with their data, please contact us and we will delete it promptly.

16. Changes to this policy

We may update this policy from time to time. The version shown at the top of this page changes, and for a significant change we may tell you in the app. A change that concerns only our website may be made without a new version.

17. Contact

For any privacy-related questions or requests, please contact William James Varcoe, Ballards Barn, Westerham Road, Oxted, RH8 0SL, United Kingdom, at will@beavergames.co.uk.

Terms of Service · Delete your Beaver account

Terms of ServicePrivacy PolicyDelete your accountwill@beavergames.co.uk