Privacy Policy

1. Responsibility and contact

Alexanda Lyon, trading as Shuttls, United Kingdom, is the controller responsible for Shuttls’ own processing of personal data.

For privacy questions, rights requests, deletion requests or complaints, email privacy@shuttlsapp.com. You can use this address even if you cannot sign in or have uninstalled the app.

A club or venue may separately determine how it uses membership, attendance and financial records. It is then responsible as controller for that processing and its own privacy information. Where Shuttls manages records solely on a club’s instructions, Shuttls acts as its processor. Shuttls remains controller for its own account, platform, security and subscription processing.

2. Data and its sources

We handle data you enter, data generated by using the Service, and information from the connected services and other people described below.

Account and player profile

Email address, account ID, sign-in credentials or provider identifiers, name, username, chosen photo and settings. The current iOS onboarding does not ask for your age. Older versions or other supported versions may have collected optional age-range, playing-experience, skill-level, training-history, competition-level or watch-ownership information. Previously supplied profile information may remain until it is updated or deleted. Sign in with Apple can supply your name, provider ID and email, including a private relay address. Authentication services handle session tokens and sign-in events.

Matches, activity and performance

Scores, opponents and teammates, results, match/session dates, duration, serving and point history, club association, experience points, streaks, ratings and competition results. Other players or organisers may record matches involving you. Compatible watches supply movement and swing measurements and timestamps used for performance estimates.

Health and fitness

With relevant permissions, heart-rate samples, average and maximum heart rate, active calories, distance and workout information. We also handle heart-rate settings and derived fitness or recovery estimates. Available data depends on your device and integration. See section 4.

Location and venue discovery

Coordinates when you allow location access, search terms, selected towns, venue addresses and location pins. A request to add nearby clubs can include your account ID, town and available coordinates. Venue information may come from organisers, users, public business listings, Google Places or Companies House. Map/location services receive information needed for searches and maps.

Social, club and racket features

Friend connections and requests, invitations, shared links and QR tokens, game/lobby participation, memberships, attendance, check-ins, session plans, court allocations, announcements, photos, reviews, reports and administration records. Racket profiles include equipment details, visibility choices and NFC tag identifiers, claim status, scan count and last scan time. Organisers can add guest player names without those players having an account.

Payments and subscriptions

Products, subscription status and expiry, purchase/transaction references, club fees, membership plans, balances, refunds and payment status; and club operators’ payment account identifiers and onboarding status. Payment providers handle card details and authentication directly. Shuttls’ application records use payment references rather than full card numbers or card security codes.

Device, technical and notification data

IP address, device/watch model, operating system, app version, linked-device identifiers, pairing codes, session tokens, time zone, notification preferences and push tokens. Error reports can include account ID, error details, app/device information and context of the failed action. Infrastructure and app-store services may supply security, diagnostic or aggregate performance information.

Advertising

Where enabled, Google’s advertising software may handle IP address and inferred approximate location, device/advertising identifiers, impressions, interactions, diagnostics and performance data. Shuttls records rewards or boost expiry when a rewarded ad is completed. See section 7.

Support, waitlist and business enquiries

Email address, name if provided, messages, attachments and request history. The Android launch waitlist collects an email address. Public listings and organisers may provide business contact details for club discovery and relevant business enquiries. For club outreach, records can include contact language, verification/claim status and message-delivery history.

Account identifiers and information necessary for a feature are required to provide it. Payment providers may require additional information by law. Optional photos, health access and location access are not required for an ordinary account; declining them limits the related feature. Avoid putting sensitive information about yourself or others in public fields.

3. Purposes and legal bases

Where UK GDPR or EU GDPR applies, the bases for Shuttls’ controller activities are below. Consent-based uses require a valid, specific choice; this table and your use of Shuttls do not establish that choice. A club acting as controller identifies its own bases.

Consent is specific to the purpose and can be withdrawn without making earlier lawful processing unlawful. Contract and legitimate interests do not replace explicit consent for optional health processing or consent required for advertising technologies.

4. Health and watch data

Health measurements and inferences can be sensitive personal data. We use them to record badminton activity, show session information and provide fitness/performance insights. These are not medical diagnoses.

• Apple Watch/Apple Health: compatible features read heart rate, active energy and distance during workouts and write workout records with permission. Match and health measurements can pass from watch to phone and your Shuttls account.
• Android Health Connect: the integration requests read access to heart rate, active calories burned and distance for the relevant session period. It reads these records rather than editing the original records. Summaries can be included in synced Shuttls matches.
• Other watches: Wear OS, Garmin and supported Amazfit/Zepp features collect supported session/sensor measurements. Linked watches transfer match information to Shuttls directly or through companion services. Garmin can also save an activity to Garmin Connect under its own privacy arrangements.

Device permissions control access to records. Explicit consent for Shuttls’ health processing must also explain its purposes, cloud syncing and any sharing. Platform permission and acceptance of this notice must not be treated as permission for every further use. Access and use must comply with Apple Health and Google Health Connect requirements, including Google’s Limited Use requirements.

We do not use health records or inferences to target ads, sell them to data brokers, or provide them to advertisers or insurers. Supabase processes synced health records as our hosting provider. Existing friend activity summaries include average heart rate and calories. Health sharing requires specific consent. In current versions, granting device health access can result in syncing and these friend summaries; do not assume there is a separate in-app switch for each recipient or purpose. Leave health permissions off if you do not want future imports, and contact us about existing copies or unwanted sharing.

Revoke access in Apple Health/Watch privacy settings, Health Connect permissions or your watch settings. Email us to withdraw health-processing/sharing consent or delete Shuttls’ copies. Revocation stops future access; it does not automatically erase previously synced records or originals in Apple Health, Health Connect or Garmin Connect. Manage those originals separately.

5. Social and public sharing

Your displayed name/username, photo, rating, rank, match results, participation and player statistics can be visible to other users through profiles, games, club lists and leaderboards. Match summaries and opponent names should not be treated as private diary entries.

Friends can see games, wins/losses, rating changes, recent-play indications and, in existing summaries, calories and average heart rate. Detailed sensor timelines are stored separately. Removing a friend restricts future friend-only access; it does not recall copies or remove information visible through another feature.

Organisers and authorised club administrators can access records needed to run the club, including member/guest names, attendance, court allocations, balances, memberships and payment status. Participants see relevant rosters and games. Public club listings and posted content can be visible more widely. Ask the club about its own use of records.

QR/NFC links: anyone with your friend QR link can view the linked player card, including username, photo, rating, games, league and win rate, without signing in. Public Shuttls Tap links also show equipment details and the player card. New racket profiles currently default to Public; review visibility before sharing. Private and Shuttls-only options restrict the relevant racket view. Public club join/check-in links reveal the relevant club/session details.

If you export results or share to another service, your chosen recipient receives the information and handles it under its own arrangements. Public material and links can be forwarded or copied. Do not share another person’s sensitive data without an appropriate basis and their knowledge.

6. Providers and recipients

Recipients below receive information needed for the features used. Providers acting on our instructions are processors; platforms may also be independent controllers for their own services.

• Supabase: authentication, database, files, backend functions and syncing, including profiles, matches, related health data, club records, tokens and waitlist submissions. Privacy information.
• Apple/Google: sign-in where offered, app distribution, purchases, permitted diagnostics, health connections, maps/location and push delivery through Apple Push Notification service or Firebase Cloud Messaging. Apple privacy; Google privacy.
• RevenueCat: purchase validation/subscription management using app user identifiers, purchase history and entitlement status. Privacy information.
• Stripe: club payments, billing, refunds and connected payment accounts, including relevant payment, fraud and verification information. Stripe handles payment details directly and supplies transaction references/status to Shuttls. Privacy information.
• Google AdMob/advertising partners: ad-related technical and interaction data where advertising operates. The consent message must identify participating partners and choices. Google partner-services information.
• Garmin/Amazfit/Zepp: connected watch/companion features, pairing and activity transfer according to the integration. Garmin privacy; see the notice in your Zepp service.
• Website/email providers: GitHub Pages for site delivery; Google Fonts on pages loading its fonts; email providers and Resend for applicable communications. They receive necessary request or contact/message data. GitHub privacy; Resend privacy.
• QR-image delivery: club outreach emails can load an image from api.qrserver.com. The request contains an app-download URL and technical request information, rather than the club claim code.
• Other users, clubs and chosen recipients: as described in section 5.

Relevant information may go to advisers, courts, regulators or authorities for legal obligations or claims. Do not send us sensitive information that is not needed for your enquiry. If the Service transfers to another operator, records may transfer subject to law, appropriate protections and notice. This does not authorise incompatible new uses of health or advertising data.

Shuttls does not offer account, match or health records for sale to data brokers. Advertising disclosures can nevertheless count as “sale”, “sharing” or targeted advertising under some US laws even without payment for data. See sections 7 and 12. Advertising identifiers are not necessarily anonymous.

7. Advertising and tracking

Some phone features include Google AdMob rewarded ads. Its SDK can collect the data described in section 2 for delivery, measurement and fraud prevention. Google/partners may combine it with other information where permissions and law allow.

Advertising storage, access, personalisation and tracking require valid consent where applicable. The current iOS app can initialise Google’s advertising SDK after the system tracking prompt even if tracking is refused. The system prompt limits permitted cross-app tracking; it does not mean the SDK is switched off or that all ad-related requests stop. Non-personalised ads can still access device information and require UK/EU consent. Watching a rewarded ad is not by itself consent to tracking.

On iOS, manage cross-app tracking in Settings > Privacy & Security > Tracking. Android provides advertising-ID and ad privacy settings. These controls do not replace service-specific consent choices or erase data already collected. Where your version provides advertising privacy options, use them to review choices; you can also email us with an objection, withdrawal or opt-out.

8. Website and email

The current public website has no dedicated visitor analytics or advertising script. Hosts still receive IP addresses, browser/request information and timestamps to deliver and protect the site. GitHub Pages logs visitor IP addresses for security.

Other site pages load Google Fonts, which receives technical request information. This privacy page uses system fonts and makes no Google Fonts request. QR/club/racket pages request records from Supabase to resolve the link. External links take you to that service.

App storage, sign-in tokens and preferences support requested features. Non-essential cookies, identifiers and similar storage/access technologies require the choices prescribed by law before use. Blocking storage can affect sign-in/settings. New website analytics or advertising requires updated disclosures and controls before activation.

The Android waitlist uses your email for the requested launch notification. Email us to leave the waitlist. Signup is not consent to unrelated marketing. The contact form opens your email application, whose provider sends the message to us. Club outreach emails can include an externally hosted QR image; loading that image can disclose technical request information to the QR-image provider. Optional promotional messages must offer appropriate opt-outs; necessary service messages are separate.

9. International transfers

Shuttls’ production Supabase database is hosted in Stockholm, Sweden (AWS eu-north-1), within the European Economic Area. This is the primary database region, not a promise that all processing stays in Sweden.

Supabase and other providers operate internationally, including in the United States. Support, infrastructure logs, email delivery, purchase services and subprocessors can involve processing outside your country, the UK or the European Economic Area. A provider’s registered office does not establish every processing location.

Where transfer restrictions apply, a valid mechanism is required: an applicable adequacy decision, including a data protection framework only for covered recipients/processing; or approved contractual safeguards such as EU Standard Contractual Clauses and the UK International Data Transfer Agreement or UK Addendum, with required transfer assessment and supplementary protections.

Email us for destinations and a copy/explanation of applicable safeguards, subject to necessary redactions. Agreement with this notice is not consent to an international transfer.

The published data-processing terms of Supabase, RevenueCat and Resend provide EU Standard Contractual Clauses and the UK Addendum for relevant restricted transfers. See Supabase’s current subprocessor list for its infrastructure/support recipients and locations. These safeguards apply according to the relevant agreement and transfer; they do not make optional processing lawful without its required consent.

10. Retention and deletion

Retention depends on purpose, continuing need, your choices and applicable legal requirements. The criteria below apply; provider copies may not disappear immediately.

• Accounts, matches, health, social and equipment records: while needed for your account/history and requested features, unless deleted or you request deletion sooner. Unneeded records should be erased or irreversibly anonymised. You can request health-data deletion independently of your account.
• Club records: for membership, attendance, billing/dispute needs and applicable legal requirements. Clubs acting as controllers set their own retention, including for guests.
• Financial/legal records: for applicable accounting, tax, fraud or claim requirements, limited to needed records. A financial retention duty does not justify retaining health history.
• Support/error records: for the enquiry/incident and proportionate follow-up, security or dispute needs; then deletion/anonymisation.
• Waitlist: until the launch email and necessary delivery handling are complete, or withdrawal sooner.
• Pairing/local data: one-time watch pairing codes expire after ten minutes. Settings, credentials and pending uploads remain until cleared, signed out or removed as supported by the platform. OS backups may remain after uninstalling.
• Backups/logs: until applicable expiry cycles, protected and restricted to necessary recovery/security purposes. Platform recovery copies, if held, follow the provider’s applicable arrangements. We do not promise a fixed seven-, fourteen- or thirty-day backup expiry without confirming those arrangements. Separately created backups need a documented expiry, and relevant erasures must be reapplied after restoration.

Use Settings > Delete Account in the phone app or email us to request deletion. Include your account email, never your password. We may require proportionate verification. Contact us if in-app deletion fails or you want particular records removed.

Uninstalling does not delete the hosted account. Account deletion does not automatically cancel store subscriptions or club memberships; manage those with the store/club. Other users’ copies, clubs’ legally retained records and independent Health/Garmin records need separate handling, subject to your rights.

These are purpose-based retention criteria, rather than a promise that every record expires automatically after a fixed number of days. The current database has no general automatic expiry job for support/error records, location requests or waitlist entries. You can request erasure through the contact route above; continued retention must be justified by a remaining lawful purpose.

11. Security

Shuttls uses encrypted HTTPS connections to its backend and account-based authentication. We distinguish account features, club administration and sharing purposes when designing access controls. Do not assume a player profile or shared result is private; see section 5. Some profile information, including health-related profile settings, can currently be accessible more broadly than the player card displayed in the app. We do not promise that every record is visible only to its owner. Contact us to report unwanted exposure or request removal of information.

No service guarantees absolute security. Protect devices, credentials and pairing codes. Report suspected privacy/security issues to privacy@shuttlsapp.com. Where required, we will notify regulators and affected people of personal data breaches.

12. Your rights and choices

Rights depend on location, applicable law and circumstances. Under UK/EU data protection law they include:

• Access to personal data and information about its use.
• Correction of inaccurate/incomplete data.
• Erasure where applicable, including after consent withdrawal where no other ground permits retention.
• Restriction of processing in specified circumstances.
• Portability of qualifying data processed automatically on consent or contract.
• Objection to legitimate-interests processing because of your situation, and to direct marketing at any time.
• Withdrawal of consent and applicable rights concerning significant solely automated decisions.
• Regulatory complaints and applicable judicial remedies.

Email us to exercise a right or request a machine-readable copy. No special legal wording is needed. We normally respond to UK/EU rights requests within one month, subject to lawful verification, clarification or extension rules. We explain extensions/exceptions. Requests are normally free; a fee or refusal is permitted only where law allows.

Your right to object: you can object to our use of your data for legitimate interests because of your circumstances. You can object to direct marketing at any time, without giving a reason. Email privacy@shuttlsapp.com and tell us which use you object to.

Edit supported profile fields, remove friends, change racket visibility, adjust notifications and revoke permissions in the relevant settings. Withdrawal affects the associated feature. Direct-marketing objections do not affect your ordinary account.

Other locations, including US states: where a law covers Shuttls and your request, additional rights may include knowing, obtaining, correcting/deleting data; opting out of sale, sharing or targeted ads; limiting specified sensitive uses; using an authorised agent; and appealing refusals. Email us for an opt-out/appeal. We verify only as necessary, explain decisions and do not discriminate for exercising protected rights. Recognised browser opt-out signals must be honoured where applicable law requires it. This does not assert that every US law’s applicability threshold is met.

13. Children and young people

You must be at least 13 to create a personal Shuttls account. Do not create a personal account if you are under 13. Current iOS onboarding does not ask for your age, and the minimum-age rule is not a claim that the app verifies every user’s age. If a younger child has supplied data, contact us so we can investigate and take appropriate action, including deletion where required. A club’s guest record is not a personal account; clubs must have an appropriate basis and provide privacy information for children’s records too.

If you are 13–17: your player name, photo, results and shared links can be seen by other people. Choose a nickname instead of your full name where supported, avoid a photo that identifies your school or home, and do not publish your address, contact details or sensitive information. A public QR/NFC link can be forwarded. Review racket visibility and only accept friend requests from people you know. Ask a trusted adult if a sharing choice is unclear.

Health and location access are optional for an ordinary account. Leave those permissions off if you do not want to provide that information. Current friend summaries can include heart rate and calories; keep health access off if you do not want those measurements synced/shared, and contact us to remove existing copies. A parent, guardian or younger user can use the privacy email to report unsafe sharing, request help or exercise applicable rights. We will use proportionate verification and will not ask you to email a password.

Parental authorisation is needed where the applicable law requires it for consent-based processing. A 13+ minimum does not override another country’s higher consent age or remove safeguards required for all under-18s. A store age rating is not privacy consent.

14. Automated processing

Shuttls calculates statistics, experience, rankings, Shuttl Scores and insights from match results, opponent ratings, playing history and permitted sensor information for fitness insights. Court allocation can use ratings/participation to suggest balanced games. Calculations affect displays and game suggestions.

These features provide sporting feedback and club organisation. They are not intended for solely automated decisions with legal or similarly significant effects, such as credit, insurance, employment or treatment decisions. Estimates can be wrong. Contact us about inaccurate inputs or an outcome you want explained or reviewed.

15. Complaints

Email us with a data protection complaint, describing the concern and desired outcome. We will acknowledge a UK data protection complaint within 30 days, investigate without undue delay, keep you informed as appropriate and communicate the outcome.

You can complain to the UK Information Commissioner’s Office at ico.org.uk/make-a-complaint or 0303 123 1113. Where EU GDPR applies, contact the authority where you live/work or where the alleged infringement occurred; see the EDPB authority directory. Other countries may have local routes. Contacting us does not remove regulatory or judicial remedies.

16. Policy changes

This policy describes data handling and your rights; it does not itself grant permission for optional processing. The policy will remain at shuttlsapp.com/privacy.html, with an updated date when changed. Material changes will receive appropriate notice through the app, website or email before new processing where required. New consent will be requested separately where needed; continued use does not supply it.

Privacy contact: privacy@shuttlsapp.com.