Privacy Policy

Tessaira Golf (“Tessaira,” “we,” “us”), the service previously published as GolfNexus, operates tessaira.com, a directory of competitive golf tournaments, tours, rankings, and college golf programs in the United States, together with a free assessment (the “honest read” and “My Player”) and a free library of practice drills for junior golfers and their families (the “Service”). This policy explains what information we collect when you use the Service, why we collect it, and the choices you have. Questions or requests about this policy can be sent to angelo@tessaira.com.

What we ask. One question, with four answers: a parent or guardian, an adult player, a player under 18, or someone outside the United States. We do not ask for your date of birth or your age. We ask whether you are 18 or older and we take your answer for it.

This is not verification, and it is not parental consent. It is what you told us. We do not check it against anything, and nothing on this site should be read as saying we did. It is also not verifiable parental consent under the Children's Online Privacy Protection Act — that is a different, formal process that Tessaira does not currently operate. What the question does is narrower and real: we decline to collect anything until an adult has said they are the one setting Tessaira up.

If you tell us you are under 18, or that you are outside the United States, we do not create an account for you, we do not accept your email address, and we do not give you an analytics identifier. We write no record about you, and we set no cookie — not even one that just remembers your answer. That means the question comes back on your next visit, which is a small annoyance we have chosen on purpose: a year-long cookie placed on your device at the moment you told us you were under 18 is exactly the kind of thing this page should not have to explain away. (We never look up anyone's location — see Location.) You can keep reading the guides and drills — they are free and they do not need an account. A parent or guardian can answer the question on their own device.

If you change your answer — you told us you were an adult before, and now you are telling us you are not — we withdraw the earlier answer on our servers, not just in your browser. That distinction matters: a cookie is a copy, and clearing one copy would leave the permission itself intact for any other copy to present. The withdrawal is the one and only thing we write when somebody answers that they are under 18 or outside the United States.

If you have not answered yet, we treat that exactly like an answer we cannot accept. Nothing is collected. That is deliberate: an unanswered question is not permission.

What we keep from an answer we can accept. Two things, in two places. On our servers we record the exact wording you were shown, which option you chose, the version of that wording, when you answered, when the answer stops applying, the purpose it covers, and whether it has since been withdrawn. In your browser we set a cookie that points at that record: it holds the wording version, a random reference number that means nothing on its own, an expiry date, and a signature that lets us detect any change to it. The cookie says nothing about you — not your answer, not your role, not the time — so anyone reading your cookie jar learns nothing from it.

Why it is arranged that way. The reference number is what lets us withdraw an answer. Because the permission lives in our record rather than in your cookie, we can mark it withdrawn and it stops working immediately, everywhere, without needing anything to change on your device. It also means an altered or copied cookie does not work: if it does not match our record, we treat you as not having answered. Both last twelve months.

Most of the Service is readable without giving us anything. When you do interact with it, here is everything we collect:

• Account information. If you create a free account, we collect your email address and a display name, and, if your sign-in method provides one, a profile image URL. These are handled by our authentication provider (Neon Auth) and also stored in our own database so we can recognize your account and provide the account features described below. Your password is created and stored only by Neon Auth, in hashed form; we never see or store it in plain text. Accounts let you save reads, schools, and drills. Premium unlocks coach email addresses and the other features listed on the Premium page.
• My Player profile. The dashboard keeps one profile row per account, and it is stored on our servers until you change or delete it. It holds the graduation year and boys or girls golf you select, and three optional fields: a U.S. state (two letters, chosen from a list — see Location for what that is and is not), a grade-point band such as “3.5 to 3.7”, and a player name of up to 80 characters, which is used to fill in the coach-email templates. Nothing checks what you type into the name field, so whatever you put there is stored exactly as you wrote it. This row is what the dashboard, the plan, and the recruiting tools read; it is a record about a minor in most cases, and it is disclosed here rather than folded into “account information”.
• Coach outreach log. On Premium, when you mark a coach email as sent from the outreach composer we store which school and which coach it was addressed to, which template you used, the channel, the current state of that outreach, when it was sent and last updated, and an optional free-text note you keep about that specific attempt. We do not store the message body, and preparing an email writes nothing.
• Assessment (“honest read”) information. If you use the assessment, we process the details you enter about a junior golfer, the player's age, gender, typical scoring range, the level of events they play, any ranking, and a few optional inputs (events per year, recent trend, academics, goals), to calculate the read. The assessment does not ask for the player's name, email, address, photo, or school. This calculation happens in your browser. An unsaved read stays on your own device in your browser's local storage. If you are signed in and save the read to My Player, we store a copy on our servers against your account. See Children's privacy and the honest read below.
• Round and practice log (the “My Player” tracker). Logging is free and needs only a signed-in account. Everything you log is stored on our servers, tied to your account, and it is usually a parent's record of a minor. For each round we store the date you played, how many holes, the score, the course par, and whether it was a tournament round. If you fill them in, we also store an event or course name, the per-round statistics the form offers (fairways hit, greens in regulation, putts, up-and-downs, penalties, three-putts), and a free-text note of up to 500 characters. Nothing checks what you type into that note or that event name, so whatever you put there is stored on our servers exactly as you wrote it. We separately store your practice sessions (the date, which drills you did, and how many minutes if you enter it) and which skill milestones you have marked as cleared, with the date. See Children's privacy and the honest read below.
• Email signups (newsletter, roadmap, quiz). If you sign up for the newsletter, download the roadmap, or complete the quiz, we store your email address and, if you pick one, a U.S. state preference. That signup can also include a small amount of context so the first email we send is relevant rather than generic: the recruiting stage you have been reading about, how many guides you have read, your quiz answers (age band, play level, and the question you picked as biggest), the page or campaign you signed up from, and your first-touch referrer or UTM tag. It does not include a location: we do not work one out. We also keep the state of your email sequence: which stage you were put on, which step you have reached, when the next message is due, whether you are still subscribed, and a log of which emails were sent to your address and when. See Email program below for how these emails work and how to stop them.
• Saved drills. The drill library is free. If you save a drill, we store which drill you saved and when, tied to your account, so your saved list is there on your next visit. That record is the only thing we store about your use of the drill library. We do not record which drills you read, open, or watch.
• Saved-school recruiting records. On Premium, each saved school can also carry the questionnaire state and completion time you record, the last contact time, a follow-up date you choose, the relationship state, camp interest, camp date, a verified official camp link, and your private contact note. Preparing an email does not create an outreach record. We record a sent-email time only after you explicitly mark the message as sent.
• Planned tournaments. The verified tournament finder is free. If you save an event, we store which tournament you saved and when, tied to your account, so it remains in your My Player schedule. We keep that row if the organizer later withdraws the event from the verified finder, and label its current status rather than silently erasing your planning history.
• Recruiting plan checklist. The checklist itself is generated from your profile and is never stored. What we store is the overlay you put on top of it: which items you have ticked off or dismissed, and, when you check off an event that has already happened, whether your golfer played it and the score you entered.
• Saved Recruiting Readiness Scorecard. If you press “Save this recruiting plan” on the scorecard, we store the answers you gave: graduation year, boys or girls golf, scoring band, level of events, ranking status, academic band, the division and geography you are targeting, the state you are searching from if you narrowed it, and your answers about your school list, coach contact, player profile and swing video. One saved scorecard per account; taking it again replaces it rather than adding another. We do not store the result itself — the readiness band, the gap it named, or the next move. Those are recalculated from your answers each time you open the plan, so what you see always reflects our current scoring rather than a verdict frozen on the day you took it.
• Parent-controlled public recruiting profile. If you choose to create one, we store a random public slug, whether the player is under 13, your adult/guardian attestation and consent time, the display name and visibility switches you selected, any parent contact email or allowlisted media link you explicitly chose to publish, and which organizer-verified saved tournaments you selected for the public schedule. Publishing is off by default. School interests, questionnaires, coach notes, outreach history, development notes, and raw score inputs are never included. For an under-13 profile, the server and database suppress full name, state, public rankings, and public media even if a browser attempts to send them.
• Ranking snapshots. If you record one in My Player, we store the ranking system, rank, scope, official source URL, date shown by that source, and when you recorded it. A parent-entered snapshot stays labeled as parent reported and not independently verified. We do not infer a rank when one is missing or combine systems into a Tessaira national ranking.
• College coach account applications. If you apply for a coach account, we store your institutional (work) email address, the program you say you coach for, the state of the application (pending, verified, or rejected), when you applied, any evidence link recorded during review, when it was reviewed and by whom, and whether you have turned the coach digest on and when one was last sent to you. We also keep a small audit trail of the actions taken on that application — what happened, when, and the institutional email address that acted. A personal address is rejected: the point of the field is that it belongs to the institution.
• Private coach prospect lists. A verified coach can save a published player profile to a private shortlist. For each saved profile we store which profile it is, the relationship stage the coach selected, an optional private note of up to 2,000 characters, and when the entry was created and last changed. The note is free text about a junior golfer written by somebody other than that golfer's family, so we describe it exactly: nothing checks what is typed there, it is stored as written, it is visible only to the coach account that wrote it, and it is never shown to the player, to their family, or to any other coach. A coach can export that shortlist as a spreadsheet, which contains the same private notes and relationship stages alongside the fields the player's parent chose to publish — display name, graduation year, boys or girls golf, state, scoring summary, ranking evidence and the public profile address. Publishing a profile is what makes it visible to coaches at all; see Your rights and choices for how to unpublish.
• Demonstration videos. Some drills include a video hosted on YouTube. Nothing is sent to Google unless you click to load one. See Demonstration videos below.
• Premium payment. If you subscribe to Premium, our payment processor, Polar, handles your card details. We never see or store your full card number. What we keep is the subscription status, the amount charged, the date the current period ends, and the customer and subscription identifiers Polar gives us, so we can unlock your account and keep it accurate.
• Analytics. See Analytics below.
• Location — we do not work one out. We resolve no location from your IP address and infer none from any substitute signal. Separately from that, a few fields let you tell us a U.S. state yourself, and those we do store. See Location below, which sets out exactly which fields those are and what the difference is.
• On-device personalization. See Cookies and local storage below.
• Logs and security data. Like nearly every website, our servers record request logs that include IP addresses and basic request metadata. We use these for rate limiting, abuse prevention, and keeping the Service running.

We do not sell your personal information, run advertising, or use advertising identifiers. We also do not derive your location: we collect neither precise (GPS-level) location nor an approximate estimate worked out from your IP address, and we do not infer one from any other signal. That is a claim about what we work out, not a claim that no place name is ever stored — the U.S. state fields listed above are ones you fill in yourself, and those we keep. See Location, which draws the line precisely.

• To operate the Service and keep you signed in.
• To calculate your assessment read from the details you enter, in your browser.
• To gate coach contact details behind Premium, which limits bulk harvesting of those addresses.
• To keep the schools, drills, and tournaments you saved available on your account.
• To keep the rounds, practice sessions, and milestones you log available on your account, and to calculate what the tracker shows you from them: the scoring average, the trend, the streak, the weakest statistic, and what to practice next. Those figures are recalculated from your log every time the page loads and are not stored separately.
• To send you the stage-appropriate emails described under Email program: the recruiting-stage content and deadlines relevant to you, and nothing else. Every message includes an unsubscribe link. We never send marketing on behalf of anyone else.
• To process your Premium payment through Polar and keep your subscription status accurate.
• To understand traffic and how well pages and the funnel work, using the first-party analytics described below, so we can fix what is not working.
• To make email more relevant, using the U.S. state you pick for the weekly digest — a preference you choose, not a location we work out. See Location.
• To protect the Service: rate limiting, abuse detection, and security investigation.
• To respond when you contact us.

We do not sell your personal information, share it for advertising, or use it to build advertising profiles.

If you sign up for the newsletter, the roadmap, or a quiz result, you may receive a short sequence of emails matched to the recruiting stage you signed up from (for example, getting started, evaluating level, or recruiting) rather than one generic blast. Emails are sent through Resend, our email delivery provider (see Service providers).

• Unsubscribe. Every email we send you includes a working one-click unsubscribe link, and the header your mail app uses for its own unsubscribe button. Using either stops all future emails; we keep no separate marketing list you have to hunt down.
• Stage switcher. Every email we send you includes a link to the recruiting-journey page, where you can pick the stage that fits your golfer if the one we picked is not the right fit.
• Reply-to. You can reply directly to any email and it reaches the owner, not a no-reply inbox.

We only send what you signed up for. We do not send marketing on behalf of anyone else, and we do not sell or share your email address.

Cookies we set. Tessaira sets only first-party cookies. There are no advertising cookies, no cross-site tracking cookies, and no cookies from ad networks anywhere on the Service. The only thing that can put another company's storage on your device is a drill demonstration video, and only if you click to load it. See Demonstration videos.

• Session cookie: keeps you signed in to your account. Set only if you sign in; expires when your session ends or you sign out.
• tsa_audience: set only if you answer that a parent, guardian, or adult player is setting Tessaira up. It holds the version of the wording you were shown, a random reference number for the record of your answer, an expiry date, and a signature. It does not contain your answer, your role, or the time — those live in the record it points at, which we can withdraw. First-party, HttpOnly, one year. See the question we ask first.
• If you answer that you are under 18 or outside the United States, we set no cookie at all. We used to set one, so the page could remember your answer without asking again. It carried no identifier, but it was still something we put on your device at the moment you told us you were under 18, and it lasted a year — which is not what “we do not save anything about you” should mean. It is gone. Nothing is written, nothing is stored, and nothing about that visit reaches our database. If you had answered differently before, the only thing that changes is that we withdraw that earlier answer. See the question we ask first.
• gn_vid: a random identifier, not tied to your name or email, that lets us recognize a returning visitor across separate visits so our analytics is not just counting the same person as a new visitor every day. It is first-party, HttpOnly (a script on the page cannot read it), and lasts one year unless you clear your cookies. It does not follow you to other sites, and no third-party ad network can read it.
• gn_signup_checked: an account-specific one-way hash that says which signed-in account this browser last checked for the sign-up milestone, so switching accounts cannot suppress the second account and the site stops re-checking a successful result on every poll. It does not contain the raw account ID. First-party, HttpOnly, one year.
• gn_internal: set only on the owner's own accounts, so our visits are excluded from our own traffic numbers. It carries no identity, just that marker, and is never set on a visitor's browser. First-party, HttpOnly, one year.
• Cloudflare Turnstile cookie: a short-lived cookie Turnstile may set to run its bot check on the sign-in, sign-up, and password-reset pages. See Service providers.

Local storage on your device. Some features store information in your browser rather than on our servers. This data stays on your device unless you take an action that sends it to us, such as submitting your email or saving a read to a signed-in account:

• Saved assessment reads: a read you have not saved to an account stays in your browser's local storage. If you are signed in and save it to My Player, a copy is also stored on our servers against your account. See Children's privacy and the honest read.
• gn_stage_affinity: records which recruiting-journey stages (for example, “getting started” or “recruiting”) you have spent time reading, so the site can lead with content relevant to you on your next visit. Stays on your device unless you submit your email, at which point the current stage is included in that signup (see What we collect).
• gn_first_touch: records the referrer or campaign (UTM) tag from your first visit to the site, so we know what brought you here if you later sign up. Stays on your device unless you submit your email.
• gn_audience_path: records whether you explicitly chose the golfer, parent, or coach path so that choice can remain consistent on your device. It contains no name, email, score, or profile information, is not sent to another company, and can be removed with the “Clear saved path” control on any audience page.
• gn_entry: the first page path of the current tab, kept in session storage rather than local storage, so it is gone when you close the tab. It is sent with the anonymous funnel milestones described under Analytics so we can tell which kind of page a visit started on.

Submitting your email copies the current gn_stage_affinity and gn_first_touch values into that signup record. It does not erase them from your device; they stay in your browser until you clear them. You can clear any of this at any time through the app's controls (the “My Player” clear control, or account settings) or by clearing your browser's cookies and site data.

Some drills in the free drill library include a short demonstration video. Those videos were made by other people and are hosted on YouTube, which is owned by Google. We do not host them, we did not make them, and we are not affiliated with the channels that did. Each one is credited on the page with its title, its channel, and a link to the original.

Nothing loads from Google until you click. The video area starts as a still placeholder drawn by our own site. No request goes to YouTube or Google while it sits there, and we do not even fetch the thumbnail image from them. If you never click, Google is never told you were on the page.

What happens if you click. Clicking loads YouTube's player into the page. At that moment Google receives your IP address, your browser's user agent, and the address of our site, and it can set its own storage on your device. That happens under Google's privacy policy, not this one. We do not control what Google does with it, and none of it comes back to us.

We use the privacy-enhanced player. The player loads from youtube-nocookie.com rather than youtube.com, which is Google's own privacy-enhanced mode. We send only our site address with the request, not the full page path. Nothing on the page can start a video on its own.

If you would rather Google receive nothing, do not click to load the video. The drill works without it: the written steps, the diagram, and everything else on the page are ours and load normally. Parents should know that a child who clicks play is the person whose information reaches Google. See Children's privacy and the honest read.

We do not count your visit until you have answered the question about who is setting Tessaira up. Before that, no identifier is created for you and no page view is recorded — and if you have not answered, or you told us you are under 18 or outside the United States, neither ever happens. Everything in this section describes what happens after an adult has answered.

We measure traffic with our own first-party page analytics. When you view a page we record the page path, the referring site's hostname, a coarse device class (mobile or desktop), one word describing what your browser identified itself as (see below), the gn_vid value described above, and a flag marking whether the visit came from one of our own accounts. No location is recorded — see Location. To identify a visit without identifying a person, your IP address and browser user agent are combined with a salt that rotates daily and reduced to a one-way hash; that hash, not your IP address or user agent, is what we store. Neither your IP address nor your user agent is ever stored in an analytics record, and the hash cannot be linked across days. Your IP address is used elsewhere for rate limiting and security, as described under What we collect and How long we keep information. Alongside that daily session hash, the gn_vid cookie described above lets us recognize the same browser across days, so we are not left guessing whether today's visitor is someone who was already here last week. There is no cross-site tracking, and analytics data is never shared with third parties or used for advertising. If your browser sends a Global Privacy Control or Do Not Track signal, we honor it and do not record the pageview at all.

The one word about your browser. A large share of web traffic is now automated, and we could not tell how much of ours was, because we do not keep the header that would say. So from July 2026 each pageview also stores a single word for what the visitor identified itself as: human, search-crawler, ai-crawler, or unknown. It is worked out from the browser's user agent at the moment the pageview arrives, and only that word is kept. The user agent itself is never written to our database. It is present in the ordinary server request log, which — like nearly every website's — records the address, the user agent, the path and the status of each request; that log is described under How long we keep information and is kept for 30 days. We are separating those two things deliberately: an analytics record is something we built and can promise about, and a request log is infrastructure that every site has. We chose a single word rather than storing the header because four words cannot describe a person or a device, and the header can. Pageviews recorded before this shipped have no value here and never will: their user agent was already discarded, which is the point.

Alongside page views, we record a small number of anonymous funnel milestones so we can measure how well the site works overall. These cover: a sign-up or profile being completed, coach contact details being revealed, a sign-up or upgrade prompt being shown, a checkout being started, reaching halfway or near the end of a guide, and the steps of the assessment (opened, started, read delivered, save clicked). Each milestone is stored with the same daily-rotating session hash described above and a coarse category for the page the visit started on. These records contain no name, email, IP address, or user agent, are not linked to your account or identity, and carry none of the answers you entered into the assessment.

When our authentication provider confirms that you are signed in, we also mark that day's rotating session hash as authenticated. This keeps automated-traffic cleanup from discarding real signed-in browsing. The marker stores no account ID, name, email, IP address, or user agent, and a public analytics event cannot create it.

If you create an account, we also keep one account acquisition record so we can measure whether search and other channels produce accounts and paid subscriptions. It stores a coarse source category (organic search, social, referral, direct, or unknown), the first Tessaira page resolved transiently from the browser's gn_vid, and the times the account was created, a checkout was successfully created, and a paid subscription was first confirmed. It does not store your IP address, browser user agent, search query, or a history of pages. The gn_vid itself is discarded and is never stored on the account-linked record. The record is linked to the account so a later server-to-server payment confirmation can be attributed without pretending an anonymous daily session hash still identifies the same visitor. It is deleted with the account.

We do not work out where you are. Your IP address is not sent to any location service, before or after you answer the question about who is setting up Tessaira. There is no such service in the product for us to send it to.

This used to be different, and the change is worth stating plainly. Every page view previously sent your full IP address to an outside company to turn it into a country, region, and city. That company was a free service we had no contract with, so we could not tell you what it did with the addresses it received. We removed the lookup rather than keep describing it.

We also do not guess. A few things about a request hint at location — your browser's language setting, the network you arrive on, your device's time zone. We do not read any of them to estimate where you are, and we do not fill in a location from the state you pick for the weekly email. A guess stored in a record that says “location” is worse than no record at all, because nobody reading it later can tell the difference.

We also do not ask for a postal code. A free tool used to take a five-digit ZIP code to suggest events near you. Whatever the intention, a ZIP code is a location: it travelled in the web address (so it reached the ordinary request logs), it was counted against your network address, and it was sent to an outside postal-code service before you had answered the question about who is setting Tessaira up. We removed the tool rather than rework it, because it was not part of this launch and there was no version of it that collected less. No form or page on this site asks for a postal code, and no page of this site uses one to decide what you are shown.

What you can tell us yourself, and why that is a different thing. Everything above is about what we would have to work out about you — from your network address, your browser, or a code we asked you to type. None of that happens. What does happen is that a few optional fields let you pick a U.S. state from a list, and when you pick one we store it, because the feature does not work otherwise. Those fields are, in full:

• the state on your My Player profile, used to place a golfer in their state's recruiting context;
• the state on a saved Recruiting Readiness Scorecard, stored only when you narrow the search to a region rather than leaving it as “anywhere”;
• the state preference on a newsletter signup, which decides which state's events the weekly email leads with;
• the state shown on a published public recruiting profile, which is the profile state above and appears only if you switch it on — and which the server and database suppress outright for an under-13 profile. When a verified coach saves that profile to a shortlist or exports it, the state travels with the rest of what you published.

A state you typed is not a location we determined, and we do not treat it as one: it is never written into an analytics record, never compared against your network address, and never used to decide what the site shows a visitor who has not filled it in. Where it is stored, it is stored because you entered it, and you can change or clear it in the same place you entered it.

The one thing we do ask everybody is whether you are in the United States, because we only offer Tessaira there for now. You tell us that yourself, as part of the same question described under the question we ask first. That answer is a yes or no about the country, not a place: we store which of the four options you chose, and nothing narrower. We take your word for it; we do not check it against your IP address.

The assessment is generated automatically. The “honest read” is produced by an automated formula (an algorithm) that runs in your browser on the inputs you enter. No person at Tessaira reviews your inputs or the result. The read is informational only: it does not make any legally or similarly significant decision about you or a junior golfer, and it does not determine eligibility, admission, financial aid, or any recruiting outcome. See the assessment section of our Terms of Use for its limits.

We do not train AI on your information. We do not use your account details, assessment inputs, a minor's information, or any other personal information to train machine learning or AI models, and we do not sell or share it for anyone else to do so.

How the site is built. Tessaira is built using AI and automated software-development tools, and some site content and parts of the assessment are generated or assisted by automated systems. We review this content, but automated systems can produce errors or omissions, so please verify anything you rely on (tournament dates, coach contacts, scholarship or aid figures, and NCAA, NAIA, or NJCAA eligibility rules) with the official source.

We use a small number of infrastructure providers that process data on our behalf, under their own security and privacy commitments:

• Neon: database and authentication (United States). Stores account records, hashed credentials, newsletter signups, and operational data.
• DigitalOcean: primary hosting (United States). Runs the servers that serve the site and produce the request logs described above.
• Netlify: standby hosting (United States). If our primary host is unavailable, the site can be served from Netlify, which would then process the same request data.
• Cloudflare: bot protection. On the sign-in, sign-up, and password-reset pages we use Cloudflare Turnstile to tell humans from bots. To do this, Cloudflare receives your IP address and basic browser signals. Turnstile does not use tracking cookies for cross-site advertising.
• YouTube (Google): hosts the demonstration videos in the drill library. Nothing is requested from Google until you click to load a video; once you do, Google receives your IP address and browser user agent and may set its own storage on your device. Unlike every other provider on this list, Google is not processing anything on our behalf and does not act on our instructions. It handles that information under its own privacy policy. See Demonstration videos.
• Resend: email delivery. Sends the account, newsletter, and stage-based emails described under Email program. Resend processes your email address and the message content to deliver it, and is not permitted to use it for its own marketing.
• Polar: payment processing for Premium subscriptions. Handles your card details directly; Tessaira never sees or stores your full card number. Polar shares back only what we need to run your subscription (payment status, the amount charged, when the period ends, and its own customer and subscription identifiers).

Apart from YouTube, which is described above and which you have to click before it receives anything, these providers act only on our instructions and are not permitted to use your information for their own purposes. We do not give any other company access to your personal information, and we do not sell or share it.

Things that are not on this list, because they receive nothing. The coach map draws from a map file stored on our own server: there is no map or tile company involved, no key, and no request from your browser to one. We load no images from anyone else's server — your browser is not permitted to fetch one. We do not display tour, conference, or event logos, because we have not recorded permission to republish them, so those appear as text instead. And there is no advertising network, no cross-site tracking, and no behavioural analytics company anywhere in the product.

One that used to be on this list. An IP geolocation service received a complete IP address on every page view and every email signup, so that we could record an approximate city. It was a free service with no contract and no agreement with us, which meant we could not tell you what it did with the addresses it received — and that is not a footnote to disclose, it is a reason not to send them. The lookup has been removed and no location service receives anything. See Location.

And one more. A free postal-code service received the ZIP code entered into a local-events tool, in order to turn it into a city and state — again with no contract and, worse than the one above, before the visitor had answered the question about who is setting Tessaira up. That tool has been removed from the product entirely. No postal-code service receives anything, because there is no longer anywhere to enter a postal code. See Location.

The Tessaira directory aggregates publicly available information about college golf coaches published by their schools and institutions, such as institutional email addresses on athletics websites. Event and rankings coverage is editorial and links parents to the relevant official organizer where appropriate. This is information about public programs and roles, not private individuals' personal lives, and coach contact details are gated behind Premium to discourage bulk collection.

If you are a coach or represent an institution listed in our directory and your listing is inaccurate, or you would prefer not to be listed, email angelo@tessaira.com from an institutional address and we will correct or remove the listing.

Two different things are described below, and we have tried to keep them plainly apart. Some of these periods are enforced by the software: the deletion happens because you did something and the code carries it out. Others are periods we have committed to and carry out by hand — they are real commitments, but there is no automatic job behind them yet, and we are not going to describe them as if there were.

• Analytics (page views and funnel milestones): 25 months, which allows one year-over-year comparison and no more. Carried out by hand today, not automatically.
• Server request logs (IP address, user agent, path, status): 30 days. Carried out by hand today.
• Rate-limiting records: 24 hours. These are the counters that stop one machine hammering a form; the key is derived from a network address, so we do not keep them past the day they were counting. Deleted by a daily job, not by hand.
• Your answer to the question about who is setting Tessaira up: the answer stops being usable after 12 months, enforced by the record itself and by the cookie. We then keep the record of what you agreed to, and when, for a further 365 days — a total of 730 days from the day you answered — so that if anyone asks what we were relying on when we emailed you last March, we can answer. Deleted by the same daily job. If you delete your account or unsubscribe, the link between you and that record is removed straight away; what stays is an anonymous record with no subject attached to it.
• Subscription and payment records: kept for seven years after the subscription ends, because they are financial records. This is the one category that deliberately outlives account deletion.
• Unsubscribe records: kept indefinitely, on purpose. If we deleted the record that you unsubscribed, the next signup or import would email you again. It is a short record — your address and the fact that you opted out.

When you delete your account, the account-scoped items below are deleted with it. One honest limitation: our database provider keeps backups, and we have not yet confirmed how long a deleted row can persist inside one. Until we can state that period, “deleted” means deleted from the live database.

• Account data: kept until you delete your account or ask us to delete it.
• Saved assessment reads: an unsaved read stays on your own device and lasts until you clear it (through the app's controls or your browser storage). A read you save to a signed-in My Player account is also stored on our servers and is kept until you delete the entry or delete your account.
• Round and practice log: kept until you clear it or delete your account. There is no automatic expiry — a round logged today is still there in five years unless you remove it. You can delete any single round from the tracker itself, which removes that round and its statistics and note immediately. Reset dashboard data in My Player settings deletes every logged round (with its statistics and note), every practice session, and every cleared milestone on the account, and deleting your account deletes them too. All three are available to any signed-in account, free or Premium.
• Email signup data (newsletter, roadmap, quiz): kept until you unsubscribe or ask us to remove you.
• Saved drills, saved schools, saved-school recruiting records, and planned tournaments: kept until you remove them from your saved lists. All three are also removed when you delete your account and cleared by Reset dashboard data in My Player settings.
• Public recruiting profile: the selected fields remain public until you unpublish. After unpublishing, we keep the private configuration and reserve its random URL until you publish again, clear dashboard data, or delete your account. Reset and account deletion remove the profile, its selected public schedule, and the profile-view analytics association.
• My Player profile: the graduation year, boys or girls golf, optional U.S. state, optional grade-point band and optional player name are kept until you change them, clear dashboard data, or delete your account. There is no expiry; the row is overwritten in place each time you save it.
• Coach outreach log: the school, coach, template, channel, state, timestamps and your optional note are kept until you clear dashboard data or delete your account.
• College coach account application: the institutional email address, the program claimed, the verification state, the review record and the digest settings are kept for as long as the coach account exists, and are deleted when that account is deleted. The audit trail of what was done to the application — including the institutional address that acted — is deleted with it.
• Private coach prospect list: a saved profile, its relationship stage and its private note are kept until the coach removes that entry or their coach account is deleted, and are removed automatically if the player's family deletes the published profile the entry points at. A spreadsheet a coach has already downloaded is a file on their own device and is outside anything we can delete; that is a limit of an export, and we state it rather than implying otherwise.
• Player ranking snapshots: kept as a dated history until you remove an entry, clear dashboard data, or delete your account.
• Recruiting-plan checkmarks: the items you have ticked off or dismissed on your plan, and — when you check off an event that has already happened — whether your golfer played it and the score you entered, are kept until you clear them with Reset dashboard data or delete your account.
• Coach email reveals: an older version of the site recorded which school's coach contacts an account had unlocked, and when. We no longer write those records. One row from that period still exists and is deleted when that account is deleted; nothing new is added. If we start keeping this record again, to spot bulk collection of coach addresses, we will say so here first.
• Analytics (page views and funnel milestones): the daily session hash cannot be linked across days by design; the underlying records are kept in aggregate for reporting. A public profile view is labeled with that profile's random slug so its owner can receive an aggregate view count later; it never identifies a coach or visitor, and deleting the profile removes that slug association.
• Authenticated-session analytics marker: the daily rotating session hash and the times it was confirmed as signed in are retained with analytics reporting. It carries no account identifier and cannot be linked across days.
• Account acquisition record: the coarse source, first Tessaira entry page, and signup, checkout, and first-paid timestamps are kept until you delete your account. They are used only for Tessaira conversion reporting, not advertising.
• gn_vid cookie: lasts one year from when it is set unless you clear your cookies sooner.
• gn_stage_affinity and gn_first_touch: stay in your browser's local storage until you clear them. Submitting your email copies the relevant snapshot into that signup record but does not remove the keys from your device.
• Approximate location: no longer collected at all. The columns that held it on older page views and signup records are now always empty, and nothing writes to them. Values recorded before the lookup was removed are covered by the page-view and signup-record periods above and age out with those records.
• ZIP or postal code: never collected, and there is now nowhere to enter one. A free tool used to take a five-digit ZIP to suggest local events; it sent that code to an outside postal-code service before you had answered the question about who is setting Tessaira up. The tool has been removed rather than changed, and no form, page or address on this site asks for a postal code. See Location.
• Rate-limiting records: to enforce request limits we keep a counter keyed to an IP address or an account. The limit window itself is an hour or less. We use these records only to slow abuse, never for analytics, profiling, or advertising.
• Server and security logs: 30 days, the same period given under How long we keep information. They record the request address, the browser user agent, the path and the status. Carried out by hand today, not by an automatic job — this bullet used to say “a short period, then rotated out”, which is not a period and was not the number stated elsewhere on this page.

You can access, correct, or delete your information at any time:

• Account deletion: delete your account yourself anytime from account settings (Danger zone), which removes every record we hold against your account — your profile, saved schools and their recruiting records, public recruiting profile and its selected schedule, saved drills, planned tournaments, ranking snapshots, saved reads, outreach history, recruiting-plan checkmarks, any saved Recruiting Readiness Scorecard, your newsletter subscription and any record of emails we have sent you, any legacy coach-unlock row still held from the older version of the site, and your whole tracker log, meaning every round with its statistics and note, every practice session, and every cleared milestone — and cancels any Premium subscription immediately. You can also email angelo@tessaira.com from the address on your account and we will delete it for you.
• Clearing your data without deleting your account: Reset dashboard data, in My Player settings, wipes the player profile, its public recruiting page, ranking snapshots, saved reads, saved schools and their recruiting records, saved drills, planned tournaments, outreach history, recruiting-plan checkmarks, and the entire tracker log from our servers while leaving the account itself, its email, and any subscription alone. Two things it does not clear. Your saved Recruiting Readiness Scorecard, which stays until you retake it or delete your account. And a legacy row, from an older version of the site, recording that an account had unlocked a school's coach contacts — we no longer write those records, and Reset leaves that old row alone. Deleting your account removes both. See how long we keep information, above.
• Saved reads: a read you never saved to an account is on your device — clear it in the “My Player” screen or by clearing your browser storage. A read you saved while signed in is also on our servers; remove that copy by deleting the entry in My Player, by using Reset dashboard data, or by deleting your account.
• Email signups: use the unsubscribe link in any email to stop all future messages, or the journey link in the same footer to pick a different stage. You can also email us and we will remove you.
• Cookies and local storage: clear any of the cookies or on-device keys listed under Cookies and local storage at any time through your browser's cookie and site-data settings. This does not affect your account or email subscription, which are stored separately.
• Access and correction: email us and we will tell you what we hold about you and fix anything that is wrong.

If you live in California or another U.S. state with a consumer privacy law (such as Virginia, Colorado, Connecticut, or Texas), you have rights over your personal information, including the right to know or access what we hold, the right to correct it, the right to delete it, the right to data portability, and the right not to be discriminated against for exercising these rights. To exercise any of them, email angelo@tessaira.com from the address associated with your information; we may ask you to confirm a few details to verify the request before we act on it, and we honor these requests regardless of the state you live in. You may use an authorized agent. For clarity under these laws: we do not sell your personal information, we do not share it for cross-context behavioral advertising, and we do not offer financial incentives for your data. We do not use or disclose sensitive personal information, including a minor's information, beyond what is necessary to provide the Service.

We do not operate verifiable parental consent. The question described above is a self-declaration, not verification, and no checkbox or notice on this site is verifiable parental consent under the Children's Online Privacy Protection Act. Because we do not operate that process, we do not knowingly accept personal information from a child under 13. A parent or guardian who is setting Tessaira up is providing information about their own player, under their own account, and can remove it at any time.

The journey quiz and a young player's age. The quiz asks roughly how old the player is so it can point you at the right guidance, and two of its answers describe a child under 13. On the page, that answer is just guidance and never leaves your browser. We only attach it to an email address or an account when an adult has answered the question above; otherwise it is discarded rather than stored beside anything that identifies a person.

What the assessment collects. The honest read asks a few questions about a junior golfer so it can produce an estimate: the player's age (10 to 18), gender, typical scoring range, the level of events they play, and any ranking, plus a few optional details. It does not ask for the player's name, email, address, photo, school, or any other direct identifier, and it never asks for free-text input. If you ask for the read as a PDF, that separate form asks for your own email address, not the player's.

Where the read is stored. The read is calculated in your browser. If you do not save it to an account, it stays on your own device in your browser's local storage and never reaches us. If you are signed in and save it to My Player, we store a copy on our servers, tied to your account, so the tracker can show progress over time. That copy contains the answers you gave the assessment: the player's age and gender, their scoring band, the level of events they play, and any ranking you entered. It does not contain their name, photo, school, or any other direct identifier, because the assessment never asks for those. You can remove it by deleting the entry in My Player or by deleting your account, which erases the saved reads with it.

What the tracker stores, and where. The “My Player” tracker keeps a log of rounds and practice. Logging is free: any signed-in account can do it, and there is no Premium requirement to write to it or to delete it. Every round you log is stored on our servers, tied to your account — the date, the score, the course par, how many holes, whether it was a tournament, any of the per-round statistics you choose to enter (fairways, greens in regulation, putts, up-and-downs, penalties, three-putts), an event or course name if you add one, and a note if you write one. Practice sessions (date, drills, minutes) and the milestones you mark as cleared are stored the same way. Put together, that is a running record of a specific child's competitive results over time, held on our servers against a parent's account. We are telling you that plainly because it is more than the assessment holds and it accumulates.

The note is free text and we do not filter it. Unlike the assessment, which only ever offers fixed choices, the note and the event name accept anything you type, and we store it exactly as written. If you type your golfer's name, their course, their coach, their school, or how they were feeling that day, that is what sits in our database. Nothing in the product requires it — a round needs only a date, the holes, a score, and a par — so if you would rather we held none of that, leave the note and the event name blank. The log works the same either way.

We do not knowingly collect personal information from children under 13. The Service is directed to parents and guardians, not to children. We do not ask children to create accounts, and we do not knowingly let a child under 13 create an account, subscribe, or submit information directly. Accounts and email signups (newsletter, roadmap, quiz) are intended for adults, not children. Where information about a child is provided, we intend for a parent or guardian to be the person providing it.

No profiling or advertising to children. We do not use any information about a minor to build advertising or behavioral profiles, we do not serve targeted advertising, and we do not sell or share a minor's information. There are no third-party advertising trackers anywhere on Tessaira.

Videos, and what reaches Google. Some drills include a demonstration video hosted on YouTube. Nothing is sent to Google while the page sits there. If your golfer clicks to load one, Google receives their IP address and browser user agent at that moment and may set its own storage on the device, under Google's privacy policy rather than ours. We do not control that and we receive nothing back from it. If you would rather that not happen, the drill works without the video. See Demonstration videos for the full description.

Parental review and deletion. A read you never saved to an account is on your device: review it in the “My Player” screen and delete it instantly with the clear control there, or by clearing your browser's storage. Everything held on our servers — the saved read, the profile, and the whole tracker log with its statistics and notes — is shown back to you in My Player. Any single round can be deleted from the tracker on its own, and you can erase everything yourself in two ways: Reset dashboard data in My Player settings, which wipes that data and leaves the account standing, or deleting the account, which removes it and cancels any subscription. Both work on any signed-in account, free or Premium — removing a minor's data is not a paid feature. To review or delete any information we hold about a minor, including an account created for a junior golfer or an email in our newsletter list, email angelo@tessaira.com and we will respond promptly and without charge. If you believe a child under 13 has given us information directly, contact us and we will delete it.

We take reasonable measures to protect your information: traffic is encrypted in transit, passwords are stored only in hashed form by our authentication provider, and the Service enforces rate limits to slow abuse. No website can promise perfect security, but we keep the amount of data we hold small on purpose. The best protection for data is not collecting it: the assessment runs in your browser, a read you do not save never leaves your device, the assessment never asks for a player's name, and the tracker requires only a date, the number of holes, a score, and a course par — every statistic, event name, and note is optional. What you do save to an account is on our servers, described above, and deletable by you at any time.

If we change this policy, we will post the updated version here with a new effective date. If a change meaningfully affects what we collect or how we use it, we will make that clear rather than bury it. That includes changes we should have written down sooner: this page previously said a saved assessment read stayed on your device and never reached our servers, which was wrong once saving a read to a signed-in account began storing a copy against it. We corrected that in July 2026 and described exactly what the copy contains, rather than quietly softening the old wording, and we disclosed the My Player tracker's round and practice log the same way. We would rather tell you more than we strictly have to than leave something out.

Privacy questions, requests, and listing-removal requests: angelo@tessaira.com. See also our Terms of Use.