Privacy Policy

AI Golfing Coach, operated by Grip Intelligence AI Limited, analyses golf swings from video. That means we handle a recording of you, which is personal data. This page says who is responsible, what we collect, why, how long we keep it, and how to make us delete it.

Who is responsible

The data controller is Grip Intelligence AI Limited, a company registered in England and Wales under company number 17387904. Registered office: Office F18, 22-25 Portman Close, London, W1H 6BS. You can check that entry at Companies House.

Contact the controller at info@aigolfingcoach.com or support@aigolfingcoach.com. We are established in the United Kingdom, so UK GDPR does not require a separate UK representative.

Where we offer this

We offer AI Golfing Coach in the United Kingdom and in other countries outside the European Economic Area. We do not offer it in the EEA. That is why we have not appointed an EU Article 27 representative. If we later offer the app or the website there, we will appoint a representative first and name them here.

What we collect

• Your email address, from Apple when you use Sign in with Apple, from Google when you sign in with Google, or the address you type when you sign in with a one-time code we email you. We never see or store a password. If you use Apple's “Hide My Email”, we only ever receive the forwarding address. That is enough to run your account; we do not need your real one.
• Your name, if your provider supplies one, and the name you enter at first-run so we can greet you.
• Your age, which you enter at first-run. We use it to enforce the 13+ floor and to compare your swing against golfers in the same age band, not against everyone. Age is stored as a number on your profile, not as a date of birth.
• The country you play in, which you choose at first-run. It sets the flag on your locker and a default language. It is not used to infer location from GPS.
• Your interface language, which you choose at first-run and can change later. We store the locale code so the app and emails can match the language you asked for.
• The swing videos you upload. These show you, and usually where you were standing. Videos you import from your camera roll can carry their original sound; we store it as part of the video and never analyse it. Clips filmed in the app record no sound.
• Pose landmarks, the coordinates of your joints in each frame, extracted from the video. This is what the scoring actually runs on.
• Swing measurements and scores derived from those landmarks, plus the date of each upload.
• An optional scoring-improvement flag on your account, off until you switch it on. If you opt in, we keep anonymised numbers from swings we already scored (tempo, joint angles, flags) to improve shared typical ranges. We do not copy your video into that dataset.
• An optional product-email flag on your account, off until you switch it on. If you opt in, we may send occasional newsletters and product updates. You can turn this off in Account, or from the unsubscribe link on those messages.
• A Sign in with Apple token, only if you sign in with Apple. Apple issues it when you sign in; we keep it encrypted and use it for one thing: when you delete your account, we ask Apple to remove this app from your Sign in with Apple list, as Apple requires.
• A coach review you buy: which swing you sent, your questions, the coach's written reply, and the sale record. The coach sees that one swing's video and our measurements under an anonymous guest id, never your name, email, or country.
• A push token, only if you are signed in and have granted notifications. iOS sends an APNs token; Android sends an FCM token when that build includes Firebase. We use it to tell you a swing finished after the app was killed. Practice reminders do not use this token.

We do not use advertising or tracking cookies, and we run no analytics that follow what you look at or how long you spend on it. The only cookie we set is the one that keeps you signed in. The one thing the Android app does report automatically is described next. The iOS app does not send crash reports.

Server logs and your IP address

Like any web service, our server sees the IP address of the device that connects to it. We use it for three things, and nothing else:

• Web server logs. Each request to our server is written to a standard access log (IP address, time, the path requested, the response code and the app or browser version). The log lives only on our own server, rotates daily and is deleted after 14 days. We read it to diagnose faults and abuse.
• Sign-in throttling. When you ask for an email sign-in code, the request count for your address and your IP is kept for up to 60 minutes so that codes cannot be guessed or spammed. That counter lives in memory on our own server (a local Redis store), never with a third party, and expires on its own. The code itself is stored only as a keyed hash and expires after 10 minutes.
• Application error logs. When the app or the analysis fails, our server writes the error to its system journal so we can fix it. Those entries can carry a swing id or an account id, never your video or a measurement. The journal is capped in size and old entries are dropped automatically.

We never use your IP address to work out where you are, and we do not keep it against your account.

Pose data and biometrics

Pose landmarks are numbers that locate joints in a video frame. We use them to measure the swing you asked us to score. We do not use them to recognise who you are, to unlock the device, to search for your face, or to build an identity graph. We do not run facial recognition.

UK law treats some biometric data as a special category when it is used to uniquely identify a person. We do not use pose landmarks to recognise you. We treat the video and the landmarks as ordinary personal data used to score the swing you uploaded: they stay with your account, they are not sold, and they are deleted on the schedule below. Whether that treatment needs a formal DPIA is a legal question. We will update this paragraph if a UK solicitor tells us it does.

Why we are allowed to hold it

For UK GDPR we rely on these bases. Other countries where we offer the service have their own privacy laws; the same collection and deletion paths apply there. EU GDPR is not the basis we use while we do not offer the service in the EEA:

• Contract (UK GDPR / GDPR Art. 6(1)(b)). Creating the account, storing the profile you typed, analysing a video you uploaded, showing the report, locker, Compare, and (if you pay) Pro features, and sending the one-time welcome and sign-in code.
• Consent (Art. 6(1)(a)). The upload itself is the consent to analyse that clip. You can withdraw it by deleting the swing or the account. Optional scoring-improvement, optional product emails, and optional practice reminders are each off until you switch them on.
• Legitimate interests (Art. 6(1)(f)). Android crash and failure reports, so we can fix filming bugs (especially 120 / 240 fps) without reading your swing. We do not put your email, name, account id, video, or measurements in those reports. You can object by emailing us.
• Legal obligation (Art. 6(1)(c)), only if we must keep a limited billing or tax record that Apple, Google, or the law requires. Payment card numbers never reach us.

A separately consented seed dataset (people who signed our Seed Dataset Training Consent and Declaration, uploaded by staff, stored apart from product accounts) is used to calibrate event timing, scoring thresholds, and anonymous typical ranges before and after launch. That dataset is not your account swings, and it is never used as someone else's Swing DNA or Trends.

After launch you may opt in, from Account, to contribute anonymised measurements from swings we already analysed. Default is off. Opting in does not share your video, name, or DNA badge. Opting out or deleting your account removes your contribution rows.

Crash and failure reports

When the Android app crashes, or when it fails at something you asked it to do, it sends a report to Google Firebase Crashlytics. The most common case is filming at 120 or 240 frames per second: many phones cannot, and when yours cannot, that report is how we find out rather than guessing. The iOS app does not include Crashlytics and does not send these reports.

A report contains the error, the place in our code it came from, your phone’s make, model and Android version, and the recent steps our own code noted on the way there. It does not contain your email address, your name, your account id, your video, or any measurement from your swing. We do not use it to identify you, and it is never used for analytics or advertising.

Practice reminders

If you turn on practice nudges, the iOS or Android app can send you a notification suggesting a session. Those are written on your phone, by your phone. The app already holds your streak, your last score and what you are working on in order to show you the Locker, and the reminder is assembled from that copy. Nothing is sent to us to produce one, we do not know whether one was shown, and practice reminders do not use APNs or FCM.

Because a reminder can name your streak or your last score, it can appear on your lock screen where somebody else might read it. You can turn them off in two independent places: the switch in Account, and the system notification setting for the app. Either one is enough, and both are checked every time before anything is shown. They are off until you turn them on.

Analyze-complete notifications

If you granted notifications and stay signed in, the app may register a device token so we can ping you when a swing finishes after the process was killed. The ping says the report is ready, or that the read failed. It carries a swing id so the tap can open that report. It does not include your video, score, or email. We store the token on your account, replace it when the phone issues a new one, and delete it when you sign out or delete the account. Without the matching server keys the ping is simply not sent; local banners still fire while the app is alive.

How long we keep it

Overlay video is kept so you can reopen a reel. A free account can replay for 30 days; Pro can replay until the 12-month deletion. Scores, landmarks and measurements stay until you delete your account: those are the analytical record, not the footage of your face.

Who else sees it

• Amazon Web Services hosts the application and stores the data, in the US East (N. Virginia) region.
• Apple handles Sign in with Apple on iOS (and the web Apple path if you use it). If you hide your email, Apple gives us only the relay address. Apple also processes App Store subscriptions when you subscribe on iOS, and delivers analyze-complete notifications through APNs when a token is registered. Apple does not receive your swing videos from us.
• Google handles Google Sign-In. Google Play processes in-app subscriptions if you subscribe on Android. Email sign-in codes are sent by us, not by Google. When an Android build includes Firebase, Google also delivers analyze-complete notifications through FCM.
• Google Firebase Crashlytics receives the Android crash and failure reports described above, and nothing else. No email address, no account id, no video, no swing measurements. Not used on iOS.
• RevenueCat verifies App Store and Play purchases so your Pro access is tied to the same account you signed in with. It receives an opaque user id and subscription status, not your swing videos.
• The PGA professional who writes your review, if you buy one, sees that swing's video and measurements under an anonymous guest id. They never see your name, email or country.
• Postmark sends the one-time welcome when your account is created, a one-time sign-in code if you sign in with email, and optional product emails if you opt in. It receives your email address and the name we greet you with, not your videos or scores. Sign-in codes expire in minutes and are not stored as the digits themselves. Broadcast messages include an unsubscribe link Postmark honours.

We do not sell your data, and we do not share it with anyone else. Our own staff can view swing data through an internal console in order to support the product and check that scoring is behaving correctly. Staff may also see aggregated counts by the playing country you chose at first-run (how many golfers, how many swings, how many subscriptions). That is not a live location, and we do not show who has the app open. We do not locate you by GPS or IP. Staff may also upload seed videos that carry their own training consent; those sit in a separate corpus and are not mixed with ordinary account uploads.

International transfers

The product is hosted in the United States (AWS us-east-1). If you are in the UK, that is a transfer of your personal data outside the UK. We use Amazon as a processor under Amazon's published data-processing terms for that hosting. Apple, Google, RevenueCat and Postmark may also process limited account or payment data in the United States or other countries where they operate, under their own terms. We do not transfer your swing video to anyone except Amazon for storage and processing.

Your rights

If you are in the UK, UK GDPR gives you the right to access, correct, delete, restrict, object to, and port your data. These are built into the app and take effect immediately. In other countries where we offer the service, local law may add rights; the same download and delete paths still work:

• Download your data. Account → Download my data. Returns everything we hold about you as a JSON file.
• Delete a swing. Locker or Reel → Delete. Removes that video, its overlay, and its measurements from storage. It cannot be undone.
• Delete your account. Account → Delete account, or follow the steps on Delete your account. Permanently removes your account, every swing, and every stored file. This cannot be undone. If you signed in with Apple, we also ask Apple to remove the link. Deleting your account does not cancel an App Store or Google Play subscription: the store bills it, so cancel it there first.

For anything else, email info@aigolfingcoach.com or support@aigolfingcoach.com. You also have the right to complain to your data protection authority, in the UK, the ICO.

Children

This service is not intended for children under 13, and we do not knowingly collect their data. First-run asks for your age so we can refuse an account below that floor. If you believe a child has created an account, email us and we will delete it.

Changes

We record which version of this policy you agreed to each time you upload a swing. If we change it in a way that affects what we collect or how long we keep it, we will ask you to agree again rather than quietly applying new terms to data you gave us under the old ones.