Privacy Policy
PadelSideQuest is a small, independent site. Here's exactly what happens with your data — in plain English, not legal fog.
PadelSideQuest is a small, independent site. Here's exactly what happens with your data — in plain English, not legal fog.
Last updated: 13 September 2026
PadelSideQuest doesn't have user accounts, doesn't run ads, and doesn't sell or share personal data with anyone. By default, the match organiser tool runs entirely in your browser — your players' names and scores stay on your device. The two exceptions are entirely your choice: getting a live shareable code, or saving results to a group leaderboard — both explained in full below, since a name typed into either does briefly live on our server. The only outside services in play are an analytics cookie (only if you say yes to it) and, if you choose to sign up, an email newsletter provider.
When you first visit, you're asked whether it's OK to use Google Analytics. If you accept, a cookie is set and Google Analytics loads to give us a rough idea of which guides are useful and how people find the site — page views, approximate location (country/city level), device type, that sort of thing. It's aggregated and anonymised as far as Google's tools allow; we don't use it to identify you personally.
If you decline (or just ignore the banner), that script never loads and no analytics cookie is set. Either way, your choice is remembered in your browser's local storage so you're not asked again on every visit. You can change your mind any time using "Cookie settings" in the footer of any page.
Google's own handling of analytics data is covered by Google's Privacy Policy.
Everything you type into the Americano/Mexicano organiser — player names, courts, scores, tournament name — is saved using your browser's local storage, on your device only, by default. None of it is sent to us, stored on a server, or visible to anyone else — apart from the anonymous counts described next.
Anonymous usage counts: so we can see whether the tool is being used, a few simple totals are kept on our server: when a game is started or finished, the organiser's browser tells us just that and how many players were in it; and when someone uses an optional feature above (a live code, a group leaderboard, match details or player insights), we add one to a daily tally. The thumbs up / thumbs down shown quietly at the end of a game is counted the same way, as just one more daily total. If you choose to type a note after that, the note (with the thumb and the game format, and the date) is stored on our server so it can be read and acted on, and deleted after 12 months; please don't put personal details in it, and nothing else identifying you is stored with it. That is all: no names, scores, codes, IP addresses or anything that identifies a person or a device is recorded with the counts, nothing is stored on your device to do it, and it works the same whether or not you accept analytics cookies. The result is a table of numbers per day that we keep indefinitely. Clear your browser data (or use a different device or browser) and it's gone.
If you use the WhatsApp, email, or SMS share buttons after a session, that message is composed by your own device and sent through your own apps — we never see or receive it.
"Play together" (optional): if the organiser chooses to get a live shareable code, the tournament data — player names, courts, scores, tournament name, and if entered, the organiser's own name and Instagram handle — is temporarily stored on our server so it can be shown to anyone entering that code, and updated live if the organiser allows others to add/remove players or add scores. A game can be set up and shared before it's even started, so people can add themselves to the player list ahead of time if the organiser allows it. This data isn't linked to any account, isn't used for anything beyond running that one shared game (and, if the organiser has filled it in, generating the optional social-media recap graphic described below), and is automatically deleted 48 hours after it was last updated. Anyone who guesses or is given the code can view it, and can manage players or add scores too if the organiser has switched that on — so treat the code a bit like a shared document link, and only share it with people you're happy to have see (and possibly edit) that game. Codes are 6 characters from a deliberately large set of possibilities (well over 800 million combinations), and code lookups are rate-limited to slow down anyone trying to guess one automatically — but treat it like any shared link regardless, since a determined, well-resourced attempt at guessing one can never be made completely impossible, only impractical. Separately, the organiser's own ability to manage the game is remembered by their own device and browser, not granted by the link itself — coming back on a different device, a different browser, or after clearing browser data only gets the same guest-level view as anyone else with the code, not organiser control.
Sharing a recap graphic (optional): after a game finishes, there's an option to generate a shareable image and caption text for social media, summarising aggregate numbers only — player count, games each, time played, total points — never any individual player's name or score. This image is drawn entirely in your own browser; it's never uploaded to or generated by our server. If the organiser has filled in their own name or Instagram handle (see above), that's drawn onto the image and included in the caption text as a "hosted by" credit — everything else on it is anonymous.
Group leaderboard (optional): separately, anyone can choose to save a finished tournament's final standings — player names, points, games played, and wins — to a leaderboard code, so the same social group can see a combined leaderboard across sessions played weeks or months apart. Only the most recent 10 tournaments saved to a code are ever kept — saving an 11th automatically deletes the oldest, so this is a rolling window rather than a full history. As with "Play together," there's no account: a 6-character code gives view-and-contribute access to anyone who has it, and a separate private code is needed to rename the leaderboard. This data isn't used for anything beyond showing that group's own leaderboard, and a leaderboard that hasn't had a tournament added to it in 12 months is automatically deleted entirely. Treat this code the same way — like a shared document link, and only share it with people you're happy to have see (and add results to) that leaderboard.
Organiser accounts (optional): organisers can sign in to keep their group leaderboards and up to two saved games in one place across devices. Players never need an account, and the organiser works without one. To sign in you either receive a one-time link by email (sent through Brevo), or choose “Continue with Google”, which loads a script from Google only when you press the button; in that case Google tells us your verified email address and name and nothing else. We store your email address (and name if Google provides it), the groups you have added to your account, and the games you save to it. There are no passwords. Sign-in links work once and expire after 15 minutes, and we keep only a scrambled (hashed) copy of them and of your session. Staying signed in uses one cookie, set only when you sign in, which is strictly necessary for that purpose, lasts 30 days and is not used for tracking. Saved games are deleted after 6 months without a change. You can delete your account at any time from the organiser area, either keeping your groups (they carry on working for anyone with their code, but are no longer linked to you) or deleting them too.
Emailing yourself your group link (optional): after saving to a group leaderboard, you can type your email address to be sent that group's link and code. The address is passed to our email provider (Brevo) only to send that one message, and is not stored on our own server or in any log. If you also tick the (unticked-by-default) box asking for updates, the address is added to our mailing list, with the free printable score sheet, and you can unsubscribe from any email; if you don't tick it, the address is not kept.
Match details (optional, off by default): when the person who created a group leaderboard saves a tournament to it, they can also tick a single box to record who played with and against whom, round by round, with each match's score, and to switch on player insights for the group (things like each player's form over time, who they play best with, and who they find toughest). The box is never ticked for you: nothing is recorded and no insights are shown unless they tick it, and only whoever created the group can do so — the 6-character code alone can't. This is stored against first names only (no email address, no account). Insights can also be switched off, or on, from the group's leaderboard page. Once on, the group's share link and QR code carry a private key, so one link opens both the leaderboard and everyone's insights; the 6-character code on its own still opens only the leaderboard. Anyone with the link can see every recorded player's insights, so the organiser should tell their group first. They can turn insights off, or replace the link to cut off old ones, at any time, and sharing a single player's insights from the page only sends a text summary. These details are kept for 12 months, independently of the 10-tournament window above, and are deleted along with the group if it goes unused for 12 months. The organiser should tell their players before ticking the box; if you play in a group and don't want to be included, ask whoever runs it to leave you out — it takes them one tap (when saving results, or later from the leaderboard page). Leaving someone out deletes the match details recorded for them straight away, stops any more being recorded, and removes their insights from the page; they still appear on the plain points table, which shows only a name and totals. You can also contact us and we'll remove the records for your name.
The Contact us form doesn't submit anywhere automatically — filling it in and hitting the button simply opens a pre-filled email in your own email app, addressed to nikki@padelsidequest.com. Nothing is collected by this site when you use it; the only record is whatever you choose to actually send from your own inbox, which is then handled like any other email.
The email signup on the homepage is a genuine mailing list, run through Brevo, a third-party email marketing platform. If you enter your email there, it's sent straight to Brevo and stored on their systems so we can send you occasional updates — this site itself never sees or stores it. You'll get a confirmation from Brevo, and every email includes an unsubscribe link that removes you immediately. It's only ever used to tell you about PadelSideQuest — nothing is sold or shared beyond what Brevo needs to run the list on our behalf.
Pages on this site link out to third parties — padel clubs, Playtomic, Instagram, TikTok, and similar. Once you click through, you're on their site and their privacy policy applies, not this one. We'd recommend having a quick look at theirs if you're ever unsure.
PadelSideQuest is intended for a general adult audience and doesn't knowingly collect personal data from children.
If how the site handles data ever changes in a meaningful way, this page will be updated and the date at the top will change. If you have any questions about any of this, just get in touch — see the Terms of Service for the rest of the small print.
Genuinely, ask away — nikki@padelsidequest.com 🩷