Privacy.

Last updated 18 September 2026

01

Who we are.

‘We’ and ‘us’ mean the Carrier.

We are the controller for the personal data described here. Write to hello@thecarrier.ai.

02

What we measure.

We count visits and see which parts of a page are read. How we do it depends on your answer to the cookie card, and the two ways are not the same.

Before you answer, and afterwards if you decline, the counting happens on our own server. Your browser tells us that something happened — a page opened, a button was clicked — and nothing is read from or written to your device. One visit is told from another by a number worked out from your network address and your browser, which changes at midnight, so it cannot follow you from one day to the next. We rely on our legitimate interest in knowing how the site is used.

If you allow cookies, PostHog runs in your browser instead, hosted in the EU. It stores an identifier on your device, so it can recognise the same browser across our pages and on later visits, and it records the session. Requests go to this site’s own address and are passed on from there. We rely on your consent, and you can withdraw it at any time under Cookies in the footer.

Session replay is kept for thirty days. It shows how the page was used. Anything you type, and the figures worked out from what you type, are hidden from the recording; the rest is the page as anyone would see it.

If you use the calculator, the parcel volume, rate and order value you put in are sent to PostHog along with the result, so we know which figures people try.

03

Two versions of a page.

We sometimes run two versions of a page to find out which one reads better. Which one you see is worked out afresh every time you ask for a page, from your network address and your browser. Nothing is stored on your device and the working is not kept.

Unlike the key that counts visits, this one does not change from day to day, so you keep seeing the same version. The version you were shown is recorded against the measurements above, which is the whole point of showing two.

We rely on our legitimate interest in knowing which version works.

04

Advertising.

We advertise on Google. Google’s tag loads on every visit with every permission denied, so it stores nothing on your device and cannot recognise you; what it sends is a note that a visit happened, which is what lets Google estimate how many of its ads led to a call being booked. If you choose Allow, those permissions are granted and Google sets cookies to tell whether an ad brought you here, under its own privacy policy.

Allowing also starts the measurement described in ‘What we measure’ above. Two other things run whether you allow or not, and are covered below: the service that tells us which businesses visit, and the booking calendar on the Talk page.

Your choice is kept in your browser for twelve months. You can change it at any time under Cookies in the footer.

05

Knowing which companies visit.

We run RB2B on every page. It tells us the business a visit came from, and it runs whether or not you allow cookies on the card.

In the United States it can sometimes name the person as well. In the United Kingdom and the European Union it cannot: its database only covers the United States. For almost everyone reading this, what we learn is a company, not a name.

It sets its own cookies on your device — ‘_reb2buid’ and ‘_reb2bsessionID’ — and it does not work alone: it brings in other companies to do the matching, so more than one business receives something about your visit. Each handles it under its own privacy policy.

We use it to know which businesses are looking at us, so we can follow up. We rely on our legitimate interest in knowing who our visitors work for. If you would rather we did not, write to hello@thecarrier.ai and we will stop it for you.

06

Booking a call.

The calendar on our Talk page is run by Calendly and is shown inside our page rather than opened somewhere else. It is still Calendly’s: it loads from them, sets its own cookies as soon as it appears, and receives the name, email address and times you enter, under its own privacy policy. Its own cookie controls and privacy link sit at the foot of the calendar. We say so on the page above it.

We receive the booking and use it to hold the call and follow it up.

If you write to us instead, we keep the correspondence for as long as we are talking, and for six years after if you become a customer.

07

Hosting.

This site runs on Microsoft Azure in the UK South region. Request logs record the address a request came from, the page asked for and the time, and are kept for thirty days to keep the site running.

08

Your rights.

You can ask for a copy of what the Carrier holds about you, have it corrected or erased, and object to its use. Write to hello@thecarrier.ai. We answer within a month.

Whether we can find your visits depends on what you allowed. If you allowed cookies, PostHog’s identifier is on your device and we can usually find them; tell us and we will. If you declined, our own counting holds nothing that traces back to you — but the service in clause 05 runs either way and keeps its own record, so ask us and we will look there too.

If you are not satisfied with our answer, you can complain to the Information Commissioner’s Office at ico.org.uk.

09

We post changes here.

When this policy changes we publish the new version on this page and change the date above.