1. Who we are
This policy covers the Badminwear Wear OS app, account website, recording service, and live-score viewer. “We” and “us” mean the operator of Badminwear, responsible for the personal data described here. The data we handle depends on the features you use and the permissions you grant.
Badminwear is operated by Aleksander Rist, Solbrinken 48, 2750 Ballerup, Denmark.For privacy requests, account deletion, or questions about these terms, email inquiry@badminwear.tech.
2. Your choice: Lite mode
You can enable Lite mode to use Badminwear without logging in. Lite mode disables live scores and microphone recording. You do not need to create an account or pair your watch with a web account to use this mode.
Lite mode does not broadcast your score or capture microphone audio. Other watch features may still use local match data and the activity or heart-rate permissions relevant to those features. Enabling Lite mode does not delete an existing account, previously uploaded recordings, or copies of scores that other people have already seen. See the deletion and rights sections below.
3. Data we handle
Accounts and watch pairing
If you create an account, we receive your name, email address, and password. We store a password hash, rather than your readable password, together with an account identifier and creation/update times. Signing in creates a session with an identifier, expiry, last-used time, and revocation status. Pairing uses a randomly generated watch installation identifier, a short-lived pairing code, and tokens that link the watch to your account. The watch name sent with a match contains the device manufacturer and model.
Matches and recordings
Connected recordings include a match identifier, watch name, start and end times, duration, and completion status. Scoring data includes which side won each point, when points and sets were won, and the match winner. A completed match’s scoring timeline is saved with its recording.
You can save private player names and link those player records to games as teammates or opponents. These records belong to your account, not to other registered accounts. We store the names and game links to organize your history and sync them to your paired watch for offline display. They are not included in public live-score links or administrator game listings. You can rename players, clear game assignments, and delete unreferenced players; deleting your account removes all player records and game links from the server.
During a recorded match outside Lite mode, the watch collects heart-rate readings, acceleration and rotation across three axes, and microphone audio. Motion is sampled approximately 100 times per second and heart rate is represented once per second. The watch converts microphone sound into twelve frequency-band measurements every 10 milliseconds. Only those band measurements leave the watch: the recorded audio itself is never uploaded, stored, or shared. The band measurements and sensor readings are stored in approximately 30-second segments and normally uploaded in batches of four, about every two minutes. Remaining segments are sent when recording ends.
The microphone records sound throughout the recording session, not just racket impacts. Microphone input can include your voice, other people’s conversations, and background sounds. The watch analyses this input on the device and keeps only fixed-reference volume bands (dBFS, not calibrated sound-pressure measurements). The audio is not stored, uploaded, or shared, and no server or third party receives a recording. These band measurements can still reflect sounds unrelated to play. Inform other people on court and obtain any permission required to record them. Use Lite mode where recording is inappropriate.
Website and service data
The account website stores an essential session token and expiry in browser local storage under badminwear_session to keep you signed in. The website also stores your dismissal of its storage notice; a passkey prompt dismissal lasts for the browser session. The live-score viewer asks before storing the selected match, locally entered player names, last score, and resume preferences on your device. If you choose “Only this visit,” those details remain in memory and are removed when the page closes. A storage choice is saved so it can be respected on later visits. Player names you type into the viewer are not sent to the server.
Our servers process connection information, including your IP address, to respond to requests. Application logs record request methods, paths, timing, and errors; live-score rate limits use a hashed IP address for short-lived connection leases. Hosting infrastructure may maintain its own access and security logs. The website does not include advertising trackers or third-party analytics scripts.
Badminwear does not request access to your contacts, camera, or location. Exercise GPS is disabled. Heart-rate access is used for the exercise session, rather than to read your entire health history.
4. What the watch permissions do
- Physical activity: starts and maintains exercise tracking through Wear OS Health Services.
- Body sensors / read heart rate: reads your pulse during exercise. The permission name depends on your Wear OS version.
- Microphone: lets the watch analyse match audio on the device for connected recordings; only the resulting volume bands are uploaded, never the audio. Microphone recording is disabled in Lite mode.
- Notifications and foreground services: shows the ongoing recording and allows exercise and microphone capture to continue when the app is not on screen.
- Internet and network state: connects to account, pairing, upload, and live-score services and retries pending uploads when connectivity returns.
- Wake lock and vibration: supports ongoing work and gives tactile feedback on the watch.
You can manage permissions in your watch’s system settings. Removing a permission can prevent the associated feature from working or stop an active recording. Stopping a recording ends new sensor and microphone capture; previously queued recordings may still upload in the background.
5. How and why data is used
We use account and pairing information to authenticate you, associate recordings with your account, and provide your match history. Recorded data is used to calculate match statistics, including pulse, acceleration, rotation, duration, and per-second charts. Live scoring distributes your scoring timeline to viewers of that match. Technical information helps operate the service, diagnose failures, and protect accounts.
Analysis and model development
Badminwear’s development tools can export stored motion and audio-band measurements for training and evaluating badminton analysis models. Exports retain match identifiers, and audio-band exports retain recording timestamps. Removing your name or email does not make these measurements anonymous. Audio itself is never stored or exported; only the band measurements exist outside the watch. Analysis and coaching features shown as previews may still be in development.
In Account settings, “Allow my data to be used for data modeling” controls whether your recordings may be included in future modeling exports. It is on by default for new and existing accounts. You can turn it off at any time to exclude all your recordings from future exports without affecting your match history or normal account features. This does not remove data already exported or undo prior model training. A default-on preference is not, by itself, affirmative consent.
Use of personal recordings for model development needs a stated purpose and an appropriate legal basis. Accepting the terms of service or granting a device permission does not, by itself, provide separate consent to model training.
Legal bases where the GDPR applies
Providing the account and connected features you request relies on performance of our agreement with you. Service security and troubleshooting rely on legitimate interests in operating a reliable service, balanced against your rights. Processing health data requires an additional legal condition, such as your explicit consent. Where processing relies on consent, you may withdraw it without affecting the lawfulness of processing before withdrawal. We may also process information where necessary to meet a legal obligation.
7. Storage, hosting, and security
The watch keeps match history and a local queue of recordings awaiting upload. A queued segment is removed only after the server confirms receiving it; uploads can resume after a connection failure or after the app closes. Uploaded recordings and account records are stored in a server database. Exports used for analysis may exist separately from that database.
Passwords and server-side session tokens are stored as hashes. The watch encrypts its session token using an Android Keystore key. The account website keeps its token in browser local storage and sends it directly to the API as a bearer token. Website JavaScript can access this token; it is not an HTTP-only cookie. Production connections use HTTPS. These measures do not make the uploaded measurements anonymous: the service can read and process the band measurements it receives. No storage or transmission system can guarantee absolute security.
The account website automatically stores previously viewed history pages, game details, charts and player names in IndexedDB for read-only offline access, bounded to 50 MiB. It stores a random cache-binding marker in local storage, not another credential copy. Cache Storage contains application code, public assets and an API-free shell, never private history or session tokens. Offline access requires the matching saved session to be unexpired. Browser storage can be evicted, so this is not permanent download storage. Edits, watch pairing, account/security and administration require connectivity. Remote session revocation cannot be detected while offline, and access to your local browser profile is not a cryptographic privacy boundary.
The watch app disables Android cloud backup and excludes its local files, database, and preferences from device transfer rules. Device manufacturers may vary in how transfers are handled; copies already made before this change are outside the app’s control.
Hosting provider: Railway. Data is processed in-house by Badminwear.
8. Retention and deletion
- Local recordings: pending segments remain until acknowledged by the server or removed with the local game/app data. Local match history can remain after an upload.
- Completed recordings and accounts: the service currently has no automatic age-based expiry. They remain stored until removed. Signing out, switching to Lite mode, or uninstalling does not delete server copies.
- Discarded or unfinished matches: the watch can request deletion of a discarded match and its uploaded segments. The server has no automatic expiry for unfinished matches, so an interrupted upload can remain until you delete the match or account. A deletion tombstone prevents late offline retries from recreating a deleted match.
- Sessions and pairing: sessions normally expire after 30 days; pairing codes expire after 10 minutes. Expired and revoked records are removed by a periodic cleanup job. Signing out always removes credentials and private offline history on this device, and attempts to revoke the server session when connected. If revocation fails or you are offline, local sign-out still completes but the server session may remain valid until revoked or expired. Expiry is checked before cached history is shown on next startup; deletion code cannot run while the app is closed.
- Live scores: viewers read the current score from the match database. If you chose to remember a match, its last score and player labels remain in that browser until you change your storage choice, clear site data, or replace them.
You can permanently delete your account from Account in the dashboard. The security confirmation and final deletion action remove your account, uploaded games and recordings (including older recordings), scores, watch pairings, and all sessions from the service database. Live score links stop working. There is no grace period or undo. You may also email the operator above to request deletion, including related analysis exports. Copies held independently on devices or by viewers may require a separate action.
9. Your choices and rights
You can enable Lite mode, stop recording, change watch permissions, sign out, and clear browser storage. Clearing the account website’s local storage signs you out in that browser; clearing the live-score site’s storage removes its saved match and player labels. These actions do not substitute for a request to delete data already held by the service.
Depending on the law that applies, you may request access to your personal data, correction, deletion, restriction of processing, or a portable copy; object to processing based on legitimate interests; and withdraw consent. Contact the operator above with your request. Under the GDPR, requests are generally answered within one month, subject to permitted extensions. You can also complain to your local data protection authority. The European Commission explains these data protection rights .
10. Children and changes to this policy
Badminwear is intended for adults aged 18 and older and is not for children. Do not create an account or use the watch app if you are under 18. Contact us if you believe a child has provided personal data.
We may update this policy as the service changes and will revise the date above. Material changes will be brought to your attention through the service or an appropriate account notice. A policy update does not replace any new consent required for a new use of your data. Also see our terms of service .