This privacy page describes the information collected through the DriveTech AutoCare website and online booking form. It is intended as practical website information, not legal advice. The business should review it against its actual hosting, email, accounting, retention and customer-management practices before publication.
Information submitted through the booking form
The booking backend accepts customer identity and contact information such as first name, last name, email address and telephone number. It can also receive address/location, post code, city and country. Vehicle information can include make, model, registration and VIN. The requested service, free-text message, source field and an optional issue photograph may also be stored. The server code records technical information including IP address and user-agent data when a booking is created.
Customers should provide only information relevant to arranging and carrying out vehicle work. The optional photo field is useful for dashboard warnings or visible issues, but customers should avoid uploading identity documents, payment-card information or unrelated personal material through that field. Where security-related work requires proof of authority over a vehicle, the workshop should use an appropriate controlled verification process rather than asking customers to place sensitive documents into a general diagnostic image upload unless the business has explicitly designed that process.
- Contact details and booking identity
- Vehicle make, model, registration and optional VIN
- Service request, message and optional issue image
- Technical request data such as IP address and browser user agent
Why booking information is used
The main purpose of the information is to receive, identify and manage a workshop booking or enquiry. Vehicle information helps the workshop understand what car is involved and whether a requested procedure is likely to be compatible. Contact details allow follow-up about timing, scope, findings or other practical matters related to the request. The booking workflow may also send booking-related email notifications so the workshop can respond to the request.
The booking system may add new make/model combinations to the vehicle catalogue and can add service names to the invoice service catalogue when a booking introduces a new value. Those functions support the internal operation of the booking interface. The business should ensure that any further use of customer data—for example marketing, analytics, finance, warranty records or third-party integrations—has an appropriate basis and is described transparently in the final policy if it occurs in production.
- Responding to booking and service requests
- Identifying the correct vehicle and requested workshop service
- Sending booking-related communications
- Maintaining operational vehicle/service lists used by the website
Storage, security and retention considerations
The website stores booking records in its database workflow and can store accepted issue photographs. Server and mail credentials must remain protected from public access, source-code exposure and client-side delivery. Production permissions should restrict access to configuration, booking records and uploaded files as appropriate.
The website does not by itself establish a complete organisation-wide retention policy. The business should decide how long bookings, messages, uploaded images and email records need to be kept for customer service, accounting, dispute handling or legal obligations, and should remove information when there is no longer a justified need to retain it. Backups and external mailboxes should be included in that review. Staff access should be limited to people who need the information for legitimate business duties.
- Protect database and mail credentials from public access
- Use HTTPS in production
- Restrict access to booking records and uploaded files
- Define and document a retention schedule that matches real business practice
Cookies, third parties and customer rights
The website does not intentionally add advertising trackers or third-party analytics libraries. It uses local CSS, JavaScript and image assets plus first-party booking functions. The contact page includes an embedded Google map, which can connect the visitor’s browser to Google. If the business later installs analytics, advertising pixels, live chat, social widgets or additional third-party services, the privacy and cookie information should be updated before or at the same time. Some hosting infrastructure may also create essential technical logs independently of the page code.
UK data-protection rights and obligations depend on the context in which information is processed. Customers who want to ask what information the business holds, correct inaccurate details or raise a privacy question can contact DriveTech AutoCare using the published workshop email. The company should verify the requester appropriately before disclosing personal information. For formal compliance, the business should have the final wording reviewed by a qualified UK privacy professional who can consider all offline and third-party systems, not only this website package.
- No advertising trackers are intentionally added by this website
- Update the policy if analytics or third-party embeds are introduced
- Handle access/correction requests with appropriate identity checks
- Obtain professional legal review for final production compliance
Planning a visit to DriveTech AutoCare
Our workshop address is Unit 6 Fleetway Business Park, 14-16 Wadsworth Road, Greenford, Middlesex, UB6 7LD. Opening hours are Monday to Friday from 09:00 to 19:30 and Saturday from 11:00 to 18:00, with Sunday closed. If you are travelling for a specialist electronic, programming, security or EV/hybrid procedure, contact us first with the exact vehicle details so the practical scope can be confirmed.
The online booking form is the most structured way to send information. It asks for your name and contact details, location information, make and model, registration, optional VIN, required service and a message. It also accepts an optional issue photograph in supported image formats. After a successful submission, the customer receives a DriveTech reference so the workshop can review the request and follow up if anything needs clarification.
Frequently asked questions
Yes. The booking system stores vehicle and booking fields needed to manage the request.
They should never be. Server credentials and configuration must remain private and should not be exposed in page content or public repositories.
No advertising or analytics tracker is intentionally added to the front end.
Yes. The final production policy should be checked against the business’s complete real-world data handling, not only the website code.