This page lists the cookies and similar technologies PlayTFL™ ("TFL") actually uses, what each one does, and how you can control them. It supplements our Privacy Policy, which explains how we handle personal information more broadly.
What is a cookie?
A cookie is a small text file a website saves on your device. We also use related browser technologies such as localStorage (browser storage that survives reloads) and the Push API. For brevity, this page covers all of them.
Scope of this policy
This policy covers the TFL website. The TFL mobile app does not use cookies for its own sign-in — it keeps your session in the device's secure storage and uses on-device storage for the same offline score queue and preference data described below. The app does, however, open some screens (help and legal pages, and the sign-up security check) in an in-app browser view, and those screens are the website and set the website's cookies described here.
Cookies we set
All cookies below are first-party (set by TFL itself):
| Cookie | Purpose | Lifetime | Category |
|---|---|---|---|
userid, apitoken | Keep you signed in. | Browser session, or 1 year if you choose "remember me" | Strictly necessary |
tfl_active_player, tfl_active_context | Remember which player (or team) you are "acting as" on player-specific pages. | 1 year | Functional |
tfl_loc | Remember the ZIP code or coordinates (rounded to four decimal places, roughly 10 metres) you last used to browse nearby courts, coaches, and tournaments, so those pages open where you left off. It is stored on your device and sent back to us with later requests; see the Privacy Policy for how location works. | 180 days | Functional |
tfl_sport | Remember which game (tennis, pickleball, …) you chose in the "Choose game" menu, so every page opens for that sport. | 1 year | Functional |
The strictly-necessary cookies are required for the site to work — the site cannot keep you signed in without them. The functional cookies are written when you use the corresponding feature (choosing a location, switching players); they store only your own choice and are never shared with third parties.
Browser storage we use
tfl.cookie-consent.v2— records the choice you made in the cookie banner so we don't keep asking.tfl.offlineScoreQueue.v1— holds tournament scores you saved while offline until they can be submitted. Required for the offline scoring feature to work.- Device preferences— your light/dark theme choice and "dismissed" flags for one-time prompts and banners (e.g., the app-install prompt), so we don't show them again.
Third-party services
- Stripe— our payment processor. Stripe's script loads on payment pages (e.g., when adding a card) and sets Stripe's own cookies for fraud prevention and security. See Stripe's cookie policy for details.
- YouTube— coach demo videos are embedded via YouTube's privacy-enhanced
youtube-nocookie.complayer, which does not set tracking cookies unless you play the video. - Vimeo— some coach and club videos use the Vimeo player, which may set Vimeo's own cookies when the player loads. See Vimeo's cookie policy for details.
- Meta Pixel— only loads if you choose "Accept all" below. It sets Meta's
_fbpcookie and sends the pages you view to Meta so we can measure and improve the ads PlayTFL runs on Meta's platforms (Facebook/Instagram). If our systems detect you in a state that requires it (California today), we automatically apply Meta's Limited Data Use setting, which restricts Meta to processing that data only to provide us this measurement service rather than its own advertising purposes. See Meta's cookie policy for details. - Plausible Analytics — a privacy-focused analytics service we use to see aggregate site traffic (which pages get visited, roughly how many visitors, which site referred them). It is cookieless and stores nothing that identifies you individually, so it always runs, regardless of your choice below.
What we don't use
We do not sell your personal information, and beyond what is listed above we do not embed any third-party analytics SDKs or advertising trackers. Plausible never sets a cookie or collects anything that identifies you personally. The Meta Pixel only loads if you accept the optional category below, and it only tells Meta that a visit or a specific page happened — never your name, email, or any other TFL account content.
Your choices
- The cookie bannerappears on your first visit and records your choice on your device. Choosing "Essentials only" keeps the Meta Pixel off entirely; choosing "Accept all" turns it on, along with the functional cookies listed above. Plausible always runs either way, since it is cookieless and does not collect anything that identifies you.
- Browser controls— you can block or delete cookies and site data in your browser's privacy settings at any time. Clearing this site's data also resets your banner choice, so it will be asked again on your next visit. Note that deleting the strictly-necessary cookies signs you out.
- Functional cookies are written only when you use the corresponding feature — if you never choose a location,
tfl_locis never set.
Changes
If we add or change cookies, we will update the inventory on this page and the "Last updated" date above. Material changes are consented before taking effect — this page previously said we ran no analytics or marketing cookies, and the addition of the Meta Pixel above is exactly the kind of change we mean: everyone with an existing banner choice was asked again, fresh, before the pixel ever loaded for them.
Contact
Questions: contact us or email [email protected].