This page lists the cookies and similar technologies Tennis For Life ("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; 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.
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 approximate coordinates (rounded to about city-block precision) you last used to browse nearby courts, coaches, and tournaments. Stays on your device; see the Privacy Policy for how location works. | 180 days | 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.v1— 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.
What we don't use
We do not set analytics cookies, advertising or marketing cookies, or any third-party tracking pixels, and we do not embed third-party analytics SDKs. If that ever changes, we will update this page and ask for your consent first.
Your choices
- The cookie banner appears on your first visit and records your choice on your device. Because we run no analytics or marketing cookies, the practical difference today is between the strictly-necessary and functional cookies listed above.
- 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 (such as introducing analytics) would be announced and consented before taking effect.
Contact
Questions: contact us or email [email protected].