Privacy Policy

Roadworthy ("we", "us") provides software for driving instructors to manage bookings, payments, routing, pupil progress and their business. This policy explains what we collect and why. We only collect what we need to run the service.

Two apps

There are two Roadworthy apps. Roadworthy is the instructor's app, where the diary, pupils, routing and earnings live. Roadworthy Student is a free companion app for the learner: it shows that learner their own lessons, what their instructor wrote up after each one, how far through the syllabus they are and anything left to pay. This policy covers both.

A learner links the Student app by scanning a code their instructor gives them, or by asking to join with the school's code and being approved by the instructor. A learner only ever sees their own record. They cannot see any other pupil, and they cannot see the instructor's diary, earnings or other business data. Nothing a learner does in the Student app changes their instructor's records.

Who controls your data

When an instructor uses Roadworthy to manage their pupils, the instructor is the controller of their pupils' data and Roadworthy is the processor acting on their instructions. For an instructor's own account, Roadworthy is the controller. The same applies to the Student app: the lesson records a learner sees there belong to their instructor, so requests to change or erase them are handled by the instructor. The anonymous identifier the Student app holds is controlled by us, and a learner can delete it from inside the app at any time.

What we collect

• Account data — your name, email and (via Sign in with Apple) an Apple identifier used only to sign you in.
• Business data you enter — pupils, lessons, availability, lesson types, prices, routes, expenses and packages.
• Pupil data — name, contact details, pickup address and lesson progress, entered by the instructor or submitted by a learner when booking.
• Location — when you use routing, your device location is used on-device to centre the map and order pickups. We do not track your location in the background.
• Payment data — card payments are processed by Stripe. We never see or store full card numbers.
• Usage data — which screens you open and which actions you take in the app and on this website, along with your device type, operating system version and app version. In the app this is linked to your account ID so we can see whether a feature is actually working for people. We never put a pupil's name, address, phone number or any lesson note into usage data.
• Learner app data (Roadworthy Student) — there is no sign-in and no account to create. The app holds an anonymous identifier on the device so it can be linked to the pupil record the instructor already keeps; we do not collect a learner's email address at all. If a learner asks to join using the school's code rather than a personal one, they type their name and mobile number so the instructor can recognise who is asking. We collect nothing else from the learner: their lessons, pickup address and progress are entered by their instructor, not by them.
• Push notification tokens — if a learner allows notifications, we store the device token so their instructor's app can tell them when a lesson moves, is cancelled or is written up. Deleting the app or signing out releases it.

How we use it

• To provide the app: your diary, routing, progress tracking, earnings and payments.
• To take card payments through your connected Stripe account.
• To send service messages (for example, booking confirmations).
• To support you and improve the product.
• To understand which parts of Roadworthy people use and where they get stuck, so we can fix them.

We do not sell your data or your pupils' data.

We do not use your data for advertising, and we do not share it with advertisers or data brokers. We do not track you across other companies' apps or websites.

Analytics

We use PostHog to measure how the app and this website are used. It is hosted in the EU and acts as our processor. It records events such as opening a screen, adding a pupil or saving a lesson, together with basic device information.

In the app, events are tied to your account ID (a random identifier, not your name or email), and session recording is switched off there — nothing on your app screen is ever captured.

On this website, analytics cookies are only set once you accept them. If you do accept, PostHog may record your session on the website — the pages you open and where you click — so we can see where the site is confusing. Decline, and no recording is made.

Personalised pages we email to driving schools. If we write to your school and you open the page made for it, we record that the page was opened, whether you followed a link from the email, and the broad kind of device you used — phone or computer, nothing more specific. No cookie is set and we do not store your IP address. We do this to know whether our email reached a real person, and to offer the right way to install the app: a computer cannot install an iPhone app, so that page shows a code to scan with your phone instead. Our lawful basis is legitimate interest in understanding whether our own outreach works. Reply to any of our emails and we will delete the record and stop writing to you.

You can opt out at any time by emailing zac@darkrhino.com, and we will exclude your account from analytics.

How we contact driving schools

We write to driving instructors and schools we have not worked with before, to introduce the app. We did not get your address from you: we collected it from your own public listing — your website, or a public directory where you publish it so that learners can get in touch. We hold your business name, that address, your area, and a record of what we have sent you.

Our lawful basis is legitimate interest in offering a product built for your trade. You can stop it immediately by replying "no thanks" to any of our emails, or by emailing zac@darkrhino.com. We record the objection so no future message is sent, and we will delete everything else we hold about you on request. We do not pass your address to anyone else for their own marketing, and we never sell it.

Before we send anything we check whether an address is still live, so that we are not repeatedly mailing a mailbox that no longer exists. That check involves sending the address to an email-verification provider (see below). Nothing else about you is sent with it.

Where it's stored, and who else sees it

Data is stored on our infrastructure provider (Supabase, hosted in Frankfurt, Germany) and our application host (Laravel Cloud). These others act as our processors, each under their own data-protection terms:

• Stripe — card payments.
• PostHog (EU) — usage analytics and, where you have accepted analytics on this website, session recording.
• Google Workspace — the mailbox our outreach email is sent from and replies are received in.
• Resend — transactional email and inbound mail handling.
• MillionVerifier — checks whether an email address is deliverable before we write to it. They receive the address only.
• Anthropic — the AI features described below. They do not train on it.

We do not sell your data or your pupils' data to any of them, and none of them may use it for their own purposes.

The AI features

Two parts of the instructor app send data to Anthropic, the company behind Claude, so that it can be processed by their model:

• Lesson notes. When an instructor dictates a note after a lesson, the words they spoke are sent so they can be turned into a written summary. That note is about a named pupil and usually names them.
• Ask Roadworthy. When an instructor asks a question about their own business, we send their question along with a summary of that school's own data — pupils' names, lesson dates, progress, and totals for what has been paid and what is owed.

What is deliberately not sent: no pupil's phone number, no pupil's email address, and no pupil's home or pickup address. Those answer none of the questions these features exist for, so they never leave our systems for this purpose.

Anthropic processes this on our instructions as our processor and does not use it to train their models. An instructor who would rather nothing went to them can simply not use these two features; nothing else in the app depends on them.

Your rights

You can access, correct or delete your data, and ask us to export it. Email us at zac@darkrhino.com and we'll help.

Contact

Questions about this policy? Email zac@darkrhino.com.

This document is a plain-English summary and will be finalised before public launch.