Cookie policy
This policy says what cookies this website uses. The short version is specific: the pages do not set cookies. There is no analytics cookie, no advertising cookie, and no banner that stores a consent choice, because there is nothing non-essential to ask permission for. The rest of this page explains what that means, what a cookie is, how that differs from the enquiry form, and what you can do in your own browser. It is written for the site as it is published, not for a generic template that assumes a marketing stack.
What a cookie is
A cookie is a small piece of information that a website asks your browser to store, and that the browser may send back when you return to that site or, in some cases, when you visit a different site. Cookies are one tool among several. They have been used for ordinary jobs, such as remembering that a shopper’s basket still has items in it, and for less obvious jobs, such as counting a person across many pages or following them with advertising. The technology is the same. The purpose is what matters.
A cookie usually has a name, a value, a site it belongs to, and a time when the browser should drop it. Some last only until you close the browser. Some last for months or years. Some are readable only by the site that set them. Some are set by a different company whose content was loaded into the page. None of those varieties is, by itself, proof that a particular site uses them. This page is about driveritics.study, not about the web in general.
Cookies are not the same thing as the words on a page, and they are not the same thing as an email you choose to send. A person can read this entire website, including the services, the portfolio, the company account, and the legal pages, without the site writing a cookie. The pages are ordinary documents. They do not need to remember you in order to be read.
What this site sets
The HTML, the stylesheet, and the script that runs the menu, the seam, and the form checks do not create a cookie. They do not call the browser’s cookie store. They do not set a session identifier. They do not drop a cookie when you open the menu, when you move between pages, or when you submit the form. If you inspect the cookies for driveritics.study after a normal visit and after sending a test enquiry, the site’s own code will not have added one.
There is no cookie named for consent, because the site does not run a consent platform. There is no cookie named for analytics, because the site does not run an analytics product. There is no cookie that remembers which service you looked at, which demonstration you opened, or whether you prefer reduced motion. Reduced motion is read from your operating system or browser setting at the moment the page is shown. It is not saved by the site.
The server-side script that receives the form, contact.php, does not set a cookie in its response. A refused submission and a failed mail attempt are HTML pages. They do not start a logged-in session. A successful send, on a server where mail can be handed on, redirects to the thanks page. That redirect is not a cookie.
Why there is no banner
A cookie banner is a way of asking permission before non-essential cookies are stored, or of recording that a person has made a choice. It is useful when a site actually sets those cookies. It is noise when it does not. A banner that only exists to be dismissed, and that itself writes a cookie to remember the dismissal, would be the site inventing a cookie in order to talk about cookies. DRIVERITICS LTD has not done that.
United Kingdom rules on privacy and electronic communications are strict about storing information on a person’s device, or gaining access to information already stored, unless an exception applies. The exception that matters for many ordinary sites is a storage or access that is strictly necessary to provide a service the person asked for. This site does not need a cookie to show its pages or to carry a single form submission. Because it does not store that information, it does not ask you to accept a category that is empty.
If you have installed a browser extension that blocks banners, you will not miss a control on this site. There is nothing for the extension to hide. If a scan of the public pages reports a banner, that report is wrong for this version of the site, and the company would want to know, at network@driveritics.study, so the pages can be checked.
Kinds of cookies, in general
It is still useful to know the usual labels, so that a later change to the site can be described with the same words, and so that a cookie you see in your browser can be compared with what this policy claims.
Strictly necessary cookies are those without which a service you asked for cannot be provided. An example on other sites is a cookie that keeps you signed in, or that remembers the contents of a basket you are in the middle of paying for. This site has no sign-in and no basket. It therefore has no strictly necessary cookie of that kind. The form works as a single submission. It does not need to remember you between pages.
Preference cookies remember a choice, such as a language or a layout. This site is in English only. It does not offer a second language, a theme switch, or a saved seam position. It sets no preference cookie.
Statistics or analytics cookies count visits, paths through a site, and sometimes the rough location of a network. They are usually non-essential. This site does not set them and does not embed a product that would set them on the company’s behalf.
Marketing cookies are used to build or follow an advertising interest. They are non-essential. This site does not set them and does not load advertising.
A first-party cookie is set by the site you are looking at. A third-party cookie is set by someone else, often because their content was included in the page. Session cookies end when the browsing session ends. Persistent cookies remain until they expire or you delete them. The site sets none of these.
The enquiry form is not a cookie
The form asks for your name, your email address, and a message. Those values travel once, in the submission, to contact.php. They are not written into a cookie on your device. If the message is accepted and the server can hand it on, they are emailed to network@driveritics.study. If it is refused, or if the mail system does not accept it, the script does not keep a database copy. Either way, your browser is not asked to store the message as a cookie for the next visit.
The form also carries a hidden honeypot, a time, and a note of which page the form was on. Those are fields in that one submission. They are described in the privacy policy. They are not cookies. Closing the page drops them. They are not sent back automatically the next time you open the site.
A person sometimes confuses a form with a cookie because both involve the browser. The difference is control and repetition. You choose to type a message and to press the button. A cookie, once set, can be sent again without that choice, until it expires or you remove it. This site uses the first pattern for the enquiry and does not use the second.
Storage inside the browser
Browsers can store information in places other than the cookie jar. Local storage and session storage are two of them. They are not sent to the server automatically with every request, but they can still remember something about a site on the device. The script on this website does not write to local storage or session storage. It does not use IndexedDB. It does not use a service worker to cache pages in the background. A refresh loads the pages from the network in the ordinary way, subject to whatever caching your browser does on its own, which is the browser’s cache rather than a cookie the company set.
The menu opens and closes in the page you are looking at. It does not record that you opened it. The seam on the homepage moves when a section is reached. That position is not saved for a later visit. If you leave and come back, the page starts again at the opening divide.
Typefaces
The pages ask your browser to load Encode Sans Semi Condensed and Rubik from Google Fonts, so the typography matches the design. That is a network request to Google’s font servers. It is not a cookie created by DRIVERITICS LTD, and the site does not read a cookie back from that request into a company system. What Google does with a request that reaches its servers is not something this policy can honestly itemise as if it were the company’s own processing. The company does not receive a report of those requests.
If you block third-party requests, or if the font service is unavailable, the pages use a fallback typeface. The text, the form, and the navigation still work. Blocking fonts is not required. It is simply available, and the site was built so that a missing font does not hide the content.
Other people’s sites
Links on this site go to the company’s own pages, to the email address, to the telephone link, and, in the privacy policy, to the Information Commissioner’s Office. Following a link to the ICO leaves this site. That other site has its own cookies and its own policy. DRIVERITICS LTD does not control them and does not receive a copy of them. The portfolio and the service pages do not embed video players, map widgets, chat windows, or social timelines. Those embeds are a common way for another company’s cookie to appear on a page you think of as one site. They are not used here.
An email programme or a telephone app that opens when you use a mailto or tel link is your own software. It is not a cookie on driveritics.study.
What you can do in a browser
Because this site does not set cookies, deleting cookies will not change how the site behaves, other than in the general way that clearing a browser’s storage can sign you out of other websites you use. You remain free to block or delete cookies. The controls sit in the browser, not in a panel this company has added.
In Chrome, cookie settings are under Privacy and security, then Third-party cookies or the site settings for cookies, depending on the version. You can block third-party cookies, block all cookies, or remove cookies for one site. Blocking all cookies can break sites that need them. It will not break the reading of these pages or the sending of the form.
In Firefox, the settings are under Privacy and Security. You can choose a stricter tracking protection, and you can manage data for individual sites. Enhanced tracking protection may block some third-party content. It should not be required for this site to make sense.
In Safari, cookie controls are under Settings, then Privacy, or under Safari settings on a Mac. You can prevent cross-site tracking and block all cookies. Intelligent tracking prevention is Apple’s own feature. It is not a cookie this site sets.
In Edge, the controls are under Cookies and site permissions. The layout is close to Chrome’s. The same point applies: a strict setting is your choice, and this site does not depend on a cookie to show its text.
On a phone, the same browsers expose the same ideas, usually under a menu labelled Privacy or Site settings. A private or incognito window starts without the cookies of your ordinary profile and drops the session’s cookies when you close it. Using one here changes nothing the company stored, because the company did not store a cookie. It can still be a reasonable habit for other sites you visit on the same day.
If you use more than one browser, each has its own cookie store. Clearing one does not clear the others. A cookie, had this site set one, would have been specific to the browser that received it. Since it does not, there is nothing to clear in any of them for this site’s own name, beyond whatever another tool may have placed there without the company’s involvement.
How to see cookies for a site
Desktop browsers let you look at the cookies stored for a particular address. The usual path is the lock or tune icon in the address bar, then cookies, or a developer tools panel under Application or Storage. If you open that view on driveritics.study after loading the homepage, the services page, and the contact page, you should not see a cookie set by this site’s scripts. If you do, write to the company with the cookie’s name and the page you were on. A cookie can also be placed by an extension, by security software, or by a browser feature. Those are not the company’s cookies, but the company would still want a report that the published claim and the observed browser disagree, so the pages can be checked.
Do not send the company a full export of every cookie in your browser. That export can contain secrets for other sites, including sign-in cookies. A name, a domain, and the page you visited are enough.
If the site changes
If DRIVERITICS LTD later adds a cookie, this policy will be updated before that cookie is described as absent. A strictly necessary cookie, if one ever became necessary for a feature you asked for, would be described here, including its name, its purpose, and how long it lasts. A non-essential cookie would not be added in silence. The page would say what it does, and the site would not pretend that a banner-free statement still applied to a tool that needs a choice.
Examples that would require a change, and that are not present now, include a visit counter, an embedded film, a chat widget, a map that drops a cookie, a “remember me” login, or a test that stores a variant of the page on your device. None of those is part of the published site. The seam, the menu, and the form checks run without them.
A change to wording that does not add a cookie can be made by updating the date on this page. The date at the top is the date of this version.
How this sits with the privacy policy
Cookies can be personal information when they identify a person or can be tied to one. Because this site does not set them, the privacy policy’s account of the enquiry form is the main account of personal information the site handles. The two documents are meant to be read together and not to contradict each other. The privacy policy describes the name, the email address, the message, the hidden form fields, the mail attempt, and the possibility of ordinary host logs. This policy describes device storage. Host logs, if a host keeps them, are records on a server. They are not cookies on your machine. Both can matter, and they are not the same thing.
The terms of service and the terms and conditions govern use of the website. They do not create a cookie. If a sentence in those terms ever seemed to assume an account or a stored preference, the sentence would be wrong for this site, and this policy plus the privacy policy would be the place to check what is actually stored.
Contact
Questions about this policy can be sent to network@driveritics.study, or by post to DRIVERITICS LTD, Summit House, 4-5 Mitchell Street, Edinburgh, EH6 7BD, United Kingdom, or by telephone on +44 7911 123456. Please say that you are writing about cookies so the note is not read only as a new project brief. The privacy policy explains how to use your data-protection rights and how to contact the Information Commissioner’s Office.