Legal

Privacy Policy

How DriveCore Service handles information on this website. Last updated 3 November 2026. This policy matches the site as it is built: static pages, a contact form that sends a message only when a delivery service is connected, and a visit planner that stores ticks in your browser.

1. Introduction

This privacy policy explains what DriveCore Service does with information in connection with this website. The site describes auto repair, vehicle maintenance, diagnostics, and related workshop topics. It is an information site with an inquiry form. It is not a shop, not a booking system, and not an account portal. Reading a page does not create a customer record.

The policy is written to match the pages you can open. Where a practice is absent, the policy says it is absent. We do not describe encryption products, audit programmes, or a privacy office we have not established. We also do not describe payment processing, because the site does not take payment. If a sentence here and a button on a page ever disagree, the button and the script are what the site does, and this policy should be corrected to match them.

Please read it with the Terms and Conditions and the Cookie Policy. The terms explain what the site is for. The cookie policy explains browser storage in more detail, including why there is no banner for optional cookies.

2. About this website

The website is a collection of HTML pages, a stylesheet, fonts, photographs used as illustrations, and one script. The script runs the mobile menu, the “more” menu, filters and search on the services and notes pages, the visit planner, the gallery lightbox, reading progress on long articles, and the contact form. It does not build a profile as you move from brakes to suspension. Moving between pages does not require you to sign in.

Content is about passenger-vehicle repair and maintenance in general terms. It does not diagnose the vehicle you drive. Submitting the form, when submission works, asks a question. It does not create a repair order. Photographs are illustrations. They are not evidence of a file we hold about you.

3. Who is responsible

DriveCore Service publishes this website from 1 Limekiln Ln, Whitehall, Dublin 12, D12 DY80, Ireland. You can call +353 85 234 3631 or email [email protected]. The site does not publish a company number or the name of a data protection officer. Those two details stay off the page because they are not confirmed. Inventing them in a privacy policy would be a different kind of contact line from the address, phone, and email that the footer already shows.

If a law that applies to you requires a controller to be identifiable, use the address, telephone number, and email above, or the contact form when that form can deliver. Until a message is delivered, the operator of the site has not received that particular form request. The email and the phone remain available whether or not the form is connected.

4. Information we collect

We do not run an account system, a newsletter signup, a booking calendar, or a payment page, so we do not collect passwords, card numbers, or appointment slots through those features. They are not features. The information the site is built to receive is the information you type into the contact form, and only if the form’s delivery step succeeds. Separately, your own browser can store planner ticks locally. Those ticks are not sent to us by the planner script.

We do not ask you to upload photographs of a vehicle, identity documents, or diagnostic printouts. The form has no file field. If you paste a long technical log into the message, you are choosing to include it. Please do not paste secrets the site does not need. A workshop question needs a system and a symptom, not a scan of a driving licence.

5. Information you choose to provide

The form fields are your name, your email address, a subject chosen from a short list, your message, and a required confirmation that you have read that the name, email, and message may be used to reply. The subject list covers a service inquiry, a general question, website feedback, a content correction, and a technical website issue. You decide what the message says. We do not add a hidden field for a price, a vehicle identification number, or a marketing preference, because those fields are not in the form.

You should not include payment card numbers, government identity numbers, medical information, or passwords. If you include them anyway, you are sending data the site did not request. We would rather you did not. A privacy request can be written in the same message box, clearly labelled as a privacy request, again only if the form delivers.

6. The contact form

The form is marked with an empty delivery endpoint in the page. On submit, the script checks that endpoint. If it is empty, the script stops the submission, tells you the message was not sent, and leaves your text in the fields. Nothing in that path is transmitted by the script. There is no second, silent request. Refreshing the page does not send the draft. Closing the page discards it unless your browser restores form fields on its own, which is a browser feature, not our storage.

If an endpoint is later connected, the script will send the form fields with a POST request and will show a thank-you note only when the response indicates acceptance. If the request fails, the script says the message could not be delivered and keeps the text in the form. We will update this policy before a provider is connected if that provider changes what is stored, where it is stored, or whether a cookie is set. Connecting a provider in silence would make this section false, which is not acceptable.

A delivered message is a request for a reply. It is not consent to a marketing list, not a booking, and not a payment. The person who receives it, if anyone does, may need your email address in order to answer. That is the purpose you confirm with the checkbox. The checkbox is required because the site should not pretend you agreed to a reply path you did not see.

7. Email and telephone

The published email address is [email protected] and the published telephone number is +353 85 234 3631. The form’s failure message names both, so a reader is not left with only a form that cannot send. Older wording that said no inbox was published is no longer accurate and should not remain anywhere on the site.

Writing or calling those details is a question, not a booking and not a recorded-line notice. This policy does not describe call recording, because none is stated. A number you find on a different website is not this channel. Opening hours are not published, and the telephone is not a roadside recovery line.

8. Technical data

Serving a website usually involves a host that sees technical data such as an IP address, a time, and the address of the file requested, so that the file can be delivered and abuse can be limited. We do not operate an analytics layer on top of that, and we do not name the host in this policy because the provider is not identified on the public pages. We do not claim to download those logs and turn them into a visitor report.

Your browser also tells sites its general technical characteristics through ordinary requests. We do not add a script that fingerprints the browser, records the cursor, or watches how far you scroll for marketing. A reading-progress bar on long articles is drawn on your screen from the scroll position. It is not transmitted. Search filters compare your typing with the text already on the page. The letters you type into search are not sent to a server by our script.

9. Cookies and similar technologies

Our pages do not set a cookie for login, preferences, analytics, or advertising. There is no login and no basket. The contact form does not drop a tracking cookie when you type. The visit planner uses local storage, which is not a cookie. The key begins with drivecore-checklist- and holds the identifiers of the boxes you tick. It is written only after you tick, updated when you change a tick, and removed when you reset the planner. Clearing site data in the browser removes it as well.

Local storage stays on the device. It is not attached to the request for the next page. It is not a copy we can open from our side. If your browser blocks storage, the planner still works for the current view but tells you that ticks will be lost when you leave. That notice is the script being honest. The cookie policy explains how this differs from analytics cookies and why the site does not show a consent banner for a cookie it does not set.

10. How information is used

If a message is delivered, the intended use is to read the inquiry and reply to the email address you gave, or to consider a correction or a privacy request you labelled as such. That is the use the checkbox describes. We do not describe a secondary use for advertising audiences, data broking, or training a public model, because those uses are not part of this site.

Planner ticks are used only to redraw your checklist. We do not use them, because we do not receive them. Technical logs, if a host keeps them, are not something we claim to mine for service suggestions. The articles you read do not become a profile of “drivers interested in brakes” on our side. We do not have that profile feature.

11. Legal bases

Different laws use different words for why an organisation may handle personal information. Where a law such as the UK GDPR or the EU GDPR applies, a common basis for answering a message that a person chose to send is that the message is a step the person asked for before any contract, or a legitimate interest in reading and replying to correspondence, or consent where the checkbox is the right frame. The published place of business is Dublin, Ireland. This policy does not pick a single legal basis for every reader in every country, and it does not pretend that one statute covers every visit.

The practical point is narrower than the legal vocabulary. If the form does not deliver, we have not received the message through the site, and there is no content to process. If the form does deliver, the content is the inquiry you wrote and the address you asked us to use for a reply. We do not rely on a basis for selling that content, because we do not sell it. Mandatory rules that apply to you are not waived by this paragraph.

12. Automated decision-making

The site does not make automated decisions that produce legal effects or similarly significant effects about you. The form script decides only whether a delivery endpoint is configured and whether the response looked successful. It does not score your driving, approve credit, or set a price. There is no price. Filters that hide a card when your search does not match are a display convenience on your device. They are not a decision about you.

We do not run a model that reads the message and returns a diagnosis. A human reply, if one is sent after a message is delivered, is not an automated decision of the website. The website’s own automation stops at transport: send, or say that you did not send.

13. Analytics

We do not install analytics scripts. We do not count unique visitors, build funnels from the gallery to the contact page, or record session replays. A workshop page can be useful without a dashboard behind it. If that changes, this policy and the cookie policy will name the tool, and the tool will not run before any consent the applicable law requires.

Server logs, if they exist at the host, are not our analytics product. We do not claim to have configured them, reviewed them, or disabled them, because we do not identify the host here. We simply do not add a second measurement layer in the pages you download.

14. Advertising technologies

We do not set advertising cookies and do not load advertising pixels or social widgets. Reading the brake page is not, on our side, a retargeting event. If DriveCore Service is advertised on another company’s platform, that platform’s own site or app is where its cookies, if any, are set. Those cookies are not placed by a tag in our footer. We do not permit those tags on these pages today.

The absence of a pixel is also a statement about honesty in advertising. The pages should match what an advertisement could fairly say: informational descriptions of repair and maintenance, no prices, no invented reviews, no guaranteed results. A tracking pixel would not create those facts, and we do not use one to compensate for them.

15. Service providers

Today the public site does not name a form provider, an email host, a payment processor, or an analytics vendor, because none is connected in the pages. Fonts are files served with the site, not a live request to a font subscription that we document as a third-party embed. The script does not call a third-party marketing domain.

If a form endpoint is added, the provider that receives the POST will be a service provider for the purpose of delivering the message. Before that happens, the policy should name the role in plain language: who receives the message, whether they may use it only to transmit it, and whether they set a cookie. Until that update, assume no such provider is in the path, because the empty endpoint means the script never starts the request.

16. Sharing

We do not sell personal information. We do not share a mailing list, because we do not keep a mailing list from page views. A message that was never delivered cannot be shared, because we do not have it. A message that was delivered may be read by the person who handles inquiries for DriveCore Service. That is the point of the form.

We do not describe routine sharing with manufacturers, roadside clubs, or parts distributors. No such arrangement is published. If a law required a disclosure, for example a valid demand from a public authority, that obligation would come from the law, not from a partnership we have invented in this policy. We do not claim that such a demand has been received.

17. International transfers

Because the site does not name a host or a form provider, it also does not name a country where a delivered message would be stored. We will not invent a data-centre region to sound specific. If a provider is later named, the update should say whether storing or transmitting a message involves a transfer that your law regulates, and what mechanism, if any, is actually in place. A sentence that claims “standard contractual clauses” without a real contract would be decorative compliance, and we do not want it.

Your own device is wherever you are. Planner data does not move to us when you travel. It stays in the browser storage for this origin until you clear it or reset the planner.

18. Retention

Undelivered drafts are not retained by us, because they never arrive. How long your browser keeps typed form fields is a browser setting, not our retention schedule. Planner ticks remain until you reset them, clear site data, or the browser drops storage. We do not set an expiry on that key. There is no server copy to expire.

If a message is delivered, we do not publish a fixed number of months for keeping it. The honest criterion is the time needed to handle the inquiry, to keep a record of what was asked and answered where a later dispute about that correspondence makes a record reasonable, and to meet a legal duty if one applies. We do not keep messages in order to build a marketing archive. When a provider is connected, this section should be updated if the provider’s own retention is more specific than this criterion. Until then, do not assume a delivered message exists, because delivery is not currently configured.

19. Security

We do not advertise a certification, a penetration test, or a particular security product. Those claims would be false if we have not made them true. What we can say is structural. The form does not send data when it cannot deliver, which avoids creating a copy we did not mean to create. The pages do not ask for card data. The planner is confined to your browser. You can reduce your own risk by not pasting secrets into the message.

No website can honestly promise that a transmission will never be intercepted or that a future provider will never have an incident. If a provider is added, their security will matter, and this policy should not overstate it. If you reuse a password in the message field, you are creating a risk the form did not need. Please do not do that.

20. If something goes wrong

If you believe a message was sent in error, or that a page is collecting something this policy does not describe, use the contact form when it can deliver and say what you observed, including the page address. If the form cannot deliver, we have not received the report through the site. A screenshot you keep for yourself is still useful to you. It is not a notice to us until it arrives.

We do not operate a bug-bounty programme on these pages, and we do not ask you to test the site by attempting to break it. Reporting a broken image or a sentence that still mentions a former business is welcome. Probing for hidden endpoints is not a service the site requests.

21. Your rights

Depending on where you live, you may have rights to ask whether personal information is held, to receive a copy, to correct it, to delete it, to restrict or object to certain uses, and to complain to a regulator. Some laws also speak about portability or about withdrawing consent. This policy does not restate every national statute. It tells you the practical limit on this website: rights run against information the operator actually holds. A draft that never left your browser is not held by us. Planner ticks are held by your browser, and you can delete them without a request.

Where a message was delivered, a request about that message is meaningful: you can ask what was received and ask for a correction if the reply chain contains a mistake about you. We do not promise a specific number of days in this paragraph, because we do not want to invent a service level. We do say that a request which never arrives cannot be actioned. Nothing in this section removes a mandatory right. Nothing in it creates a right to a price list, a booking record, or a staff file that the site does not keep.

22. How to make a request

Send the request through the contact form, label it as a privacy request, and describe what you want and which email address you used if you wrote before. We may need that address to tell one message from another. Do not send identity documents unless a later, specific reply asks for a proportionate check and explains why. This paragraph does not ask for them.

If the form reports that delivery is not connected, the request has not been made through the form. You can send it by email to [email protected], by post to 1 Limekiln Ln, Whitehall, Dublin 12, D12 DY80, Ireland, or by telephone on +353 85 234 3631. Those are the same details as the contact page and the footer. A guessed inbox from another business is not an extra channel.

23. Complaints

If you are in a place that gives you a regulator for information rights, you may complain to that regulator. The published place of business is Dublin, Ireland. A regulator will usually expect you to have tried to reach the organisation first. On this site, that attempt is the form when it can deliver, or the email, post, and telephone published above.

A complaint about workshop work that was agreed outside the website is a different subject from a complaint about personal information. This policy covers the website’s information practices. It does not publish a workshop complaint procedure, a goodwill policy, or an ombudsman membership. Those processes are not confirmed here.

24. Children

The site is written for adults who are asking about vehicle repair and maintenance. It is not directed at children, and we do not knowingly ask children to send inquiries. The form cannot reliably know the age of the person typing. If you are a parent and you believe a child has sent a message that was actually delivered, use the privacy-request route to say so. If the message was not delivered, we do not have it to delete.

Nothing on the site is a game, a membership for minors, or a collection of a child’s location. Please do not include a child’s personal details in a vehicle inquiry. They are not needed to describe a noise or an oil service.

Pages link among themselves and to nowhere else for social embedding. If a future page linked to another site, that site would have its own policy, and this one would not cover it. At present the legal pages, the service pages, and the form are the destinations. We do not frame third-party checkout pages, because we do not have a checkout.

Some browsers send Do Not Track or Global Privacy Control signals. Because we do not run cross-site tracking, there is no tracker on these pages for the signal to switch off. If an optional tool is ever added, it should respect a legally meaningful opt-out rather than ignore it. Until then, the absence of analytics is stronger than a signal. The measurement is not present. The cookie policy repeats this point so the two documents stay aligned.

26. Changes and contact

We will update this policy when the site’s information practices change, especially if a form provider, an analytics tool, or a published contact channel is added. The date at the top of the page is the version to trust. A change that starts cookies or starts sending messages to a new provider should be described before that practice begins, not afterwards as a surprise. Small clarifications may be made so the policy stays aligned with button labels. If a button and a paragraph drift apart, the button is what the script does.

Questions about privacy can be sent through the contact form when delivery works, or by email to [email protected], by post to 1 Limekiln Ln, Whitehall, Dublin 12, D12 DY80, Ireland, or by telephone on +353 85 234 3631. Explain that the message is a privacy question. If the form cannot send, that attempt has not reached us. The email, post, and phone are the other published routes. You can also reread the planner section and the cookie policy and check your browser’s storage for this site. An empty cookie list and, after you tick a box, a local storage key beginning with drivecore-checklist- are what this version of the site is built to produce. An advertising cookie would not be consistent with this policy, and we would want it removed.

DriveCore Service provides this policy so visitors can see what the auto repair and maintenance website actually does with information. It is part of the public description of the site, together with the terms and the cookie policy, and it is linked from the footer of each page. It does not create a customer relationship by being read.