Privacy policy

Last updated: 25 October 2026

1. Who we are

Delaywise is an iPhone app made by Mirentha Ltd (“Mirentha”, “we”, “us”), a company registered in England and Wales, company number 17207914, registered office 71–75 Shelton Street, Covent Garden, London, WC2H 9JQ. For anything about this policy or your data, write to [email protected].

This policy covers the Delaywise app. Visits to mirentha.com are covered by our website privacy policy.

2. The short version

3. What the app handles

Your journeys and tickets

The journeys you save (stations, train times, travel days and the dates of one-off trips) and your tickets (the kind of ticket, the ticket type as printed, its stations, the price you paid, its dates, where you bought it, and if you add them, the ticket number or booking reference, railcard and smartcard number). Delaywise uses them to check your trains, work out amounts and fill in the claim pack. They’re stored in the app’s own storage on your iPhone, only you can see them, and they stay until you delete them.

Proof files

A photo or PDF of a ticket or receipt that you add from Photos or Files. Delaywise copies it into its own storage on your iPhone and shares it only when you tap Share proof. It never reads any text from it. The system’s photo picker gives the app only the picture you choose, so Delaywise has no access to your photo library.

Travel days and claims

Your answer for each travel day, the running records fetched for it, how late the train was, the company to claim from, and for each claim the estimated amount, how it was worked out, the claim-by date, its status, any amount you mark as paid and any note. They’re stored on your iPhone and used for Today, Claims, reminders and the export.

Settings kept on your iPhone

Whether the free journey has been used and which one it is, whether a first look has been shown, whether reminders and the morning check are on, the date the rules and station list were last refreshed, whether you have Delaywise Plus and its last known renewal date (so a renewal made while you’re offline doesn’t lock you out), and how many claims you’ve marked paid with the app version Apple’s rating prompt last asked in, so it asks at most once per version.

What is sent to our server

To check a train, Delaywise sends our server at api.mirentha.com two station codes, a date and a scheduled departure time. For the first look it sends a date range and the days of the week you travel; for the list of departures, a window of times. It also asks the server for the train companies’ Delay Repay rules and the station list. Each request carries a label naming the app (“X-App: delaywise”), never you. Like any app’s requests, they also carry the app’s and iOS’s version and your language setting, which the server doesn’t store. No account, device identifier, journey name, ticket, price or claim is ever sent.

The server runs on Cloudflare Workers. It reads National Rail Enquiries’ historical running data for the train asked about, and stores the running records and timetables it fetches, keyed by station pair, date and time, which say nothing about who asked. Our server’s own logging is turned off: it records no request and stores no IP address. To limit each caller to 60 requests a minute, Cloudflare’s rate limiter counts requests by IP address in its memory, only for the minute it counts over. As for any website, Cloudflare handles your IP address to deliver each request, and keeps its own short-lived traffic and security records for its network, under Cloudflare’s privacy policy.

Mirentha doesn’t receive personal data from the app. The handling of IP addresses described above, to deliver requests and limit their rate, rests on our legitimate interest in running the service securely (Article 6(1)(f) UK GDPR). Cloudflare runs a worldwide network, so a request may be handled outside the UK, under the safeguards in Cloudflare’s Data Processing Addendum.

The claims export

When you tap Export claims, Delaywise writes your claims to a temporary file, delaywise-claims.csv, and opens the share sheet. Where you send it is up to you.

Notifications

Day-21 reminders and the morning check’s questions are scheduled by the app on your iPhone. Delaywise asks for permission only when you turn reminders or the morning check on, and nothing about them is sent to us. Everything a notification says also shows in the app.

4. Apple services and third parties

• The App Store handles Delaywise Plus. Apple takes the payment and shares no personal data with us. See Apple’s privacy policy.
• National Rail Enquiries. Our server asks its Historical Service Performance service, through the Rail Data Marketplace, for running records by station codes, dates and times only. Nothing about you is sent.
• Cloudflare hosts our server, as described in section 3.
• Train companies. The claim pack’s button for your train company’s claim form opens the company’s own website in your browser. What you type there goes to that company, under its own privacy policy, not to us.
• Crash reports. If you’ve chosen to share analytics with app developers (Settings › Privacy & Security › Analytics & Improvements), Apple may share crash reports and usage statistics with us. Delaywise has no analytics, advertising or crash-reporting code of its own.
• Backups. Delaywise has no iCloud sync. Your iPhone’s own backups, to iCloud or a computer, include the app’s data, as they do for any app, under Apple’s terms.

Cloudflare is the only company that handles anything for us, and only the IP address each request comes from, to deliver it and limit its rate. It does so as our processor under its Data Processing Addendum, which gives that data the same or equal protection as this policy. We share no data with anyone else: National Rail Enquiries receives only station codes, dates and times from our server, never anything about you.

5. Purchases

Delaywise Plus is bought through the App Store. Apple handles payment, renewals and refunds, and we never see your payment details. We receive only Apple’s sales reports, which don’t identify you. The app keeps whether you have Plus, and its renewal date, on your iPhone.

6. Keeping and deleting data, and permissions

Everything Delaywise stores stays on your iPhone until you delete it. You can delete a journey or a ticket in the app. Settings › Delete all data removes every journey, ticket, proof file, travel day and claim, the last export and every pending or delivered notification, and turns reminders and the morning check off. It keeps a few settings that aren’t your records: that the free journey has been used and which one it was (so deleting doesn’t give another free journey), that a first look has been shown, whether you have Plus and its renewal date, the date the rules were last refreshed, and the version the rating prompt last asked in. Deleting the app removes everything.

Our server keeps the running records it fetches to answer later checks. They contain no personal data.

You can change notifications in Settings › Notifications › Delaywise, and Background App Refresh (which the morning check uses) in Settings › General › Background App Refresh. The photo picker and the file picker need no permission. Delaywise doesn’t use your location, contacts, camera or microphone, and doesn’t track you.

7. Your rights

Under UK GDPR you have the right to access, correct and erase your personal data, to restrict or object to its processing, and to data portability. Your Delaywise records are on your iPhone and we don’t receive them, so you can see, export (Export claims), change and delete them yourself in the app. For anything else, write to [email protected]. If you’re unhappy with how we’ve handled your data, please tell us first; you can also complain to the Information Commissioner’s Office at ico.org.uk/make-a-complaint.

8. Children

Delaywise isn’t aimed at children. It receives no personal data from anyone, and we don’t knowingly collect personal data from children under 13.

9. Changes to this policy

If Delaywise changes what it stores or sends, we’ll update this policy, and the date at the top, before the version that makes the change is released.

10. Contact

Mirentha Ltd, 71–75 Shelton Street, Covent Garden, London, WC2H 9JQ. Email [email protected].