Privacy Policy

Last updated: August 6, 2026

Who we are

Fourth Official is a record-keeping tool for soccer referees — a place to track your games, pay, mileage, expenses, and the people you work with. This policy explains what we collect, who else sees it, and the choices you have. It describes the service as it actually works today.

What we collect

Account information. You sign in with Google. We receive your name, email address, and profile image, and nothing else — we request only basic profile access, never your Gmail, Drive, or Google Calendar. We never see or store your Google password.

The records you enter. Games and assignments, pay and payment status, the people you add (crew, assignors, assessors, including any contact details you choose to save), leagues, venues, expenses, assessments, and notes. This is the core of the service and stays private to your account.

Your home address, if you enter one. It is used to measure the distance and drive time from home to each venue. See “Addresses and maps” below — this is the one thing you give us that we have to share with someone else to make useful.

Schedule feeds you connect. If you subscribe to a schedule from an assigning platform, we store the feed address you paste in. These links usually contain a private access token, so we encrypt them before saving and only decrypt them to fetch your schedule.

Files you import. Spreadsheets you upload are parsed into game records. We keep the resulting records, not the uploaded file. If you use the option to upload a file that isn't our template — a PDF, a screenshot, an assignor's own spreadsheet — see “Reading files with AI” below.

Basic usage and error data. Page-level traffic measurement, and diagnostic reports when something breaks, so we can fix it.

Addresses and maps

To turn an address into mileage, we send it to Google Maps Platform. Specifically: your home address and each venue address are sent to Google's Geocoding API to find their coordinates, and to the Distance Matrix API to measure the driving distance and time between them. If you use the address suggestion box, what you type there is sent to Google's Places API as you type.

We cache the results so the same address isn't looked up repeatedly. Google's handling of these requests is governed by its own privacy policy. If you would rather not share your home address, you can leave it blank and enter mileage manually — every other part of the app still works.

Reading files with AI

The import page can read a file that isn't our template — a PDF, a screenshot, or an assignor's own spreadsheet. When you use it, that file is sent to Anthropic and read by its Claude model, which transcribes the assignments it contains so we can show them to you for review. This only happens when you upload such a file. Importing our CSV template never sends anything anywhere.

These files often list other officials — names, and sometimes phone numbers — so they go too. Anthropic acts as our processor here: under its commercial terms it does not use data submitted through its API to train its models. We store the games we read out of the file; we do not store the file itself.

A transcription is a best effort, not a guarantee. Nothing is saved until you review the games on screen and confirm them, and you can leave any of them out. If you would rather not send a file to a third party, use the CSV template instead — the rest of the app is unaffected.

How your data is stored

Your records live in a Postgres database hosted on Supabase, in the United States. Access is restricted to the application itself; no other user can reach your data. Schedule-feed addresses are encrypted at rest. We do not sell your data, share it with advertisers, or use it to train anything.

Who else touches your data

We rely on a small set of providers, each handling only what its function requires:

  • Google — sign-in (name, email, profile image), and Maps Platform for the address lookups described above.
  • Supabase — the database your records live in.
  • Vercel — hosting, and privacy-friendly traffic analytics that count page views without cookies or cross-site tracking.
  • Sentry — error monitoring. Crash reports can include the page you were on and your account identifier, so we can reproduce the bug.
  • Anthropic — only if you upload a file for AI import, and only that file, to read the assignments out of it. See “Reading files with AI” above.
  • Your assigning platform — only if you connect a schedule feed, and only in the sense that we fetch the schedule they publish to you. We send them nothing about you.

Cookies

We use one cookie: the session cookie that keeps you signed in. We do not use advertising or cross-site tracking cookies, and our analytics does not set one.

How long we keep it

Your records stay until you delete them or close your account. Deleting your account removes them permanently — see below. Error reports and traffic analytics are retained on a rolling basis by the providers named above and are not tied to your records.

Your rights

Export. You can download your games, mileage log, and expenses as CSV at any time from the Reports page. Your data is never held hostage.

Deletion. You can delete your account from Settings. This permanently removes your account and every record attached to it. It cannot be undone.

Access and correction. Everything we hold about you is visible and editable in the app. If you want a copy in another form, or have a question we haven't answered here, write to us.

Children

Fourth Official is not directed to children under 13, and we do not knowingly collect their data. Referees you log as crew members may be minors — treat the contact details you save about them accordingly, and enter only what you need.

Changes to this policy

If we make material changes, we'll update the date above and notify you in the app before they take effect.

Contact

Questions about your privacy, or a request about your data? Email support@fourthofficial.net.