Privacy Policy

PlayTFL™ ("TFL") is a service of HonestTech Services LLC, a Delaware limited liability company with a registered address at 8 The Green, Suite B, Dover, DE 19901, United States ("HonestTech", "we", "us").

This Privacy Policy describes how we collect, use, share, and protect information about you when you use our website, mobile app, and related services (the "Service"). TFL is operated from and intended for users in the United States.

1. Information we collect

1.1 Information you give us

• Account info — name, username, email address, mobile phone number, home ZIP code and state, and password (stored only as a salted hash, never in plain text). Your email and phone are each verified with a one-time PIN before your account is active.
• Player profiles — for each player you manage: name, date of birth, gender (optional), home court, profile photo if you upload one, and the tennis zones the player joins. TFL computes its own per-zone rating and class level for each player from reported match results; we do not collect external ratings from players.
• Contact book — additional email addresses and phone numbers you add for notification routing. Each is PIN-verified before we will send anything to it.
• Pro details — for Pros: business name, credentials and certification details you choose to list (e.g., a coaching certification or NTRP-related credential), lesson listings, and demo video links.
• Payment method — card details are entered directly with Stripe, our payment processor; the full card number never touches our servers. We store a Stripe payment-method reference plus card brand, last four digits, expiration, and a Stripe card fingerprint (a token we use to detect duplicate cards and free-trial abuse).
• Communications & content — messages you send through the platform, support tickets, community posts and replies, reviews, reported match scores, and incident reports.
• Consents — your email/SMS/push preferences per category (critical, activity, marketing), with a change history.
• Shipping address — only if you claim a physical reward (e.g., a trophy or t-shirt program), to fulfill the shipment.
• Referral invites — if you use refer-a-friend, the email address or phone number of the person you invite. We use it only to send the invitation; you must have their permission to share it.

1.2 Information from visitors without an account

• Contact form — if you use our public contact form, we collect your name, email address, optional phone number, and your message, stored as a support ticket so we can reply.
• Guest lesson inquiries — if you send an inquiry to a coach from a public lesson listing without an account, we collect your name, email, optional phone, and message, and forward them to that coach so they can respond to you.
• Referral invitations — if a member invites you, we hold your email address or phone number to deliver the invitation.

1.3 Location information

Location on TFL is on-demand only— nothing is read until you tap "Use my location", and we never track you in the background. When you do, we take a single fix, round it to four decimal places (roughly 10 metres), and send it as a search parameter so we can rank results by distance. Because those coordinates travel in the request URL, they can appear in routine server and content-delivery access logs, which we keep only as long as we need them for security and troubleshooting and then delete. We do not save them to your profile, attach them to your account, or build a location history from them. Your last choice is remembered on your own device — in the tfl_loc cookie on the web, in app storage on mobile — and is sent back to us on later visits so discovery pages open where you left off (see our Cookie Policy). If you enter a ZIP code instead, we use only the ZIP. On public discovery pages we may use the approximate region suggested from your IP address, again only transiently, to show nearby results.

1.4 Information we collect automatically

• Security & log data — IP address and basic request data for sign-ins, failed sign-in attempts, and consent changes (which record IP address and browser user-agent for the audit trail). We keep a login history for your account.
• Cookies & device storage — a small set of first-party cookies and browser-storage keys; see our Cookie Policy for the complete list. We run no advertising tracker by default; it turns on only if you accept the optional category in our cookie banner. We also run a cookieless analytics tool that collects nothing that identifies you and is not gated by that choice — see the Cookie Policy for exactly what each one does.
• Push subscriptions— if you enable web push, the subscription endpoint and keys provided by your browser's push gateway (FCM / Apple / Mozilla).
• Error reports — front-end exceptions and stack traces, with the requested URL and your user identifier, sent to our internal error log.
• Notification log — a record of the notifications we sent you, with read state, powering your in-app inbox.

1.5 Information from third parties

• Payments — Stripe shares the payment-method metadata described in Section 1.1 and the status of charges, refunds, and payouts.
• Email/SMS delivery — SendGrid and Twilio share delivery and bounce events tied to your account so we can troubleshoot notifications.

We do not use federated sign-in (e.g., "Sign in with Google"), and no third-party login provider shares data with us.

2. How we use your information

• Match you with opponents, coaches, partners, and tournaments in your zones
• Send transactional notifications (match scheduled, score reported, lesson booking confirmed) via email, SMS, or push per your consent settings
• Compute TFL ratings, rankings, class levels, and statistics from match results
• Bill subscriptions, process entry fees and lesson payments, and resolve payment disputes and refund requests
• Detect abuse, fraud, free-trial misuse, brute-force sign-in attempts, and policy violations
• Respond to support requests, reports, and incident reports
• Investigate and reproduce problems you report — which can include a member of our support team viewing your account as you see it, under the safeguards in Section 6.1
• Comply with legal obligations and respond to lawful requests
• Produce aggregate, de-identified statistics about the Service

2.1 SMS & text messages

If you provide a mobile phone number, we may send you text messages via Twilio, depending on which category applies:

• Account & security (always sent)— login verification codes, password-reset codes, and security alerts. These are sent regardless of your notification preferences; they're how we verify it's really you.
• Account activity (opt-in, off by default) — match reminders, booking confirmations, and similar updates about your own account.
• Promotional messages (opt-in, off by default) — occasional updates about the Service. We only send these to numbers that have agreed to receive them.

Message frequency varies by your account activity and preferences — most users receive occasional security or activity texts, not a recurring schedule. Message and data rates may apply. Reply STOP to any text to stop that category, reply HELP for help, or manage every channel at once from your notification preferences.

We do not sell or share your mobile phone number with third parties for their own marketing purposes. It's used only to deliver the messages described above through our SMS provider, Twilio (see Section 3).

3. How we share information

• With other TFL members — your player profile fields shown in the product (name, photo, age group, zone presence, rating/class), published match results, posts, and reviews you write.
• With service providers — including Stripe (payments), SendGrid (email), Twilio (SMS), browser push gateways (FCM/Apple/Mozilla), LocationIQ and IPinfo (address and ZIP lookup, approximate region from IP), Cloudflare (network, security, and email routing), and our cloud hosting and database infrastructure. Each processes data only to provide its service to us. This list names the providers that handle personal information in the ordinary course; it is not exhaustive, and we may add or change providers as the Service evolves.
• With Pros you contact or book — when you book a lesson, enroll in a class, join a club, or send a lesson inquiry (with or without an account), your name, contact info, and the details of your request are shared with that Pro so they can deliver the service.
• In aggregate / de-identified form— anonymous statistics that can't reasonably be tied to you.
• In response to legal process — court orders, subpoenas, or to protect rights, safety, or property.
• In a corporate transaction — merger, acquisition, or sale of assets, subject to standard confidentiality protections.
• With advertising partners, only if you opt in— if you accept the optional category in our cookie banner, Meta's advertising pixel receives the pages you view and a browser identifier, which we use to 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, restricting Meta to processing that data only to provide us this measurement service rather than its own advertising purposes. Rejecting the optional category keeps this off entirely; see our Cookie Policy for details. We separately use Plausible, a cookieless analytics service that never receives anything that identifies you, so it is not gated by your cookie choice and is not shared with anyone.

We do not sell your personal information. We share information with the advertising partner described above only if you accept the optional category in our cookie banner; otherwise, we do not share personal information with third-party advertisers for cross-context behavioral advertising.

4. Your rights & controls

4.1 All users

• Access & correction — edit your account and player details from your account and player pages.
• Export— download a machine-readable copy of your data (profile, players, zones, billing, posts, login history, match history) from Account → Security → "Export my data".
• Deletion— request account deletion from Account → Security, or, if you can't sign in, see our account deletion pagefor how to request it without the app. Deletion runs on a 30-day grace period during which you can change your mind; after that, your personal information is permanently removed or irreversibly de-identified. Match results remain in anonymized form to preserve the integrity of other players' ratings and rankings (see Section 5).
• Communication preferences — control activity and marketing email/SMS per category from your notification settings; for device-level choices see our Cookie Policy.

4.2 California (CCPA/CPRA)

California residents have the right to:

• Know what personal information we collect, use, share, and sell (we do not sell)
• Delete personal information we hold about you
• Correct inaccurate personal information
• Limit the use of sensitive personal information
• Opt out of sharing for cross-context behavioral advertising — reject (or change) the optional category in the cookie banner shown on your first visit (see our Cookie Policy); we also restrict this sharing automatically for California traffic via Meta's Limited Data Use setting
• Not be discriminated against for exercising these rights

To exercise these rights, email [email protected]or use the controls in Account → Security. You may designate an authorized agent to make a request on your behalf. We will verify your identity before acting on a request.

Shine the Light (CA Civ. Code § 1798.83). California residents may request a list of categories of personal information we shared with third parties for direct-marketing purposes in the prior calendar year. We do not share for third-party direct marketing.

4.3 Other US state privacy laws

Residents of Colorado, Connecticut, Virginia, Utah, Texas, Oregon, and other states with comprehensive privacy laws have rights similar to those listed above, including access, deletion, correction, and opt-out of targeted advertising and sale. To exercise these rights, email [email protected].

5. Data retention

We retain account data for as long as your account is active and for a period afterward for legal, tax, and dispute-resolution purposes. Specifically:

• Account & profile: permanently removed or irreversibly de-identified 30 days after a deletion request (the grace period during which you can cancel the request).
• Billing records: retained 7 years for tax and accounting compliance.
• Match results & rankings: retained for as long as the player profile exists — they are the substance of the Service. After account deletion or profile removal they persist only in anonymized form, which is no longer personal information, to preserve ranking integrity for the other players in a result.
• Community posts: deleted on request; quoted excerpts in replies may persist.
• Support tickets, security logs & error logs: retained as long as reasonably needed for support, security, and abuse prevention, then deleted or de-identified.

6. Security

We use industry-standard safeguards, including TLS encryption in transit, salted and iterated password hashing (PBKDF2), one-time-PIN verification of email addresses and phone numbers, automatic temporary IP blocking after repeated failed sign-in or PIN attempts, rate limiting on sensitive endpoints, and internal access controls. Card payments are handled by Stripe; full card numbers never reach our systems. No system is perfectly secure; please choose a strong, unique password.

6.1 Support access to your account

When you report a problem we can't reproduce from a description, an authorized member of our support team may open a short, time-limited session that shows them the Service as your account sees it. Often that is the only way to find the cause of a problem on a screen only you can reach.

These sessions are read-only by default — our staff can look, but cannot change your settings, post or message as you, book or cancel anything, or make a payment. If fixing your issue requires a change, the staff member has to separately turn on the ability to act and record why first. Every session requires a stated reason, expires automatically after a short period, and is recorded against the staff member who opened it, so any change made during one can be traced back to them. Staff cannot open a session against another staff account. We never see your password (we do not store one in readable form) or your full card number (only Stripe holds it).

You may ask us whether support sessions have been opened on your account, and why, by writing to [email protected].

7. Children (COPPA)

TFL accounts are for adults (18+). Players under 18 ("Juniors") may only be registered as player profiles by a parent or legal guardian, who manages the Junior's information and consents to our processing of it. Juniors have no accounts, logins, or private messaging on TFL — all communication goes through the managing adult's account. We follow the US Children's Online Privacy Protection Act (COPPA) for Juniors under 13. Parents may review, delete, or refuse further collection of their child's information from their own account or by contacting [email protected].

8. Do Not Track

Our Service does not respond to Do Not Track ("DNT") browser signals, because there is no industry-standard interpretation of the signal. We do run one cross-site tracker — Meta's advertising pixel, which loads only if you accept the optional category in our cookie banner — and one cookieless analytics tool that sets no cross-site identifier; see our Cookie Policy for exactly what we set on your device and when.

9. Changes to this Policy

We may update this Privacy Policy from time to time. Material changes will be communicated by email or an in-app notice at least 14 days before they take effect, and the "Last updated" date above will change.

10. Contact

Privacy questions or requests: [email protected].