Privacy policy

1. The app

What it asks for, and why

Calendar

Today's jobs are read from the calendars you choose, to work out when you need to leave. Jobs you add, change or delete in the app are saved back to the calendar.

Contacts

Your customer list, looking a customer up when you book a job, and finding the number so you can call or message in one tap. A customer you add is saved to your contacts, and you can save a job's address onto a customer you already have. Nothing is ever removed from your contacts.

Location, while using the app

Where a journey starts from, so the app can work out how long it will take to reach the next job. Only while the app is open, and the app keeps no copy.

Notifications

Telling you when to leave. Nothing else is ever sent to you.

All four are optional, and the app tells you what it will do with each one before iOS asks. Refusing any of them changes what the app can do rather than whether it runs.

What it keeps on your device

Two small records, and they are the only things the app writes to the phone:

• Your settings. How you travel, your buffer, how early the reminder fires, how often it recalculates, which calendars it reads, which calendar and contact group it writes to, and the address your working day starts from, including any day you have told it starts somewhere else.
• Counters for the support prompt, so it can stop asking. How many days you have used the app, when it last asked, and how many times.

No jobs, no customers, no phone numbers and no location are stored by the app. It reads them when it needs them and forgets them. Deleting the app removes both records with it.

What leaves the device

Three requests, all of them made by iOS to Apple, and all covered by Apple’s privacy policy rather than this one:

• Finding an address. The address autocomplete asks Apple’s map search as you type.
• Working out a route. Travel time means asking Apple Maps about a journey. That request carries where you are and where you are going, exactly as the Maps app does it.
• Supporting the app. Asking Apple whether the account on this phone holds a subscription, and taking a payment. Apple is the merchant. We never see a card, a name or an address, and we are told nothing about who supported the app.

There is no fourth. The app has no server of its own, no account, no analytics, no telemetry, no crash reporting and no third-party code: Package.swift has no dependencies, which is a fact you can check rather than a promise you have to take.

Where your calendar and contacts live is up to you

Everything above is about the app. None of it is about your phone. Your calendar and contacts are your own stores, and for most people they sync to iCloud, which puts the same data in an Apple account, on your other devices and in your backups. That is true whether this app is installed or not. It neither causes it nor can prevent it, so it is not ours to promise away. What is true, and is stronger for being checkable, is that the app adds no new place for your day to live.

2. This website

No cookies are set. No analytics, no tracking pixels, no advertising tags and no third-party fonts. Nothing is stored in your browser and there is nothing to consent to, which is why you have not been asked.

Serving the pages

The site is delivered through Cloudflare, which processes your IP address and the details of the request in order to serve the page and to keep the site up. Our server keeps the ordinary web-server log of requests it has answered.

The three forms

• Keep me posted. Your email address, held on our own platform on our own servers, used to send occasional posts about the app. Nothing else, and never passed to anybody.
• Test what is next. Your name, email address, trade, town and whatever you write in the message, held on the same platform, used to decide who joins a test and to contact you about it.
• Support. Your email address, the subject and your message. These go to our support system, which stores the ticket and copies the message into an issue in the development tracker we run on GitHub, so that the problem can be worked on and answered. Your email address is kept with the ticket so we can reply to you.

Every form runs a spam check by Cloudflare Turnstile before it is accepted, which sends a one-time token and your IP address to Cloudflare.

Referral links

A link or QR code of the form /r/<code> counts the scan before sending you on. Your browser’s user agent, the page you came from and the country Cloudflare works out from your connection are passed to our platform so that a real scan can be told apart from a bot. No cookie is set, you are not identified, and nothing about you is kept by the site itself.

Videos

The player only loads when you press play, and YouTube videos load from the no-cookie host. The still image on the card is fetched from the video host when the page opens, which shows them your IP address. If that matters to you, the videos page is the only page that does it.