Privacy policy

Who runs it

LawFive is run by Scott Roach, a sole proprietor in California, doing business as LawFive ("we"). Questions go to privacy@lawfive.app.

If you use your own server

LawFive is open source, and the apps can connect to a server that someone else runs. If yours does, this policy doesn't apply to it: whoever runs that server decides what happens to your data, and we never receive it. Ask them for their policy. The one exception is notifications: if you turn them on, your phone's notification token and your server's address pass through our push relay, as described under Who else sees it, and only that part of this policy applies. Whoever runs your server can switch this off.

What we keep

• Your account: name, email address and a hashed password, and your settings such as units and currency.
• Your matches: teams, kickoff times, venues, competitions, templates, the score, goals, cards and injuries with player numbers, notes, tags and fees.
• Other people's details that you enter: names, email addresses and phone numbers of referees you work with, and team names. Only add what you have a right to keep.
• Location: the GPS track your watch records during a match, the pitch corners you mark, kickoff direction, and the places you save for venues.
• Heart rate: the readings your watch records during a match, the maximum heart rate you set, and the figures worked out from them. In some places this counts as health data; we only keep it because you chose to record it, and you can turn track recording off on the watch or delete a track at any time. On an Apple Watch the readings come from Apple Health during the match, and on Wear OS from the watch's health service. Apart from those readings we read nothing from Apple Health or Health Connect.
• Photos you add to matches, venues and referees. The apps make them smaller before uploading, which removes where they were taken and the camera's details.
• Devices: each signed-in browser, phone and watch, with its name, type or model, software version and when it was last active, which you can see and sign out in Settings.
• Notifications: if you turn on weather risk notifications, a sealed code for reaching your phone, kept with that phone's sign-in, and which risks you've already been told about for each match, so you're told once.
• How a recording went: with each match from a watch, its battery level at kickoffs and period ends, app and watch software versions, restarts and GPS quality. We use this only to trace problems.
• Server logs and limits: your IP address, used briefly to limit repeated attempts such as wrong passwords, and in server logs kept for 30 days.
• Sign-in locks: an email address typed with a wrong password, with a count and the time, to lock it for a while after repeated tries. It's forgotten after a day without a wrong password.

Why, and on what basis

• To provide the service you asked for: keeping your record and syncing it across your devices (performing our contract with you).
• To keep it secure and working, such as limiting attempts and tracing faults (our legitimate interests).
• To record heart rate and location, which you choose to do (your consent, which you can withdraw by turning recording off or deleting the data).
• To save each match to Apple Health (from an Apple Watch) or Health Connect (from the Android app, for a Wear OS watch) as a workout, if you allow it. That copy stays on your devices; we never see it, and you can switch it off in the app.
• To send email about your account: invitations, approvals, password resets, a warning when wrong passwords lock your sign-in, notice before a plan ends, and notice of changes to your plan, the service, our terms or this policy. We don't send marketing without asking.

Who else sees it

We don't sell your data or share it for advertising. These services help run LawFive:

• Cloudflare, which sits in front of the service and this site.
• Advin Servers, whose server in Los Angeles runs the service and its database for us.
• Backblaze, which keeps our backups in the western United States. They're encrypted before they leave our server, and only we hold the key.
• Resend, which delivers account email.
• Open-Meteo, for weather. The server asks for a rough place, a square about 5 km across around your venue, not who you are.
• OpenStreetMap's Nominatim, for address search. The server sends what you type, not who you are.
• Map providers: OpenFreeMap, and a satellite imagery provider where it's turned on. Your browser or phone asks them directly for map pictures, so they see your IP address and the area you're viewing. The iPhone and Apple Watch apps use Apple's maps instead.
• Our push relay and Google's Firebase Cloud Messaging, only if you turn on notifications, on Android for now. Your phone gets a token from Firebase. Our relay, which runs on Cloudflare, seals that token together with your server's address, and doesn't keep a copy. Each notification tells Firebase only its type and a random ID for the match, never names, teams, places or the forecast; your phone then asks its own server for the details. Firebase sees your phone's token and that a notification went to it, under Google's terms. The relay keeps a scrambled form of the token and your server's address to count the day's notifications, which is cleared the next day. If a server reaches the relay's limit, or tries to use it while blocked, the relay notes that server's address in its logs, once a day, never anything about you or your phone. There's no advertising or analytics in this.
• Garmin: if you use a Garmin watch, its sync passes through Garmin Connect on your phone, and the activity it records is yours in Garmin Connect, under Garmin's own privacy policy. Apple and Google likewise run the devices and stores you get the apps from. On Android, scanning a QR code uses Google's code scanner.

Your data stays private unless you share it: a share link shows a reduced copy of one match to anyone who has the link, until you turn it off. Webhooks and API keys send your data where you tell them to. We may disclose data when the law requires it.

Cookies and browser storage

LawFive uses one cookie. When you sign in on the website, a session cookie, named __Secure-better-auth.session_token, keeps you signed in. The website can't work without it, the page's scripts can't read it, and it lasts 90 days, renewed each day you use LawFive. Signing out removes it. There are no analytics, advertising or tracking cookies. This site and the docs at lawfive.dev set no cookies, and the phone and watch apps don't use them: they keep their sign-in in the system's protected storage. The one exception is Cloudflare, which protects the service, this site and the docs from attacks: if a visit looks automated, Cloudflare first asks the browser to show it isn't, and one that passes gets a cookie named cf_clearance, so it isn't asked again for 30 minutes. It's there only to protect the service, not to track you, and ordinary visits never get it.

The website and this site also remember a few of your choices in your browser's local storage, which stays on your device and is never sent to us: which tips you've seen and notices you've closed, the map layer you chose, how you last filtered your matches, and, on this site, the match screen you set up in Try a match and how far you got in its tour. Clearing this site's data in your browser removes them.

As the cookie is needed to sign in, and the rest only remembers what you chose, there's no cookie banner asking for consent.

How long we keep it

Until you delete it or your account. Sign-in sessions end after 90 days without use, invitations after 14 days, and password reset links after an hour. Turning notifications off or signing out removes what reaches your phone, and the sealed code stops working after 90 days unless the app renews it. Deleting your account removes everything in it straight away, and copies in backups go within 30 days. See how to delete your account.

Your rights

You can see and correct your data in the apps, download all of it with Download everything (Settings → Account on the website), and delete it. Depending on where you live, including under GDPR, UK GDPR and California law, you may also have the right to object to or restrict how we use it, to withdraw consent, to know what we keep, and to complain to your data protection authority. We don't sell or "share" personal information as California law defines it. To ask for anything here, write to privacy@lawfive.app.

Young referees

LawFive isn't aimed at children. You must be at least 16 to have an account, wherever you are, and anyone under 18 should have a parent's or guardian's permission. If we learn that someone under 16 has an account, we'll delete it. Personal information that identifies anyone under 16, such as their name, photo or contact details, isn't allowed in LawFive (the terms); team names, age groups and shirt numbers are fine, so if you referee youth matches, record players by shirt number.

Security and where data lives

Data travels over HTTPS, passwords are hashed, and sessions on phones and watches are kept in the system's protected storage. No service is perfectly secure; if something goes wrong that affects you, we'll tell you as the law requires. Data is kept in the United States. If you're elsewhere, you send it there when you use LawFive, and it's protected as this policy describes.

Changes

If this policy changes in a way that matters, we'll say so in the apps or by email before it takes effect.