HoopTracks Privacy Policy

Privacy Policy

Written in plain language, and accurate about what the software actually does. Where something is imperfect, it says so.

Last updated 28 September 2026 · Version 1.0

HoopTracks is a basketball statistics and scouting application for high school coaches. Coaches track games, enter rosters, and compare their team against others in the league. This policy explains what the application holds about three different groups of people, who can see it, and what you can ask us to do about it.

Who is responsible for this data

HoopTracks is operated by CF Sports Tracking LLC, based in Oklahoma, USA. Questions, corrections, and requests to remove information all go to cfsportstracking@gmail.com.

There is one person reading that inbox. You will get a real answer, but not always a fast one during basketball season.

1 · The three groups of people in the database

Almost every privacy policy is written about its users. This one has to cover two groups of people who are not users, and that difference matters more than anything else on this page.

GroupRelationship to HoopTracksWhat is held
Coaches Account holders. They sign in and agree to the Terms. Email address, display name, role, plan, team, and sign-in activity.
Players
high school students, some of them minors
No account, no sign-in. A coach enters them. Name, jersey number, graduation year, position, availability, handedness, and the statistics recorded from games.
Officials
adult referees
No account, no sign-in. A coach enters them from the scorebook. Name, state registration number, and the foul calls recorded from games they worked.

2 · What we do not collect

These are not optional fields left blank. There is nowhere in the application to enter any of them:

The roster does include fields for height, wingspan and weight. As of this writing not a single player record uses them, and we are likely to remove the fields rather than keep collecting something nobody fills in.

3 · Where player information comes from

A coach types it in. HoopTracks has no relationship with players or their families, does not contact them, and has no way to reach them.

This means the decision about what is appropriate to enter about a student belongs to the coach and their school, not to us. Coaches agree in our Terms of Service that they are authorised by their school to enter this information and will follow their school's rules about student data. If your school has told a coach not to share a particular student's details, that instruction governs, and the coach is the person who knows about it.

Team results from public sources

Game results, schedules and team classifications also come from the publicly posted schedules and rankings at ossaarankings.com, back to the 2013-14 season, along with the coaches' poll rankings and playoff rounds printed there. That information is about teams: school names, dates, scores, classes and ranks. No player information comes from those pages.

We deliberately do not claim any particular legal status over this data. We are not asserting that we are a school official, or that we sit inside any school's own compliance arrangements. We are describing what the software does and leaving the judgment where it belongs.

Players under 13

HoopTracks is built for high school basketball and is not directed to children under 13. No player ever holds an account. We do not knowingly collect information from a child under 13, and we recognise that a freshman can be 13 or 14 — which is exactly why coaches are asked to confirm they have their school's authority before entering any roster.

If you are a parent or guardian and believe a child under 13 has information in HoopTracks that should not be there, email us and we will remove it. See section 9.

4 · What the public can see

No player name and no official name is ever published on the public site.

This is not a setting that could be switched off by accident. The code that builds a public page never loads names from the database in the first place, and an automated test fails the build if a name or an official's ID number ever appears in a public response.

When a coach turns on a fan link for a game, anyone with that link sees: team names, the score, the clock, jersey numbers, shot locations, and officiating crew positions labelled R, U1 and U2 with the number of fouls each called. Those crew labels are positions, not identities — no name and no registration number is attached to them.

Never public, under any circumstances: player names, official names, play types, defensive assignments, turnover types, ratings of any kind, minutes played, or possession counts.

There is no public profile page for any player. HoopTracks does not create a permanent, searchable record of a student that follows them after they finish playing.

Fan links

A fan link is a long random address — it cannot be guessed, and games are not listed anywhere unless a coach turns them on. But it is the link itself that grants access: anyone holding the link can view that game, including someone it was forwarded to. A coach who turns a link off and later turns it back on gets the same address again, on purpose, so a link already texted to parents keeps working.

5 · What other coaches can see

This is the part most worth understanding, because it is the product working as designed rather than an accident.

HoopTracks is a league-wide scouting tool. Any coach signed in to HoopTracks can look up any team in the league and see its roster — player names and jersey numbers — along with basic box score statistics. Deeper analysis (ratings, tendencies, advanced statistics) is restricted to a coach's own team, their own tracked games, or teams they have agreed to share with.

When a season ends and rolls over, that season's data is opened to every coach on the platform. This is a deliberate design decision and it is described the same way in the in-app FAQ.

What a coach sees about another school's players is the same class of information they could gather by attending the game: who played, what number they wore, and what they did on the floor. What HoopTracks adds is that it is collected, calculated and kept. Coaches agree in the Terms to use it for coaching and scouting only, and not to republish or redistribute another school's roster.

6 · Signing in with Google

Coaches sign in with a Google account. We request only the basic sign-in scopes — openid, profile and email.

HoopTracks' use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. You can disconnect HoopTracks at any time from your Google account permissions page, and you can ask us to delete the email address and display name we hold by emailing us.

7 · Logs, and the honest part about IP addresses

Three separate things get recorded. They are described separately because they behave differently.

Server request logs — these contain IP addresses

Our web server writes an ordinary request log, and that log records the IP address of each visitor, including visitors to public fan pages who never sign in. This is standard web server behaviour and we would rather state it plainly than let you assume otherwise.

These logs live on the server, are readable only by the system administrator, and are not published, sold or shared. They are not linked to a player, and for a fan page there is no account attached to them at all. We are working to reduce how much of this is retained.

Usage analytics

We record which pages coaches open inside the application, to decide what to build next. These records are kept for 90 days and then deleted automatically.

Change history

When a coach adds, edits or deletes data, the application records what changed, when, and which coach did it. This is what makes it possible to answer "who changed this score?" — it is a bookkeeping record, not a behavioural profile. Entries are kept for 12 months and then deleted automatically.

Fan page view counts

We count how many people viewed a game's fan page each day. The count is a number and nothing else — no viewer identifier of any kind is stored in the database.

8 · No trackers, no cookies, no third-party content

The public fan pages set no cookies and use no storage at all. There is no Google Analytics, no advertising pixel, no social media button, no content delivery network, and no external web font. Every file the page loads comes from HoopTracks' own server.

The public scores page can remember which teams you chose to follow. That list is stored in your own browser, on your own device, and is never sent to us.

We do not sell personal information, we do not share it for advertising, and we run no advertising of any kind.

9 · Retention, and what deletion really means

We would rather explain this accurately than promise something the software does not do.

A player's statistics are part of a game, and a game involves two teams. If we simply erased a player row, the box scores of every game they appeared in — including the opposing team's — would stop adding up. So the application does not do that.

If you ask us to remove a player:

Being honest about the limit: a jersey number plus a team plus a graduation year is not perfectly anonymous, because rosters are published elsewhere. Removing the name removes it from HoopTracks. It does not remove it from everywhere.

Officials are handled the same way — the name can be replaced with a placeholder while the game record stands.

Backups. The database is backed up automatically, and backups are kept for 90 days. A record you ask us to remove today may still exist in an encrypted backup for up to 90 days afterwards. Backups are never browsed; they exist to restore the system after a failure.

Coach accounts. Ask and we will delete your account and the email address and display name attached to it. Games your team played remain, for the same reason above.

10 · Where the data lives

HoopTracks runs on a small number of services. None of them are advertising companies, and no data is sold to any of them or by any of them.

ProviderWhat it does
DigitalOceanHosts the server and the database (United States)
Cloudflare R2Stores encrypted database backups, 90-day retention
Cloudflare DNSDomain name resolution only
GoogleCoach sign-in; also hosts the source document behind the in-app FAQ
Let's EncryptIssues the site's security certificate

11 · Security

Data is transmitted over HTTPS. The server is firewalled, administrative access requires a cryptographic key rather than a password, and database backups are encrypted in transit and at rest.

HoopTracks is built and maintained by one person. No system is perfectly secure, and we will not pretend otherwise. If something happens that affects your information, we will tell you what happened and what we are doing about it.

If you believe you have found a security problem, please email us before disclosing it publicly.

12 · Your choices

Email cfsportstracking@gmail.com to:

You do not need to give a reason, and we will not ask for one. A request about a student is best sent by a parent, guardian, or someone at the school; we may ask how you are connected to the player before removing information, purely so that one person cannot remove another person's data.

Depending on where you live you may have additional rights under state law. We will honour them.

13 · Changes

If this policy changes in a way that matters, we will update the date at the top and tell coaches inside the application. We will not quietly broaden what we do with information already collected.

14 · Contact

HoopTracks · CF Sports Tracking LLC · Oklahoma, USA
cfsportstracking@gmail.com