Loading TFScore
How we handle your account, public results, private coaching information, and activity on TFScore.
TFScore uses Vercel Web Analytics and Speed Insights to understand traffic and real-world performance. Optional PostHog product analytics is enabled only when the site is configured with its public analytics keys.
Analytics measures page types, feature use, section reach, active time, and performance. TFScore removes URL query strings and fragments from analytics page addresses and excludes raw search text from its product events. Session replay and automatic interaction capture are disabled. Optional PostHog analytics does not persist identifiers in browser cookies or local storage.
These measurements help identify slow pages, ignored controls, navigation friction, and which profile sections are useful. They are not used to alter athlete ratings or ranking logic.
Athlete pages display names, team affiliations, recorded competition results, and derived ratings. Profiles can exist without an account or endorsement by that athlete. An “Athlete verified” badge means TFScore has reviewed and approved a profile claim; it does not certify every performance record.
Optional accounts use Google Firebase Authentication for email/password or Google sign-in. Firebase processes login credentials and maintains necessary sign-in state in your browser. TFScore does not store passwords.
We store the account identifier, verified email, display name, and your news and updates preference in our database. Email addresses and individual voting histories are not displayed publicly.
News and updates are enabled for new accounts and can be turned off in Settings. Existing saved preferences are preserved. Account and verification messages are separate.
New 1v1 votes require an account with a verified email. We store your selected athlete, matchup, time, Elo change, and a keyed account identifier for vote integrity. Accounts receive ten votes per gender per UTC day.
Earlier anonymous pilot votes and pseudonymous browser identifiers remain in the totals; a necessary signed browser cookie can still be used for guest matchups. A keyed hash of the network address, changed each UTC day, helps enforce shared-network voting limits; raw network addresses are not stored in voting tables. Agreement percentages count accepted votes, not verified unique people.
For athlete claims, we store the school email, selected athlete and school, mailbox-verification time, claim status, and review evidence. Resend delivers school-email verification codes. Codes expire after twenty minutes, permit at most five attempts, and are stored only as keyed hashes.
Hashed email and network identifiers enforce sending limits. If your signed-in email already matches your school email, no extra code is needed. If delivery fails, you can email support from your school address for a manual check. We record the confirmation method and review evidence. School mailbox access and a name match are supporting evidence; ownership is reviewed separately.
Claims and review records remain while needed to administer ownership and resolve disputes. You may cancel a claim in your account or contact us for account and data-removal requests.
Fan Rating is an experimental community preference rating, separate from performance-based TFScore. The initial pilot stores at most 5,000 accepted votes. For questions, removal requests, or concerns about an athlete appearing in voting, contact the address below.
Search terms are sent to TFScore to return matching results. Hosting and analytics providers may process technical request information to deliver and measure the service; removing search terms from product events does not remove them from every infrastructure log.
For accounts with coaching access, TFScore stores watchlists, selected athletes, notes, recorded availability information, and saved scenarios, including projected rosters, coach-entered marks, and the public-result snapshots used in those comparisons. Workspace access is checked on the server and restricted to authorized workspace members. This content is not published on athlete profiles, used to calculate public ratings, or included in product analytics. TFScore and its service providers process this information to operate, secure, support, and back up the service.
Only add information you are authorized to use. Avoid medical records, financial information, or other sensitive student information in notes. You can remove saved items in the workspace and contact us about account or workspace data removal.
New paid coaching access is arranged directly with TFScore after an email or form request. We store account access, plan, subscription status where applicable, billing identifiers, and access dates. Existing online subscriptions, if any, are handled by Stripe; TFScore does not store full card numbers or card security codes. Payment providers process the payment and billing information you supply under their own privacy policies. A coaching inquiry does not start a subscription or authorize a charge.
When you submit the coaching contact form, we store your name, email, program or organization, optional phone number, preferred plan, and any additional details so we can respond to your request. Resend delivers the inquiry to our support inbox. We also store a keyed network identifier and delivery status to limit spam and avoid duplicate messages. Contact details are not displayed publicly or included in product analytics. An inquiry does not subscribe you to marketing messages. Contact us to request removal of your inquiry.
TFScore uses Vercel for hosting, Neon for database storage, Firebase for authentication, and Resend for email. Public history archives and encrypted database backups support availability and recovery. Information is kept while needed to provide the service, handle support requests, prevent misuse, and meet applicable recordkeeping requirements. Removed data may remain in backups until those backups expire. Public competition records are maintained separately from account and coaching workspace information.
For corrections or questions about information shown on TFScore, email help@tfscore.com. Information you include in an email is used to review and respond to your request.