Ride Studio

Privacy policy

Your footage. Your information.

This explains what Ride Studio collects, why we use it and how to ask us to remove it. Last updated 25 September 2026.

Who is responsible

Ride Studio is operated by Greg Sharples as a sole trader. Greg Sharples is the data controller for this service, including the analysis service that runs behind Ride Studio.

Greg Sharples, trading as Ride Studio
Fuel Studios, Pottergate
Norwich, Norfolk
NR2 1DX
United Kingdom
[email protected]

What we collect

  • Account information: your name, email address, sign-in details, account settings and subscription status. Passwords, where used, are stored as hashes.
  • Your rides: uploaded videos and session footage, the waves you choose, titles, surf spot, rider selection, height, stance, equipment details, markers and notes you choose to provide.
  • Analysis: body poses, image tracks, the stance we detect from how the rider moves, measurements, confidence and quality checks, processing times, versions and diagnostic records generated from your footage.
  • Payments: Stripe customer and subscription references, payment status, invoices and upload allowances. Stripe handles payment details; Ride Studio does not receive or store your full card number.
  • Support and technical information: messages and issue reports, device/browser information, security logs, IP addresses where needed by hosting or security services, and service errors.

A video may also show other identifiable people. Please only upload footage you have the right to use, with appropriate permission from the rider and anyone else whose permission is required.

Why we use it

We use account details, footage, rider information and payment records to provide the service you request: storing and playing videos, running analysis, managing your allowance, taking payments and sending essential account or job updates. Our legal basis is performance of our contract with you, or steps you ask us to take before entering that contract.

We use limited technical records and support information to secure the service, prevent abuse, investigate problems and correct results. Our basis is our legitimate interest in operating a reliable service. Where uploaded footage includes other people, we limit processing to what is needed to analyse the selected rider and protect the service.

We retain records where required to meet tax, accounting or other legal obligations. If we ask for consent for an optional use, you can withdraw it without affecting processing that took place before withdrawal.

Some information is necessary to provide the service. For example, without a video, a rider selection and the requested scale information, we cannot carry out that analysis.

How your video is used

Our algorithms process footage to estimate movement, body position, stance and wave measurements. We detect whether the rider surfs regular or goofy from their movement, and you can change it on the ride. The algorithms do not identify you through facial recognition, and the results are not medical assessments or decisions about your legal rights.

Authorised operators can view footage, overlays and diagnostic information when maintaining the service, investigating a failure or reviewing a result. Customer accounts can access only footage they are authorised to see.

Uploading a video does not give us permission to publish it in marketing or use it to train a general model. We will ask separately before using your footage for either purpose. Improving or correcting your own analysis is part of providing the service.

Service providers and storage

We use Cloudflare for website delivery, security and private object storage; Stripe for payments; Resend for transactional emails; and Proton for support email. We also use hosting and backup services to operate Ride Studio. These providers receive the information needed for their role. A ready-email link requires your normal authorised sign-in; it is not a public link to your footage.

When you start analysis, the ride’s footage and the details needed to analyse it are processed on GPU servers rented from RunPod. Those servers run only our software and models, receive the ride through a short-lived private link, and return the result to us. Our analysis service keeps processing copies and versioned results so jobs can recover and results can be reviewed without running the analysis again.

If you upload longer session footage to choose a wave, we make a small private preview. To suggest where the waves are, we send reduced-resolution frames from that preview through OpenRouter to a Google Gemini video model, with zero data retention and no data collection requested. You can always choose the wave yourself.

Some providers, including RunPod and OpenRouter, may process information outside the UK, for example in the United States or the European Union. Where a restricted international transfer occurs, we use the applicable adequacy arrangements or contractual safeguards required by data-protection law. Contact us for information about the safeguards relevant to your data.

We do not sell your personal information. We may disclose information where required by law or where necessary to establish or defend legal rights.

Cookies and site statistics

Necessary cookies keep you signed in and support account security. Your browser may also store display preferences. Stripe may use cookies or similar technology on its payment pages, under its own privacy information.

We use our own hosted Plausible service for aggregate page statistics. Our analytics integration does not set analytics cookies or send your email address, ride identifiers, authentication tokens or URL query strings. Private Studio pages are recorded as the general Studio page, rather than an individual ride.

Retention and deletion

Your account and saved rides remain available while you use the service, including the saved access described in your plan. Cancelling a paid subscription does not itself delete your account or footage.

Session footage and its preview are removed after seven days; any wave you save remains in your library until you delete it. Deleting a ride removes it from your Studio library and queues removal of its Studio upload. Processing copies, diagnostics and compute files held by our analysis service are retained separately. To request removal of those copies, all rides or your account, contact [email protected]. We will verify the request, identify the associated records and explain any information we must retain.

We keep support and diagnostic records for as long as needed to resolve the relevant request, maintain or correct the analysis, investigate abuse or handle a dispute. We keep financial records for the applicable statutory period; UK sole-trader tax records are normally required for at least five years after the relevant 31 January filing deadline.

Routine server backups are normally retained for around one week and off-site backups for around two weeks. Deleted information may remain in a protected backup until that rotation completes. If a backup is restored, valid deletion requests must be reapplied. A specific legal obligation or documented dispute may require some records to be kept longer.

Your choices and rights

You can ask for access to your personal information, correction, deletion, restriction or a portable copy where the relevant right applies. You can object to processing based on legitimate interests and withdraw consent for optional uses. Contact [email protected]; we may need information to verify your identity before acting.

We normally respond to data-rights requests within one month. Where the law permits extra time for a complex request, we will explain why. You can also complain to the Information Commissioner’s Office. You do not need to complain to us first.

If this policy changes materially, we will make the updated policy available and notify you where appropriate.