Footy Scores for Wear and for Watch

Privacy Policy

Last updated 22 August 2026 · Jonathon Denholm, Melbourne, Australia

The short version

The app does not collect anything about you. There is no account, no sign-in, no analytics, no advertising, no crash reporting and no tracking of any kind. Nothing you do in the app is sent to me, and I have no way to identify you or your watch.

This page is not short because it says nothing. It is short because there is nothing to say, and the rest of it is spent being specific about the few things that do leave the watch, rather than padding a page that could have been three lines.

What the app stores

Three things, on the watch, in the app's own private storage:

The club you picked, as a short abbreviation such as COLL.
The dates you opened the app during the free trial, as a list of plain dates. This is how the fourteen-day trial is counted. It records the date only, with no time and no record of what you looked at.
Whether you have unlocked the app, as a yes or no.

The app also keeps a cache of the score data it last downloaded, so it can show you something when the watch is out of signal. That is a copy of the same public football data anybody can fetch, and it holds nothing about you.

All of it is removed when you uninstall the app. There is no server-side copy, because there is no server.

One qualification, which is the platform's doing rather than mine. Both apps allow the operating system's own backup to run. On Android, if you have backup enabled, Google may copy the app's stored settings into the backup held against your Google account. On Apple Watch the same is true of iCloud backup.

In both cases the backup belongs to you. It is governed by Google's or Apple's privacy policy rather than this one, and I have no access to it.

What leaves the watch

To show scores, the app makes requests to five places, all over HTTPS.

Every outbound request the app makes.
Who	What for	What they receive
ESPN `site.api.espn.com`	Live scores, match detail, goals, the ladder	Your watch's IP address, the time, and the address of the score page requested
Squiggle `api.squiggle.com.au`	Fixtures and the ladder, as a fallback when ESPN is unavailable	The same, plus a header identifying the app (see below)
AFL `aflapi.afl.com.au`	Fixtures, scores and the ladder, as a further source when ESPN is unavailable	Your watch's IP address, the time, and the address of the page requested
AFL `api.afl.com.au`	Live scores for women's matches, which the address above does not carry until the final siren. The app first asks this host for a short-lived access token, then uses it to read the round being watched	Your watch's IP address, the time, and the address of the page requested
GitHub Pages `footyscore.app`	A small settings file, which lets me change how often the app refreshes, or switch a broken data source off, without shipping an update	Your watch's IP address and the time

Yes, this means ESPN, Squiggle and the AFL see your IP address. Any request to any website does. It is how a reply finds its way back to you.

I am naming it because a privacy policy that says "we collect nothing", while the app quietly talks to three large third parties, is not telling you the truth.

Those requests carry no name, no account, no device identifier and no advertising ID, only the ordinary metadata of an HTTP request.

What ESPN, Squiggle and the AFL do with their own server logs is governed by their policies, not mine.

The request to Squiggle carries a header identifying the app: Footy Scores for Wear - jonathon.denholm@gmail.com, or Footy Scores for Watch - jonathon.denholm@gmail.com from the Apple Watch app. That is my email address, not yours.

It is there because Squiggle's terms of use ask every caller to identify itself and leave a contact. It tells Squiggle which app is calling, and nothing about who is wearing the watch.

The request to footyscore.app fetches a fixed settings file. It sends nothing about you, and the file it downloads is the same for every user. It happens at most about four times an hour.

That file is served by GitHub Pages, so GitHub receives the request, not me. GitHub's handling of it is covered by GitHub's privacy statement.

The domain is mine. The machine is not, and no request from the app goes to any computer of mine.

No request from this app ever goes to a server that reports back to me about you. I do not run the score APIs and I do not see their logs. I do not run any server at all: the settings file sits on GitHub Pages, and I am not given its access logs.

Purchases

The app is a one-off purchase. On Wear OS it is made through Google Play Billing, and on Apple Watch through Apple's In-App Purchase.

Whichever store you bought from handles the entire transaction. Your payment details are entered into Google's or Apple's systems and never touch this app or reach me. I never see a card number, a billing address or a name.

Each store gives me the sales and payout reporting every developer gets in its console. Their handling of your purchase is covered by Google's Privacy Policy and Apple's Privacy Policy.

Inside the app, the result of a purchase is stored as the single yes-or-no flag described above.

What the app cannot do

Worth stating plainly, because these are the things people reasonably worry about on a device worn against the skin.

On Wear OS the app declares five permissions: internet access; the ability to read which network the watch is on, and to ask the platform for the watch's own wi-fi when the phone has walked out of range; Google Play billing; and permission to post a notification, which is how a goal alert reaches your wrist. That last one is asked for at the moment you switch alerts on, and it lets the app send you a notification. It does not let it read yours. On Apple Watch the app asks for none at all beyond making network requests and buying the unlock.

It therefore has no ability to read any of the following.

Location
Heart rate
Steps and workouts
Any health or fitness data
Contacts
Calendar
Messages
Notifications sent to you by anything else
Call history
Photos and files
Microphone
Camera

It has no access to anything else on the watch, or to your phone.

On Wear OS a sixth entry appears in the app's technical manifest, DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION. It is added automatically by Android's own support libraries, it is a permission the app defines for itself so that other apps cannot reach one of its internal components, and it grants access to nothing.

Children

The app is not directed at children and collects nothing from anyone, of any age.

Your data rights

There is no personal data held about you to access, correct, export or delete, because none is collected. Deleting what the app has stored is done by uninstalling it.

If you believe otherwise, or want to ask about any of this, write to me and I will answer.

What this policy does not claim

I would rather be accurate than reassuring, so, plainly:

I do not claim to control what ESPN, Squiggle, the AFL, GitHub or Google do with the requests and transactions they receive. I have named them so you can read their policies.
I do not claim any special security measure beyond the ordinary. Requests use HTTPS, and the app's stored settings sit in the private per-app storage that Android and watchOS give every app. There is no additional encryption scheme, because there is no sensitive data to protect.
I am not affiliated with, endorsed by, or connected to the Australian Football League, ESPN or Squiggle. Score data is third-party, unofficial, and can be late or wrong.

Changes

If this ever changes, I will update this page and change the date at the top. That means if the app gains a feature that collects something, or if a data source changes. The app collecting nothing is a design decision, not an accident, and I do not expect it to change.