Privacy Policy

This policy explains what JoltMile does with your personal data, why, and what rights you have over it. It is written to meet the UK General Data Protection Regulation (UK GDPR) and the Data Protection Act 2018.

Who is responsible for your data

JoltMile is run by Reeksac, a business based in the United Kingdom, trading as JoltMile. A postal address for the service of documents is available on request from support@joltmile.com. Reeksac is the data controller for the personal data described here, which means we decide what data is collected and why.

For any privacy question, or to exercise any of the rights below, email support@joltmile.com.

What we collect

You give us this directly:

• Account details - your email address, an encrypted form of your password, and a display name if you set one.
• Your records - shifts (dates, times, odometer readings, mileage, earnings and tips, notes), any shift you save as a draft to finish later, expenses and any receipt images you attach, saved postcodes, and your settings.
• Other income you choose to add - money you earn outside the driving, if you enter it: what you called the source and what kind it is, then each payment with its date and amount. For a job, that is the pay before tax plus the tax already deducted from it, which is what lets the tax estimate credit the tax your employer has already paid. Any invoice or receipt you attach is stored the same way as an expense receipt. None of it is required, and leaving it out only means the tax estimate assumes the driving is all you earn. If you import a job from HMRC, we also keep the employer's name and PAYE reference, which the Self Assessment walk-through shows you on the employment pages.
• Account security events - a record of when a change to your email address was requested, approved, completed or cancelled, with the addresses involved and the IP address it came from. This is what lets us tell you if someone tries to move your account to an address they control.
• Setup answers - your vehicle and fuel from setup, your insurance if you add it, and a few tax-status questions, asked on the Self Assessment screen, used only to decide which deadline reminders apply to you.
• Deadline emails, if you turn them on - a record of each time you turn them on or off, when, and the words the switch showed you, plus which of those emails we have sent you. This is our record of your consent. They are off unless you turn them on in the app, under Settings, Reminders.
• Messages you send us - anything you write on the contact form, and the kind of message you pick. From the phone app it also carries the app version and build, whether it is iPhone or Android, the phone's operating system version, the screen you came from, and a screenshot if you add one. When you are signed in we add your account id and account email, checked from your sign-in. The form lists all of this before you press Send.

How the phone app is used. The iOS and Android apps record a small set of steps so we can see where the app loses people: opening setup and each setup question reached, finishing or skipping setup and the tour, your first and second shift, reaching the free limit, seeing a subscription screen and which one, starting, completing, cancelling or failing a purchase, tapping restore, answering the reminders question, seeing the summary after a shift, and opening or using one of the newer tools: the quarterly updates, the year-end tidy-up, the check against what platforms told HMRC, the calendar export, screenshot import, Best times, the help answers, the driving reminder, a shift started from Siri, a widget or a shortcut, the home and public charging switch, the local fuel price suggestion, the weekly put-aside line, the service notice, whether a This week widget is on your home screen, and the Ready to drive checklist before a shift: when it is shown, which check was sorted or still needed (such as location or your vehicle, never the answer itself), putting it off, and starting a shift from it. Each record holds that step's name from a fixed list, the day (not the time), the app version, iPhone or Android, a short label such as which setup question it was, and your account id, so that a person is counted once. It never holds your email, your location, anything you typed, or any of your figures. Records are sent straight to our database, which only lets the app add them, not read them back. There is no third-party analytics or tracking code in the app, and the website sends none of this.

Location, in the phone app only. Your location is used only between Start shift and End shift, to measure your business miles and to find the postcode where the shift started and finished. The miles and those two postcodes are kept with the shift. The positions themselves stay on your phone: they are turned into postcodes on the phone, using a postcode directory built into the app, and deleted once that is done. The one exception is a Northern Ireland postcode, which the built-in directory does not cover: then the position is sent to our own server to find the nearest postcode, and it is not stored or logged there. If you allow location Always on an iPhone, it is used for the same thing and nothing more: it lets the app carry on measuring if your phone closes JoltMile during a shift. While a shift runs, the On shift screen can draw the route you have driven so far as a heat map. It is drawn from those same positions, held only in the phone's memory, never saved or sent, and gone when the shift ends or the app closes. You can choose to show streets under it. They are off unless you turn them on. With streets on, your phone downloads the map for the area around you from our own map storage on Cloudflare, never from a map company, so that storage can tell roughly where the phone is. The request carries nothing that says who you are, and we keep no record of it. Your route itself is still never sent. We never keep a record of where you went, and the app does not use your location when no shift is running, with one exception you have to turn on yourself, below. The website does not use your location at all. There are no advertising cookies and no cross-site trackers.

Remind me when I am driving, if you turn it on. It is off unless you switch it on under Settings, Reminders. On an iPhone it uses the phone's low-power "significant change" location signal, which needs location Always, together with Motion & Fitness, to notice that the phone is in a moving car while no shift is running. On Android it uses the phone's own activity recognition (Physical activity) and no location at all. Either way the check happens on your phone, and nothing from it, not a position and not an activity, is stored or sent to us or anyone else. All the app keeps is the time of the last reminder, on the phone, so it can offer to start a shift from then.

About postcodes. A shift can carry a start, end and return postcode, and you can save postcodes you use often. These are stored with the shift for as long as your account exists, shown in your shift log, and included when you export your data. They are also sent to a lookup service when you ask for a driving distance. They are postcodes only, never a full address and never a live location.

Postcode data. The postcode directory built into the phone app contains OS data © Crown copyright and database right 2026, Royal Mail data © Royal Mail copyright and database right 2026, and data from the Office for National Statistics licensed under the Open Government Licence v3.0.

Anonymous benchmarks

How you compare, in the app, shows your earnings per hour, per mile and per shift, your shift length and your miles per shift beside the same figures for other drivers. To make that possible we work out those averages from the shifts of every driver who has not turned it off, every hour or day, and keep one figure per driver per platform and time range for no longer than the next refresh. Other drivers only ever see rounded ranges: the middle, the typical spread, and the 10th and 90th percentiles. Nobody sees your figures, your name, or how many drivers are behind a figure, and a figure is not shown at all until it is built from at least 10 drivers and 30 shifts. Your own position is worked out on your phone and never sent.

It is on by default. Turn off Include my data in anonymous benchmarks in Settings, Preferences and your shifts leave every comparison straight away; you can still see how you compare.

Referral codes and the partner programme

JoltMile partners are people and businesses who recommend the app and are paid a commission when somebody they referred subscribes. If that applies to you:

• If you arrive through a partner's link - we count the visit. To tell repeat clicks apart we keep a scrambled, one-way code made from your IP address and browser, never the address itself, and nothing is stored on your device.
• If you tap “Get the app” after arriving through a partner's link - we copy that link to your clipboard, so the app can fill in the partner's code for you. The first time the app opens it checks the clipboard once for a JoltMile link, and only if there is a web link on it; your phone asks your permission before the app can read it. Nothing else on the clipboard is kept or sent anywhere. On Android, Google Play passes the code to the app directly instead.
• If your account is linked to a partner's code - we record which code and when. We use your subscription payments to work out the partner's commission, and keep a record of each payment and the commission on it. The partner sees totals only: how many people clicked, signed up and subscribed, and what they earned. They never see your name, email address, records or anything about your driving.
• If you are a partner - we hold your name, email address, the bank details you enter on your partner dashboard (the name on the account, the sort code and the account number), your codes, and the commission and payout records for your account, to run the partnership and pay you under the partner agreement. Only JoltMile sees your bank details in full; your dashboard shows them with most of the numbers hidden.

Inviting other drivers

Drivers can invite other drivers with their own link or code, and both get a free month of JoltMile once the invited driver subscribes and keeps using the app. If you invite someone, or join with an invite:

• What the person who invited you sees - only that someone joined, and whether the invite is pending, qualified or not eligible, with a date. Never your name, email address, payments or anything you log.
• What we keep to stop people inviting themselves - a scrambled, one-way code made from your phone's app identifier (on iPhone, the identifier Apple gives our apps; on Android, a random id the app makes), a scrambled code made from your email address, and a scrambled code made from the network you joined from and your phone's model. None of these can be turned back into the original. We compare them with the account that invited you, and use them for nothing else.
• What we check before an invite counts - that the subscription was paid and not refunded, and that the invited account has logged a few shifts. We look at the shifts as a count and dates, and sometimes a person reviews an invite before it counts.
• The legal basis is our legitimate interest in running the invite programme fairly and stopping misuse. These records go when your account is deleted.

Cookies and browser storage

JoltMile sets no cookies at all, and there is no consent banner because there is nothing to consent to. Under UK law consent is needed to store or read information on your device beyond what the service you asked for requires - and everything below is exactly that. Our analytics store nothing on your device, so they do not need consent either; they are still described above, because being told about them is a separate right. There is a fuller explanation on the cookie policy page.

What the app keeps on your device (on the website, in your browser's own storage):

• Your sign-in session, so you stay logged in between visits.
• An offline cache of your own shifts, expenses and settings, so the app works without a connection and syncs when you reconnect.
• In the phone app, the app usage steps described above, held until they are sent, which is usually a few seconds later.
• Small device preferences, such as when you last exported a backup, which reminders this phone sends, and, in the app, whether your last five shifts were timed or typed in, which decides whether the main button is Start shift or Log a shift.
• A partner's referral code, only if you arrived through their link and chose to have it remembered. It is kept for 60 days. See the cookie policy.
• Nothing from the in-app assistant. Its conversations are not stored, here or anywhere else. Close the panel and the conversation is gone.

Deleting the app, or clearing your browser storage, removes all of this. Your account and records on the server are unaffected.

Why we are allowed to use it (lawful basis)

• Performance of a contract - holding your account and records so the app can do what you signed up for.
• Legitimate interests - keeping the service secure, preventing abuse, and fixing faults. We only rely on this where it does not override your rights.
• Legal obligation - keeping records of payments for the period tax law requires.
• Legitimate interests, for referrals - counting visits through partner links and linking an account to a partner's code, so we can pay partners fairly. Partners never see who you are.
• Performance of a contract, for partners - using a partner's details to run the partnership and pay them.
• Consent, for deadline emails - the two January emails about the 31 January deadline are only sent if you turn them on. Withdraw that at any time with the one-tap unsubscribe link in either email, or the switch in the app, and they stop.
• Legitimate interests, for analytics - counting page views and page load times so we can tell which parts of the site are slow or unused. This needs no consent because nothing is stored on your device and nothing identifies you or follows you between sites.
• Legitimate interests, for anonymous benchmarks - comparing your rates with other drivers', which drivers ask for and which shows nobody's figures. It is on by default and you can turn it off at any time in Settings.
• Legitimate interests, for how the app is used - the app steps described above, so we can see where setup or the subscription screens go wrong and fix them. They are kept to the fixed list, carry nothing you typed, and are never shared with anyone or used for advertising. You can ask us to delete yours at any time.

We do not sell your data, share it with advertisers, or use it to train any AI model.

Who else processes it

We use a small number of service providers, each of which only ever acts on our instructions:

• Supabase - hosts the database and the receipt files you attach, and handles authentication.
• Vercel - hosts and serves the application.
• Google Maps - calculates the driving distance between two postcodes, for example your commute at the end of a shift. Only the postcodes are sent, never your identity or your records.
• postcodes.io - looks up the location of a postcode when the Google Maps route is unavailable, so a distance estimate can still be given. Only the postcode is sent, never your identity or your records. For a Northern Ireland shift in the phone app, our server also sends it the position where the shift started or ended, with nothing else attached, to find the nearest postcode.
• Google Gemini - answers the questions you type into the in-app assistant. What is sent is your question, up to the last two messages of the same conversation, and the Knowledge Centre extracts we picked to answer it. Your name, your email address, your shift records, your earnings and your tax figures are never sent. Questions about your own figures are worked out inside the app and never reach Google at all. We use the paid tier, under which Google does not use what is sent to train its models. Nothing you ask is stored by us. It also reads a picture, if you ask it to: a weekly earnings summary you import as shifts, a platform's annual tax summary on the Check against HMRC screen, or screenshots of the HMRC app or a photo of your P60 when you import PAYE income. Those HMRC pictures can show your name and part of your National Insurance number; only the employer, PAYE reference, pay and tax are kept, and only once you have checked and saved them. Only the picture is sent, never your other records, and we do not keep it after it has been read. The same paid-tier terms apply to it. The days or the figure read from it are shown to you to check before anything is saved. When you look up a registration, it is also asked, with Google Search, for the vehicle's typical type, fuel and fuel economy; only the make, model, year, engine size and fuel are sent, never the registration.
• The DVLA and the DVSA - if you add a registration to a vehicle in the phone app, our server sends that registration, and nothing else, to the DVLA's Vehicle Enquiry Service and the DVSA's MOT History service. They send back the make, model, colour, year, engine size, fuel, MOT and tax dates and the last MOT mileage, which we use to fill in the vehicle and remind you before the MOT and tax are due. We keep the registration and those dates with your vehicle, and a copy of the answer for each registration for up to two days, with no account attached, so the same plate is not looked up twice. We note when your account made a lookup, never which plate, for two days, to stop the service being misused.
• Cloudflare - checks that a new account, a password sign-in or a password reset request came from a person rather than a script, which is what stops accounts being made or guessed at in bulk. Cloudflare sees your IP address and some details of your browser for that check. It runs invisibly and there is almost never anything for you to click. Cloudflare also stores and serves the street map under the On shift heat map, which is on unless you turn it off, so it carries those map requests. They carry nothing that says who you are, and they are not logged.
• Brevo - delivers the emails we send you: sign-up confirmation, password reset links, email-change approvals, contact-form messages and, if you turned them on, the deadline emails. Brevo sees your email address and the contents of those messages.
• Hostinger - provides the joltmile.com mailbox that support replies come from and go to.
• Apple and Google - take subscription payments made in the app, through the App Store and Google Play, and offer Sign in with Apple and Sign in with Google if you choose them. They handle card details directly; we never see or store your card number.
• RevenueCat - confirms with Apple and Google which app subscriptions are active, so your account is unlocked on every device. It receives your JoltMile account id, which is a random code, and the subscription details, not your name, email address or records. When you delete your account we delete you from RevenueCat as well. If a subscription is still running at that point, RevenueCat keeps its record until the subscription ends, because that is how we would hear about a refund or a renewal; email us once it has ended and we will remove it.
• Sentry - receives a report when the app crashes, so faults get fixed rather than going unnoticed. Reports are stripped before they are sent: no user identity, no cookies, and none of the figures or postcodes you have entered. Session replay, performance tracing and profiling are all switched off.
• Vercel Analytics and Speed Insights - count page views and measure how quickly pages load. They store nothing on your device, set no cookies, and do not follow you between sites; what they record is the page, the referrer, and coarse device and country information, with no identifier that ties visits together into a profile.

Where your data is held

Your database is hosted in London, United Kingdom (eu-west-2), so your records stay in the United Kingdom.

Some of the providers above operate internationally and may process limited data (such as an email address or a postcode) outside the UK. Where that happens it is covered by the UK International Data Transfer Agreement, UK Addendum to the EU Standard Contractual Clauses, or an adequacy decision.

How long we keep it

• While your account is open - your records are kept until you delete them or delete your account.
• Deleted and edited shifts - when you delete or change a shift, we keep a copy of how it was for a year, so it can be put back if it was a mistake. You can restore anything deleted in the last 30 days yourself from Recently deleted in the app, and we can restore older ones if you ask. These copies go straight away if you delete your account.
• After you delete your account - your records are removed immediately and disappear from routine backups within 30 days. Deleting your account does not cancel a subscription: cancel that in your App Store or Google Play account.
• Payment records - kept for six years after the relevant tax year, as UK tax law requires. Apple and Google keep the records of payments made through them, whether or not you delete your JoltMile account. Brevo also keeps a delivery log of emails already sent to you.
• Account security events - the IP address recorded against one is removed after 12 months, and the event itself is kept without it. Finished and cancelled email-change requests, including the old and new addresses, are deleted after 12 months. Long enough to look into somebody trying to take an account over, and no longer.
• Benchmark figures - rebuilt from your shifts every hour or day, so each one lasts until the next refresh, and deleted straight away if you delete your account.
• Contact messages - kept for up to 12 months so we can follow up on an issue.
• How the app is used - the app step records are deleted after 13 months, a year of comparisons with a month to spare, and straight away if you delete your account.
• Partner programme - which code your account came through is deleted with your account. Commission and payout records are kept for six years after the relevant tax year, because they are payment records. When you delete your account we take your account id off them, so nothing in them points back to you. Visit counts keep only the scrambled code described above. A partner's bank details are kept while the partnership runs and deleted once the last payout after it ends has been made; the payout records keep only the amount, the date and the bank reference.

Your rights

Under UK GDPR you have the right to:

• Access your data - sign in at joltmile.com and open Your data (joltmile.com/account/data). Its "Download all my data" button gives you every record held under your account, including your account email address, as a JSON file. In the app, Settings, Your data, Download your records takes you there. If you would rather we sent it to you, email us and we will.
• Correct anything inaccurate - every record in the app is editable.
• Erase your data - delete your account from Settings, which removes your records and your login.
• Restrict or object to how we process it.
• Portability - the backup file in the same place is a machine-readable copy of your driving records that you can take elsewhere, or restore into JoltMile again.
• Withdraw consent where we relied on it.

Email support@joltmile.com to exercise any of these. We will respond within one month.

Complaints

If you are unhappy with how we have handled your data, please tell us first so we can put it right. You also have the right to complain to the Information Commissioner's Office (ICO), the UK regulator, at ico.org.uk.

Security

Data is encrypted in transit. Every record is tied to your account and protected by database-level row security, so one user cannot read another's records even if the app had a bug. Receipt files are kept in private storage, in a folder only your account can open, and are only ever shown through a link that stops working after ten minutes. Passwords are stored only as a salted hash and are never visible to us.

Children

JoltMile is not intended for anyone under 18, and we do not knowingly collect data from children.

Changes to this policy

If we make a material change we will update the date at the top of this page and, where the change significantly affects you, tell you by email. The current subscription price is £7.99 per month, including VAT.