Privacy Policy

Effective and last updated: 27 July 2026

Translogic Limited, a private limited company incorporated in England and Wales, trading as ShuttleSense and of 71-75 Shelton Street, Covent Garden, London, United Kingdom, WC2H 9JQ (company number 17350018) (“ShuttleSense”, “we”, “us”), is the controller of the personal data described in this policy. This policy applies to the ShuttleSense mobile app, website and related support and analysis services.

ShuttleSense analyses user-selected badminton footage. We do not sell personal data, show third-party advertising or use personal data for cross-app tracking.

1. Data we collect

Account and profile

• Your email address, authentication provider identifier, internal user ID and account/security records. If you use Google sign-in, Google supplies the account details you choose to share.
• Your display name and confirmation that you are at least 16. You may optionally add a profile avatar, handedness, playing level, home club and notification preference.
• The version and time of the Terms you agreed to and Privacy Policy you acknowledged.

An email address, display name, 16+ confirmation and account identifiers are required for a hosted account; without them we cannot create or secure one. Uploading a video is optional, but a selected video and the upload-rights confirmation are required for each analysis. Other profile fields and support-content access are optional.

Uploads and analysis

• A match title and the video you choose to upload, including any audio already in that file, plus file metadata such as duration, size, resolution and upload state. The current analysis does not use the soundtrack as an analytical input, but the audio is stored and may remain in a highlight export.
• Your per-upload confirmation that people appearing or heard in the recording have been informed and that you have the rights and permissions needed to upload it.
• Analysis generated from the footage, which may include rally boundaries, timestamps, player and shuttle positions, pose/keypoint and court features, trajectories, sporting-performance statistics, model confidence, shot or coaching outputs where enabled, thumbnails and generated highlights.
• Participant names or labels you add, highlight choices, share settings, and other match-library information.

Corrections and service feedback

• If you add or remove a detected rally or correct its start or end, we store the action and corrected timestamps so we can apply the edit and keep the match history consistent.
• If you report an analysis problem, we store the limited information described below so we can investigate and respond.
• We do not use corrections, feedback or support material to train or fine-tune AI models.

Support and communications

• If you report an analysis problem, we store the category, an optional note, the optional playback/rally context, the support reference, consent and withdrawal times, and an audit log of authorised access.
• Support access to the source footage and model outputs requires a separate, unchecked permission for that report. You can withdraw it at any time.
• Completion emails are enabled by default. You can turn them off in Settings. When enabled, we send the account email address, your selected match title and the ready/failed result state to our email delivery provider.
• If you join the website waitlist, we store your email address, signup time, signup source and the country code supplied by our website host. The waitlist is a separate website record.

Technical and security information

Our app and infrastructure providers may process request IP address, user agent, timestamps, session and authentication events, app/version information, job IDs, errors and similar logs needed to deliver and secure the service. We minimise these fields and do not use them for advertising.

2. Why we use data and our lawful bases

• Contract: to create and secure your account, upload and analyse the footage you select, present results and highlights, maintain your library, respond to support requests, and provide requested service notifications.
• Legitimate interests: to prevent abuse, keep the service reliable, investigate failures, record limited rally corrections and measure operational reliability. We balance these interests against the rights of users and people in recordings.
• Consent: for launch marketing and for time-limited human access to source footage or model outputs when you ask us to investigate an analysis problem. You can withdraw consent without affecting processing that was lawful before withdrawal.
• Legal obligations and claims: where we must keep or disclose a limited record under law, or need it to establish, exercise or defend a legal claim.

Automated analysis produces estimates and does not make legal, medical or similarly significant decisions about you. ShuttleSense does not use facial recognition and the current release does not automatically identify people in footage.

3. Other people in a recording

Only upload footage when you have the right to do so and the people shown or heard have been appropriately informed. A person in someone else’s upload can ask us to investigate or remove their data by emailing shuttlesenseai@gmail.com. Include enough non-sensitive detail to locate the recording, such as the date, venue, uploader or match title and approximate time in the video. We may ask for proportionate verification, but never send a password or an identity document unless we specifically explain why it is necessary and provide a secure route. We may restrict access or delete the relevant content while respecting the privacy of the uploader and other people.

4. No AI-model training on customer data

ShuttleSense does not use customer uploads or data derived from them—including video, audio, frames, player or shuttle tracking, pose features, analysis results, participant labels, corrections, feedback or support material—to train or fine-tune AI models. Existing models process uploads only to provide the requested analysis and related service functions described in this policy. We do not copy customer content into model-development or model-evaluation datasets. If we ever propose customer-data model training, we will update this policy before it begins and, where required, ask for a separate choice.

5. Service providers and recipients

We disclose only the data needed for the relevant service. Our current or release-configured providers are:

• Supabase: authentication, the primary database and profile-avatar storage. The primary project is hosted in Germany.
• Cloudflare: website delivery and security, waitlist storage, and source/highlight object storage.
• Novita AI: configured GPU processing for badminton analysis. It receives a time-limited route to the selected source and the job data needed to return results.
• Resend: optional account/service email delivery.
• Google: Google sign-in when selected, Google Play distribution for an Android release, and Gmail hosting for support, privacy and deletion correspondence sent to our published address. Website and app fonts are packaged or use system fonts; we do not intentionally call Google Fonts at runtime in the release covered by this policy.
• Apple: App Store distribution and Apple sign-in only in a release where those features are configured.
• RunPod: contingency analysis or highlight compute only in a backend release explicitly configured to use it.

Sentry is disabled in the current release: although the source includes its software library, no Sentry DSN is supplied and no crash or performance events are sent to Sentry. We will update this policy and the store disclosures before enabling it.

RevenueCat and paid billing are not active in the current production beta: the source includes RevenueCat's purchases software, but the production billing key and checkout switch are disabled, so no purchase can be completed and the software is not configured to send billing data. Before paid subscriptions launch, this policy and the store disclosures will be reviewed against the exact billing-enabled release.

A future web checkout is planned to use Paddle as merchant of record and RevenueCat for entitlement management. In a billing-enabled release, they may process the ShuttleSense account ID, email, country, product, price, currency, tax, subscription and purchase history needed to complete and manage a purchase. Paddle, rather than ShuttleSense, will process the full payment-card details used in its checkout. Apple or Google will process equivalent information for purchases made through their mobile stores.

We may also disclose information when required by law, to protect users and the service, or as part of a business transfer subject to appropriate confidentiality and notice. We do not permit service providers to use customer content for their own advertising.

6. International transfers

Some service providers may process personal data outside the UK. We maintain data processing agreements or equivalent data-processing terms with the processors used for the service. Where required, an international transfer is protected by UK adequacy regulations, the UK Addendum to the EU Standard Contractual Clauses, the UK Extension to the EU–US Data Privacy Framework, or another lawful safeguard. We record the provider, destination and safeguard that applies and review material subprocessor changes. Contact us for information about the safeguard used for a particular transfer.

7. Retention

• Account and profile: while the account remains open. An uploaded avatar remains until you replace it or delete the account.
• Unpinned source video: normally 7 days on Free and 90 days on Pro.
• Pinned source video: pinning suspends automatic expiry, so the source can remain beyond 7 or 90 days until you unpin it, delete the match or delete the account. After unpinning, an already-expired source is removed by the next lifecycle sweep.
• Analysis, statistics, highlights and corrections: retained with the match so your history works, until you delete the match or account. Normal source-video expiry does not itself delete these smaller results.
• Support: human access to source/model outputs expires no later than 14 days after you grant it and ends sooner if you withdraw or delete. A report and its access audit remain with the match until match or account deletion.
• Support, privacy and deletion correspondence: We retain support, privacy and deletion correspondence for 12 months after the case closes, unless we need it longer to comply with law or handle a legal claim. We then delete or anonymise it.
• Waitlist: until launch communications finish, you unsubscribe or ask us to remove it.
• Security and provider logs: only for the period needed for security, delivery, troubleshooting or a legal requirement under the relevant provider schedule.

8. Deletion and limited exceptions

You can delete an individual match or request permanent account deletion in the app. If you cannot sign in, use our signed-out account-deletion page. Deletion may run as a queued, retryable process because active analysis work and stored objects must be cancelled and verified. An explicit match or account deletion overrides a pin and support hold.

During account deletion we may keep a restricted working case and a pseudonymous execution receipt so we can verify completion and retry safely. The correspondence, email/account mapping and detailed receipt are destroyed no later than 30 days after completion. We may retain only:

• the minimum transaction, tax, fraud, dispute or other record required by law, for the applicable legal period;
• encrypted provider backups until they expire under the provider’s normal backup cycle; they are isolated from ordinary product use; and
• non-identifying aggregate operational information that cannot reasonably be linked back to you.

A future subscription must be cancelled through the provider that sold it, such as Paddle, Apple or Google. Before Paddle checkout launches, the account-deletion workflow must also be updated and independently tested so a web subscription cannot continue renewing for a deleted account. In-app deletion cannot reliably identify a separately submitted waitlist email, so ask us to remove that record too.

9. Your rights

Depending on where you live, you may have rights to access and receive a copy of your data, correct it, delete it, restrict processing, object to processing based on legitimate interests, and receive certain data in a portable format. You can withdraw consent at any time. You also have the right to complain to the UK Information Commissioner’s Office at ico.org.uk, or to your local data-protection authority where applicable.

Your right to object: you can object at any time to our use of legitimate interests for service-quality measurement, rally-correction analysis, security or reliability. Tell us which activity concerns you. We will stop unless we demonstrate compelling legitimate grounds that override your interests and rights, or the processing is needed for legal claims. We do not use your data for direct marketing on this basis.

Use the in-app controls or contact us. We may need proportionate information to verify your request and protect other users. These rights can have legal exceptions; if one applies, we will explain it.

10. Security, age and changes

We use access controls, encryption in transit, restricted signed links and other organisational and technical safeguards. No online service can guarantee absolute security. ShuttleSense is for people aged 16 and over, and we do not knowingly create accounts for younger children.

We will update this policy when our data practices change. For a material change, we will provide an appropriate in-app or email notice and request a new agreement or consent where the law requires it. The date above identifies the current version.

11. Contact

Controller: Translogic Limited, 71-75 Shelton Street, Covent Garden, London, United Kingdom, WC2H 9JQ.

Privacy and support requests: shuttlesenseai@gmail.com.