Privacy policy
Privacy policy
In short.
- The app records rowing outings: the boat's motion and, if you switch it on, its position. The recording is a file on your phone. You choose whether to store it in your account or share it with a club.
- A cox's audio is recorded only when the mic is switched on, and only to the phone. If the boat is streaming live, the audio is relayed to the coach as it happens and is not stored by us, unless the person recording chooses at the start to keep it for seven days for the crew and coaches to review the outing. It is never kept anywhere for longer.
- We keep what we need to run the service and nothing for advertising. We do not sell personal data. We use no tracking cookies, on the site or in the app.
- You can delete your account from inside the app. You can complain to us, and to the Information Commissioner's Office.
1. Who we are
Renegade Dynamics is the trading name of Jon Davies, a sole trader in the United Kingdom ("we", "us"). Address for service: Flat 3 Doyle House, 46 Trinity Church Road, London, SW13 8ED. Email: support@renegadedynamics.co.uk.
Our registration with the Information Commissioner's Office as a data controller is pending; this page will carry the number when it is issued.
We are the controller for your account, for the telemetry the app sends about its own behaviour, for the live relay, and for this website. A club that keeps its roster and sessions in the app decides who in the club may see them and how long they are kept. For that data the club is the controller and we process it on the club's behalf under the club terms.
2. What we collect and why
The table lists each kind of data, where it comes from, and the lawful basis under UK GDPR that we rely on.
| Data | What it is | Basis |
|---|---|---|
| Account | Your name, email address, a stable identifier from the sign-in provider you chose (Apple, Google, or an email one-time code), and the time and method of each sign-in. Sign-in is run by Microsoft Entra External ID; we never see a password. | Contract: providing the service you signed up for. Legitimate interests: keeping the account secure. |
| Club membership | Which clubs you belong to, your role in each, who granted it and when, join requests and invitations, and claims of a club with the evidence given. | Contract. |
| Sessions | A recording of a boat being rowed: motion from the phone (and from sensors, when used), the boat class, start and end times, which seat was which, and the crew and coaches named from the roster. Motion data on its own does not identify anyone. A session becomes personal data when it names a crew or includes position. | Contract. Where a club names you in a session, the club's legitimate interest in coaching its members. |
| Position | GPS position, speed and heading over the outing. Recorded only while you have location switched on in the app. Off by default. | Consent, given by the switch and withdrawn by it. |
| Audio on the phone | What the microphone hears while the mic switch is on, saved into the session file on the recording phone. It leaves the phone only if you send it (see Audio). | Consent of the person recording. The recorder is responsible for telling the crew, and the club notice covers coaching sessions. |
| Live audio | While a boat is streaming and the mic is on, the audio passes through our relay to the coaches watching that session and is discarded within sixty seconds. It is never written to storage. | Legitimate interests: coaching, where a crew expects the cox to be heard by the coach, with the on-screen indicator and the mic switch as the opt-out. |
| Talk-back | A coach's voice sent to the boat during a live session. Relayed the same way and not stored. | Legitimate interests, as above. |
| Kept cox audio | Only when the person recording ticks "Keep audio 7 days" at the start of a streamed session: the audio of that outing is kept in its own storage, separate from the session, for seven days after the outing ends, so the crew and coaches can review the outing with it and for the cox report if one is asked for. Then it is deleted. Only signed-in members of the club who may open the session can hear it; share links carry no audio. | Consent of the person recording, given by the tick and its notice at that moment. The recorder is responsible for telling the crew, and the club notice covers coaching sessions. |
| Subscriptions | Whether your account or club has the Live or Club tier, from Apple, Google or Stripe through RevenueCat: an app-user identifier, the product, the dates, and transaction identifiers. We do not receive card details. For a club buying on the web: the contact's name, email address and billing address. | Contract. |
| Telemetry | What the app did, without the content of what it recorded: app version, device model, operating system, errors and crashes, request timings, and named events such as "a session was recorded" or "a live session was watched", with durations. | Legitimate interests: keeping the software working and knowing which parts are used. |
| Problem reports | When you choose "Report a problem": your text, the app version, device and operating system, the session identifier if any, and the app's last few hundred log lines. | Contract: answering the report you sent. |
| Support email | Whatever you send to support@renegadedynamics.co.uk, and our replies. | Legitimate interests: answering you. |
| Sensor waitlist | The email address you give, and the boat class and club if you add them. | Consent. Unsubscribe by replying or by the link in any message. |
3. Audio
Audio is the one kind of data in the app that is about people other than the user, so here it is in plain words.
- Nothing is recorded until the mic is switched on. While it is on, the recording screen shows a recording indicator. Switching the mic off stops it.
- The recording stays on the phone. It is part of the session file on the device that recorded it. The copy of the session in your account does not contain the audio.
- Live audio is relayed, not stored. If the boat is streaming, the audio goes through our relay to the coaches watching and to the talk-back ear, and is dropped after a buffer of at most sixty seconds that exists so a coach who joins late hears the last minute. A coach cannot scrub back through it. Our tests check that a stored session contains no audio.
- Seven days, by choice. The person recording can tick "Keep audio 7 days" at the start of a streamed session. Then, and only then, the outing's audio is kept in its own storage for seven days after the outing ends, so the crew and coaches can review the outing with it in the app, and for the cox report if one is asked for. It is deleted on the seventh day by the app and, independently, by a rule on the storage itself, and it is never copied anywhere that keeps it longer. Only signed-in members who may open the session can hear it. The tick shows this notice at that moment, and the crew and coach should be told.
- Sending audio to us is a separate act. If a future feature needs the audio (the AI outing report), you will choose a file and see what it is for before it leaves the phone. We will not use audio to improve the software, and we will not train anything on recordings of people who are not users.
- The club tells its members. The club terms include a notice that coaching sessions may be relayed live to the club's coaches, shown to a member on joining.
4. How we use it
- To run the service: recognising you, storing the sessions you choose to store, showing you the sessions you are entitled to see, streaming a live session from a boat to its coaches, and sending talk-back the other way.
- To analyse the rowing: rate, split, distance per stroke, the stroke shape, seat and oar movement where sensors are used, for the crew and coaches of that session.
- To let a club run its roster, squads, display sets and retention setting.
- To take payment for a subscription through Apple, Google or Stripe, and to know which tier applies.
- To answer a support request or a problem report, and to keep the software working.
- To send you a message about the sensor waitlist, if you joined it.
We do not use personal data for advertising or profiling, we make no automated decisions with legal or similar effect, and we do not sell it.
5. Who can see it
| Who | What |
|---|---|
| You | Your account, your sessions, and sessions you were named in. |
| Your club's administrators and coaches | The sessions recorded into their club, including crew names and position where recorded, for the club's retention period. |
| Athletes in your club | Sessions they were part of. |
| Anyone with a live link | A recorder may share a live session by link or QR code for the length of that session. The link stops working when the session ends. |
| Us | Account, membership and subscription data to run the service. Session content only to diagnose a problem you or your club have reported. A site administrator's access to a club's data is granted by the club and logged. |
| Our processors | The providers in section 6, under contract and on our instructions only. |
| Authorities | Only where the law requires it. |
6. Who processes it for us
Each provider processes data for us under a data processing agreement in its terms. We keep a register of them.
| Provider | What for | Where |
|---|---|---|
| Microsoft Azure | Hosting: the relay, the session store, the database, telemetry, backups. | United Kingdom and European Union regions. |
| Microsoft Entra External ID | Sign-in and account identity. | European Union. |
| Apple | Sign in with Apple, if you choose it; App Store purchases and subscriptions. | Apple's terms; international. |
| Sign in with Google, if you choose it; Google Play purchases and subscriptions. | Google's terms; international. | |
| RevenueCat | Subscription status across the stores and Stripe. | United States, under the UK addendum to the standard contractual clauses. |
| Stripe | Payment for the Club tier and the sensor waitlist. Stripe holds card details; we do not. | Stripe's terms; European Union and United States. |
| Azure Communication Services | Sending email from the service: sign-in codes, invitations, problem-report receipts. | United Kingdom and European Union. |
| Microsoft 365 | Our support mailbox. | United Kingdom and European Union. |
| Cloudflare | Serving this website and its server logs. | International; logs held under Cloudflare's data processing addendum. |
Where a provider is outside the United Kingdom, the transfer is covered by the UK's adequacy regulations, the UK International Data Transfer Addendum, or the UK–US data bridge, as the provider's terms state.
7. How long we keep it
| Data | Kept |
|---|---|
| Sessions in your account | Until you delete them or delete your account. |
| Sessions in a club | For the club's retention setting (the default is twelve months), or until a club administrator deletes them. |
| Kept cox audio | Seven days after the outing ends, when the person recording chose to keep it; never longer, wherever it is. |
| Live audio and talk-back | Not retained. A relay buffer of at most sixty seconds. |
| Account and membership | While the account exists. Deletion replaces the account record with a marker so the identifier cannot be reused. |
| Invitations and join requests | Until accepted, declined or expired, at most 30 days. |
| Subscription records | While the subscription and the account exist, then as long as tax law requires for the transaction records. |
| Telemetry and crash reports | 90 days. |
| Problem reports and support email | 12 months. |
| Waitlist | Until you unsubscribe, or until the sensor has shipped and the list has served its purpose. |
| Backups | The database keeps a continuous backup for 7 days; deleted session files are recoverable for 14 days. Deleted data leaves backups on that schedule. |
| A record that a deletion request was received and carried out | 12 months, holding only the date and the email address used. |
8. Improving the software
We may use telemetry that has been de-identified, and session data that contains no names, no position and no audio, to test and improve the analysis and the app. Audio is never used for this. Recordings of people who are not users are never used to train anything. We may publish aggregate figures (for example, how many outings were recorded in a month) that cannot identify anyone.
9. Your rights
Under UK data protection law you can ask us for a copy of your personal data, ask us to correct or delete it, restrict or object to how we use it, or ask for it in a portable form. Where we rely on consent (position, audio on the phone, the waitlist), you can withdraw it at any time; withdrawing it does not affect what was recorded before. Where we rely on legitimate interests (the live relay), you can object, and the mic switch is the immediate way to do so.
Your sessions are already portable: every session is an RGIF file, an open format you can export from the app at any time. See the data promise.
To exercise any right, email support@renegadedynamics.co.uk from the address on your account. We reply within one month. If we need longer for a complex request we will tell you why within that month.
10. Deleting your account
In the app: Account → Delete my account. The screen says exactly what will happen; you type your email address to confirm, and the deletion happens seven days later unless you sign in before then and choose Keep my account. You can also email us with the subject "Delete my account" from the address on your account.
What is removed: your account, your memberships and roles in every club, invitations to you, your name from the crew and coach lists of every session, sessions you recorded that are in no club, and any telemetry that identifies you. What is kept: sessions recorded into a club stay with the club, with your name removed, for the club's retention period, because they are the club's records under the club terms. The session files on your own phone are yours to delete from the phone.
Deletion takes effect in the live service on the seventh day after you ask, and clears from backups on the schedule in section 7. Sessions a club keeps show the recorder as "Deleted account". Full instructions are in Deleting your account and getting your data out.
11. Complaints
If you think we have handled your personal data wrongly, tell us at support@renegadedynamics.co.uk with "Complaint" in the subject. We acknowledge every complaint within 30 days, make the enquiries it needs, and tell you the outcome without undue delay. If you are not satisfied with the outcome, or at any time, you can complain to the Information Commissioner's Office at ico.org.uk or on 0303 123 1113.
12. Children and junior rowers
- You must be at least 13 to hold an account. We do not knowingly hold an account for anyone younger. If you believe a child under 13 has an account, tell us and we will delete it.
- A junior of 13 or over may hold an account. We collect nothing from a junior's account beyond what an adult's account collects, and the app is not listed in the stores' children's categories.
- A club can put a junior on its roster without the junior holding an account, so that a session can name its crew. That record is the club's, holds a name and a seat, and is deleted when the club removes it or the club's retention period ends. Schools and junior clubs should read this section before signing up.
13. Security
Data is encrypted in transit and at rest. Session files are stored in private containers and served only to signed-in users who are entitled to them; live links expire with the session. Access by us to the production service is logged. If a breach puts your rights at risk we will tell you and, where required, the Information Commissioner's Office within 72 hours of becoming aware of it.
14. This website
This site sets no cookies and loads nothing from third parties: the fonts are served from this domain. Cloudflare, which serves the site, keeps ordinary server logs (IP address, the page requested, the time, the browser's user-agent string) for a short period for security. If we add analytics later it will be a cookie-free, aggregate service and this section will say so.
15. Changes
We will post changes on this page with a new effective date. For a change that affects what we collect or how we use it, we will tell signed-in users in the app or by email before it takes effect.
16. Contact
Jon Davies, trading as Renegade Dynamics
46 Trinity Church Road
London
SW13 8ED
Email: support@renegadedynamics.co.uk