Privacy Policy
EFFECTIVE 6 OCTOBER 2026
EIHL Tracker (the "Service") is an unofficial, fan-made app and website for the Elite Ice Hockey League. This policy covers both the mobile app (Android and iOS) and the website at eihltracker.co.uk. The short version: there are no accounts, we don't show ads, we don't sell data, and we don't share data with third parties for marketing. The mobile app keeps a small backup of your club, theme and tips seen against a random install identifier, and if you turn on notifications we store a small amount of data about your device so we can send them. You can delete all of it at any time.
What we collect
There are no user accounts, sign-ups, or sign-ins. We do not collect names, email addresses, phone numbers, payment details, or contacts. The mobile app does not ask for access to your microphone, camera, or photos. It asks for your location only when you tap Check in at the rink, and never stores it (see Venue check-ins below).
These narrow categories of technical data are involved:
•
On-device settings (app and website). Display preferences such as your selected season, competition toggles and view options are stored on your device only. They aren't sent to our servers. The exceptions are the app settings backup and the notification settings, covered next and below. The website likewise keeps its display preferences, and when you last closed its get-the-app banner, in your browser's local storage; neither is sent to our servers.
•
App settings backup (mobile app). Whether or not you use notifications, the app keeps a copy of your club, your theme (system, light or dark), and which in-app tips you have already seen on our server, against the anonymous install identifier described below, each with the time you last changed it, so a reinstall brings them back. Nothing else from your display preferences is copied. It is deleted with your device if you delete your data, as described under Notifications below.
•
An install identifier, sent with requests (mobile app only). The mobile app sends the random install identifier described under Notifications below as a header on its API requests, whether or not you use notifications. It is used for one thing: so our servers can apply rate limits fairly between devices sharing the same network, such as at a rink or on a mobile carrier, instead of treating everyone on that network as a single client. It is not used to build a profile, it is not shared with any other party, and the website does not send it at all.
•
Shared and saved Player Cards (mobile app). If you use Player Cards, the cards you share or save are kept on our server against your anonymous device so they appear in your collection. You can remove any of them from the collection. They are deleted with your device if you delete your data, as described under Notifications below.
•
Venue check-ins (mobile app). If you use Player Cards and tap Check in at the rink, the app reads your location once, at that moment, and sends it to our server, which compares it with the rinks' locations and the fixture list and then discards it. Your location is never stored or logged, on our server or on your device, and the app never reads it in the background or at any other time. What is kept, against your anonymous device, is which rink you checked in at, the date and the match, so your Venue cards appear in your collection. It is deleted with your device if you delete your data, as described under Notifications below.
•
Server logs (both surfaces). Our backend records standard HTTP request metadata (IP address, request path, user-agent, timestamp) for operational and security purposes. When a request is rate limited we also record a short, one-way hash of the install identifier above, which is enough to spot a single device making too many requests but cannot be turned back into that identifier. The identifier itself is not written to these logs. They are retained for a short period (typically no longer than is needed for operational review and security investigation) before being rotated out, and used only to keep the Service running and diagnose problems.
•
Aggregate web analytics (website only). The website uses Plausible Analytics, a privacy-focused, cookieless service that produces anonymous aggregate counts (pageviews, referrers, country, device class). Plausible does not use cookies, does not track individuals across sessions or sites, and does not retain raw IP addresses. On the get-the-app page, taps on the App Store and Google Play buttons are counted as well, and so are taps on the GET and close buttons of the website's get-the-app banner, all as anonymous totals with no identifiers.
•
Crash and performance reporting (mobile app). The mobile app uses Sentry to collect crash reports and aggregate performance data (cold start, screen transitions, slow frames). The SDK is configured to collect no personal information: no user identifiers (the app has no accounts), no contact data, no recorded user input. IP addresses are scrubbed by Sentry before storage. Data is used only to diagnose stability and performance issues.
Notifications (mobile app)
The app can send notifications about the teams you follow, and about the app and the league. To make that possible we store the following on our servers:
•
An install identifier. A random identifier the app generates on first launch. It is not derived from your device, your hardware, or anything about you, and it is not shared with anyone. On iPhone it is kept in the device's Keychain, so reinstalling the app on the same iPhone keeps it and the choices linked to it; it never moves to another device. On Android, reinstalling produces a new one and leaves the old data unreachable, unless Android restores the app's data from your device backup. The app also sends it with its API requests for rate limiting, which is covered above and happens whether or not notifications are on.
•
A push token, issued by Apple, but only once you turn a notification on. Without it there is no way to deliver a notification to your device.
•
Your notification choices. Which teams you follow, which types you want (goals, game start, final score, Lock Screen activities), any per-game changes, and whether you want app updates and league news. Also whether you have answered the notifications prompt, so a reinstall brings it back.
•
Basic device details. Platform, OS version, app version, and the app's own storage location on your device, which is used to show team crests on notifications.
This is not linked to your name or to any account, because there are none. We do not use it to build a profile of you, to track you across other apps or websites, or for advertising.
App updates and league news are off unless you turn them on. We will not send you anything promotional unless you have asked for it, and you can turn it back off at any time under More, then Notifications.
Deleting it. Email us at the address below and we will delete your device and everything above from our servers. Where notification settings are available in your version of the app, More then Notifications also has a Delete Notification Data control that does the same thing straight away.
What we don't do
•
No advertising or marketing trackers.
•
No third-party SDKs collecting your behaviour for marketing, sale, or profiling.
•
No selling, renting, or trading data.
•
No advertising profiles, no cross-app tracking, no device fingerprinting.
App updates
The mobile app uses Expo's over-the-air update infrastructure to deliver app updates. Expo's update servers receive standard request metadata (app version, platform, runtime version) when the app checks for or downloads an update. See Expo's privacy policy for their handling of update-check traffic.
League data
The statistics and match information shown in the app are derived from publicly-available data published by the Elite Ice Hockey League. We do not represent or speak for the league; EIHL Tracker is an independent fan project.
Children
The Service is suitable for all ages. There are no accounts and we never ask anyone for their name, age, or contact details, so we do not knowingly hold identifying information about children.
Changes to this policy
If we change how we handle data, we will update this page and update the "Effective" date at the top. Material changes will be announced in the app's release notes.
Contact
Questions about this policy, or requests to see or delete data we hold about your device, can be sent to
[email protected].