Information you provide
The appointment form may collect your name, phone number, optional email address, preferred location, vehicle description, requested service and message. This information is used to review and respond to the request, route it to the appropriate workshop and maintain a basic service-enquiry record.
Technical and usage information
Web servers normally record request time, requested URL, browser information and network address for security and operations. The established /collect/ integration may receive language, time, time zone and referring-page information. Local development traffic is excluded. The production implementation must be verified before this notice is finalized.
Cookies and local storage
A short-lived session cookie is used to protect form submissions and confirmation flow. The current build does not use advertising identifiers or a placeholder advertising account. If analytics, advertising or embedded services change, this notice and any required consent controls must change before those tools are enabled.
Retention and access
Appointment information should be retained only for operational, security and record-keeping needs, then deleted or anonymized according to a confirmed business schedule. Access should be restricted to people who need it to respond or maintain the service. No internet system can promise absolute security.
Sharing and external services
Information may be shared internally for handling a request and with service providers that operate hosting or communications where configured. The site should not sell appointment details. A future insurer or other third party must receive information only when the process requires it and the appropriate notice or permission exists.
Your choices and contact
You can avoid the online form and call a workshop instead. For an access, correction or deletion enquiry, contact the published site email with enough information to identify the relevant request. Legal rights depend on the applicable circumstances; this page does not claim a jurisdiction that has not been confirmed.
Children and changes
The appointment service is intended for people arranging vehicle service, not for children. Material changes to data collection should be reflected here with an accurate effective or update date.
Legal basis and purpose limits
The site should process appointment information only for clear operational purposes such as responding, scheduling, preventing abuse and maintaining necessary service records. The production operator must confirm the applicable legal basis and privacy contact before release; this build does not invent a registration, jurisdiction or compliance certification.
Data collected for one request should not automatically become an advertising list. A new marketing purpose would require an appropriate notice and choice before activation.
Security practices
The local implementation uses server-side validation, a form-session token, a hidden spam field, parameterised database statements and a one-way hash of the network address rather than storing the raw address in the appointment table. Production also requires access control, backups, patching, log review and secure transport.
Security measures reduce risk but cannot guarantee absolute protection. Suspected misuse or unauthorised access should be investigated and handled under the operator’s confirmed incident process.
International and service-provider processing
Hosting, email, analytics or communications providers may process information in locations determined by their services. Those providers and transfer arrangements must be inventoried before launch. No provider should be named here until its actual production role is confirmed.
Deletion and record integrity
Deletion requests must be balanced with legitimate operational, security and record-keeping needs. Where full deletion is not appropriate, access restriction or anonymisation may be considered. The production retention schedule should define separate periods for unconfirmed enquiries, completed service records, security logs and backups.
Effective date and production review
This policy is a development draft dated 18 September 2026. Before production publication, the operator must confirm contact ownership, hosting, analytics, communications, retention, third parties and applicable rights. A material configuration change requires another review.