Privacy policy
Last updated 20 August 2026
Longscore has no accounts. There is nothing to sign in to, and we do not ask for your name or email address.
What your device keeps
The app keeps these things on your phone:
- the competitions you follow
- the teams you follow
- the matches you star
- the matches you turn alerts on for
- a random id that match alerts use
- your sort choice: by competition or by time
The site keeps the same kind of data in your browser: the competitions and teams you follow, your stars, and your sort choice. Match alerts exist only in the app.
This data stays on your device. If you clear the site data for longscore.app, or delete the app, the data is gone. We keep no backup. Match alerts also use the server records described in "What our servers keep" below.
Cookies
We set no cookies of our own. The ad code on the site sets its own cookies. The "Advertising" section below explains what our ad partners use them for.
What our servers keep
We keep a copy of the match data on our servers, and every visitor shares that copy. There is nothing personal in it.
When the app or the site loads matches for your teams or your stars, the request includes those team and match ids. We use the ids to answer the request, and we do not keep them.
If you turn on match alerts in the app, we keep an anonymous record for your copy of the app. The record holds a random id, a push token (the address an alert is delivered to), your platform, and the ids of the matches you want alerts for. No name or email address is attached to it.
We delete each alert request after its match ends. We keep delivery records for fourteen days. A delivery record says which alert went to which copy of the app. If the app does not check in for ninety days, we delete its record and its push token. Turning off your last alert does not delete the record. Deleting the app stops the check-ins, so the record is deleted ninety days later.
What our host can see
Our host logs the basic facts of each request: your IP address, your browser or app version, the page you asked for, and the time. We use these logs to keep Longscore running and to find out why something broke. We do not build profiles from them, and we do not link them to anything else.
How we count visits
On the site, we count page views with an analytics service. It sets no cookies and stores nothing in your browser. It turns each visit into a random code, and it deletes that code after twenty-four hours. So we cannot recognise you from one day to the next, and no other site can recognise you either.
A page view stores:
- the time and the page you looked at
- the page you came from
- your rough location, down to the city
- your browser, your operating system, and your device type
Your IP address is not stored with a page view, and nothing ties a page view to a name. We use these counts to see which competitions people use and which pages are broken.
Other services
Club crests and competition badges come from an image cache we run. It holds copies of the images that our data supplier publishes. The server that sends you an image sees a normal image request. Nothing in that request says who you are.
The site serves its own fonts from longscore.app. No font request goes to Google.
If you turn on match alerts, our delivery service hands each alert to Apple or Google, and they deliver it to your phone. They receive the push token and the text of the alert.
Ad code loads on every page of the site, so your browser also talks to our ad partners' servers.
Advertising
Ads pay for the cost of running Longscore. On the site the ads come from Google and from other ad partners. In the app they come from Google only. Google is still reviewing the site, so you may not see ads there yet.
When ad code runs on the site, the ad partner sees your IP address, the page you are on, and your browser details. It can also read and set cookies in your browser. It uses all of this to choose which ad you see and to count the ads it showed. We send our ad partners no data of our own.
The app shows one ad at the bottom of each board. When that ad loads, Google receives your device's advertising id, your rough location based on your IP address, and the screen you are on. Google uses this to choose the ad and to count that it was shown. We send Google no data of our own.
On iPhone, the app never asks for permission to track you. Ads in the app are matched to the screen you are on, not to you.
Google explains what it does with this data in how Google uses information from sites that use its services.
If you are in the UK, the EU, or Switzerland, you are asked for your consent before any of this happens. If you say no, you still see ads, but they are matched to the page instead of to you.
The app asks the same consent question before it loads any ad. You can change your answer at any time in Settings, under "Ad privacy choices".
Your rights
We hold no name, no email address, and no account for you. If you use match alerts, we hold the anonymous records described above. The data on your device is yours to clear at any time. If you want to know what a record holds, or want it deleted, email us.
Google keeps its own record of the ads it showed you. In Google's My Ad Center you can see that record, change what Google uses, or turn off personalised ads on every site that shows Google ads.
Our other ad partners keep their own records. You can turn off personalised ads from most of them in one place: Your Online Choices in Europe, or YourAdChoices in the United States.
Changes
The date at the top shows when this page last changed.