Terms of Service & Privacy

By creating an account, subscribing, or using SCOUTSWING in any way, you agree to these terms. If you don’t agree, don’t use the service. We may update these terms from time to time — see Changes to these terms, below — and continued use after an update means you accept the new version.

SCOUTSWING is a football-scouting intelligence platform. We answer questions about players, teams, and matches, and we produce grades and analysis built from statistical data disclosed on this page (see Data sources & provider terms, below).

Every grade, answer, and figure we produce is an analytical opinion, built transparently from the sources we name. It is not a claim of certainty, and it is not advice of any kind — see Disclaimers & limitation of liability, below.

You’re responsible for the accuracy of the information tied to your account and for anything that happens under it. One account is for one person — accounts aren’t shared across multiple users, and credentials aren’t passed around.

We can suspend or terminate an account that abuses the service — including the acceptable use terms below — without a refund of any remaining subscription period.

SCOUTSWING is built for individual use, read through the product itself. You may not:

• Scrape, crawl, or bulk-extract data, grades, or answers from the service.
• Resell, redistribute, or republish our data, grades, or content as your own or as a data feed for others.
• Circumvent the paywall, subscription gating, or any access control.
• Run abusive automation against the service — including automated querying at a rate or pattern designed to extract data at scale.

SCOUTSWING Pro is billed at $99/yr or $9.99/mo, processed by Stripe. We don’t store your card details — Stripe handles that.

Cancel any time from your account settings; cancellation takes effect at the end of your current billing period, and you keep Pro access until then. We don’t give partial refunds for the unused part of a period, except where the law requires it.

SCOUTSWING’s product, design, grading methodology, and brand are ours. Using the service gives you a limited, personal license to use it — it doesn’t transfer ownership of any of that to you.

Your own notes, shortlists, and saved searches are yours. We don’t claim ownership of them, and we use them only to run the service for you, as described under Privacy, below.

The statistical data behind SCOUTSWING comes from named third-party providers under terms that permit our use of it (see Data sources & provider terms, below). Those providers’ own terms flow through to how that data may be used — our license to show it to you doesn’t grant you a broader right to extract or redistribute it than we ourselves have.

Everything SCOUTSWING produces — grades, answers, comparisons, and forecasts — is analytical opinion built from disclosed sources. It is not financial or legal advice, and it is not a guarantee of any outcome on the pitch or anywhere else.

The service is provided as-is. To the extent permitted by law, our liability to you for any claim arising from your use of SCOUTSWING is capped at the total fees you paid us in the 12 months before the claim arose.

You can stop using SCOUTSWING and cancel your subscription at any time. We can suspend or terminate your access for breach of these terms, including the acceptable use section above. Sections that by their nature should survive termination — intellectual property, disclaimers and limitation of liability, and governing law — continue to apply after your account ends.

We may update these terms as the service changes. Material changes will be notified — for example, via the app or by email to the address on your account. The “Last updated” date at the top of this page always reflects the current version.

These terms are governed by the laws of the State of Delaware, United States, and any dispute arising from them is subject to the exclusive jurisdiction of the state and federal courts located in Delaware. SCOUTSWING is operated by STATSWING Inc. If you use SCOUTSWING as a consumer in the United Kingdom or the European Union, you keep every protection your local consumer law grants you that cannot be waived by agreement — nothing in these terms takes those rights away.

We run PostHog, a product-analytics tool, on every page of SCOUTSWING without an analytics cookie. In a normal browser tab its analytics identity stays in memory and is not persisted. In the installed app, PostHog uses first-party local storage so the app can recognise its own analytics visit across app-shell reloads; it is not used to track you across other sites. PostHog still processes your IP address and browser/device details to count pageviews and clicks. It does not read the content of anything you type into a form unless you submit it.

When you ask SCOUTSWING a question, we do not send its wording or an excerpt to analytics. Our server normalises the question in memory and turns it into a keyed code that changes every UTC day. PostHog receives that daily question-group code plus structured outcomes: whether the answer resolved, needed disambiguation, was not found or unavailable, or hit a rate limit; and, when resolved, the entity type and internal id. The code can show that the same question pattern recurred that day, but does not reveal its wording. See the identity model below for exactly how that's grouped without identifying you.

If you create an account (magic-link email sign-in), we collect your email address and the players, teams, leagues, and coaches you track, shortlist, or forecast — the data the instrument needs to function. Two vendors handle that on our behalf: Resend delivers the sign-in email (it sees your email address and the one-time link, nothing else), and Neon (Postgres) hosts the account and instrument data itself. Neither is used for anything beyond running the instrument.

If you turn on alerts for a tracked player, team, league, or coach from the installed app, your browser creates a push subscription — an address (endpoint) and a pair of encryption keys your browser generates for that purpose — which we store, tied to your account, solely to deliver the specific alert you asked for. It carries no location, device model, or identity beyond what's needed to reach that one browser. We delete it the moment it stops working (your browser reports it dead) or you turn alerts off; it is never used for anything but the fact-only entity-change alerts described here, never for marketing or editorial content.

We don't sell your data to advertisers, and we don't share it with third parties for marketing purposes. PostHog data is used to understand how the instrument is used and where it breaks — nothing more. The daily question-group code and the anonymous visitor/day code use one server-only key but different cryptographic domains, so one code cannot be reused as or derived from the other. A search event necessarily pairs its daily question group with either the anonymous visitor/day code or, when signed in, your account user id; that is how same-day recurrence and outcomes are counted. Neither daily code is joined to the anonymous-shortlist cookie below, and the event still contains no question wording or excerpt.

PostHog sets none — see above. SCOUTSWING itself sets two, both strictly functional (never analytics or advertising):

• tsari_session — set only if you sign in; keeps you signed in across visits. Removed when you sign out.
• sw_anon_id — set the first time you shortlist or track something before signing in; lets that anonymous shortlist survive a return visit and lets us re-attach it to your account the moment you do sign in. Cleared automatically once that claim happens.

Neither is used to track you across other sites, and both exist only to run a feature you directly invoked — the class of cookie most privacy law treats as not requiring a consent banner. We name them here anyway rather than claim we use no cookies at all.

You can use SCOUTSWING — ask questions, read grades, build a shortlist — without an account. The mechanisms below are deliberately separate:

• Your shortlist is tied to the sw_anon_id cookie above. Sign in later, and that shortlist becomes yours automatically — the cookie is cleared once the claim completes.
• The question pattern gets its own keyed daily code, computed from a normalised version of the question. The wording and normalised input are not sent to PostHog or stored by this mechanism. The same pattern on the same UTC day produces the same opaque code; a new day produces a different one.
• An anonymous visitor/day gets a separate keyed daily code computed from IP address and browser details on our server. It groups anonymous server events within that UTC day, is never written to a cookie or browser storage, and changes the next day. A separate cryptographic domain prevents this code from being reused as or derived from the question-pattern code, even though both reuse one protected server key. Within a search event, PostHog receives both daily codes so it can count same-day recurrence per anonymous visitor; neither code survives the UTC-day boundary.
• A signed-in ask uses your account user id as the server event's analytics identity instead of the anonymous visitor/day code. Signing in does not change the question boundary: analytics still receives only the daily opaque question group and structured outcome, never the wording or an excerpt.
• Your PostHog analytics visit is not persisted at all (see Cookies, above) — it exists only for the duration of that one page load/session in memory.

Because PostHog sets no analytics cookie, there's no tracking cookie to opt out of — but an ad/ tracker-blocking browser extension will still stop it from loading at all, and we honor “Do Not Track” where a browser sends it. You can clear the installed app's first-party analytics storage from your browser/app site-data controls. You can block or delete tsari_session/sw_anon_id from your browser's own cookie settings at any time (doing so signs you out, or clears an unclaimed anonymous shortlist, respectively). Account-level data export and deletion are handled from your account settings once that self-service capability ships; until then, contact us directly for either. Sharing exact question wording in the future would require a separate, explicit opt-in and a fresh privacy/legal review; this cookieless analytics posture does not authorize it. Jurisdiction-specific legal clearance of the analytics posture remains a production-launch gate.

Every figure on SCOUTSWING is sourced from a named data provider — API Football and comparable statistical partners — under terms that permit editorial, non-commercial display with attribution. We show the source and as-of date on every audited figure (the chain, per our provenance system) rather than asserting a number as our own.

This is the single place the full provider-terms posture lives — surfaces elsewhere link back here rather than repeating it. If you're a provider or rights-holder with a question about how your data or footage is used, contact us directly.

SCOUTSWING is photo-free by design— player, team, coach, and match cards render from type and data only, never a photo. This is a deliberate instrument and legal posture (v1), not a missing feature: it removes a whole category of image-rights risk rather than relying on “editorial use” as a shield. It does not extend to unrelated contexts (for example, a founder's own photo on the About page sits under a different rights basis entirely).