Prepared on 20 October 2026.
Who this notice is for
This notice describes the Isle of Skye Tyres website and booking tools. It applies to people requesting tyre assistance, making an appointment, using a private booking link or contacting the team. Staff location handling is described below because it can appear in dispatch and customer arrival information.
Information used for a booking
The booking service can store your name, email address, telephone number, vehicle registration, tyre size, tyre quantity, service request, vehicle address and postcode, preferred date and time, and the notes you provide. If you choose to supply precise location coordinates, they can be stored with the booking to help locate the vehicle.
Operational records include your booking reference, assigned van, booking status, callout charge, payment status and record timestamps. Please keep notes relevant to the tyre job and avoid sending payment-card details or sensitive information through a booking note or WhatsApp message.
Why the information is used
- To respond to your enquiry, check tyre and job suitability, reserve available appointment capacity and arrange a visit.
- To show dispatch staff the schedule and give the assigned fitter the location and details needed for the job.
- To manage the quote, callout payment, job status and any follow-up about your booking.
- To protect booking and team tools against unauthorised access or abuse.
Handling a requested quote or booking is intended to take steps towards, or perform, the service contract. Security controls are intended to support the operator’s legitimate interests in running a secure service. Records may also need to be retained for applicable accounting or legal obligations. The operator must confirm and document the lawful basis for its live processing before launch.
Location and route information
When you type at least three characters in the address search, that text and the selected service area are sent through our server to Mapbox to find matching addresses on Skye. Selecting a suggestion fills the address and postcode and supplies a location pin for the booking. A Mapbox map preview loads for the selected address. You can enter the address manually instead, and should check any suggested pin before continuing.
You can provide the vehicle address and access notes manually. Where a location button is offered, your browser asks for permission before it supplies coordinates. A location pin is used to help plan a visit; providing one does not create an emergency-service dispatch.
Fitters can explicitly share a location update through the team tool. The current interface requests a single position when the button is pressed; it does not run continuous background tracking. A stored update has a timestamp so dispatch can see its age. A customer view may show information about an assigned van for that customer’s job.
Where configured, Mapbox can receive coordinates to calculate a driving route. Opening a Google Maps directions link sends the selected stop addresses or postcodes to Google. The map service then handles that request under its own privacy terms.
Vehicle registration lookup
If you request the vehicle lookup, the registration is sent from the server to the DVLA service. The lookup can return vehicle details such as make, year, colour, fuel type or MOT information. Its response is not stored as a separate lookup record by this application. A registration lookup does not establish the tyre size currently fitted to the car.
Payments
When online payment is enabled, Stripe Checkout handles the callout payment. Card entry happens in Stripe’s checkout rather than in this booking form. The application stores payment references and status, not full payment-card details. The tyre price and additional work are separate from the callout charge unless a specific agreed quote says otherwise.
A payment is marked as successful only after a verified server notification from the payment provider. Returning to a confirmation page alone is not treated as proof of payment.
Storage and who receives information
The application is designed to store booking and dispatch records in Cloudflare D1. Authorised dispatch staff and the assigned fitter can access information needed for their work. The operator must control staff access and confirm its hosting, provider contracts and international-transfer arrangements before live use.
The providers involved can include Cloudflare for hosting and data storage, DVLA for requested vehicle lookups, Stripe for enabled payments, and Mapbox for enabled routing. If you choose WhatsApp or Google Maps, your message or directions request is also handled by that external service. The booking system does not send an email or SMS notification unless a separate messaging service is actually configured.
Cookies and browser storage
Dispatch sign-in uses a necessary session cookie named skye_dispatch_session; the separate van-scoped fitter sign-in uses skye_fitter_session. Both are restricted from JavaScript access and expire after eight hours. On HTTPS they are marked Secure, and their SameSite setting restricts cross-site use. Fitter access codes are stored as hashes on the server, and replacing a van code revokes its earlier sessions.
A private booking link contains a secure token. The tracking interface can keep that token in the current tab’s session storage so the page can continue to show your booking. Once the token is safely stored, it is removed from the visible URL. If browser storage is blocked, the fragment can remain so refreshing the page still works. Keep the original private link safe and do not share it publicly; someone with that link may be able to access the associated booking view.
The application does not add an advertising or analytics tracker by default. Any future optional analytics or marketing storage needs its own disclosure and, where required, a choice before activation. External checkout and map providers may use their own storage within their services.
Retention
Booking records currently have no automatic deletion period configured in the application. The operator must set and publish a retention schedule for customer, payment, dispatch and location records before live use, taking account of the job, accounting obligations and privacy risk. Temporary abuse-prevention records use short expiry windows rather than permanent customer profiles.
Your choices and rights
Contact 0141 266 0690 with a privacy question or a request about your information. Depending on the circumstances, you may ask for access, correction, erasure, restriction or portability of your data, or object to certain processing. Where processing relies on consent, you may withdraw it without affecting earlier lawful processing. Identity may need to be checked before information is released.
You can also raise a concern with the Information Commissioner’s Office. The operator must add its confirmed legal contact details to this notice before launch.
Changes and related information
This notice should be updated whenever the operator, providers, booking workflow or retention arrangements change. For service and appointment information, read the booking terms or contact the team.