What the fan app stores
Your favourite team, alert choices, onboarding state and display preference are stored on your device. The app does not require a fan account and does not upload those preferences to a fan profile database.
Notifications
If you enable alerts, the app uses Firebase Cloud Messaging to subscribe your device to public team topics. Firebase processes a device messaging token to deliver fixture reminders and match updates. Notifications contain public tournament information only.
Website and tournament information
The website reads public fixtures, scores, tables, team profiles, news and media from Firebase. Manager and administrator contact details, draft content and internal notes are not part of the public fan data feed.
Optional YouTube broadcasts
Cup TV automatically retrieves public channel information through a shared server cache to show active broadcasts and recent videos. Video thumbnails load from YouTube’s image service. The video player connects only after you choose to watch. Playback comes directly from YouTube using its privacy-enhanced embed service, not from Firebase. YouTube may process information about your device and playback under Google’s privacy policy. No YouTube account details are requested or stored by this website. You can use the rest of this website without loading the player, or choose the separate link to watch on YouTube.
Website match alerts
Website match and favourite-team alert choices stay in your browser. Alerts use the public live data already received by the page; no fan account or server-side messaging subscription is created. Keep both the browser and the tab open and connected. Closing either stops these website alerts, and your device may pause background or locked-screen tabs. Device notifications require your permission and browser support; otherwise updates appear in the open tab.
Optional fans’ player voting
If the tournament enables Fans’ Favorite voting, you can choose one shortlisted player per match. Voting is optional and separate from the official Player of the Match award. Staff choose either browser-based voting or verified-email voting before a ballot opens. Published results show aggregate totals, not individual voters.
Browser-based voting does not require an account or email address. A random voting identifier stays in your browser; a different match-specific token is sent to check and record your vote. The server keeps a hashed receipt and your player choice with the ballot to prevent repeat submissions.
Where verified email is required, Firebase Authentication sends you a sign-in link to confirm that you own the address. No voting password is needed. Firebase keeps an email sign-in account and a separate voting session on your device. This does not grant backend or manager access. Voting records use match-specific hashes of the verified email and account identifier, not your raw email. This lets us prevent the same verified email or account voting again from another device. Common Gmail dot and plus aliases count as the same address. Verification is for voting, not consent to marketing emails; an email address is not proof of a unique person.
Abuse controls also use a hashed network-address identifier for rate limiting; raw IP addresses are not stored in voting records, although infrastructure providers may process standard network logs. Voting receipts are retained with the ballot. Browser storage and private browsing can affect browser-based duplicate detection. In verified-email mode, the same verified address remains limited to one vote per match across browsers and devices, but someone controlling multiple addresses may still vote again. Your final vote cannot be changed. Disabling the feature hides ballots and stops new votes without deleting recorded results.
Daily visit reporting
We count the same browser on this site once per Barbados calendar day, including repeat visits, reloads and other tabs. A random anonymous browser identifier stays in your device's local site storage; only a different daily token is sent to the visit counter. Daily receipts prevent duplicate counts. We do not attach names, email addresses, favourite teams, page histories or device fingerprints to visit records. The visit counter does not store IP addresses; hosting providers may process standard network logs to operate the service. Daily aggregate counts are retained; deduplication receipts expire after three days through the database retention policy. Counts estimate browsers, not identifiable people or physical devices: different browsers, private sessions and cleared site data can count separately. Browsers with blocked storage are not counted. Historical visits before collection began are unavailable.
We respect browser Do Not Track and Global Privacy Control signals. You can also opt out here:
Optional website analytics
With your permission, Google Analytics helps us estimate unique visitors over a selected date range, sessions, page views and engagement. It also provides broad country, device and traffic-source reports. These are estimates of browsers and devices, not a verified count of people: using another browser or device, clearing cookies, privacy tools and declining analytics can affect the totals. Daily visitor totals must not be added together to claim unique visitors for the whole tournament.
We do not load Google Analytics before you opt in. If enabled and accepted, Google processes browser identifiers, technical device information and network information under Google’s privacy policy. We send only approved public page paths and broad competition categories, not names, emails, account identifiers, setup links, search text or private portal information. Advertising personalisation and Google Signals are disabled in our collection settings. Staff browsers are excluded after a successful portal sign-in. Do Not Track, Global Privacy Control and your daily-reporting opt-out also prevent optional analytics collection.
You can change your choice at any time. Declining does not affect fixtures, live updates or other site features. Revoking permission stops future optional analytics and clears this site’s Google Analytics cookies; it does not erase previously aggregated reports.
Checking this browser’s analytics preference…
Permissions
The Android app asks for notification permission only after you choose a favourite team or enable alerts. Calendar and sharing actions open Android’s standard apps; the Cup app does not silently modify your calendar or contacts.
Service providers and retention
Firebase provides database, hosting and messaging infrastructure. Short-lived delivery records support reliable, duplicate-free alerts and are stamped with an expiry time for the production retention policy. Your device controls its local app data; uninstalling the app removes those local preferences.
Your choices
- Turn fixture or score notifications on or off independently in app settings.
- Change or clear your favourite team at any time.
- Use the website without creating an account.
Contact
For privacy questions or correction requests about published tournament information, email info@theprimeministerscup.bb.
Effective date: 24 October 2026.