What we record,and what we don’t.

When you browse

If your browser allows it (see Do Not Track below), the site records:

• A random visitor id, kept in a cookie. It is made up when you first arrive and isn’t based on anything about you or your device.
• The pages you view, how far down a page you scroll, which of the site’s buttons and links you tap, and when you play a film.
• How you arrived: the campaign tags on the link you followed (for example “instagram”, “bio”), the short link you used, and the name of the website that sent you, if any.
• Whether you’re on a phone, a tablet or a computer, and whether you’re in Instagram’s in-app browser. We work these out from your browser and keep only the answer.

These go to the studio’s own system.

What we don’t record

• Your IP address. The site uses it, scrambled and in memory only, to stop itself being flooded with requests. It isn’t saved with your visit or passed on.
• What you type into the enquiry form. Analytics only notes that the form was started or sent.
• Third-party trackers or advertising pixels. There are none on this site.

The companies that host the site and its films may keep their own server logs.

Do Not Track and Global Privacy Control

If your browser sends Do Not Track or Global Privacy Control, the site records nothing about your visit and sets none of the cookies below. Everything else on the site works the same.

Cookies

All four are set by this site only, can’t be read by scripts on the page, and are never shared with other sites.

mbs_vid

The random visitor id. Kept: 180 days.

mbs_sid

Groups one visit together. Kept: 30 minutes after your last activity.

mbs_ft

How you arrived the first time (campaign tags, short link, referring site, first page). Kept: 180 days.

mbs_lt

How you arrived this time, in the same form. Kept: 180 days.

When you send an enquiry

The details you give us (your name, how to reach you and your message) go to the studio’s own system so we can reply. If the cookies above are set, the enquiry also carries your visitor id and how you first and most recently arrived, so we know which post brought you. If the page’s address had campaign tags, those come with it too.

Google Calendar, for businesses on our console

A business using our console can connect its Google account so its bookings (test drives, rental pickups and returns, appointments) appear on its Google Calendar, and so its busy times aren’t offered to customers. When it does, we:

• create one calendar in that account for the bookings, and add, change and remove events only on that calendar;
• list the account’s calendars, so the business chooses which ones count as busy;
• ask Google when those calendars are busy. We never read what the events on them are;
• read the account’s email address, to show which account is connected.

The access Google gives us is stored encrypted and used only for this. It is never sold, shared, used for advertising, or used to train AI models. The business can disconnect it from its settings at any time, or remove our access in its Google account, and we stop at once. Our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy (opens in a new tab), including the Limited Use requirements.

Asking us to delete your data

You can ask us to delete an enquiry you sent, along with the visits recorded under the same visitor id. Send it through the enquiry form.

If you haven’t sent an enquiry, your visits aren’t tied to your name, so we can’t pick them out. Clearing this site’s cookies in your browser starts you over with a new visitor id.