Privacy policy

This explains what GotGame collects, why, who can see it, how long we keep it, and what you can do about it. It was written from the database, not from a template, and where something is awkward it says so.

1. The short version

We need your mobile number or your email address, because it is how you sign in.
We need your location, because the whole app is games near you. Only while you are using it — never in the background.
We ask your date of birth once, to check you are 18 or over. We keep it and never show it to anybody.
Other players see your name, photo, bio, level and the area you play in — not your address.
If you enter one of our leagues, your name and points are on its table, and the final table is kept.
Every photo you add is checked by Google for sexual or violent content before anybody else can see it. Google does not keep it.
If you pay in the app, you pay with Apple Pay or Google Pay, and the money goes through Stripe to the club, coach or venue running the game, event, lesson or court. In the web version, at app.gotgamenow.com, you pay on Stripe's own page instead, with Apple Pay, Google Pay or a card. We never see your card number, and we keep nothing about your card. A game a player hosts for friends is not paid in the app.
If you get paid in the app, as a club or a coach, Stripe checks who you are and holds your bank details. We keep only your bank's name and the last four digits of the account, so we can show you which one it is.
If you coach, what you write in your application, where you coach, your price and your free lesson times are shown to signed-in players once we approve you.
Venues can book you a court at their desk. They give us your name and, if they choose, your mobile and email, and we text you about that booking for them. Nothing else is ever sent to that number.
We do not sell your data, we do not run ads, and there is no advertising or tracking SDK in the app.
You can delete your account from inside the app, and it is a real deletion.

2. Who we are

GotGame is operated by Hype & Swagger Ltd, a company registered in England and Wales, which is the data controller for everything described here.

Hype & Swagger Ltd
20 Wenlock Road
London N1 7GU
United Kingdom

For anything about your data — a question, a correction, a copy of what we hold, or a deletion — email support@gotgamenow.com. That address reaches us, and it is the right one for every kind of contact. Paul Caruana is the person responsible for data protection here.

3. What we collect, and why

What you give us

What	Why	Who can see it
Mobile number	Your login, if you sign in with your phone. We send a one-time code to it. Each time we do, we note when, against a one-way fingerprint of the number rather than the number itself, so that no number can be sent codes over and over. The note is deleted after two days.	You and us. It is never shown on your profile or to another player.
Date of birth	To enforce the 18+ minimum.	Nobody. It is kept in a separate restricted table, and only a decade band is ever displayed.
Name and short name	So people know who turned up.	Any signed-in player.
Email address	Your login, if you sign in with email. We send a one-time code to it. Otherwise optional: it lets you sign in with an emailed code if you lose your number.	Not shown on your profile.
Profile photo	Optional. So people recognise you at the court.	Any signed-in player.
Bio, the level you say you are, where it came from	So games and partners suit you.	Any signed-in player.
When you usually play	Optional. So games at those times reach you first. It changes the order things are shown in, never what you can see.	Any signed-in player who can see your profile.
Photos you add to a game	Optional.	Only people who can see that game.
Documents you add to a club you run	So the club's members can read its rules and policies. A PDF is kept by us; a link points to the page you chose.	That club's members.
A club's photo and contact email, if you run a club and add them	Optional. The photo so players recognise the club; the email so there is a way to reach whoever runs it.	The photo: anyone. The email: the club's admins, and us.
A venue you tell us you run, and changes you ask for to it	So we can check with the venue, through its own website, before anything on its page changes. We keep which venue, what you do there (owner, manager, staff, coach or something else), what you wrote, and what the venue told us when we checked. A claim made before 14 October 2026 also named the club that ran the court, and we keep that too. If we don't confirm it, we tell you why, in the app, on the venue website and by email to the address on your account, and we keep the reason we gave you.	Only us, until we have confirmed it. Then you are one of the venue's managers, and players who join the venue can see you among its members, with your role, as they can a club's admins. What you wrote, and what the venue told us, stay with us.
A venue's courts, opening hours and closed days, if you manage one	So the venue's details are right, ready for courts to be booked in GotGame. A venue's managers set them on venues.gotgamenow.com (§12): each court's name and kind, the hours for each day of the week, the days it is closed or open different hours, and the times a court is out of use, with a reason if they give one. For a closed day and a court out of use, we also keep which manager set it and when.	The venue's managers and staff, and us. Once a venue takes bookings in GotGame, any signed-in player can see its courts, its hours and its closed days, and when each court is free; and anyone can see its courts, when each is free and its prices, on its booking page (§12).
A venue's VAT or sales tax, if you manage one	So the tax in what a venue takes is worked out from what it set. A venue's managers set it on venues.gotgamenow.com (§12): whether the venue is registered for VAT or collects sales tax, its VAT or sales tax number, its rates, and the rate its court hire and its own games are charged at. Each booking and game keeps the rate it was made with. We keep which manager last changed it and when.	The venue's owner and managers, and us.
Messages you send	To deliver them.	The people in that conversation. Not end-to-end encrypted — see §9.
Photos you send in a chat	Optional. So the people in that conversation can see them.	The people in that conversation. Not end-to-end encrypted — see §9.
Applying to coach	So players can choose a coach, and so we can show who approved one. We keep what you write about yourself and your qualifications, when you applied, and whether we approved you, when and who decided. If we don't approve you, we tell you why in the app, and keep the reason we gave.	Until you are approved, or if you are not: you and us. Our moderators are told when you apply. Once you are approved: any signed-in player can see what you wrote, when you applied and your Coach badge, but not who approved you or when; only we can see that. Visitors who are not signed in see none of it. The reason we give if we don't approve you: you and us.
Your coaching hours	So players can book a free time with you. If you coach, we keep the court you coach at, the days and times you take lessons each week, how long a lesson is, its price and how many players it is for, the days you have blocked off, and whether you are taking bookings.	You and us. Once you are approved, signed-in players can see your court, a lesson's price, length and number of players, whether you are taking bookings, and your free times, but not your weekly hours or days off as such: a day off, or a time you are already playing or coaching, just shows no free times.

What the app records as you use it

What	Why	Who can see it
Your location	To show games near you and to place a game you create on the map.	Other players see a place name and a distance. See §5.
Games you host, join, save or leave	It is the product.	People who can see those games.
Your games in your phone's calendar	Optional. If you tap Add to your phone's calendar, we make a private link for your phone's calendar to read, so your games, and any changes or cancellations, reach it on their own. We keep the link's code, whose it is and when it was made, until you tap Turn off on the Calendar or delete your account. The link carries the games you host or have a place in, from 60 days ago to about 13 months ahead: for each, the time, its name as My Games shows it (a lesson's name includes the coach's) and the place. Never another player's name.	Whoever has the link: your phone's calendar, and the calendar service it keeps in step with if it uses one, such as iCloud or Google Calendar, which reads the link from our server and keeps what it is given under its own privacy policy. Keep the link to yourself. Turn off ends it, and your games leave the phone's calendar the next time it updates.
Clubs and venues you save	So you can find them again under Favourites.	You and us. Nobody else can tell who saved a club.
Clubs and crews you are in	It is the product.	Clubs: any signed-in player can see which clubs you are in, and how many, on your profile; only members see inside a club. Crews: your crew.
Your friends, and friend requests	So you can find the people you play with again.	You and the other person. Your friends also see when you become friends with someone (next row).
What your friends see you do	So your friends hear about games they could join.	Your friends, under Crew → Friends, and nobody else; never anyone you have blocked. It shows when you join a public game or a club, put on a game anyone can join, or become friends with someone. Private and members-only games are never shown.
Whether your club membership is paid up, if your club keeps track	So a club that charges membership knows who has paid. You pay the club yourself, outside the app.	You and the club's admins. They enter it (paid up to which month or year, and an optional note) and can save it, with members' names and roles, as a spreadsheet.
When you joined	Your profile shows the year, as “Member since 2025”.	Any signed-in player.
Payments you make	So you can see what you have paid and get refunds, and so the organiser knows who has paid. For each payment in the app we keep the game, event or lesson, who it was paid to, the price, what you were charged, GotGame's fee, Stripe's charge and what the organiser got, when you paid, and any refund, how much and why. Stripe tells us whether a payment went through; we keep nothing about your card. In the web version you pay on Stripe's own page, which asks for your card (or Apple Pay or Google Pay) and your email address, for its receipt; we never see them. Stripe's own record of each payment, which we can look at as the platform, shows the type of card and its last few digits. If the organiser marks you as paid in cash, we keep that mark, the amount and who made it.	You, the organiser of that game, event or lesson (for a club, its admins), and us. A mark that you paid in cash can also be seen by the game's co-hosts.
Payouts, if you run a club or coach	So we can pay you. Only a club, or a coach we have approved, is paid in the app; a player hosting a game for friends is not. We keep your Stripe account's id, the country you chose, whether Stripe has finished checking you and whether it needs anything more, the name of the bank (or card) Stripe pays you into with the last four digits of that account, which Stripe tells us, and what you have been paid and when. When you set up getting paid, for yourself or for a club, we give Stripe your email address, if your account has one. Stripe asks for your full bank details and checks who you are on its own pages, including the form on our payout page (§12); apart from the bank's name and last four digits, we do not store any of that. When you tap Change to change your bank, we make a pass to that page which works once, within 10 minutes, and we keep who made it and when. We keep only a scrambled copy of the pass, so our records cannot be used to open the page. As the platform, we can look up in Stripe what you gave it, and we do that only to help with your payouts.	You (for a club, its admins) and us. Players can tell only that they can pay you in the app.
A payment disputed with your bank	So the club, coach or venue you paid can answer it, and so everyone's money is right. If you tell your bank a payment made through GotGame wasn't right, Stripe tells us. We keep which payment it is, the amount, the kind of reason your bank gives (such as "not recognised" or "cancelled"), the date it must be answered by, how it ends, and whether we gave back our fee. What you told your bank, and what the club, coach or venue sends in reply, stay with Stripe and your bank: the club, coach or venue answers on Stripe's own form, which shows them your bank's claim. To help it answer, a venue can download its record of the booking: the court and time, who booked and paid, who marked you as arrived, and its cancellation rules.	The club, coach or venue you paid (for a venue, its owner and managers; its front desk sees only that the payment is disputed), and us.
Lessons you book	So the lesson happens, and is paid for and refunded like any other game. When you book a lesson it becomes a private session in My Games, run by the coach, with you named as the person who booked it: the time, the place, the price and that you booked it. If you have not paid 15 minutes after booking, the booking is removed and the time is free again; if a payment is going through, it waits for it, but never past 45 minutes after you booked. Paying is recorded like any other payment (above). The friends you bring do not need the app, and we record nothing about them.	You, the coach and us. The coach is told who booked it once you have paid. Other players see only that the time is no longer free, not who took it.
Results, and the level they earn you	So a level means something. The level your results earn is worked out in the background, but it is not shown at the moment (§6).	A result: people who can see that game. The level it earns you: nobody at the moment, you included.
Stars you give a court, a host or a club	So players can see which courts are good and who puts on a good game. After a game or event you can give its host, or the club for a club's games, one to five stars, and you can rate a court from its page. We keep your stars, who or what they are for, the game they were after, and when. Each person counts once, with their latest stars.	Nobody is shown who gave which stars, not even the host. The app shows signed-in players only an average and how many people it comes from, and only once five people have rated.
GotGame leagues you enter	When you tap Enter on one of our leagues, we record that you entered and when. That is your agreement to that league's rules. If we take you off a league's table, we record who did it, when and why. We also record your answer to whether you, or anyone you live with, work for Hype & Swagger Ltd or that league's sponsor, because they can play but cannot win a prize (terms §6). We can correct it, and we mark our own staff once for every league. None of this is ever shown on the table.	You and us.
Your place on a GotGame league table	So a league has a table and a winner. It shows your name, picture, points, games and wins in that league. When the league ends, the final table is written down once and kept, so a result cannot change after a prize has been given. To claim a prize you email us.	Any signed-in player who can see that league: everybody, unless it is a local league, which only players who live inside its area can see.
A GotGame league's prize	Who the prize was offered to, when their 30 days to claim it end, and whether it was claimed or passed on to the next player on the final table, with who decided and why. So the prize goes to the right person, and we can show it was really awarded (terms §6).	You, for an offer made to you, and us.
Attendance	Whether you turned up to games where a register was taken. Counted, not voted on. It is switched off at the moment: nobody is asked who turned up and nothing is counted (§6). Answers given before that are kept.	Nobody is shown it at the moment.
"I'm here" at a court	So people can see whether anyone is about.	Friends see your name; everybody else sees only a number. It expires within a couple of hours and no history is kept.
When you open the app	So we can tell whether people are still using it and coming back to it, how many use it each day, week and month, and whether an account that has been reported is still active.	Only us. It is never shown on your profile or to another player, and any numbers we share outside GotGame are totals that don't identify anyone. We keep the last time you opened it, overwritten each time, and a list of the days you opened it: the day only, not the time or how many times. Each day is deleted after two years (§8).
Which terms and privacy policy you agreed to, and when	So we can show what you agreed to, and ask you again when either changes. Every time you agree is kept, not only the latest.	Only us.
Push notification token	To tell you when something about your game changes, about games near you that need players, about new games at your clubs if you turn Club news and events on, about our leagues if you turn Leagues and prizes on, about the answer to a coaching application, if you coach, about each lesson booked with you, if the money set aside on your card for a court you booked can't be taken, and, the morning after a game you have not paid for, one reminder to pay. We note that the reminder was sent, so that it is only sent once. In the web version, if you turn notifications on, we keep your browser's notification subscription instead: an address at your browser's push service and two keys that only your browser can use to read what we send.	Only us.
Which notifications you want	Settings has a switch each for Game reminders, Last-spot alerts near me and Club news and events. We keep whether each is on, and when you turned Club news and events on, so we only send what you asked for. Turning Club news and events off forgets the date. With Game reminders or Last-spot alerts off, those still appear in the app's Alerts.	Only us.
Whether Leagues and prizes is on, and when you turned it on	So we only send league and prize notifications to people who asked for them, and can show that you did. Turning it off forgets the date. With it off, new leagues and results still appear in the app's Alerts.	Only us.
Whether Open to meeting people is on, and when you turned it on	It puts a small mark by your name. Turning it off forgets the date.	Only players who have also turned it on see the mark. Nobody else, and nobody sees the date.
Games and events for meeting people	When you make a game or event, you can make it one for meeting people. It carries the same mark, and making one turns your own Open to meeting people on, as the switch says.	Only players who have Open to meeting people on, the people in it (anyone with a place, who has asked, been invited or is waiting, and whoever runs it), and our moderators. Visitors who are not signed in never see one. Turning your own switch off never takes you out of one you are in.
Reports and blocks	Safety.	Only us. A block is visible only to the person who made it.
If you are one of our moderators	So only the right people can act on reports. Our moderators are our own staff. We keep that you are one, who made you one and when, and a record of every time somebody was made a moderator or stopped being one.	Only us.
If we invite you to see our numbers	So only the people we choose can see GotGame's numbers, and we know who has seen them. We keep your name, your firm if we have it, and your email address; who on our team invited you, and when; how many times the invite was emailed, and when you took it up; when your access ends, and whether you can see our burn and runway; and each time you looked at the numbers. You sign in at management.gotgamenow.com with a code sent to your email. That makes a sign-in for that email, which isn't a player profile and isn't shown in the app. You see totals only, never a player, venue, club or coach by name.	Only us.
A photo the check refused	Safety. Every photo you add is checked before it is stored — see §7. If one is refused, we note that it happened: when, which kind of photo it was, and the check's ratings. The photo itself is never kept.	Only us.
Crash reports	So we can fix what broke.	Us and Sentry — see §7. A crash report carries the error, where in the code it happened, your device model and OS version, and your account id, which is a random identifier and not your name or number.

What we do not collect. We do not collect your card number or your bank account number (Stripe holds those — see §7; if you are paid in the app, we keep only your bank's name and the account's last four digits, as above), advertising identifiers, your browsing, or anything from your photo library beyond the individual pictures you choose. We do not keep your IP address with your account, though the services in §7 see it when your phone talks to them, as any internet service does. There is no advertising SDK, no attribution SDK and no session recording in the app. Nothing tracks you across other apps or websites.

There are three third-party SDKs in the app, and two more in the Android app.

Sentry reports crashes. It is set up to send as little as possible: automatic personal data off, performance tracing off, session replay off. The only thing in a crash report that points at you is your account id.
Stripe's SDK opens the Apple Pay or Google Pay sheet when you pay. Stripe says it collects details of your device and how you use the payment sheet, to prevent fraud and to improve its service, and never uses them for advertising.
Google's Maps SDK draws the maps. Google says it collects your device model and system version, your IP address, an identifier it makes up for the SDK, crash reports from its own code, and how you move the map, to run and improve its service.
Google's Firebase Cloud Messaging, in the Android app only, delivers notifications to Android phones. Google says it uses one thing about you: an identifier it makes for your phone's copy of the app, so it knows which phone to deliver to. It keeps that until we ask it to delete it.
Google's Wallet library, in the Android app only, is what Stripe's SDK uses to open the Google Pay sheet. Google says that when you pay it collects which apps are on your phone (to check the app asking for payment is registered with Google Pay, and for its own analytics), your device's identifier, your location and your phone number (to check for fraud), your Google account (to show your saved cards), and an identifier it makes up to count payments that finish. Google handles this under its own privacy policy.

At a venue that runs its courts in GotGame

What	Why	Who can see it
Joining a venue's team	So the venue's owner and managers can say who works there and what each person can do. We keep your role (manager, front desk or coach), who invited you and when, and when you joined or left. If the invite was emailed, we keep the address it went to and how many times it was sent (three at most), but only until the invite is used, cancelled or runs out. Then the address is removed, and we keep only that an invite was sent. The invite's link works once and runs out after 7 days, and we keep only a fingerprint of it. We also keep the front desk's limit on what can be taken without a manager, and who set it.	The venue's owner and managers, and us. Players who join the venue can see you among its members, with your role, as they can a club's admins.
Who did what at a venue	So a venue's owner and managers can see who changed what, and who took or gave back money. Each line says who did it and when: a change to courts, hours, prices, tax or the team; a booking made, moved or cancelled; someone marked as arrived or as not turning up, or that taken back; a payment taken, given back or disputed; a text sent; courts closed; customers and bookings brought across from another booking system; the customer list or the money downloaded. A line made at a desk names the person on the desk, and the manager who OK'd it if one did. Lines about a booking name the customer.	The venue's owner and managers, and us. The lines about a booking also show in that booking's history, which the venue's front desk can open.
Your desk code, and who was on the desk	A venue can make a device its desk, signed in as the venue rather than as a person, and each of the team types their own 4-digit code to use it. We keep your code only scrambled (bcrypt), so nobody can read it back, not even us; how many wrong tries in a row (5 lock it); and who reset it. We keep each time you're on a desk, from when you typed your code until you switched or it was left untouched for 5 minutes, and each time a manager typed their code to OK one thing for you: who, what and when. When you leave the team, your code there is deleted.	Your code: nobody. Who's on a desk now: whoever is using that desk. The rest: the venue's owner and managers (in who did what), and us.
If a venue books a court for you	So the venue can run its bookings. It gives us your name and, if it chooses, your mobile number and email address; if you're in GotGame and a member of the venue's club, it can choose your account instead. Its team can write notes about you, and we keep who wrote each one and when. If it brought you across from another booking system, we keep which system and its reference for you, and whether you agreed there to hear from the venue. The venue's owner or a manager can record whether you've agreed to hear from it, and can stop you booking it online; we keep who did each and when. For each booking we keep the court, the time, the price, how you said you'd pay and how long it's held if you're asked to pay first; who else is playing (by name, or by account if they're in GotGame; a junior by first name only); when you arrived, or that you didn't turn up, and who marked it; and anything moved or cancelled, with who did it and how, and whether a cancel was at your request. From your bookings the venue sees how often you play there, when you usually play, what you've spent, and how many you didn't turn up for or cancelled late (only cancels you asked for count); and your level, if you have Public skill ratings on.	The venue's owner, managers and front desk, and us. A coach at the venue sees only that the court is taken. If you're in GotGame, you see the bookings the venue sends you in the app.
Booking a court at a venue with your GotGame account	So the venue can run your booking and reach you about it, for example if rain closes the court. When you book a court at a venue that runs its courts in GotGame, you become one of the venue's customers, as if its desk had booked you (the row above). The venue gets your name, and the mobile number and email address on your account. The booking page tells you this before you pay. We email you a confirmation with a link to see or cancel it, as for a guest (the row below).	The venue's owner, managers and front desk, and us. Anyone with the link in your email can see and cancel that booking, so keep it to yourself.
Booking a court at a venue as a guest	So the venue can run your booking, and you can see or cancel it. If you book without a GotGame account, on a venue's booking page (gotgamenow.com/book/…, which its own website may link to), you give us your name, email address and mobile number, and tick that you're 18 or over; we keep when you ticked it. You become one of the venue's customers, as if its desk had booked you (“If a venue books a court for you”, above), and we keep the same about the booking. We email you a confirmation with a link to see or cancel it. We keep that link only as a fingerprint, and it stops working once the booking has passed or been cancelled. Paying is as in “Paying a venue”.	The venue's owner, managers and front desk, and us. Anyone with the link in your email can see and cancel that booking, so keep it to yourself.
Emails about a court you booked	So you know where you stand with a court you booked yourself, with your account or as a guest. We email the address the venue has for you: a confirmation once you've paid; an email if you cancel it yourself; if you cancelled after the venue's free-cancel time, another if the money is let go or comes back after all, because the venue booked the court again or closed it; and, if the money set aside on your card can't be taken, an email to say your court is still booked and to pay the venue when you arrive; and if the venue cancels your booking, moves it to another court or time, or closes its court, an email to say so and what happens to your money. If you booked with your account, the app tells you too. We keep your address with each email only until it's sent, or until we stop trying after five tries, and for a moved booking, where and when it was before; after that we keep only which booking it was about, which email it was, and when it was sent.	Nobody but us, and Resend, which sends them (§7).
Where a booking came from	So a venue can see which of its links bring bookings. Each booking made online keeps how it was made: the app, the venue's booking page from its own website (the panel of free times on it, its link or its button), its QR code, or its Google profile. The same label goes into Stripe's record of the payment. It's a label on the booking, not anything about you or your browser.	The venue's owner and managers, as counts; and us.
Holding a court while you pay	So one person can't hold a venue's courts and stop others booking them. While a court is held for you (15 minutes to reach paying, then as long as Stripe's payment page is open), we keep the hold with your account or, as a guest, your email address, and with a random number our booking page keeps in your browser. That number identifies only the browser, not you, and is used for nothing else. We take it off the hold when the hold ends, whether you paid or not. Clearing the site's data in your browser removes it from there.	Nobody but us.
Paying a venue	So the venue is paid and anyone owed money back gets it. We keep what you paid, how and when: cash, the venue's card machine, a QR code on its desk's screen, a link it texts you, or in the app. For a payment made online we also keep our fee and Stripe's references, and the texts on the venue's tab that came out of it. Your card details go to Stripe, never to us or the venue. We keep any refund (how, how much, who gave it) and when the venue was paid out. If you dispute a payment with your bank, we keep what the row above says.	The venue's owner and managers; its front desk sees what's still to pay and what it takes; you, what you've paid, in the app; and us.
Texts a venue sends you	If a venue books you a court and you aren't in GotGame, it can ask us to text you: a link to pay and how long the court is held, that the hold ended because it wasn't paid, or that your booking was cancelled, moved, or the courts were closed. We keep the number, the text, when it was sent, what it cost the venue (10p, or 10¢ in the US) and Twilio's reference, or Twilio's reason if it couldn't be delivered. A link in a text is kept only as a fingerprint and stops working when the hold ends. A venue in the UK texts UK mobiles, and a venue in the US texts US mobiles. If you're in GotGame, you get these as notifications in the app instead, and no text is sent.	The venue's owner, managers and front desk, and us.

When our team adds or closes something for you

Our team can set some things up for you, and close them, from our own management site. Only the owner of our team can do this, and each time we keep a record of who did it, when, and why.

What	Why	Who can see it
An account we make for you	If you ask us to set you up, we can make your account with your name and email address, and email you how to sign in. Nobody can see you in GotGame until you sign in, agree to our terms and this policy, and answer the questions every new player answers. We keep who on our team made it, when, and any note they wrote. If you don't want it, reply to that email and we will remove it.	Your name: as for any player, once you have signed in. Who made it, and the note: only us.
Your account being erased, started by us	For example, if you ask us by email to delete your account. It is the same erasure as deleting it in the app (§8): your profile disappears from the app at once and the account is erased after 30 days. We email you the date and our reason, and until then you can keep your account with Keep my account, or ask us to stop it. We keep who started it, when and why.	You, in our email. The record: only us.
Being made a coach, or no longer being one	We can make you a coach without an application, or stop you coaching, for example if a coaching qualification lapses. We tell you, with our reason. Lessons you gave stay in your history. We keep who did it, when and why.	That you coach: as for any coach. The reason: you and us.
A club or venue we add, put live, close or reopen	We can add a club and name the player who runs it, add a venue and set it up for the person who will run it, put a venue live, and close or reopen either. Nothing is erased when something closes. Whoever runs it is told, with our reason. When a venue goes live, its owner and managers are emailed and told in the app. We keep who on our team did it, when and why.	The club's admins or the venue's team, and us. Players see only that it is closed.

Your contacts, when you ask us to look

GotGame can tell you which of your contacts already play. This happens only when you tap Check My Contacts — never automatically, never at sign-up, never in the background. If you never tap it, your address book is never read.

When you do, the numbers in your address book are turned into fingerprints on your phone before anything leaves it. We compare those against the numbers registered to accounts and show you who matched. We store nothing from this — not the numbers, not the fingerprints, not who matched and not who did not. The comparison happens inside a single query and nothing is written down. The one thing kept is a count of how many times you used the feature that day, which exists to stop it being used to test numbers in bulk, and which contains no contact data.

Something most apps would not tell you: a fingerprint of a phone number is not anonymous. There are only about ten billion possible numbers, so anyone holding a fingerprint could work back to the number by trying them all. What protects your contacts is that we keep none of them — not the fingerprinting. That is why this says "never stored" rather than "never uploaded".

Those numbers belong to other people, who have agreed to nothing. That is why they are compared and then discarded. If you would rather we did not, decline the contacts permission or turn it off later in your phone's settings — everything else works normally, and you can still add people by name.

4. Why we are allowed to (lawful bases)

What	Basis under UK GDPR
Your account, profile, games, messages and photos you send in a chat, clubs and crews, your friends and what they see you do, the clubs and venues you save, and what you add to a club you run	Contract — we cannot provide the app without them.
Payments, refunds, disputes and payouts	Contract — paying and being paid is what you asked the app to do. Keeping payment records afterwards is a legal obligation under UK tax law.
A mark that you paid in cash	Legitimate interests — the organiser's own note, so that the app stops asking you to pay.
Whether your club membership is paid up	Legitimate interests — the club's own record of who has paid it, like the organiser's note of a cash payment.
Applying to coach, your coaching hours and days off, and lessons you book or give	Contract — you asked to coach, or to book a lesson. Deciding who can coach is our legitimate interest in players being able to trust the Coach badge.
Your date of birth	Legal obligation and our legitimate interest in keeping under-18s off a service built for adults meeting strangers.
Location	Consent, given through your phone's permission prompt. You can refuse and set your area by hand, and you can withdraw it at any time in your phone's settings.
Reading your contacts	Consent, given by tapping the button and the permission prompt.
Telling us you run a venue, and what we checked	Legitimate interests — making sure only the people who really run a venue can manage its page, and being able to show how we checked.
A venue's courts, opening hours and closed days, and which manager set them	Contract — running the venue in GotGame is what its managers asked to do. Keeping which manager set a closed day or took a court out of use is our legitimate interest in the venue being able to see who changed what.
A venue's VAT or sales tax, and which manager changed it	Contract — working out the tax in what a venue takes is part of running it in GotGame, which its managers asked us to do. Keeping which manager changed it is our legitimate interest in the venue being able to see who changed what.
Joining a venue's team, your role, your desk code, and who was on the desk	Contract — running the venue's desk is what you joined its team to do. Keeping who did what is the venue's and our legitimate interest in knowing who took or gave back money.
A venue's customers, their bookings, payments and the texts about them	The venue's legitimate interests in running its bookings, and the contract between the venue and its customer. Keeping payment records is a legal obligation under UK tax law.
Booking a court at a venue, with your account or as a guest, its link, the emails about it, where a booking came from, and holding a court while you pay	The contract between you and the venue, which we run for it. Limiting how many courts one person can hold is our and the venue's legitimate interest in courts not being blocked.
Your games in your phone's calendar	Contract — you asked for it by tapping Add. Turn off ends it.
Reports, blocks, bans and moderation records, and who is on our moderation team	Legitimate interests — keeping people safe on a service that arranges for strangers to meet.
If we invite you to see our numbers	Legitimate interests — showing our numbers to the investors we choose, and knowing who has seen them.
Checking the photos you add, and noting one that is refused	Legitimate interests — keeping sexual and violent images off a service that arranges for strangers to meet.
When you open the app	Legitimate interests — knowing whether the service is being used and whether people come back to it, and whether an account that has been reported is still active.
A note of when we texted a sign-in code to a number	Legitimate interests — stopping anyone using our sign-in to send a phone code after code, or to run up texts.
Which terms and privacy policy you agreed to, and when	Legitimate interests — being able to show what each person agreed to, and when.
Crash reports	Legitimate interests — an app that crashes and never gets fixed serves nobody.
Push notifications about your own games	Contract. You can turn them off in the app or at the operating-system level.
Entering one of our leagues, and its table	Contract — you enter a league on its rules, and the table is what you entered for. Keeping the final table after the league ends is our legitimate interest in a result that cannot change once a prize has been given. Recording who can win, and who a prize was offered to and what became of it, is part of the same contract (terms §6); keeping that record is our legitimate interest in showing a prize was really awarded.
Club news and events notifications	Consent, given by turning Club news and events on in Settings. You can turn it off at any time.
League and prize notifications	Consent, given by turning Leagues and prizes on in Settings. You can turn it off at any time.
Open to meeting people, and games and events for meeting people	Consent, given by turning it on in Settings, or by making a game or event for meeting people, which turns it on. Turning it off withdraws it.

5. Location, in detail

Location gets its own section because it is the most sensitive thing we hold.

Only while you are using the app. There is no background location, no location tracking and no movement history. The app asks for "while using" permission and nothing more.
Roughly, not exactly. The app asks the phone for a balanced-accuracy fix — about a hundred metres, not a doorstep. In the web version it asks your browser for its ordinary accuracy, not its most precise.
You can refuse. The app still works: you set your area by hand and drop pins yourself.
We store a point for your home area and for each game's venue. Your profile shows other players a place name and a distance, such as Bishopton, Scotland — not an address.
The place name comes from your own phone. Turning the coordinates into a town name is done by the operating system, not by an outside service. In the web version a browser can't do that, so the app sends Google's Geocoding service the rough point, and nothing that says whose it is, and Google sends back the name (§7).
"I'm here" at a court is one row that expires within a couple of hours and is overwritten each time, so there is no record of where you have been. Friends see your name on it; everyone else sees a count.

You can stop players near you finding you at any time: turn off Show me in Players near you in Settings. Then only people in your games can find you.

6. What the app decides automatically

Two numbers are worked out by the system rather than typed in by a person. Neither is shown at the moment.

Your earned level is worked out in the background when a result is recorded — on who won, not by how much — but it is not shown, to you or to anybody else, until we have re-fitted its maths on real padel. Until then your profile shows the level you picked or brought over from another platform. Where the number came from is always shown next to it, so a figure you set yourself reads as exactly that, next to somebody else's brought over from another platform. A level never stops you joining a game. A game can suggest a band, and you can ignore it. What a level does affect is search: if you have Public skill ratings on, somebody filtering by level can find you, and if you turn it off, they cannot.

Attendance counts finished games where a register was taken and you were on the roster. It is switched off at the moment: nobody is asked who turned up, nothing is counted and nothing is shown. Answers given before that are kept. If we switch it back on, this page will say so first. When it is on, it is counted, not voted on, it shows nothing at all until you have at least three such games, and it does not stop you joining anything.

Neither of these is a decision with a legal or similarly significant effect on you, and neither is used to profile you for advertising, because we do not advertise. If you think a number is wrong, email us and a person will look at it.

7. Who we share it with

We do not sell your personal data and we do not share it for advertising.

Your mobile number and text messages. We do not sell or share your mobile number, your SMS opt-in data or your consent to receive texts with any third party or affiliate for marketing or promotional purposes. Twilio, below, receives your number to deliver your sign-in code and, if a venue books a court for you, the venue's texts about that booking. We never send marketing by text.

We use these processors to run the service:

Who	What they handle	Where
Supabase	Database, sign-in, file storage. This is where your data lives.	EU / UK
Twilio	Delivers your sign-in code by SMS, and a venue's texts about a court it booked for you. Receives your phone number and the text.	United States
Resend	Sends the emails the app sends you, such as a sign-in code, an invite to join a venue's team that its manager asked us to email, our reason for not confirming that you run a venue, or the emails about a court you booked: its confirmation, with its link to see or cancel it, and what happens to your money if you cancel it, if it can't be taken from your card, or if the venue cancels it, moves it or closes its court. Receives the email address and the message.	United States
Stripe	Takes Apple Pay and Google Pay payments (and, in the web version, payments on its own page: Apple Pay, Google Pay or a card), makes refunds and pays clubs and coaches. Each payment is made on the club's or coach's own Stripe account, not ours. Stripe gets a stand-in for your card from Apple or Google, never from us. In the web version, Stripe's page asks for your card and email address; we never see them. From us it gets the amount, GotGame's fee, and ids for the payment, the game and your account. For a club or coach, Stripe checks who they are and holds their bank details; from us it gets the email address of whoever sets up getting paid, if they have one, and the country they chose, and it tells us the name of their bank and the last four digits of the account. When they change their bank, they do it in Stripe's own form, on our payout page (§12). Stripe also takes payments to a venue that runs its courts in GotGame, on the venue's own Stripe account: in the app, or at the desk on Stripe's own payment page, from a QR code on the desk's screen or a link the venue texts you. Stripe asks for your card and email address on that page; we never see them. If you dispute a payment with your bank, Stripe tells us, and shows the club, coach or venue your bank's claim on Stripe's own form, where they answer it. Stripe also uses some of this for its own purposes, such as preventing fraud and meeting financial rules, under its own privacy policy: stripe.com/privacy.	United States
Apple (Apple Pay) and Google (Google Pay)	Your phone's wallet, not ours. When you pay, it hands Stripe a one-time stand-in for your card instead of the card number. Apple and Google handle that under their own privacy policies.	United States
Google (Places API)	Venue search. Receives what you type and your approximate coordinates, so results near you come first.	United States
Google (Cloud Vision)	Checks every photo you add for sexual or violent content before it is stored. Receives the photo and nothing that says whose it is. Google says it processes the photo in memory, does not store it, and does not use it to train its models.	United States
Google (Maps SDK)	Draws the maps in the app. Google says the SDK collects your device model and system version, your IP address, an identifier it makes up for the SDK, crash reports from its own code and how you move the map, to run and improve its service. In the web version your browser loads Google's map (its Maps JavaScript API) straight from Google, so Google sees your IP address, your browser and how you move the map.	United States
Google (Geocoding API)	In the web version only: turns the rough point of your location into a place name, such as Bishopton (§5). Receives the point and nothing that says whose it is.	United States
Expo	App delivery and push routing. Receives your push token and the text of the notification.	United States
Apple and Google	App distribution and push delivery. On an Android phone, notifications are delivered by Google's Firebase Cloud Messaging, which receives the notification and the identifier described in §3.	United States. Firebase Cloud Messaging can run in any of Google's data centres.
Your browser's push service (Apple, Google, Mozilla or Microsoft)	In the web version only, if you turn notifications on: delivers them to your browser. It receives each notification encrypted, so it can't read it, and the address of your browser's subscription (§3).	United States
Sentry	Crash reporting. Receives the error, the code location, your device model and OS version, and your account id.	United States

Transfers outside the UK. Several of those are in the United States. Where personal data leaves the UK we rely on the UK Addendum to the European Commission's standard contractual clauses, or on the UK–US data bridge where the provider is certified under it. If you would like to know which applies to a particular provider, ask us.

We will also disclose data where the law requires it, or where it is necessary to protect somebody's safety.

8. How long we keep it

We would rather be plain than reassuring here.

While your account exists, we keep it. There is no automatic expiry on your profile, your games, your messages or your photos. They are there until you delete your account or ask us to remove something.
When you delete your account — Settings → Delete account, at the very bottom — your profile disappears from the app immediately and the account is erased after 30 days. It is the same if our team starts it for you (§3): we email you the date and our reason. The delay is so you can undo an accidental deletion and so any open safety report can be dealt with. Undoing it is the Keep my account button on that same screen; signing back in does not cancel it on its own.
What survives, and why. Anything you shared with other people stays, with your name taken off it: messages and photos you sent in a chat, photos you added to a game or a club, documents you added to a club, votes you cast, games you hosted, your line on the final table of a league that has ended, and the record of a league's prize offered to you. Deleting those would rewrite other people's record of games they actually played. Everything that is only yours goes. If you coach and delete your account, your application, hours and days off go with it; lessons you gave stay in the records of the players who booked them, with your name taken off, like any game you hosted. A lesson you booked stays in the coach's records, but no longer says who booked it.
Payment records — what was paid, to whom, when, GotGame's fee, and any refund or dispute — are kept for six years after the payment, because UK tax law requires a business to keep them. If you delete your account, the record stays but no longer says it was you. A mark that you paid somebody in cash goes when your account does. Deleting your GotGame account does not close a Stripe account you set up to get paid, or erase Stripe's own records, which Stripe keeps under its own rules; money you are owed is still paid out.
A venue's bookings and its customers. Payment records for a court a venue booked for you are kept for six years, as above. The details a venue gives us about you as its customer (your name, mobile and email, its notes about you, and the names of anyone it added to your bookings) are removed two years after your last booking there, or sooner if the venue removes you; your bookings and payments stay, without them, as above. If you book a court yourself, with your account or as a guest, you're one of the venue's customers, so what it has about you is removed two years after your last booking there, or sooner if the venue removes you, as above. An email about a court you booked keeps your address only until it's sent (§3). The record of who was on a venue's desk and who did what is kept while the venue uses GotGame, with a removed customer's name taken out. Deleting your GotGame account does not delete a venue's record of you as its customer: the name and number the venue gave stay with the venue, no longer linked to your account, until they are removed. To have them removed sooner, ask the venue, or email us at support@gotgamenow.com and we will deal with it with the venue. Your desk code at a venue is deleted when you leave its team. If the venue's owner or a manager downloads its customer list or its money, the file is theirs to look after; we keep only who downloaded it, when, and how many customers, bookings or payments it held.
The days you opened the app, for two years: each day is deleted two years after it. They all go, with the last time you opened it, when your account is erased.
If we invited you to see our numbers, while you have access and for two years after it ends, or two years after an invite you didn't use ran out or was cancelled. Then it's deleted. The sign-in for your email stays until you ask us to remove it.
A note of each sign-in code we text, for two days, then it is deleted. It holds a one-way fingerprint of the number, made with a secret key that never leaves our server, and when the code was sent: never the number or the code.
A record that a deletion happened and when. That is how we can show we did it.
Any abuse report naming you, because an account that can erase the reports against it is not a safety system.

And fingerprints, if you were banned. If we ban an account for abuse we keep a one-way fingerprint of the phone number it used, and of its email address if it had one, so that deleting the account does not clear the ban. Plainly: we erase you, and we keep what cannot be read back, so that a ban cannot be escaped by asking to be erased.

It is used for that single check and nothing else — never to identify you, contact you, match you against contacts, or link you to another account. It is produced with a secret key that never leaves our server, without which the value is useless even to somebody who obtained the whole list. If the ban is lifted they are destroyed. If you have not been banned, we keep nothing about your number or your email address after deletion, except the note of any sign-in code we texted it in the last two days, which is deleted when those two days are up.

If you want something removed sooner than any of this, email support@gotgamenow.com and say so.

9. Security, honestly

Data is encrypted in transit and at rest by our hosting provider.
Access rules are enforced by the database, not just by the app, so a rule cannot be bypassed by anything other than the app.
Messages, and photos sent in a chat, are not end-to-end encrypted. We can technically read and see them, and we will if a safety report requires it. Do not use GotGame for anything you need to be private from us.
A club's quick-join code is a shared word an organiser reads out, like a wifi password. It is not a credential and it is not your account password. Do not reuse a real password there.
No system is perfect. If you find something wrong with ours, email us and we will take it seriously.

10. Your rights

Under UK GDPR you have the right to be told what we hold about you, to get a copy of it, to have it corrected, to have it erased, to object to or restrict how we use it, and to have it given to you in a portable form.

Several of these you can exercise yourself, immediately:

See and correct your profile — Settings → Personal details.
Hide your level, and come out of level search — the Public skill ratings switch.
Stop players near you finding you — turn off Show me in Players near you, in Settings.
Turn off notifications, one kind at a time or all of them — in Settings, or at the operating-system level.
End your calendar link — Turn off on the Calendar.
Withdraw location or contacts permission — in your phone's settings.
Delete your account — Settings → Delete account.

For the rest — a copy of your data, a correction we cannot make ourselves, an objection, or a restriction — email support@gotgamenow.com. There is no download-my-data button in the app yet, so a copy is something we put together by hand when you ask. We will respond within one month.

If you are not happy with how we have handled it, you can complain to the Information Commissioner's Office at ico.org.uk, or on 0303 123 1113. We would rather you told us first so we can put it right.

11. Children

GotGame is for adults. The minimum age is 18, your date of birth is checked at sign-up, and the check is enforced by the database rather than only by the sign-up screen. We do not knowingly collect anything from anybody under 18. Someone booking a court as a guest confirms they're 18 or over. If you believe somebody under 18 has an account, email us and we will deal with it. A venue may name a junior who is playing in a booking it made, by first name only; a junior never has an account, and we keep nothing else about them.

12. This website

gotgamenow.com is a plain set of pages. Our pages set no cookies, have no analytics, and run no tracking of any kind — there is nothing here to opt out of. The one cookie you may see is our web host's: Hostinger, which serves the site, sometimes checks that a visitor is a real browser before showing a page, and when it does it sets a cookie called hcdn, which goes when you close your browser.

It collects only what you type into its three forms.

Get Early Access: your email address, and whether your browser's clock is set to the UK or the US, so we can tell you when the app opens where you play.
Register your interest, on the page for venues: your venue's name, your name and your email address, and the same UK or US, so our team can get in touch about running your venue on GotGame.
Register your interest, on the page for coaches: your name, your email address, where you coach (a town or a club), and the same UK or US, so our team can get in touch about coaching on GotGame.

Only our team sees them. We use them for that and nothing else, we don't pass them on, and nothing is sent to you automatically. You can have them removed at any time by emailing support@gotgamenow.com. The lawful basis is your consent, given by submitting the form.

The page loads its typefaces from Google Fonts, which means your browser makes a request to Google and Google sees your IP address in the course of serving them. Nothing else on the page talks to anybody but us.

One page is different: the payout page (www.gotgamenow.com/payout). A club's admin or a coach opens it from the app, with Change, to change the bank they are paid into. It loads Stripe's own script as soon as it opens, and shows Stripe's form inside it, so Stripe sees your IP address and what you do in that form, and may set cookies of its own, under its own privacy policy. Stripe may text you a code first, to check it is you. The page itself stores nothing: it hands our server the one-time pass from the app, once, and gets back Stripe's key to your account, which it never keeps.

And one more site: venues.gotgamenow.com, where the people who run a venue manage it in GotGame. Only a venue's managers and staff can sign in there: with a code to the account they already have (nobody can make an account there), or, on a device the venue has made its desk, as the venue itself, with each person typing their own desk code. It keeps that sign-in in your browser's own storage for that site, as the app does on your phone; it is used for nothing else, and clearing the site's data in your browser removes it. If the site breaks, it sends Sentry a crash report like the app's (§7), with your browser and its version in place of your phone's model.

Two of its pages are for a venue's customers, without signing in: the page a venue's text links to, which takes you straight to Stripe's own payment page, and the page Stripe sends you back to. Stripe's page is Stripe's: its privacy policy and cookies apply there. The site itself sets no cookies, has no analytics, serves its own typefaces rather than loading them from Google, and talks to nobody but us, Sentry, and Stripe's payment page when you choose to pay.

A venue's owner and managers answer a disputed payment on Stripe's own form, inside the site's Disputes page. That page loads Stripe's script when it opens, so Stripe sees their IP address and what they do in the form, and may set cookies of its own, under its own privacy policy. The record of a booking they can download is made in their browser; we keep nothing about it.

Booking a court at a venue. gotgamenow.com/book/… is a venue's booking page. It's part of venues.gotgamenow.com, served at this address. It shows free courts and prices without signing in. If you sign in there, it keeps that sign-in in your browser's own storage for this site, as the venue website does. While a court is held for you, it keeps the random number in §3. If you book as a guest, the page also keeps the email address you typed, in that tab's own storage, so it can show it back to you once you've paid and a mistake can be spotted. It goes when you close the tab. It sets no cookies, has no analytics, serves its own typefaces, and talks to nobody but us, Sentry if it breaks (§7), and Stripe's payment page when you choose to pay.

A venue's free times on its own website. A venue can put a panel from us inside a page of its own website (gotgamenow.com/panel/…). It shows the venue's free courts and prices, and nothing else: it asks nothing of you, keeps nothing in your browser, sets no cookies, has no analytics, serves its own typefaces, and talks to nobody but us, and Sentry if it breaks (§7). Picking a time opens the venue's booking page in a new tab (above). The rest of that page is the venue's own website, under the venue's own privacy policy.

The web version. app.gotgamenow.com is the app in a browser, for a phone the app isn't on yet or anyone who'd rather not install it. It's the same app, under this same policy, and keeps the same things about you. The differences: it keeps your sign-in in your browser's own storage for that site, as the app does on your phone, and clearing the site's data in your browser removes it; while you're on Stripe's page paying, it keeps which game you're paying for in that tab's own storage, until you're back or the tab closes; you pay on Stripe's own page, where Stripe's privacy policy and cookies apply (§7); your browser loads Google's map from Google, and the place name comes from Google (§5, §7); it asks your browser for your location, only while you use it; and if you turn notifications on, your browser's push service delivers them (§3, §7), and a small script your browser keeps for the site shows each one and opens the app when you tap it. That script keeps no copy of the site and nothing about you. It sets no cookies, has no analytics, serves its own typefaces, and talks to nobody but us, Google's maps, Stripe's page when you pay, your browser's push service if you turn notifications on, and Sentry if it breaks (§7).

13. Changes

If we change this in a way that materially affects you, we will tell you in the app before it takes effect. The date at the top is always the current version.

What changed on 6 November 2026. We now keep a list of the days you open the app, the day only and for two years, so we can count how many people use GotGame and whether they come back. Until now we kept only the last time you opened it (§3, §4, §8). Later the same day: investors we invite to see our numbers, what we keep about them and for how long (§3, §4, §8).

What changed on 4 November 2026. Notifications in the web version, if you turn them on: what we keep (§3), your browser's push service, which delivers them (§7), and the small script that shows them (§12). Later the same day: a note of each sign-in code we text, kept for two days, so that no number can be sent codes over and over (§3, §4, §8).

What changed on 3 November 2026. If you book a court with your GotGame account, your confirmation email now has the link to see or cancel it that guests get (§3). When we put a venue live, its owner and managers are now emailed as well as told in the app (§3). And if you book a court as a guest, the booking page keeps the email address you typed in that tab until you close it, to show it back to you once you've paid (Booking a court at a venue). Later the same day: the web version, app.gotgamenow.com (§12), with paying on Stripe's own page (§1, §3, §7), and Google's map and place names in the browser (§5, §7).

What changed on 2 November 2026. An email when a venue cancels a court you booked, moves it, or closes its court (§3, §7).

What changed on 30 October 2026. An email, and a notification in the app if you booked with your account, if the money set aside on your card for a court can't be taken (§3, §7). Later the same day: a venue in the US can text you about a court it booked for you (§3).

What changed on 28 October 2026. Booking a court yourself at a venue that runs its courts in GotGame, with your account or as a guest: what the venue gets, the link in your email to see or cancel it, the 18+ tick, where a booking came from, and how we stop courts being held up (§3, §4, §7, §8, §11, §12). And who can see a venue's free courts: now anyone, on its booking page (§3). Later the same day: the emails about a court you booked, including when you cancel it, and how long we keep the address they go to (§3, §4, §7, §8). And a panel of a venue's free times that it can put on its own website (§3, §12).

What changed on 26 October 2026. An emailed invite to join a venue's team now keeps the address only until the invite is used, cancelled or runs out (§3). Later the same day: when you dispute a payment with your bank, what we keep and who sees it (§3, §4, §7, §8), and the venue website's form for answering it (§12).

What changed on 25 October 2026. Our team can now make an account for you if you ask, start erasing your account (for example when you ask us by email), make you a coach or stop you coaching, and add, close or reopen a club or venue. §3 says what each keeps and who is told, and §8 says that an erasure we start works the same as one you start.

What changed on 24 October 2026. The page for venues has a form to register your interest: what it keeps, who sees it and why (§12). We also now say that the early-access form keeps whether you're in the UK or the US, which it always has. Later the same day: the page for coaches has a form to register your interest too, and §12 says what it keeps. And if we don't approve an application to coach, we now tell you why (§3).

What changed on 23 October 2026. If we don't confirm that you run a venue, we tell you why, in the app, on the venue website and by email, and keep the reason we gave (§3, §7).

What changed on 22 October 2026. Whether a cancel at a venue was at your request, and that only those count as cancelling late (§3). A booking's history now shows the venue's front desk who did what about that booking, and keeps marking someone as arrived or not turning up, and taking that back (§3).

What changed on 21 October 2026. Venues that run their courts in GotGame: their teams and invites, front desk's limit, and who did what (§3). A venue's desk, its staff's desk codes, and who was on it. Courts a venue books for you, who's playing (a junior by first name only, §11), paying for them, and the texts a venue sends you through us (§3, §7, where Twilio's row now says so). Stripe's payment page for paying a venue, and the pages on venues.gotgamenow.com that take you there (§12). And, if a venue brought you across from its old booking system, whether you agreed there to hear from it (§3). Later the same day: a venue's notes about you, whether you didn't turn up, whether you've agreed to hear from it and whether it has stopped you booking online, each with who recorded it; what it sees from your bookings; and a venue downloading its customer list or its money (§3, §8). And how long a venue keeps its customers' details: two years after their last booking, or less if it removes them (§8). And a venue's VAT or sales tax: whether it is registered, its number, its rates and who changed them (§3).

What changed on 16 October 2026. Adding your games to your phone's calendar, in §3; it should have been here when it arrived, on 13 October. Games and events for meeting people, and who can see them. Telling us you run a venue no longer involves a club, and makes you one of its managers; §3 now says what a venue's managers set up, and §12 describes venues.gotgamenow.com, where they do it. Google's Firebase Cloud Messaging, which delivers notifications in the Android app. Your earned level and attendance are switched off for now, and §3 and §6 now say so. A banned account's email address is fingerprinted as well as its number (§8). Moderators, a mark that you paid in cash, and the one reminder to pay are named. The names of buttons and settings match the app. And we now write our name as GotGame.

What changed on 14 October 2026. Only clubs and coaches we have approved are paid in the app; a player hosting a game for friends is not. If you are paid in the app, we now keep your bank's name and the last four digits of the account, and §12 describes the payout page where you change it. §12 also names our web host's cookie.

What changed on 13 October 2026. Paying in the app, with Apple Pay and Google Pay through Stripe, and getting paid as a host, club or coach. Coaching: applications, hours and lessons. Stripe's and Google's Maps SDKs are now named. Earlier this month we added your notification choices and "Member since" (5 October), the stars you give a host, club or court (6 October), and telling us your club runs a court (9 October).

14. Contact

Email support@gotgamenow.com for anything at all — questions, corrections, a copy of your data, a complaint.