Sign in with Google to use your free Badminton Hub account. Your saved matches automatically sync to your account on Cloudflare. Other players cannot open your private scorecards.
Match cards include team and player names, dates, scores, signatures and league upload status. Your Google account identifier, email address and display name connect those cards to your account. Google sign-in requests only your basic profile and email, not access to Google Drive, Gmail or private spreadsheets. Public league spreadsheets supply fixtures, players and venues separately.
New club cards save to their team’s shared space by default, visible to the club admin and the sub-captains assigned to that team. Existing private cards remain private. Separate local copies are kept for each account and shared team on each device. Choosing “Share with team” creates a separate shared copy; later edits to that copy do not change the private original. Changes save locally first and automatically upload after a short pause while the app is open and online. Check for “Saved to cloud” before relying on another phone. Sign in on another device to load your cards automatically. Offline edits sync when the app reconnects or reopens. If two devices edit the same card, different versions are kept separately.
A previously signed-in device can use its offline copy without internet for up to 30 days. Protect your device with its screen lock. Signing out hides your cards and stops uploads but keeps the account's local copy for the next sign-in. This local copy is not encrypted by the app.
The League area reads public fixtures, results, standings and published cumulative player statistics from LeagueRepublic. This public data is cached on Cloudflare and on your phone so it can be shown during outages. Your scorecards, signatures and sign-in details are not sent to LeagueRepublic. Following an official match or statistics link opens its website.
Your captain name, chosen teams, leagues, divisions and per-team reminder preferences are stored with your account. Choosing a team does not give other captains access to your private cards.
Notifications are optional and require your permission on each device. We store that device’s Web Push subscription address and encryption keys so Cloudflare can send encrypted messages through your browser’s push provider (such as Apple, Google or Mozilla). Reminders can include team names and that a card needs uploading; these may appear on your lock screen.
Fixture-change alerts show the old and new dates when a change is found in the official league sheet; recent changes remain visible in the app for 30 days. Game reminders start at 9am UK time the day before and on match day if selected. The upload reminder is due 24 hours after all rubbers have a result, unless you mark the card uploaded. Offline changes must reach the cloud before the service can act on them. Delivery depends on your phone, internet connection, notification settings and hosting limits. Reminder delivery records are kept for up to 30 days after expiry. You can turn off this phone’s subscription or change reminder preferences under My club. Signing out stops reminders for that browser session.
Private cards are visible only to their account through the app. Shared team cards, including names, scores and signatures, are visible to the club admin and the sub-captains assigned to that team. The club admin can view fixtures and shared cards across all their club’s divisions; sub-captains can access only assigned shared teams. Selecting one team during initial captain setup creates your club workspace and includes its other teams from the league list. Selecting a league team does not automatically join another captain’s shared space. Invitations are bound to the recipient’s Google sign-in email, expire after seven days, and may be revoked. Invitation tokens are stored as hashes. Team members can see each other’s names and email addresses. A captain can remove a sub-captain’s future cloud access, but previously downloaded or exported copies cannot be recalled. The app owner administers the Cloudflare database and can access the stored data. Connections use HTTPS; scores are not end-to-end encrypted.
The owner-only admin portal lists registered names, email addresses, join dates and team assignments. The app owner can correct names, assign or remove sub-captains, sign accounts out and suspend or restore cloud access. Administrative changes are recorded with the acting owner, target account, action and time. Suspension does not erase copies already downloaded to devices.
Every scorecard is a shared team card. The team’s captains and sub-captains and the club admin can see it. Only the person who entered a card can change or delete it; everyone else sees it view only.
If you do not use Google, you can create an account with your name, email address and a password. The Hub never stores your password itself, only a scrambled code made from it that cannot be turned back into the password. We email you a link to confirm your address and, if you ask, a link to reset your password; these emails are sent through Cloudflare’s email service. Until your address is confirmed you cannot accept invitations sent to it.
Current cards remain in your account until you delete them. Moving a card to the bin syncs to the other phones using that space. The card is kept in Recently deleted for 30 days; shared cards are recoverable by current team members. Cloud deleted-card records are cleaned by the scheduled task, and expired local entries are cleaned when Recently deleted is opened. Undo/redo history stays in memory for the current editing session. An earlier private version may also remain in account recovery history. The app keeps one automatic recovery copy before the first change each day, for up to 30 days, cleaned up when you next sync. Earlier backups from the previous app remain available. Restoring keeps current cards and adds differing versions separately.
Each private or shared space supports up to 200 cards and 1.5 MB per sync request, including signatures. An account can captain up to 50 teams, each with up to five invited sub-captains. If a limit is reached, the app shows a pending sync message and keeps local changes. Export older cards under Saved before removing them.
Club night organisers add players by name. The Hub keeps each club’s player names, the games they played on club nights, and a rating that is updated from the results, used to pick fairer games. Organisers see a level (A, B, C or New), not the rating itself. Club night data is visible only to that club’s admin and captains. Ask your club admin if you want your name and club night history removed.
To recognise the same person on league scorecards and at club nights, the Hub keeps one record per player in each club: their name and the other spellings used for it. These come from the names typed for your own club’s side of scorecards and from club nights; opponents’ names are not turned into records. The club admin can correct, merge or mark these records inactive.
A player can sign in and ask to be linked to their club player record. The club admin, or a captain of one of the club’s teams, approves each request, so nobody can claim someone else’s record. A linked player sees only their own results, partners and level, their teams’ upcoming matches and their calendar link. They cannot see other players’ levels or change scorecards. A player can unlink their account at any time under My badminton; their results stay with their club, and the club admin can remove their record on request.
Players under 18 are linked only after the club admin confirms that a parent or guardian agrees. A junior’s results and level are seen only by the junior and their club admin; they are left out of club night stats shown to captains, and captains cannot open a junior’s player page.
A team’s captain or club admin can ask the squad who can play a league match. The squad is everyone who has played for the team this season, plus anyone the captain adds. Players reply in the Hub, or the captain records a reply given elsewhere. Replies and the chosen line-up are seen only by the team’s captains and the club admin; each player sees their own reply and whether they were picked. Players who turn on match alerts get a notification on that phone. Messages shared in WhatsApp go through WhatsApp, not the Hub.
The Hub can suggest a line-up from this season’s results. If the captain asks for an explanation, the names, levels and results of the players involved are processed by the same AI model as the badminton helper; juniors are never described to it.
A linked adult player gets a short written overview of their own recent results on My badminton, which their club admin can also see. To write it, their results (and the names of the club partners they played with) are processed by the same AI model as the badminton helper, at most once a day after new games. Players under 18 get no overview, and their names and results are never sent to the AI.
A club can split club nights into groups (for example Intermediate and Intermediate+/Advanced). Organisers see which group each player is in, who said they are coming and who is checked in. The Hub may suggest who could move up or down a group from club night results; if the organiser asks for an AI explanation, those players’ names and club night records are processed by the same AI model as the badminton helper (juniors are never named to it).
When you ask the badminton helper a question, your question and the player stats shown with it (team and player names, results and partnerships from your scorecards) are processed by an AI model (Google’s Gemma) run on Cloudflare’s Workers AI service, which already hosts the Hub, to write the answer. The Hub keeps only a count of how many questions you asked each day, to limit use. Answers can be wrong and are not medical advice.
Players are not charged to use this app. Hosting uses Cloudflare's free allowances; these have daily usage and storage limits. If a hosting limit is reached, cloud saving may be unavailable until capacity is available again. Local scoring and manual exports remain available on a signed-in device.
You can export or restore files under Saved. Contact the person or club that provided this app to request deletion of your account, cloud cards and recovery history. Deleting an account removes its sign-in, private cards, backups, team access and alerts; shared team scorecards and the club’s player record and results stay with the club, no longer linked to you, unless you also ask for those to be removed. Uninstalling the app does not delete cloud data.