Only the information needed to handle the job.

Anonymous site statistics — your choice

To understand where the enquiry process becomes difficult, these aggregates also include coarse scroll-depth thresholds (25%, 50%, 75%, 90% and the bottom), visibility of fixed page elements, the names of fields edited, and whether those fields passed the browser’s standard validation. Validation errors are grouped as missing required information or an invalid format. Field values, keystrokes, selection contents and recordings are not collected. Visibility means at least half of the marked element is within the area outside the header and cookie panel. Scrolling or visibility does not prove reading or intention; these counts indicate what to investigate, not why a particular person left.

We use our own aggregate counters solely to improve this website and enquiry form. These count HTML responses, browser page starts, enquiry-button clicks, form visibility, the start of filling, errors identified only by a fixed field name, submission attempts, server-confirmed new enquiries, submission errors and separate phone or WhatsApp link clicks. These event totals do not identify unique people. The separate aggregate route diagrams described below temporarily connect steps within a technical visit.

Our event-counter tables contain only daily totals, a fixed page group, an event label and, for validation errors, a fixed field name. They contain no entered values, contact details, vehicle details, full URLs or query parameters, IP addresses, device fingerprints or persistent visitor IDs. Nothing from these counters is sent to Google, Microsoft or other advertising platforms. Our hosting provider necessarily processes network requests to deliver the website; network addresses are not copied into these analytics tables.

No analytics cookies, localStorage or sessionStorage are used by these counters. An in-memory, one-hour operation token and separate unlinkable technical receipt hashes prevent repeat counts. Receipt hashes contain no event history or visitor identity, expire after one hour and are removed during subsequent statistics requests. Aggregate daily counters are kept for up to 90 days, with expiry cleanup during subsequent statistics requests. Known automation and explicitly marked tests are counted separately.

You can turn these counts off below, in the cookie panel or in the footer, free of charge. This is independent of accepting or rejecting optional Google or Microsoft cookies. We also respect Do Not Track and Global Privacy Control signals. A necessary preference cookie, solved_statistics_off=1, remembers only your objection for up to 180 days, with no unique ID. Turning counts back on removes that cookie. If cookies are blocked, your choice works in the current page but may not be remembered after navigation. Previously aggregated counts cannot be linked back to you or individually removed.

To build aggregate route diagrams, we temporarily connect fixed public page identifiers and enquiry stages of a visit using a random, short-lived first-party navigation token. It is passed only in links within this site as _sf and removed from the visible page address before Google or Microsoft tags load. No analytics cookie, localStorage, sessionStorage, device fingerprint, field value or IP address is used for this route diagram, and advertising-ID values are never retained or matched. We do not recognise people across separate visits or devices. A new session starts after 30 minutes of inactivity, at a new UK calendar day, or when continuation is unavailable. Temporary session state is aggregated and deleted on the next website, collection or report request after expiry, with a hard ticket lifetime of at most 24 hours; cleanup does not run while the service receives no requests. Only route totals without a visitor identifier or precise event times remain for up to 90 days. The owner report shows aggregated branches, not individual visitor records. The last recorded step does not prove that someone closed the website. Link-copying, direct navigation, disabled JavaScript or unavailable collection may split or omit visits. These diagrams are for improving the site; they are not linked to GCLID, individual ad clicks, contact details or advertising partners. For new visits, we keep only a broad entry-source category, fixed on the first recorded page and retained during that visit. The rules run in this order: Google Ads URL marker (gclid, gbraid, wbraid or gad_source present); Google Maps/business profile only when utm_source=gbp; Facebook when utm_source=facebook or the referrer is facebook.com/m.facebook.com; Google organic search for a Google referrer without the earlier signals; other referrers; and direct when neither a referrer nor external parameters were supplied. Unrecognised parameters without a referrer remain unknown. A missing referrer does not prove a typed or bookmarked entry, and a URL marker does not prove a fresh paid click. Old records are not reclassified. Only this fixed category is sent to our collector: not click-ID values, UTM values, referrer addresses, IPs or form details. Call and WhatsApp clicks are counted separately and deduplicated by an in-memory operation receipt; genuine repeated clicks can add more than one click to a visit. New server-confirmed saves linked to a route are counted once per saved enquiry, including retry protection. The diagram is limited to 40 steps, but aggregate click/save totals continue; legacy rows contain only the events actually observed at the time. Signed-in administrators are excluded using the site's existing verified account identity, which is not copied to these statistics. Without sign-in we do not try to recognise an administrator; marked control checks remain separate. These categories and counters are used only to improve the site, not to match individual ad clicks, build audiences or share conversions with advertising platforms. Your statistics objection and browser privacy signals apply to these categories and steps too.

For new direct-entry technical visits, we also use the incoming User-Agent header to derive only a broad device category and browser family. We never retain the full User-Agent, version, hardware model or an identifying hash of it. While a page is visible, a best-effort signal no more often than every 30 seconds estimates foreground visibility; background time is not added. The private report shows minute-rounded start times, broad visibility-duration bands and recognised automation categories. Matching rows are combined as counts, without a visitor identifier. These extra technical aggregates expire after 24 hours and are removed during subsequent requests or report access; the existing route totals retain their separate 90-day period. A recent signal is not proof of an active person, and a short homepage-only visit is not automatically treated as a bot. The same statistics opt-out and browser privacy signals apply.

Optional Google cookies and Clarity session recordings continue to require their own separate consent. Google tags also send limited measurements without cookies under denied Consent Mode defaults, as explained below. These anonymous counts do not attribute every advert click to an enquiry. See the ICO guidance on statistical purposes and a simple means to object.

Optional website analytics — Google Analytics

Only after you choose Website analytics in Cookie settings, Google Analytics 4 uses analytics cookies to measure visits, page usage, enquiry starts, validation or submission errors, submission attempts, successful enquiries and clicks on Call or WhatsApp links. Google Analytics also loads with analytics storage denied before a choice or after rejection, and may send limited measurements without analytics cookies for modelling. We do not turn a refusal into consent. Events use fixed labels, not what you enter into the form. A contact click does not confirm a call or conversation. A successful submission sends a generate_lead event without form details, photos or the enquiry reference. Google may receive page addresses, device information, IP address and cookie identifiers. We do not send enquiry details or photos as analytics events. This choice is separate from advertising measurement and Microsoft Clarity. Earlier consent to advertising or Clarity does not grant GA4 consent.

We remember this choice for up to 180 days. You can withdraw it through Cookie settings in the footer. Withdrawal sets analytics storage to denied and clears the Google Analytics cookies this site can access. See how Google uses information from partner sites.

Optional analytics — Microsoft Clarity

Only after you choose Session insights in Cookie settings, Microsoft Clarity records browsing interactions, such as clicks and scrolling, to provide session recordings and heatmaps. Microsoft processes page addresses, device and browser information, IP address and cookie identifiers. Analytics consent is separate from advertising consent; we do not load Clarity before consent or after rejection.

The enquiry and review pages are explicitly masked, including entered details, messages and any displayed confirmation. We do not send names, phone numbers, email addresses, vehicle details, photos or enquiry references through Clarity custom identifiers or events. Do not put personal information in page links. Clarity may process data outside the UK under Microsoft’s applicable transfer arrangements.

We remember your analytics choice for up to 180 days. Change or withdraw it through Cookie settings in the footer. Withdrawal stops recording by reloading the page and clears the Clarity cookies this site can access (_clck and _clsk). Microsoft’s session recordings are generally retained for 30 days; heatmap and aggregate data for up to 9 months; labelled or favourited recordings may also be kept for 9 months. See Microsoft’s Privacy Statement and Clarity’s masking information.

Optional advertising cookies

The shared Google tag loads with ad_storage, analytics_storage, ad_user_data and ad_personalization denied by default. With your advertising-measurement consent, Google Ads may use advertising cookies to measure whether an advert leads to a successfully submitted enquiry or a click on our Call or WhatsApp links. Contact clicks are measured separately and do not confirm that a call or conversation took place. Google receives advertising and device information, such as cookie identifiers, the page address and IP address, and a random enquiry reference used to prevent duplicate counting. We do not send the form's name, telephone number, email, vehicle details, message or photos to Google Ads. Personalised advertising is disabled in our tag settings.

Before you accept advertising measurement, or if you reject it, Google tags may send limited conversion and consent measurements without advertising cookies. Advertising storage and ad user data remain denied, and ad click data is redacted. This may support modelling; it does not identify every ad click or guarantee a reported conversion. We do not include the enquiry reference in denied-consent conversion measurements. The form remains available. We remember your cookie choice on this browser for up to 180 days; you can change it at any time through Cookie settings in the footer. With consent, this browser also remembers conversion references for the current session to prevent duplicates. Google advertising cookies may remain for their configured lifetime; withdrawing consent clears the advertising cookies this site can access. See how Google uses information from sites that use its services.

Who controls your information

SOLVED Auto Electrical & Diagnostics is responsible for the personal information described in this notice. Contact us at solvedautoelectrical@gmail.com for privacy questions or requests.

What we collect

Name, telephone number, postcode, vehicle registration, fault description and vehicle starting condition. Email, how you found us, preferred appointment details and up to three photographs are optional. We also keep relevant booking messages, diagnostic results and invoices.

Why we use it

To answer enquiries, check coverage, arrange and perform the requested service, provide quotes and records, take payment, handle complaints and meet tax or legal obligations.

The lawful bases we use are taking steps at your request before a contract, performing a contract, complying with legal obligations and limited legitimate interests such as keeping service records and preventing misuse.

Saved enquiry measurement diagnostics

For up to 90 days we keep a technical record against the existing enquiry reference: whether advertising parameters were available (not their values), the separate Google consent choices, whether the browser called an event, a tag loading error, a reported content-security block, or whether the Google tag callback ran. This is not a visitor profile or session recording. It contains no contact details, form values, full page addresses or IP addresses. It is restricted to the site owner and used to investigate measurement failures; it is not sent to advertising platforms. A local callback is not proof that Google received or attributed a conversion. Test enquiries are kept separate. Earlier enquiries have an unknown diagnostic state. This operational record of saved enquiries is separate from optional cookies and the aggregate page-use counters.

Who may receive it

Our website hosting provider (Cloudflare infrastructure via Sites) stores pending enquiries for transfer to our workshop CRM. Enquiry notifications are also delivered to SOLVED through Telegram and by email using Resend. With advertising consent, we keep the ad click ID (gclid), campaign source, medium, campaign name and landing page for the current browser session (up to 24 hours), and attach them to your private enquiry for attribution. These values are not added as visible form fields. We clear stored campaign attribution when advertising consent is withdrawn. Telegram therefore processes the information included in the message under its own service and privacy terms. Review submissions may be sent through WhatsApp for verification and moderation; they are never published automatically, and only the name option and review details approved by the customer will be displayed. Other providers may be used only where needed for payments, accounting, cloud storage or professional advice. Some service providers process information outside the UK under their applicable international transfer arrangements. Contact us for information about the providers used for your enquiry.

How long we keep it

Enquiries that do not lead to work are kept for up to 12 months, then deleted. This applies to our enquiry records and copies in email and messaging systems. Service, invoice and accounting records may need to be kept for up to six years or longer where law, a dispute or a warranty requires it. Website photo links expire after 30 days. Expired uploads are removed during subsequent enquiry processing or when an expired link is opened. Copies deliberately saved with a job record or messages follow the applicable service-record retention period. Diagnostic photographs and working notes will be reviewed and deleted when no longer needed.

Your rights

Depending on the circumstances, you may ask for access, correction, deletion, restriction, objection or transfer of your information. You may also complain to the Information Commissioner’s Office.

Contact and complaints

For privacy enquiries, email solvedautoelectrical@gmail.com. You can find independent guidance at the Information Commissioner’s Office.