- We keep your sign-in details, the venues you follow, the bookings you save, the games and lessons you set up, the alerts you set and your avatar, if you make one, so the app can show and remind you of them.
- We never see your venue password or your card number. You sign in and pay on the venue’s own website, and a court:scout Extra or Pro subscription is paid through Apple, through Google, or by card through Stripe on this website.
- Your location, your calendar and your venue login stay on your phone. Your players’ names are kept on your account, so every phone you sign in on shows the same list; their numbers, emails and pictures stay on the phone you added them on.
- Adding players is optional. You are only linked with someone on court:scout when one of you accepts the other’s invite, and a player only sees the bookings you put them on.
- No ads, no tracking, no analytics from other companies and no selling of data. The app keeps its own simple counts of how it is used, and a record of how your alerts work out kept under a code instead of your name. You can switch both off in Account, under Privacy and your data.
- You can delete your account and everything in it from the app at any time.
Contents
- Who we are
- What we collect
- What stays on your phone
- Why we use it, and our legal basis
- Who we share it with
- Transfers outside the UK
- How long we keep it
- Your rights
- Deleting your account
- Phone permissions
- Children
- Security
- This website and cookies
- Changes to this policy
- Contact and complaints
1. Who we are
court:scout is a mobile app that shows tennis court availability at venues in the UK, alerts you when a court frees up, keeps a record of the courts you book, and lets players, organisers and coaches run games and lessons on them. It is run by ODD MACHINE LTD, a company registered in England and Wales, company number 17498960, with its registered office at 124 City Road, London, EC1V 2NX (“we”, “us”). We are the controller of the personal data described here, registered with the Information Commissioner’s Office under registration number ZC279124.
Contact us about privacy at support@courtscout.uk.
court:scout is independent. It is not affiliated with, or endorsed by, any venue, club, governing body or booking provider.
2. What we collect
We only collect what the app needs to work. It is stored in Google Firebase, in the London region (europe-west2), unless noted otherwise.
| What | Details | Where it comes from |
|---|---|---|
| Account | A user ID, your email address, your name and whether you signed in with Google or Apple. If you use Apple’s “Hide My Email”, we only get a private relay address. Firebase also records when the account was created and when you last signed in, and we note whether it was made on this website. | Google or Apple, when you sign in in the app |
| Browsing without an account | If you tap “Browse without an account”: a random user ID with no email or name, under which the app keeps the venues you follow and your basket, and the day’s app use counts. Firebase records when it was made. If you sign in later, the same ID becomes your account and keeps them. | The app, when you browse |
| Venues you follow | The list of venues you choose to see. | You |
| Bookings | For each booking: venue, date, start and end time, court, the venue’s booking reference, the gate PIN if the venue gives one, and whether it is confirmed or cancelled; the court price and ball fee, if you type them or the venue shows them; how many players it is for; and, on Pro, which game or lesson it is for. When the venue’s details or your own were last changed, and whether from an iPhone, an Android phone, the website or our servers, with a random install ID. | The venue’s confirmation or “my bookings” page, which the app reads when you open it in the app (see below), and you |
| Alerts | The venue, day or weekdays and time window you want to hear about, whether the alert is paused, when you set it, and the app’s record of what it has already told you about. Some alerts follow a venue’s booking window, which can reflect your membership or coach status there. | You, and our alert service |
| Email alerts on the web | Only if you ask for alerts by email on courtscout.uk/app: your email address, the alerts you set there (venue, day, hours, and a court if you picked one), a one-way code of the address, the code we email you to check it (kept as a one-way code, with when it was sent and how many tries were made), when you confirmed, and what the alert service has already told you about. If you tick “Also email me now and then about the court:scout app”, those words and when you ticked the box. No account, name or password. | You |
| Notification settings | Which kinds of notification you want: free court alerts, cancellation reminders, upcoming reminders, games and lessons, and News (announcements and offers, off unless you turn it on). | You |
| Your Schedule (Pro) | If you coach or organise on Pro: how you set out Schedule (how court bookings are shown, your available hours, and whether free slots, a continuous feed and costs are shown), and for each day from today on the times you made unavailable or free and the bookings you joined or split, by venue and time. When each was last changed and whether from an iPhone, an Android phone or our servers, with a random install ID. No names. The app deletes each day once it has passed. | You |
| Games and lessons (Pro) | For each game or lesson you set up, on its own or on a court you booked: whether it is a game or a lesson, the venue, date, start and end time, how many players it is for, who you put on it and who you took off it, and when it was made and last changed, and whether from an iPhone, an Android phone or our servers, with a random install ID. A game or lesson that repeats is kept as one of these for each date. | You |
| Your players and clients | The players you add, by hand or from your contacts: the name you give each one, their court:scout user ID if one of you accepted the other’s invite, the groups you put them in and the names you give those groups, whether you marked them as a client (Pro) and when you added them. For each booking: which of them you put on it, which you asked, and how many places it has. When each was last changed and whether from an iPhone, an Android phone or our servers, with a random install ID. Not their phone number, email address or picture: those stay on your phone (section 3). They need not use court:scout. See Your players. | You |
| Push tokens | A token for each phone you are signed in on, so we can send it notifications. It is removed when you sign out or it stops working. | Your phone, via Google Firebase Cloud Messaging and Apple Push Notification service |
| Bookings shared with players | When you put a player who is on court:scout on a booking: its venue, date, start and end time and court, the gate PIN if the venue gives one, the court price and ball fee if the booking has them (not its reference), how many players it is for, your name and user ID, their user ID, whether they have confirmed or declined, and the first names of the other players on it, as your phone has them. Those players need not be on court:scout. | You, and the player’s answer |
| Bookings opened to players | When you open a booking for players to sign up: its venue, date, start and end time and court, the court price and ball fee if it has them, how many places it has, your name and user ID, the user IDs of the players you opened it to, who has signed up, who is on the wait list and who said no, with when each took a place, the first names you know them by, the first names of your own players you put on it, and whether sign-up is closed. The gate PIN, if the venue gives one, is kept apart and only you and those with a place can see it. | You, and the players who answer |
| Avatar | If you make one: a short code naming the hat, glasses, tennis kit, eyes and mouth you picked from the app’s own drawings. It is not a photo. | You |
| App settings | Choices you make in the app, kept so they are the same on every phone: whether I coach is on and how long your lessons usually are, courts you hid at a venue, the players whose invites you switched off (by user ID), which tours, tips and News items you have seen, whether you switched the counts off, and the app version on each kind of phone you use. | You, and the app |
| Invites | When you invite a player by link: a random code, your user ID and name, an ID for that player on your list (not their name or number), when the invite expires, 30 days on, and an ID for the phone it was sent from: random on an iPhone, kept on that phone alone so it stays the same if the app is put back; on Android, a one-way code made from the ID Android gives court:scout on that phone. Neither names you or the phone. Whoever accepts it adds their user ID, name and their own phone’s ID. | You, and whoever accepts |
| Who you are linked with | The user IDs of the accounts you are linked with, because one of you accepted the other’s invite, and when. It decides who can put you on a game or lesson, and whose you can see. Only our servers write it, and only you can read your own. | Our servers, when an invite is accepted |
| Friends who joined | When we run “invite friends, get a month free”: how many friends have made a court:scout account from your invites, and any free months of Extra or Pro that earned you. So that nobody is counted twice, for anyone who joins from an invite we keep a one-way code made from their Google or Apple sign-in ID, and another made from the phone ID they accepted it on, each with when it was made: neither can be turned back into the ID, and they name no one, not even whose invite it was. The same goes for anyone given a free month as a tester: a one-way code made from their sign-in ID, so the month is given once a person. | Worked out from invites when they are accepted |
| court:scout Extra and Pro | If you subscribe to court:scout Extra or Pro, or we give it to you: which of the two, the store’s product, the plan (monthly or yearly), whether it is a free trial, when it runs out, whether it will renew, whether it was bought from Apple, from Google or on this website, and when the trial and the paid subscription began. No card or billing details. | Apple, Google or this website’s checkout, through RevenueCat (see section 5) |
| Payments by card | Only if you buy court:scout Extra or Pro on this website: the email address you give at the checkout, the amount and date of each payment and refund, and your card’s type, last four digits, expiry date and country. Never the full card number or its security code, which only Stripe handles. These are kept by Stripe and RevenueCat, where we can see them, and in our accounts; they are not in the app’s database. | You, at the checkout |
| Crash reports | When the app crashes or freezes, or something in it fails: what the app was running at the time (the code, not what was on the screen), the phone model, system version, app version and a random install ID. Not your account, email, venues, courts or players. Sent to Google’s Firebase Crashlytics and kept 90 days. Not sharing usage data, when the app asks or in Account, switches these off too. | The app, via Google Firebase Crashlytics |
| App use counts | For each day you use the app: how many times you opened it and used its features (such as bookings made, a venue login screen opened, or something that failed), how many players and signed-in venues the app holds, the app’s version, and whether it is an iPhone or Android. Numbers only: never which venue, court, time or player. If you switch the counts off in Account, we keep only the fact that you did. | The app |
| Alert results | For each day one of your alerts was for: how many alerts, how many found a court and how many you booked from, how many were still to come, the venues they watched, your share of the requests our servers made that day, the hour they started in, and how many days ahead you set them; with the dates you joined, set your first alert and first had a court found, and whether you use an iPhone or Android. It is kept under a code made from your user ID with a secret key, never your name, email or user ID, and only the people who run court:scout can see it, after signing in. Nothing is kept if you switch the counts off in Account. | Worked out each night from your alerts |
| Reports | If you report someone: their user ID and yours, the reason you picked, any words you add, where you reported from (their sheet in Players or a friend invite), and when. We email it, with both accounts’ names and email addresses, to our support inbox. The person you report is not told who sent it. | You |
| Service logs | Our alert service writes a short technical summary of each run (such as how many alerts were checked and pushes sent). They are used to keep the service running. | Our servers |
| Fair use records | Kept by our servers under your user ID: a copy of your alerts for the alert service to read, how many notifications your invites sent other people today (we send up to 60 a day; past that, invites still arrive, without one), when they last matched your games and lessons to your courts, and how many requests to venues’ systems they made for you each day. They keep the service fair and stop misuse. | Our servers |
| Weather requests | When the app shows the forecast for an outdoor court, it asks our servers for the forecast at that venue, signed in as you. Only the venue’s area goes on to Apple Weather, and forecasts are kept by area, not by person. Your account is not logged with it, and your own location is never used. | The app |
How bookings get into the app
When you book, the venue’s own booking website opens inside the app. You sign in to the venue and pay there, just as you would in a browser. When the venue shows your confirmation, when you open your list of upcoming bookings, and each time the app syncs your bookings, the app reads the court, time, reference and gate PIN from that page and saves them to your account. It is built to skip your name, email, contact details and the names of other players on those pages.
We never see, store or send your venue password, or the card you pay a venue with. If you subscribe to court:scout Extra or Pro, the payment is taken by Apple, by Google, or, on this website, by Stripe: we never see or hold your full card number.
What we don’t collect
No phone number, postal address, precise location or photos, and no card numbers. The app never reads your contacts: when you add a player from them, your phone’s own picker hands over only the contact you pick, and it stays on your phone. Once, the first time you sign in on a new account, the app looks at your clipboard for a court:scout invite link copied on this website, so that an invite comes with you through the install; anything else there it leaves, and nothing is sent. No advertising identifiers. The app contains no analytics or advertising tools from other companies; the only record of how you use it is the app’s own counts, listed above. The parts of the app made by other companies are Google’s Firebase Crashlytics, which sends the crash reports above; RevenueCat’s, which runs court:scout Extra and Pro subscriptions; and the map, which loads from Google Maps on Android and Apple Maps on iPhone (see section 5).
3. What stays on your phone
Some data is only ever kept on your phone. We cannot see it.
- Your venue login. court:scout opens venue websites in a built-in web browser, which keeps their sign-in cookies on your phone so you stay signed in, like your normal browser. So that you stay signed in after the app closes, they are kept in the app’s private storage on that phone only (on iPhone, a copy is kept in the Keychain). When a sign-in expires, the app renews it using the cookies it already has, never your password: as the venue’s own website does, or for ClubSpark venues by signing you back in through your LTA login. Cookies are never sent to us. Logging out of court:scout keeps them on that phone for when you sign back in; if another account signs in there, or someone browses without an account, they are removed first. Sign out on the venue’s site, or delete your account, to remove them. See Cookies.
- Your location, if you allow it. It is used at town-level accuracy to sort venues by distance, and the map shows where you are on it. It is never sent to us. To draw the map, your phone asks Google Maps (Android) or Apple Maps (iPhone) for the map around you, under their own privacy policies.
- Your calendar, if you turn on calendar sync. The app adds your court bookings, games and lessons to a calendar you choose, with the first names of the players and clients on them and whether each is going, the cost on the bookings you made if you show costs, and the gate PIN if you ask. If that calendar syncs to Google, Apple or another provider, it is shared with that provider under your account with them, not by us.
- Your players’ numbers, emails and pictures. The phone numbers, email addresses and pictures of players you add, by hand or from your contacts, are kept in the app’s private storage on the phone you added them on, and are left out of backups. They are never sent to us. Their names are kept on your account (see Your players). If you browse without an account, the whole list stays on that phone.
- Coaches and organisers on Pro. The people you invite are court:scout users in their own right: we hold what they give us as we hold yours, under this policy, and they can see, change or delete it themselves. When you send a lesson to more than one client, each of them sees the first names of the others on it and whether they have confirmed or declined. Your groups, the names you give them and which players you mark as clients are kept on your account with your players’ names. court:scout has nowhere to type notes, health details or what a client pays you, and none of it reaches us. The court price you type on a booking is the court’s, and the players on it see it. Any records you keep about your clients outside court:scout are yours to look after.
- Reminders are scheduled on the phone itself.
- Your status at each venue (for example whether you are signed in there, or a coach), which the app checks to show the right booking windows.
- On Pro, your basket of courts you are about to book, and a local copy of your account data so the app works offline.
Your players and clients
On Pro, your clients are players you mark as a client: they are on the same list and held the same way. Adding players is optional. Each name you add is kept on your court:scout account with the groups you put them in, so the list is the same on every phone you sign in on, and is still there when you change phones. Only you can see your list. The people on it are not told they are on it and cannot see it. A player you put on a booking you share or open sees that booking, and the other players on it see their first name as you have it (see Who we share it with). We don’t use anyone’s list for anything else: not for marketing, not to suggest people to you or anyone else, and not to match one person’s list against another’s.
Removing a player in the app removes them from your account and from every phone signed in to it. Deleting your account removes the whole list.
If you are on someone’s list (as a player or a client). We hold only the name they gave you, the groups they put you in, whether they marked you as a client, and which of their bookings they put you on: no phone number, email address or picture. We hold it so they can organise games and lessons with you (section 4). To have it removed, ask the person who added you, or email support@courtscout.uk with your name as they would have it and their name or email address, so we can find it. We remove it within one month and tell you when it is done. A parent or guardian can ask for a child in the same way. You have the other rights in section 8 too.
4. Why we use it, and our legal basis
| Purpose | Data | Legal basis (UK GDPR) |
|---|---|---|
| Create and secure your account, and sign you in | Account | Contract: we need it to provide the app you asked for |
| Show your venues, bookings and gate PINs across your phones | Venues, bookings | Contract |
| Watch availability and tell you when a court frees up, without telling you about a slot you already hold | Alerts, bookings, notification settings, push tokens | Contract |
| Invite players by link, share bookings with the players you choose, show them your avatar, and tell each of you when the other adds, cancels or answers | Invites, who you are linked with, shared bookings, bookings opened to players, avatar, push tokens | Contract |
| Show the players on a booking (or the clients on a lesson) who else is playing, by first name, and whether each has confirmed or declined, including players who don’t use court:scout | Shared bookings, bookings opened to players (players’ first names) | Legitimate interests: letting the people on a booking know who they are playing with. Only a first name is kept, only the players on that booking see it, and it goes when the booking does |
| Keep your players list on your account, so it is the same on every phone you sign in on | Your players and clients | Contract, for you. For the people on it, legitimate interests: letting you organise games and lessons with them. Only a name is kept, only you see the list, and anyone on it can have their name removed (see Your players) |
| On Pro, give each game or lesson the court you booked at its time, and send it, and each change to it, to the players and clients you put on it. Our servers do this from your account whenever it changes, so it is done even while your phones are off | Your Schedule, games and lessons, bookings, your players and clients, bookings shared with players, bookings opened to players, fair use records | Contract |
| Show the weather forecast for outdoor courts | Weather requests | Contract |
| Keep your settings the same on every phone you sign in on | App settings | Contract |
| Sell court:scout Extra and Pro, take and refund payments for them, know which accounts have which, watch every alert of an account that has either, and let a Pro account invite players, tag them and open bookings to them | court:scout Extra and Pro, payments by card, account (user ID) | Contract |
| Give a free month of court:scout Extra for every three friends who join from your invites, and count each person once | Invites, friends who joined, account (user ID, sign-in ID) | Contract |
| Email a subscriber before a free trial ends, before a yearly renewal and every six months, saying when they will be charged, how much and how to cancel | court:scout Extra and Pro, account (email address) | Legal obligation, and contract |
| Keep the records of payments that tax and accounting law requires | Payments by card | Legal obligation |
| See which features are used and where the app fails, so we can improve it. We look at totals across all users, not at one person’s counts. | App use counts | Legitimate interests: understanding and improving the app |
| See how alerts work out for the people who set them (which venues, times and ways of setting them find courts, and who keeps missing out), so we can make alerts find more courts. We see a code, never who you are. | Alert results | Legitimate interests: making alerts work better |
| Keep the service working, find faults and prevent misuse | Service logs, fair use records, account | Legitimate interests: running a reliable, secure service |
| Act on reports of abuse: look at what was sent and, if needed, remove it and close the account that sent it | Reports, account, shared bookings, invites | Legitimate interests: keeping people safe from abuse in the app |
| Answer you when you contact us, and keep track of each email to support until it is dealt with | Your email address, name and message | Legitimate interests: replying to you |
| Email you, once, when a court comes free on an alert you set on the web, after you confirm your address with the code we email you | Email alerts on the web | Contract: you asked for the email |
| Check that whoever asks for web email alerts is a person and not a program, and limit how many codes go to one address and how many addresses one network can try in a day | Email alerts on the web, your IP address (seen by Cloudflare for its check; we keep only a one-way code of it, for that day’s count) | Legitimate interests: stopping our emails being used to pester people |
| Never email again an address that bounced, marked our email as spam, or said “This wasn’t me” | A one-way code of the address | Legitimate interests: not emailing people who didn’t ask |
| Mention the court:scout app in the court-free emails, only if you ticked “Also email me now and then about the court:scout app” | Email alerts on the web | Consent: tap “Stop app emails” in any of those emails |
| Meet legal obligations | Any of the above, as needed | Legal obligation |
| Send our announcements and offers as notifications, only if you turn on News | Notification settings, push tokens | Consent: turn News off at any time in the app |
We don’t use your data for marketing, profiling or automated decisions with legal or similar effects. If we ever want to send marketing messages, we will ask first.
5. Who we share it with
We don’t sell or rent personal data. We share it only with the following:
- Google (Firebase and Google Cloud) hosts our database, sign-in, alert service, push notifications, crash reports and this website, as our processor.
- Apple provides Sign in with Apple and delivers notifications to iPhones. Apple Weather provides the forecasts: it receives only the area of the venue asked about, from our servers, never your account or your location. Apple Maps draws the map on iPhones.
- Google also provides Sign in with Google, delivers notifications to Android phones, and draws the map on Android phones (Google Maps), under its own privacy policy.
- RevenueCat runs court:scout Extra and Pro subscriptions for us, as our processor. Where the app offers them, RevenueCat receives your court:scout user ID, technical details of the app and phone (such as their versions, language and country), and, if you subscribe, the record of your purchase: the plan, its dates, price and country. If you buy Extra or Pro on this website, RevenueCat also runs the checkout: it receives the email address you type there, which it uses to send your receipts and the link to manage your subscription, and it passes your card details to Stripe without keeping them. It does not get your name, or anything about your venues, bookings, alerts or players, and it gets no email address unless you buy on this website.
- Resend sends our emails for us, as our processor: the court:scout Extra and Pro reminders, the emails about your data (a coach’s records about to go, and an unused account about to be deleted, section 7), the web email alerts (the code that checks your address, and the email when a court comes free), and reports to our own support inbox. For an email to you it receives your email address and the email itself, which for a reminder says your plan, its price, the store you pay through and the date of the next payment. For a web email alert it receives your address and the email, which names the venue, the day and the hours. For a report it carries the report (see “Reports” above) to us. It tells us if an email bounced or was marked as spam, so we stop emailing that address. It gets nothing else about you.
- Stripe takes the card payment when you buy court:scout Extra or Pro on this website. It receives your card details, the email address you give at the checkout, the amount, and technical details it uses to prevent fraud, such as your IP address and browser. Stripe handles card details under its own privacy policy, and we never receive the full card number.
- Apple and Google, as the stores. If you subscribe to court:scout Extra or Pro in the app, you buy it from the Apple App Store or Google Play, which takes the payment under its own terms and privacy policy. We never see your card.
- Venues and their booking provider. When you open a venue’s booking site in the app, you deal with the venue and its booking provider (for most venues, ClubSpark) directly, under their own terms and privacy policy. We send them nothing about you.
- Your players on court:scout. A player you put on a booking sees its venue, date, times and court, its gate PIN, price and ball fee if it has them, your name, the first names of the other players and whether each has confirmed or declined, and gets a notification; you see whether they confirm or decline. A lesson works the same way: each client on it sees the first names of the other clients and their answers. A player you open a booking to sees the same, but the gate PIN only once they have a place, and sees who has signed up or is waiting. When a game or lesson moves, everyone on it is told; when someone accepts your invite, you are told their first name. Someone who accepts your invite sees your name, and you see theirs. Nobody else sees any of it. If you make an avatar, the app shows it to players linked by invite, in place of your initials; it holds nothing about you beyond the parts you picked.
- Cloudflare receives the emails you send to our courtscout.uk addresses, such as support@courtscout.uk, and passes them on, without keeping them, to our mailbox, which Google runs for us (Google Workspace) as our processor. For support@courtscout.uk it also passes a copy of the email’s text, without attachments, to our own database, where only the people who run court:scout read it, so each email is tracked until it is dealt with (section 7). Cloudflare also serves the private pages where the people who run court:scout read the app’s counts and alert results, as our processor. It holds them only to show them to those who sign in, and sees no names. It also keeps a second copy of our nightly backup (section 7), encrypted, in Western Europe, so the app can be put back if our Google account were lost. When you ask for web email alerts, its Turnstile check, as our processor, looks at your browser and IP address to tell a person from a program; it tells us only whether it passed.
- Authorities, if the law requires it, or to protect the rights and safety of our users or others.
- A new owner, if court:scout is ever sold or reorganised, who would have to honour this policy.
To show availability, our servers fetch public timetables from venues’ booking systems. Those requests carry only a venue and a date, never anything about you.
6. Transfers outside the UK
Our database and alert service run in London. Google’s sign-in and messaging services, and Apple’s, run on their global infrastructure, so some data (such as your email and push tokens) may be processed outside the UK, including in the United States. RevenueCat processes court:scout Extra and Pro subscription records in the United States, Resend sends emails from the European Union and the United States, and Stripe processes payments in the UK, the European Union and the United States. Apple Weather and the maps run on Apple’s and Google’s global infrastructure, and so does the Google mailbox that receives your emails to us. Cloudflare passes on those emails from its global network, serves the private pages of counts and alert results from its global network, keeps the second backup copy in Western Europe, and runs the Turnstile check on the web from its global network. Where data leaves the UK, it is protected by the UK’s adequacy regulations (including the UK Extension to the EU–US Data Privacy Framework) or by the UK International Data Transfer Addendum in Google’s, Apple’s, RevenueCat’s, Resend’s, Stripe’s and Cloudflare’s data processing terms.
7. How long we keep it
- Account, venues and settings: until you delete them or your account, or until nobody has used the account for two years (see Accounts nobody uses).
- Bookings, lessons and games: played or cancelled, 30 days after their date, or sooner if you delete them or your account. If you coach on Pro, see the next line.
- A coach’s records: while you are on court:scout Pro with I coach switched on, your bookings, lessons and games, and who was on them, are kept for two years after their date instead of 30 days, so you can look back on what you taught. If Pro ends or you switch I coach off, they are kept as they are for 90 days more; 2 weeks before those 90 days end we email you once, saying on what day, and after it the 30 days apply again, so anything older goes that night. Switch Pro and I coach back on before then and the two years carry on. While both are on, Export lessons in Account’s Schedule settings saves your lessons, games and bookings as a spreadsheet (CSV) file on your phone, to keep or send where you choose. That file is your own record, for your tax return or anything else; it is made on your phone, we never receive it, and we don’t keep a copy of it or your records for you beyond the two years.
- Browsing without an account: the random user ID and what is kept under it are deleted automatically 30 days after you first browsed, unless you have signed in by then. To have them deleted sooner, email us (see Contact).
- Alerts: until you delete them. Alerts for a single date are removed automatically once that date has passed.
- Email alerts on the web: an address never confirmed with its code is deleted after 7 days. Once confirmed, each alert ends after its email, or once its hours have passed, and the address and everything kept with it are deleted 30 days after the last one ended. Stop in any email, or in the Alerts sheet, deletes them at once. If an email bounces, is marked as spam, or you tell us “This wasn’t me”, the address is deleted at once and we keep only its one-way code, so it is never emailed again. The day’s counts of codes and of tries from a network are deleted the next night.
- Avatar: until you remove it in the app, or delete your account.
- Your players and clients: until you remove a player or a group, or delete your account. Who you put on a booking goes with the booking, 30 days after its date. Someone on your list can ask us to remove their name (see Your players).
- Bookings shared with players: 30 days after the booking’s date, or sooner if the player is taken off the booking or either of you deletes your account.
- Bookings opened to players: 30 days after the booking’s date, or sooner if you take the booking off or delete your account. A player who deletes their account is taken off it.
- Invites: one nobody accepted is deleted once it expires, 30 days after it was sent. One that was accepted is deleted by the sender’s phone once the two of you are linked.
- Who you are linked with: until either of you deletes your account.
- Fair use records: each is replaced as it changes and goes with your account; the daily counts of requests made for you are deleted after 7 days.
- Friends who joined: the count and the months it earned, until you delete your account. The one-way codes for someone who joined from an invite, for the phone they joined on, and for someone given a tester’s month are kept after their account is deleted, for as long as court:scout gives months for invites or tester’s months, as that is what stops the same person, or phone, being counted again; they identify nobody on their own.
- court:scout Extra and Pro: while a subscription runs, and afterwards as a record that there was one (so that a free trial is given once per account), until you delete your account. Deleting your account deletes this record, and we have RevenueCat delete its copy.
- Payments by card: six years from the end of the financial year of the payment, because tax and accounting law requires us to keep records of what we were paid. They stay with Stripe and in our accounts, and are not deleted with your account.
- Push tokens: until you sign out on that phone, or the token stops working.
- App use counts: five weeks, or until you switch them off or delete your account. After that only daily totals across all users remain, which don’t identify anyone.
- Alert results: each day for 90 days, then it is deleted. All of it is deleted the night after you switch the counts off, or when you delete your account.
- Reports: as long as needed to deal with them, and no more than two years; the email to our support inbox, the same.
- Service logs: up to 30 days.
- Backups: every night we copy our database, so it can be put back after a fault or a mistake. The copies are kept for 7 days in Google Firebase, 14 days in Google Cloud in London and 31 days with Cloudflare, then deleted. Something you delete, or your whole account, stays in the copies until then. If we ever put a copy back, we delete again whatever was deleted after it was made.
- Emails you send us: as long as needed to deal with them, and no more than two years. The copy of an email to support@courtscout.uk that we keep to track it is deleted after 90 days.
- Emails we send about your data: the record that we sent one, and on what day, is kept with your account, so that each goes once. It goes when your account does.
Accounts nobody uses. If nobody has used an account for two years (no sign-in and the app not opened signed in to it), we delete it, in the same way as if you had deleted it yourself (section 9). We email you 30 days before, and again 7 days before, from court:scout (ODD MACHINE LTD) to the email address on the account, saying on what day; these are service messages about your account, not marketing. To keep the account, just open court:scout and sign in before then. We never delete an account in this way while a subscription, a gift or a tester’s month runs on it, or while a coach’s records are being kept for two years.
8. Your rights
Under UK data protection law, you have the right to:
- access the personal data we hold about you and get a copy of it;
- correct data that is wrong;
- delete your data (you can do this yourself in the app, see below);
- restrict or object to our use of it, where we rely on legitimate interests;
- data portability: receive the data you gave us in a machine-readable format (JSON).
To use any of these, email support@courtscout.uk from the email address on your account, or tell us which one it is. We will reply within one month, and it is free.
The first time you open the app on a phone, it asks whether to share usage data, and counts nothing until you answer. If you choose Don’t share, nothing is counted and no crash reports are sent. You can change your answer at any time: open the Account tab, tap Privacy and your data, and switch “Share usage data” off or on. Off stops the counts on every phone signed in to your account, and the counts kept so far are deleted within a day. Daily totals already added up across all users stay, as they don’t identify anyone.
9. Deleting your account
In the app, open the Account tab, tap Privacy and your data, then Delete my account, then Delete. To confirm it is you, the app asks you to sign in once more with Google or Apple. If you back out at that point, nothing is deleted.
This permanently deletes your venues, bookings, games and lessons, alerts, your players list and its groups, who you are linked with (on both sides), notification settings, push tokens, app use counts, every booking you shared or were shared, the invites you sent, your avatar, and your sign-in account. If you signed in with Apple, it also removes court:scout from your Apple ID. It does not cancel bookings you have made with venues, or close your account with a venue’s booking system: do those with the venue.
It also deletes the record of court:scout Extra or Pro, if you ever had either: ours, and RevenueCat’s copy. A subscription bought by card on this website is ended, and no more payments are taken. A subscription bought from Apple or Google is different: we cannot cancel those for you, so cancel it in your App Store or Google Play account first, or it will go on being charged. Three things are kept (section 7): the record of payments already made by card, because the law requires it; the one-way codes that stop an invite’s or a tester’s month being given twice, which identify nobody on their own; and reports, until they are dealt with.
The phone you delete from also clears what the app kept on it: the calendar events it added (past ones too), its reminders, your venue login, the venue booking rules it read, your players’ numbers, emails and pictures, and your basket. On any other phone signed in to the same account, upcoming calendar events and reminders are removed once the app there notices the account is gone, usually within an hour of it next running. Uninstalling the app there removes the rest.
Copies of it in our nightly backups are deleted within 31 days (section 7).
An account nobody has used for two years is deleted in this same way, after two emails, 30 and 7 days before (see Accounts nobody uses). A subscription bought from Apple or Google is never running when that happens, as we don’t delete an account while one runs.
If you no longer have the app, see how to delete your account without it.
10. Phone permissions
Each one is optional, and the app works without it. You can change them at any time in your phone’s settings.
- Notifications: to tell you when a court frees up, to remind you about your bookings, games and lessons, to tell you about invites and changes to them, and, if you turn on News, to send our announcements.
- Location (approximate, while using the app): to sort venues by distance and show where you are on the map. It is never sent to us.
- Calendar: to add your schedule to a calendar you choose, and keep it up to date.
- Contacts: the app doesn’t ask for access to them. To add a player from your contacts, it opens your phone’s own picker, which gives the app only the contact you pick.
11. Children
court:scout is for people aged 18 or over. We don’t knowingly collect data from anyone younger. If you think someone under 18 has an account, email us and we will delete it.
12. Security
Data is encrypted in transit and at rest. Each account can only read and write its own data and the bookings shared with it, and access to our systems is limited. No system is perfectly secure, so please keep your phone locked. Anyone who can see a calendar you sync can see the gate PINs in it, if you choose to include them.
13. This website and cookies
courtscout.uk sets no cookies and uses no analytics from other companies. When you tap a link to Google Play, or a venue’s Coaching link on its page, the page tells our server, which adds one to that day’s count of taps: nothing is stored on your device, and the count holds no IP address, nothing about you and not which page you were on. The site’s fonts and images are served from this site. It is hosted by Google (Firebase Hosting), which processes your IP address and basic request details to deliver the pages and protect against attacks. Cloudflare runs the domain’s name service: it answers the lookup of “courtscout.uk” and does not carry the pages.
The tennis court pages (courtscout.uk/tennis-courts) show a map. Its code is served from this site, but the map itself is drawn from tiles your browser fetches straight from OpenFreeMap (tiles.openfreemap.org), a free map service built on OpenStreetMap. So OpenFreeMap receives your IP address and the part of the map you look at, as any website you visit would. It sets no cookies, and we send it nothing about you. If you tap the map’s location button, your browser asks whether to share your location; if you agree, it is used in your browser only, to centre the map and measure distances to venues, and is never sent to us or to OpenFreeMap.
The court grid on the web (courtscout.uk/app) uses the same map. To show a venue’s free courts, your browser asks our server, which reads the venue’s public booking times and passes them back (for ClubSpark venues, through our own reader on Amazon Web Services in London); the request names only the venue and the day, never you, and Amazon receives nothing about you. You need no account there, and unless you ask for email alerts we keep nothing about you: the venues you save stay in your browser’s storage until you clear it, and the courts you pick stay there until you close the tab. You book and pay on the venue’s own website, in its own window, and we never see your venue sign-in or your card. We count, without anything about you, how often a venue’s booking page is opened from the grid, and how often the grid is opened from a tennis court page’s “See free courts”.
Find a lesson on the web (courtscout.uk/tennis-lessons) works the same way. To show a ClubSpark venue’s lessons, your browser asks our server, which reads the venue’s public coaching listings through the same reader on Amazon Web Services in London and passes back the lessons: their names, times, prices and spaces left, never the coaches’ or organisers’ details. The request names only the venue, never you. The venues you add stay in your browser’s storage until you clear it. You sign up and pay on the venue’s own ClubSpark page; we count, without anything about you, how often a lesson’s sign-up page is opened.
The alerts you set on the grid stay in your browser. If you want them by email, you give an address and we email a 6-digit code to check it is yours; nothing is watched until you enter it or tap the email’s button. Before that code is sent, Cloudflare’s Turnstile check makes sure a person is asking (this is the only time the page loads code from another company). From then on our alert service watches those alerts and emails you once when a court comes free; each alert then ends. Every email has a link to stop them all or one, and the address goes as set out in How long we keep it. We count, without anything about you, how many addresses are confirmed and how often a link in these emails is tapped. The court:scout app is mentioned in those emails only if you ticked “Also email me now and then about the court:scout app”; “Stop app emails” in any of them takes that back.
You cannot sign in, join court:scout or buy a plan on this website: that is done in the app. If you bought Extra or Pro by card here before, the checkout was RevenueCat’s page, with Stripe’s card form. RevenueCat’s emails about your plan link to its own page, where you can see, change or cancel it; RevenueCat and Stripe set the cookies they need there to take a payment safely and prevent fraud.
14. Changes to this policy
If we change this policy, we will post the new version here with a new date. If a change significantly affects your data, we will also tell you in the app before it takes effect.
15. Contact and complaints
Email support@courtscout.uk.
If you are unhappy with how we have handled your data, you can complain to the Information Commissioner’s Office (ICO) at ico.org.uk/make-a-complaint, or by phone on 0303 123 1113. We would appreciate the chance to put things right first.
