Hashmarks.
Book 20 min
Hashmarks

Hashmarks Privacy Policy

Effective date: November 5, 2026

Who we are: Hashmarks ("Hashmarks," "we," "us") is operated by Hashmarks LLC, a Delaware limited liability company. Contact: support@hashmarks.football.

1. What Hashmarks is

Hashmarks (hashmarks.football) is a web app that football coaching staffs use to chart plays, view tendencies, design plays, build game plans and quiz their staff. Accounts are for coaches, staff and other adults working with a team ("Users"). A team's workspace is called an "Organization."

2. Information we collect

Access requests. To request an account you give us your name, email address, team name, level (for example youth or high school), tackle or flag, your role, an optional message, and optionally how you heard about Hashmarks. We also record how your visit started: the name of the website that sent you (for example "google"), the first Hashmarks page you opened, and any campaign tag in the link you followed. Your browser remembers that only for the open tab, without a cookie, and sends it only when you submit the form. We use all of this to review the request, contact you, and learn which ways of finding us work, and we keep it with the request's outcome.

Account information. Name, email address and password (stored only as a one-way hash). Optional profile picture URL.

Team and football data that Users enter or import. Organization name and level, seasons, games, opponents, scores, play-by-play data, playbooks, play diagrams, opponent looks, game plans, custom terminology, notes, quiz results, and data imported from CSV files (for example Hudl exports) or video-import jobs.

Roster information about players. Users may add player names, jersey numbers, positions, class year, height, weight and photo links, typed in or extracted from a web page the User provides. Players do not have Hashmarks accounts. See Section 7.

Voice entries. If a User records a play by voice, the audio is sent for transcription (Section 5) to turn it into play data.

Links you create. Collector links and game-plan share links are random, revocable, expiring links. We store when they expire, whether they were revoked and, for share links, a view count and last-viewed time. We store a hash of share-link tokens, not the link itself.

Feedback and support tickets. When you use the Feedback button or the Support page, we store your message, the type you picked (for example a problem, idea, question or account issue), an optional subject, and your name, email address, role and team. To help us fix problems without asking you to describe them, the report automatically includes the page you were on (with any link tokens removed), the page title, time and time zone, screen size, browser type, whether you were online, recent in-app error messages and failed requests (not their contents), the last few pages you visited in the app, and details of what was on screen (for example the quiz question or play you were viewing). If you leave "Include a screenshot" checked, a screenshot of the page you were viewing is attached; untick it to send without one. Hashmarks staff use these reports to answer you and to improve the app, and may reply to you by email.

Technical information. Our hosting provider and app servers log requests (such as IP address, browser type, pages requested and timestamps) for security, debugging and reliability. We use a strictly necessary session cookie to keep you signed in. The app stores some data in your browser (local storage / IndexedDB) so charting keeps working offline and remembers preferences such as whether you finished the onboarding tour.

Site visit counts. On our public pages (such as the home page, blog and sign-up pages, but not inside the app), your browser sends a small notice to our own servers when a page loads. We add one to a daily count for that page, and keep only the name of the website that sent you there (for example "google" or "reddit.com"), never the full address of the page you came from. We don't set a cookie for this, and we don't store your IP address, browser details or anything else that identifies you. If your browser sends a "Do Not Track" signal, no notice is sent. We also count how many sign-ins happen each day and record the time of your last sign-in, so we can tell how much the app is used.

We do not use advertising cookies, sell personal information, or use third-party analytics or ad-tracking scripts.

Sponsor ads. Some public pages (blog posts and the site footer) show an ad or a credit for a sponsor. The ad images are served from our own servers, and a click goes through a Hashmarks link that adds one to a daily count of ad views and clicks before sending you to the sponsor's website. We don't record who saw or clicked an ad, we don't set cookies for ads, and we don't share any information about you with sponsors. Once you're on a sponsor's website, its own privacy policy applies.

3. How we use information

  • To provide the service: sign-in, storing and showing your team's data, live syncbetween staff devices, charts, reports, play diagrams, quizzes and share links.
  • To send service emails, such as staff invitations and account notices.
  • To run optional AI features a User triggers (Section 5).
  • To secure the service, prevent abuse, fix problems and improve features.
  • To develop, train and improve Hashmarks, including our own machine-learning and AImodels and features (for example formation and play recognition, tendencyprediction, voice entry, and generated quizzes, diagrams and reports), as describedin Section 3A of our Terms of Service.
  • To comply with law and enforce our Terms.

How we train models. We use team and football data (plays, playbooks, diagrams, game data, imports and how features are used) to improve Hashmarks. Before any data is used to train or evaluate models, we remove or de-identify personal information, such as names, email addresses, photos and other details that identify a player, parent, coach or other person, and we don't use information that identifies a player to train models. We don't use one team's plays or scouting data to show them to another team, we don't let third parties train their own models on your data, and we don't use your data for advertising.

4. How information is shared

  • Within your Organization. Data in an Organization is visible to its membersaccording to their role (owner, admin, coach, assistant, collector).
  • Through links you create. Anyone with an unexpired, unrevoked collector or sharelink can use or view what that link covers (for example a read-only game plan). Sharelinks are hidden from search engines. Revoke a link at any time.
  • Service providers that process data for us under contract:
    • Amazon Web Services (hosting, database, file storage, email delivery) — United States.
    • OpenAI (voice transcription; some AI text features) and Anthropic (AI scoutingreports, voice-entry parsing, roster extraction) — only when a User uses those features.
  • Legal and safety. If required by law, or to protect the rights, safety or propertyof Users, players, the public or Hashmarks.
  • Business transfers. In a merger, acquisition or sale of assets, subject to this Policy.

5. AI features

Some features send the relevant data to an AI provider to produce a result: voice entry (audio + play context), AI scouting reports (play statistics you've selected), and "import roster from a web page" (the page text). We send only what the feature needs. You can use Hashmarks without these features.

6. Retention and deletion

We keep Organization data while the Organization is active. Imported source files are deleted automatically after about 90 days and temporary uploads after about 1 day; the data extracted from them stays in your workspace until you delete it. Users can delete games, plays, roster entries, playbook entries, game plans and links in the app. To delete your account or an entire Organization, email support@hashmarks.football from your account email; we'll delete it within [30] days, except where we must keep information for legal reasons. Backups roll off within [35] days. De-identified or aggregated data, and models already trained on it (Section 3), may be kept after deletion because they can't reasonably be separated back out; they don't identify you or your players.

7. Children and student-athletes

Hashmarks accounts are for adults (18+). The service is not directed to children and we do not knowingly collect personal information directly from children under 13.

Coaches may enter information about players, who may be minors. The Organization is responsible for having the authority and any consents needed (from the school, league, parents or guardians) to enter that information, and should enter only what it needs (for example name, jersey number and position). A parent, guardian or player who wants information reviewed, corrected or deleted can contact the team, or email us and we'll work with the Organization to handle it.

8. Security

Passwords are hashed; data is encrypted in transit (HTTPS) and at rest on our database and file storage; access is restricted by Organization and role; share-link tokens are stored hashed. No system is perfectly secure; tell us about any concern at support@hashmarks.football.

9. Your choices and rights

You can view and update most information in the app, and ask us to access, correct, export or delete your personal information by emailing support@hashmarks.football. Depending on where you live (for example California, Colorado, Virginia or the EU/UK), you may have additional rights; we will honor applicable requests and will not discriminate against you for making them.

10. Changes

We'll post updates here and change the effective date. If changes are material we'll notify account owners by email or in the app before they take effect.

11. Contact

support@hashmarks.football · Hashmarks LLC