Legal

Cookie Policy

What DriveCore Service stores in your browser, why there is no cookie banner for optional cookies, and how you can clear the visit planner. Last updated 3 November 2026.

Short version

This site sets no cookies of its own. It does not use analytics, advertising, or social media cookies. The only similar technology we use is local storage for an optional visit planner. That is why you do not see a cookie banner: there is no optional cookie to accept or refuse. You can clear the planner in your browser settings or with its reset button.

1. Introduction

This cookie policy explains how the DriveCore Service website uses cookies and similar technologies. It should be read with the Privacy Policy, which describes personal information more broadly, and with the Terms and Conditions, which describe what the site is for. The policy matches the site as it is built: static pages about auto repair and maintenance, a small script for navigation and filters, a contact form that does not set a cookie, and a planner that writes only to local storage when you tick a box.

The workshop topics on the site, from brakes to electrical systems, do not change the storage story. Reading the brake page does not drop a “brake interest” cookie. The same is true of the engine, suspension, and diagnostics pages. If you expected a banner because other automotive sites use advertising tags, this one does not, and the banner would be a pretence.

2. Who we are

The site is published as DriveCore Service, 1 Limekiln Ln, Whitehall, Dublin 12, D12 DY80, Ireland. The telephone is +353 85 234 3631 and the email is [email protected]. Questions about cookies can be sent through the contact form when delivery is connected, or through those details, as the final section explains. The operator is the same operator described in the privacy policy. A message that the form refuses to send has not been received through the form.

3. What cookies are

Cookies are small text files a site can store on your device through the browser. They are sent back with later requests to that site, or sometimes to another site, depending on who set them and how they were marked. People also use the word “cookie” loosely for other storage. This policy keeps the words apart.

  • Cookies are the files or values the browser stores and may attach to requests.
  • Local storage and session storage let a site store data in the browser. Unlike cookies, this data is not automatically attached to every request for a page.
  • Pixels and scripts from other domains can set their own cookies if they are loaded. This site does not load them.

Because the words are easy to mix up, this policy uses “cookie” for cookie files and “local storage” for the planner. Both are browser storage. Only the planner is used by our own pages, and only after you interact with it. The search box on the services page and the search box on the notes page do not write a cookie to remember your query.

4. Types of cookies in general

People often sort cookies by duration and by who sets them. Session cookies disappear when you close the browser. Persistent cookies remain until they expire or you delete them. First-party cookies are set by the site you are visiting. Third-party cookies are set by another domain, often an advertiser or an analytics firm. Cookies are also sorted by purpose: strictly necessary, functional, analytics, and advertising.

Those categories are useful even when a site uses none of them. They give you a checklist. The next section applies the checklist to DriveCore Service instead of copying a banner from a shop that actually runs ads. A category with nothing in it is still worth naming, so you can see the absence rather than wonder whether we forgot a row.

5. What this site uses

CategoryUsed by us?Notes
Strictly necessary cookiesNone set by usA host might set a technical cookie (section 6)
Functional cookiesNoPreferences are not stored in cookies
Local storageYes, if you use the plannerKey begins with drivecore-checklist-
Analytics cookiesNoNo measurement tools (section 8)
Advertising cookiesNoNo ads or retargeting (section 9)
Social cookiesNoNo share buttons or embeds (section 10)

There is no login cookie, because there is no login. There is no basket cookie, because there is no basket and no price. The contact form does not drop a tracking cookie when you type. If it later posts to a delivery service, that request is a message, not a cookie change, unless the provider sets a cookie, in which case this policy will be updated before that provider is connected.

6. Essential cookies

Our pages do not need a cookie to remember you, because they do not keep a session. You can move from the gallery to the brake page without a token. The hosting provider that serves the files may still set a strictly necessary cookie for security, load balancing, or abuse prevention. If it does, that cookie is part of delivering the site safely, is not used by us to advertise, and does not require a consent banner under the rules that exempt strictly necessary cookies. We do not name a host in this policy because the provider is not identified on the public pages. We also do not invent a cookie name we have not observed. If we later confirm a specific host cookie, we will list its name, purpose, and duration here.

The mobile menu, the lightbox, and the filters work without storing a preference cookie. When you close the menu, the page does not write “menu closed” into a cookie. The state lives in the page until you reload. That is why a functional-cookie row in the table says no.

7. The visit planner

The service approach page includes a checklist. When you tick a box, the script saves the identifiers of the ticked boxes in local storage. The key starts with drivecore-checklist- followed by the planner name, which on the current page is visit-planner. The value is a list of those identifiers, not your name, not your vehicle, and not the text of an inquiry. The script reads the list when you return so the ticks reappear. It does not send the list to a server.

You can erase it in three ways. Press “Reset planner” on the page and confirm. Use the control that hides finished notes if you only want a quieter list; that control does not delete storage by itself. Or clear site data, cookies, and local storage for this site in your browser, which removes the key along with anything else the browser stored for the origin. The rest of the site still works. The planner simply starts again at zero.

If storage is blocked, the page says that ticks will be lost when you leave. That message is accurate. It is not an error report sent to us. The planner is optional. You can write an inquiry, when the form works, without ever ticking a box. Nothing in the automotive articles depends on the planner being full.

8. Analytics

We do not use analytics cookies or analytics scripts. We do not count unique visitors, record cursor movement, or build a funnel from the gallery to contact. If that changes, we will update this policy and ask for consent where the law requires consent before the script runs. An auto repair page can be useful without a dashboard behind it.

Search terms you type into the on-page filters are handled in the browser. They are not an analytics event. We do not claim to see which chip you pressed. The status line that says how many cards are showing is calculated locally for you.

9. Advertising cookies

We do not set advertising cookies and do not load advertising pixels. Your reading of a brake or battery page is not, on our side, a retargeting event. Third parties who advertise workshops on their own platforms are outside this website. Their cookies, if any, are set on their sites or in their apps under their policies, not by an invisible tag in our footer. We do not permit those tags on these pages today.

This matters if you arrived from an advertisement. The advertisement, if one exists, should match a site that does not invent prices, reviews, or guarantees. The cookie policy is part of that match: we do not quietly tag you in order to make the advertising relationship look larger than the pages. If a tag were added, the honest sequence would be to describe it here first and to gate it on consent where consent is required.

10. Third-party content

The site does not embed maps, videos, social posts, or payment buttons. Fonts are files included with the site, not a request we document as a third-party cookie. Illustrations are image files on this origin. They do not come with a tracking pixel in the markup we publish. If you open an image in a new tab, you are still requesting our file, not a social network.

A link you follow away from the site, if we add one in the future, would leave this policy behind. At present the internal links stay on DriveCore Service pages: services, legal pages, and the form. The form’s empty endpoint means the script does not contact a form vendor as you type.

Optional cookies that are not strictly necessary generally require consent before they are stored, under rules such as those in the UK and the EEA. This site does not set those cookies, so it does not show a banner that would ask you to accept something that is not there. A banner with no real effect would be decorative compliance, and we do not want it. The planner is not started by a cookie and is not switched on until you tick a box, which is itself the interaction that writes the storage.

If we add analytics or advertising, the sequence will be: update this policy with names and durations, add a real choice that defaults to off where the law requires an opt-in, and only then load the tool. Silence after a policy edit is not consent to a new cookie. The same sequence applies if a form provider would set a non-essential cookie. Delivery of a message and setting a marketing cookie are different acts, and only the first is even contemplated by the current form.

12. How to manage storage

You can control cookies and site data in the browser you use. The names of the menus change, but the major browsers all provide a way to see and delete site data.

  • Chrome: Settings, Privacy and security, then cookies and other site data.
  • Firefox: Settings, Privacy and Security, then Cookies and Site Data.
  • Safari: Settings, Privacy, then Manage Website Data.
  • Microsoft Edge: Settings, Cookies and site permissions, then Manage and delete cookies and site data.

The labels move slightly between versions. Look for cookies, site data, and local storage together. Deleting them for this site removes the planner. It does not delete a message that was never sent, and it does not delete a message that was already delivered to a provider, because that copy is no longer only in your browser. Delivered messages are described in the privacy policy’s retention section. Today, delivery is not configured, so the usual case is that there is no server copy at all.

Private browsing modes often discard storage when the window closes. The planner will still count ticks during that session and then forget them. That behaviour is the browser’s, and it is compatible with this policy. You do not need our permission to use private mode.

13. Do Not Track and similar signals

Some browsers send a “Do Not Track” signal or a Global Privacy Control signal. Because we do not run cross-site tracking, there is no tracker on these pages for the signal to disable. We still design the site so that an optional tool, if one is ever added, can respect a legally meaningful opt-out signal rather than ignore it. Until then, the absence of analytics is stronger than a signal: the measurement simply is not present.

A signal does not clear the planner. If you want the ticks gone, use reset or delete site data. A signal also does not submit or block the contact form. The form’s behaviour is the endpoint check described in the privacy policy, not a tracking preference.

14. Updates

We will revise this policy when the storage story changes. The date at the top is the version to trust. Significant changes, especially the addition of a non-essential cookie, will be described before the cookie is used. Small wording clarifications may be made so the policy stays aligned with the planner’s button labels. If the button ever says something different from this page, the button is what the script does, and the policy should be corrected to match it.

A change of workshop topic, such as adding a clearer note about cooling or brakes, is not a cookie change. Content edits do not by themselves set storage. Only a change to the script’s storage behaviour, or to an embedded third party, needs a new cookie description. We will not bury that description in a service article. It belongs here and in the privacy policy together.

15. Contact

Questions about cookies and local storage can be sent through the contact form when it can deliver. Explain what you want to know, for example whether a particular cookie name is ours. At the time of this writing, the honest answer to “which cookies do you set?” is none. The planner key is local storage, not a cookie. If the form cannot send, the question has not reached us through the form. Email [email protected], call +353 85 234 3631, or write to 1 Limekiln Ln, Whitehall, Dublin 12, D12 DY80, Ireland. Please do not guess an inbox from an older project.

You can also reread the planner on the approach page and watch what your browser stores, using its own tools. Seeing an empty cookie list for this site is consistent with this policy. Seeing the local storage key after you tick a note is also consistent. Seeing an unexpected advertising cookie would not be consistent, and we would want it removed. The footer links this policy from every page so you can check the storage story without hunting through the service articles.

DriveCore Service keeps this cookie policy beside the privacy policy and the terms so the auto repair website’s actual browser behaviour stays visible. The policy is not a banner in disguise. It is the reason a banner is not shown.