BadScore
← Back to BadScore

BadScore legal

Privacy Policy

Effective date: 11 September 2026
Operator and data controller: SWILLEX LTD
Postal address: 4 Latimer Street, Romsey, England, SO51 8DG
Website: badscore.co.uk
Privacy requests and complaints: privacy@badscore.co.uk
App support: support@badscore.co.uk
Policy URL: badscore.co.uk/privacy

1. About this policy

This policy explains how BadScore handles information when you use the BadScore Apple Watch app, its score complication, and BadScore History for iPhone and iPad where available. It also covers information we receive when you contact us, participate in testing, or visit our privacy and support pages. “We”, “us” and “our” mean the operator identified above.

BadScore is a sports scorekeeper. It supports badminton, table tennis, squash, pickleball, beach volleyball and volleyball. BadScore History provides match records, scoring timelines, statistics and exports. Features depend on the product and version you install; describing a History feature here does not mean that it is included in your Watch app purchase or available in your country.

We are responsible for personal information we process as a controller, including support correspondence and the app processing for which we determine the purposes and means. Apple is separately responsible for processing it carries out for its own Apple Account, App Store, iCloud and system-service purposes. Those services are also governed by Apple’s privacy information and terms.

2. The main points

  • You do not create a BadScore account. The app does not ask for your name, email address or a player profile to keep score.
  • Your devices store scores, settings and match records. Where iCloud is available for BadScore, match history can automatically synchronise through Apple’s private CloudKit database associated with your Apple Account.
  • The app does not send a copy of your match history to a developer-operated server. We do not have an app administration feature for browsing your private match records.
  • BadScore has no advertising, advertising identifiers, third-party tracking SDKs or app-installed analytics service. We do not sell personal information or share it for targeted advertising.
  • If you contact us, send a diagnostic report or join a beta test, we may receive information about you through those separate channels.
  • The History app’s Delete action is reversible: it marks a record as deleted and excludes it from statistics, but keeps the record and its scoring events. It is not permanent erasure.

3. Information handled by the apps

Scores, match settings and local preferences

BadScore stores the selected sport, scoring and match format, scores for the two sides, completed games, serving and rally state where relevant, colour positions, and information needed to restore the current scoreboard. It also stores whether introductory guidance has been completed and internal references linking a scoreboard to its history.

The Watch complication receives a small score snapshot through storage shared locally between the Watch app and its complication. That app-group storage is separate from the iCloud history database.

Match history and activity records

The history store can contain:

  • Random record identifiers for matches, games and scoring events, together with sequence numbers and schema information used to keep the records consistent.
  • The sport, format, score, game totals, winning side and whether a match is in progress, completed or abandoned.
  • Start, end and scoring-event times, and a time-zone identifier where recorded. A time zone is not GPS location data, although it can indicate a broad region.
  • Actions such as points scored, serving changes, corrections, undo actions, resets, format changes and swaps of side positions.
  • Stored snapshots of match state and references connecting a correction with an earlier action. Correcting a score does not necessarily erase the original event from the timeline.
  • Whether a record came from an older scoreboard and whether it has been marked as deleted.

These identifiers identify records within the app; they are not advertising identifiers. Match information can still be personal information when associated with you, your Apple Account or other identifying context. The absence of player names does not make every record anonymous.

Personal participation and statistics

In BadScore History, you may identify the side you played on, indicate that you did not play, or leave your participation unassigned. The app can also use an outcome you select to assign your side where the match result supports that assignment.

The app uses recorded matches and your assignments to calculate personal and all-match statistics, such as wins, game and point totals, score runs and recorded duration. For doubles or team sports, these describe the side’s recorded results; they do not identify individual shots or every participant. Unassigned participation is not automatically treated as you having played.

These calculations are for your own viewing. We do not use them to make decisions about your employment, insurance, credit, eligibility or other matters with legal or similarly significant effects, or to target advertising.

4. iCloud synchronisation and backups

The apps are designed to keep history locally and synchronise it using Apple’s private CloudKit database when the relevant iCloud services and app permissions are available. Synchronisation can begin automatically under your existing Apple settings; there is no separate BadScore sign-in or in-app opt-in switch in the current version. The Watch can record and synchronise history even if you have not installed BadScore History.

Synchronised information includes the match, game and event records described above, and participation assignments made in History. Compatible installations using the same Apple Account can access that history. It is not published to a public leaderboard or automatically shared with your opponents or family members using different Apple Accounts.

Apple operates the iCloud infrastructure and the account authentication needed for this service. BadScore does not receive your Apple Account password. We do not operate a separate history database or receive a routine feed of your private records. We may receive individual records if you deliberately send us an export or screenshot for support.

Local scoring can continue without an internet connection. Synchronisation may be delayed or unavailable because of account settings, connectivity, storage limits, service availability or device configuration. Information recorded while offline may synchronise later when iCloud becomes available. Cloud synchronisation is not the same as a separate backup.

Your device backups may also contain app data according to your Apple settings. Apple controls its backup and cloud retention processes. We do not promise that uninstalling an app, turning off synchronisation or deleting one device copy will remove all cloud, backup or other-device copies.

To review the relevant settings, use your device’s Apple Account and iCloud controls and consult Apple’s guidance on third-party app data in iCloud. The available controls and their effects depend on your devices and operating-system versions. See section 10 for the important limitations of deletion in BadScore.

5. Information we may receive outside the scoring features

Support and privacy enquiries

If you contact us, we receive your contact details and the information you send, such as your name, email address, message, device model, operating-system version, app version, screenshots, exports and diagnostic attachments. We use it to respond, investigate problems, handle complaints and maintain an appropriate record of the outcome.

Please send only what is needed. Do not send Apple Account passwords, payment-card details, health information or information identifying other players unless it is necessary and you are entitled to share it. You can redact a screenshot or export before sending it.

Apple diagnostics, store reports and beta testing

Apple may make app performance, crash, sales or usage reports available to developers under its services and the applicable user settings. This is separate from an analytics SDK installed in BadScore. A diagnostic report may include technical details such as the device or operating-system version, app version, crash information and diagnostic identifiers. We use reports we receive to investigate faults and improve reliability.

If you join a TestFlight test, Apple may provide us with tester information, installation and session information, crash reports and feedback, depending on how you join and what you submit. An invitation may involve your name and email address. TestFlight is optional and has its own privacy information. Do not submit confidential information in beta feedback.

App Store purchases and payment details are handled through Apple. The current apps do not contain an in-app payment form or subscription system. We do not receive your full payment-card details from Apple. Developer sales and financial reports, and any purchase information you send for support, are handled only for administration, support and legal requirements.

Visits to our web pages

Opening an online privacy or support page sends a request to its hosting provider. This can involve your IP address, requested page, time of access, browser information and security logs, even where the page itself has no analytics scripts.

Hosting provider and relevant processing: Cloudflare is configured to provide the website’s hosting, content delivery and security services. To deliver and protect the site, Cloudflare processes requests from visitors and may process information including IP addresses, traffic-routing data, system-configuration information, requested URLs, timestamps and security signals. Cloudflare may make limited request and security information available to us through its service dashboard.
Website configuration: the public information pages do not use advertising, analytics, tracking pixels or browser-storage identifiers. Cloudflare processes requests to deliver and protect the site as described above.

The public pages do not embed third-party media or load external fonts. Opening an external link is subject to the destination site’s own privacy practices.

6. Information the app does not request

The current app features do not request access to your contacts, photo library, camera, microphone, precise location, HealthKit records or fitness sensors. Scores and participation are entered through the app’s controls; BadScore does not monitor your physical activity or infer a medical condition.

Spoken scores use Apple’s speech synthesis and audio playback services. This feature speaks text generated from the scoreboard; it does not listen to you or record your voice. System settings can affect voice availability and playback.

We do not use your match history or support correspondence to train an AI model. We do not operate public profiles, social messaging, data-broker integrations or cross-app advertising tracking.

Where UK or European data protection law applies to processing for which we are responsible, we rely on the following bases, according to the particular activity:

  • Providing the app features you request: performance of our contract with you, insofar as processing scores, retaining history, synchronising it under your settings and producing your requested statistics or export is necessary to provide those features.
  • Support and troubleshooting: performance of our contract where necessary to resolve a service issue; otherwise our legitimate interests in answering enquiries and operating a reliable app. We limit the information used to what is relevant and consider your interests and expectations.
  • Security and fault investigation: our legitimate interests in protecting the app, investigating failures and preventing misuse, subject to your rights. This does not authorise advertising tracking or access to private history we do not otherwise receive.
  • Legal duties: compliance with applicable obligations, for example responding to a valid rights request or retaining required business records.
  • Legal claims: our legitimate interests in establishing, exercising or defending a claim, where necessary and proportionate.
  • Activities requiring consent: consent where the law requires it. We will identify that activity and ask separately. Reading this policy or accepting the app’s terms is not consent to every form of processing.

Apple determines the legal bases for processing it carries out independently. Turning an Apple service on or off is a system choice and is not a blanket consent to additional processing by us.

Providing contact information is optional, but we may be unable to reply or investigate a request without sufficient information. Without usable local storage, scoring persistence may fail; without available iCloud services, cross-device history synchronisation will not work. No advertising consent is needed to use BadScore.

8. Recipients and disclosures

Information may be handled by Apple for the platform and cloud functions described above; by the provider of an export destination you choose; and by our email, support and hosting providers where needed to deliver their services.

Emails sent to BadScore are routed by Cloudflare and processed by Google and Apple so that we can receive, store and respond to them. This processing can include the message content, sender and recipient addresses, attachments, and delivery and security information. Access is limited to the people responsible for handling support, privacy requests and contractual notices.

We may disclose information we actually hold to professional advisers subject to confidentiality, or to a regulator, court or other authority where disclosure is required or lawfully justified. A request to us does not give us access to private iCloud match records we do not hold.

If responsibility for BadScore changes through a sale or transfer, we will assess what information needs to transfer, apply appropriate protections and provide any required notice. We will not treat a business transfer as permission to sell your data for advertising or expand its use without a lawful basis.

Service providers acting on our instructions must be subject to appropriate contractual and security requirements. Where a provider acts independently, its own notice also applies. We do not rent contact lists or disclose your information to advertisers or data brokers.

9. International processing

Apple and other service providers may process information in countries other than the one where you live. BadScore does not offer a setting guaranteeing that private iCloud records remain in a particular country. Apple’s international processing is explained in its Privacy Policy.

For restricted international transfers for which we are responsible, we must identify an appropriate legal mechanism, such as a relevant adequacy decision or approved contractual safeguards, and apply any additional protections required. You can contact us for information about the applicable safeguards or a copy, subject to necessary redactions.

Cloudflare, Google and Apple operate internationally and may process information outside the UK. Where a restricted transfer is involved, we rely on the transfer safeguards provided under the applicable service terms, such as adequacy arrangements or approved contractual clauses. You can read more in Cloudflare’s Data Processing Addendum, Google’s Privacy Policy and Apple’s Privacy Policy, or contact us for information about the safeguards relevant to your information.

10. Retention, deletion and your controls

Scores and history on your devices and in iCloud

The apps do not currently impose a fixed automatic expiry on match history. Records remain in local storage and, when synchronised, iCloud unless removed through effective storage-management controls. Starting a new match resets the active scoreboard but may retain the earlier match and its events in history. Clearing a participation assignment does not delete the match or scoring timeline.

Selecting Delete in History does not permanently erase anything. It marks the match as deleted, retains its games and events, and excludes it from statistics. It can still appear as a deleted match and can be restored. There is no automatic purge period for these marked records in the current version.

The current apps do not provide a dedicated permanent-erasure command. To remove all copies, you may need to manage app storage on every relevant device, the shared BadScore iCloud data and any backups or exports separately. Removing shared cloud data may affect both BadScore and BadScore History. Data left on another synchronising device may later reappear.

Apple provides cloud-storage management controls, but we cannot promise a specific permanent-deletion sequence for every device configuration. Contact us if you need assistance. Do not send your Apple Account password. We cannot sign into your account or remotely erase your private records on your behalf. These practical limitations do not remove any legal obligation that applies to us.

Exports

Where History is available, you can export an individual match in JSON or CSV format. Exports can include record identifiers, participation information, times, results and scoring events; the fields differ by format. The destination you select may be a local folder, cloud-storage service or another supported location.

An export is an independent copy. Deleting or editing the original match does not update or delete it. You control what you save or share and must manage copies with their recipients or storage providers. The app’s export feature is not a promise that every format contains every item covered by a legal access request.

Information held by us

We keep support and complaint information only for the period needed to deal with the matter and a justified follow-up period. Gmail moves its forwarded copy to Trash, where Google states that messages are permanently deleted after 30 days. The destination copy remains in iCloud Mail until it is deleted according to the criteria below, subject to the providers’ deletion and backup processes. We minimise diagnostic attachments and remove them when they are no longer needed. Records relevant to a legal obligation or actual dispute may need to be held longer, with access limited appropriately.

We use the following criteria to decide how long to retain information under our control:

  • Support enquiries: the time needed to answer the enquiry, resolve the issue and handle relevant follow-up. We consider whether the matter remains open, whether a recurring fault needs investigation and whether a record is needed for a complaint or legal claim.
  • Privacy requests and complaints: the time needed to verify and respond to the request, record its outcome and meet applicable accountability or legal requirements. We remove unnecessary identity-verification material and attachments when they are no longer needed.
  • Diagnostic files, screenshots and match exports: the time needed to investigate and resolve the reported problem. We remove raw attachments when that purpose has ended and keep technical notes free of unnecessary personal information.
  • Beta tester details and feedback: the time needed to administer participation and act on relevant feedback. We consider whether the tester is still participating, whether the programme remains active and whether a reported issue is unresolved.
  • Website and security information available to us: the time needed to deliver and protect the website or investigate a specific incident, taking account of the hosting provider’s retention settings and any legal requirements.

We delete or anonymise information when the relevant purpose ends, unless a legal obligation or actual or reasonably anticipated dispute requires us to retain it. Where longer retention is necessary, we limit it to the relevant information and restrict access.

Deletion from an active mailbox or service may not immediately remove provider-managed backups. Their expiry and deletion processes are controlled by the relevant provider; we do not promise a fixed expiry for copies outside our control. You can contact us to ask about the retention of information relating to a particular enquiry or request.

These criteria do not set the retention period for Apple’s independent App Store or TestFlight records, your private iCloud history, your device backups or exports held by you or another recipient. Their retention and controls are described separately above.

11. Security

The apps use platform-provided application storage and Apple’s CloudKit access controls rather than a public match database. Device security, Apple Account security, cloud configuration and your export destinations also affect protection.

We limit access to support information and reports to people who need it for the stated purposes, and use appropriate security measures for the systems under our control. Keep your devices updated, protect your Apple Account and use suitable device locks. A score complication or spoken score may be visible or audible to people nearby.

No system can guarantee absolute security or uninterrupted availability. We do not claim that all app records, exports or backups are end-to-end encrypted. If a personal-data breach for which we are responsible occurs, we will investigate and notify the relevant regulator and affected people when legally required.

12. Your data protection rights

Depending on your location and the circumstances, you may have rights to access and obtain a copy of your information; correct inaccuracies; request erasure; restrict processing; object to processing based on legitimate interests; and receive or transmit eligible information in a portable format. Where we rely on consent, you may withdraw it without affecting earlier lawful processing.

These rights have conditions and exceptions. Send requests to privacy@badscore.co.uk. We may ask for information reasonably needed to verify your identity or clarify the request, but not your Apple Account password. We normally respond without undue delay and within one month, subject to lawful extensions or other adjustments, which we will explain where applicable. Requests are normally free.

We will address information and processing for which we are responsible. If the request concerns private data we cannot access, we will explain the limitation and available controls rather than pretend to hold a copy. For Apple’s independent processing, you may also need to contact Apple.

You may complain to us at privacy@badscore.co.uk. We will acknowledge a data protection complaint within 30 days, investigate it and keep you informed of progress and the outcome. You may also complain to the UK Information Commissioner’s Office or the relevant authority where you live or work. You do not have to give up your right to contact a regulator or court in order to ask us for help.

13. Children and information about other players

BadScore is a general-purpose scorekeeping tool. It does not offer child profiles, child-directed advertising or a social network. We do not ask users to submit their age or date of birth, and we do not independently verify a user’s age through the scoring interface.

Children may use an appropriate version with the permissions and supervision required by their parent or guardian, local law and Apple’s rules. The fact that the app has no named player profiles does not mean that a child’s match records cannot be personal information. Apple applies its own account and family controls.

If a child sends personal information to support, or a parent or guardian believes that we have received information we should not hold, contact us so we can assess it and take appropriate action. Do not include unnecessary information identifying other players in a support request or shared export. If you use BadScore for a club, school or organised group, consider your own privacy responsibilities towards participants.

14. Changes and contact

We may update this policy when features, providers or legal requirements change. We will update the effective date and provide additional notice where a change materially affects how personal information is used. If a new use requires consent or another legal step, we will take that step before starting it; an updated policy alone is not permission.

For a privacy question or request, contact SWILLEX LTD at privacy@badscore.co.uk or write to SWILLEX LTD, 4 Latimer Street, Romsey, England, SO51 8DG. For app assistance, use support@badscore.co.uk. Our related Terms and Conditions explain use of the app and do not override your data protection rights.