Cookie policy

Published by KLAIM LIMITED on 5 October 2026. This page is the company’s own statement for this website. It is not a substitute for advice on a particular engagement.

What this policy covers

This cookie policy explains how the website at https://klaimlimited.business uses cookies and similar technologies. The site is published by KLAIM LIMITED, 9 Corbets Tey Road, Upminster, RM14 2AP, United Kingdom. Questions about it can be sent to help@klaimlimited.business or made by telephone on +44 7520 619384.

The policy is meant to be read with the privacy policy, which describes personal data in enquiries, and with the terms of service, which describe use of the pages. It does not describe an advertising network, because the site does not run one.

A cookie is a small piece of text that a site can ask a browser to store and send back. Cookies can be session cookies, which usually end when the browser is closed, or persistent cookies, which stay until a date or until the person deletes them. They can be first-party, set by the site the person is visiting, or third-party, set by another domain. This distinction matters because the site’s own session cookie and a request for a font file are not the same kind of thing.

Similar technologies include local storage, session storage, and pixels. The site’s own script does not write to local storage or session storage. It does not place a tracking pixel. This policy still explains those technologies so that a reader can see what is absent as well as what is present.

The short version

Reading the pages does not require an account and does not set an analytics cookie or an advertising cookie. The contact script may set a first-party session cookie so that it can limit repeated form posts. Fonts may be requested from a third-party font host. That is the whole cookie picture of this version of the site, published on 5 October 2026.

There is no cookie banner that pretends to offer a choice about analytics, because there is no analytics cookie to accept or refuse. Adding a decorative banner would not make the site more honest. If a non-essential cookie is introduced later, this policy will change first, and the site will not set that cookie as if it were required to display a page.

Cookies the site sets

When a person submits the contact form, the server script starts a PHP session. PHP’s default session cookie is named PHPSESSID. It is a first-party cookie. It holds a random session identifier. The identifier points to a small server-side record. That record stores the time of recent form posts so the script can refuse a burst of messages.

The cookie is essential for that abuse control. Without it, the server could not tell that several rapid posts came from the same session. The company uses the control because the form sends email to a real inbox. It is not used to remember a person’s name between visits, and it is not used to build a marketing profile.

The cookie is a session cookie in the ordinary PHP sense. It is not given a long expiry date by this website’s own pages. Closing the browser ends a typical session cookie. The server-side count of posts is relevant for about an hour of activity within the session. It is not a twelve-month tracker.

Static pages — the home page, services, portfolio, about, contact, the legal pages, and the confirmation page — do not themselves start that session. Opening them in a browser does not, by the site’s own code, set PHPSESSID. The cookie appears when the form script runs.

The confirmation page and the error page are produced by the same script, so a session may already exist when they are shown. They do not add a second tracking cookie.

What the session contains

The session is used to store timestamps. It may store the time of the last accepted post and a short list of post times within the hour. It does not need to store the message body once the script has either mailed the message or refused it. People should still assume that an email, once accepted, exists as email, which is a different record and is described in the privacy policy.

The session identifier is a random value. It is not the person’s name or email address. Someone who copies the cookie value out of their browser has a key to that session until the session ends. People should not send cookie values to anyone else.

The script also reads a timing field and a honeypot field that are submitted with the form. Those are form fields, not cookies. They are explained here so they are not mistaken for cookies. The timing field is set when the form is displayed. The honeypot is a field that ordinary visitors are not asked to fill. A filled honeypot causes the post to be refused.

Cookies the site does not set

The site does not set a Google Analytics cookie, a Matomo cookie, a Meta pixel cookie, a LinkedIn insight cookie, a TikTok cookie, or any other advertising or measurement cookie. It does not use Google Tag Manager. It does not embed YouTube, Vimeo, or a map widget. Those absences are deliberate for this version of the site. They are not a promise about every future page unless this policy is updated.

The site does not set a cookie to remember a cookie-banner choice, because it does not show a banner for non-essential cookies. It does not set a cookie to keep a shopping cart, because it does not sell through a cart. It does not set a cookie to keep a logged-in session, because it does not offer accounts.

The portfolio and the service pages do not set a cookie when a person hovers a link or opens the menu. The menu and the image changes are handled in the page itself.

Font requests

The pages ask the browser to load Commissioner and Faculty Glyphic from Google Fonts. That request goes from the browser to Google’s font servers. It can include an IP address and the usual technical data of an HTTP request, under Google’s own practices. KLAIM LIMITED does not receive a report of those requests through this website.

The font request is not a cookie set by klaimlimited.business. A font host may set or read its own cookies according to its own policy. The company does not control that host’s cookies and does not use them to advertise. Readers who prefer not to contact a font host can block third-party requests in the browser or use a browser setting that limits them. The pages remain readable in a fallback typeface.

This policy does not copy Google’s privacy policy and does not claim that Google does or does not use a particular cookie on a font request. Readers who want that detail should read the font host’s current documentation.

Essential and non-essential

UK practice and the Privacy and Electronic Communications Regulations distinguish cookies that are strictly necessary to provide a service the person has asked for from cookies that are not. A session cookie that only exists to stop the contact form being abused, on a site the person is using to send a message, is treated here as strictly necessary for that submission. It is not used for a secondary purpose.

Analytics, advertising, and social cookies would not be strictly necessary to read these pages or to send one message. The site does not use them. If that changes, the company will not rely on this paragraph to avoid asking for a proper permission. The cookie policy will be rewritten to name the cookie, the provider, the purpose, and the lifetime, and non-essential cookies will be off unless the person makes a choice the law allows.

Strictly necessary does not mean secret. This page names PHPSESSID and says what it is for. A person can still delete it. If they delete it before a second post, the rate limit for the old session will not follow them, which is an ordinary consequence of deleting a session cookie, not a penalty.

How long cookies last

PHPSESSID, as used here, is a session cookie. Its practical life is the browsing session, unless the browser is configured to restore sessions or the server expires the session sooner. The company does not set a multi-month expiry on it in the pages’ own code.

The server forgets the rate-limit timestamps when the session ends. An hour is the window used to count posts inside a living session. It is not a retention period for the cookie file on the person’s computer beyond the session.

Font requests do not create a retention period that this website controls. Any cookie a font host sets lives under that host’s expiry. Blocking the request prevents it.

How to control cookies in a browser

Every major browser can block or delete cookies. The control is usually in the privacy or security settings, sometimes under “cookies and site data”. The names of the menus change. The company cannot keep a screenshot of every browser current, so this policy describes the kinds of control rather than a single click-path.

A person can delete existing cookies for klaimlimited.business. That removes PHPSESSID if it is present. The pages will still load. The next form post may set a new session cookie. Deleting cookies does not delete an email that was already sent.

A person can block all cookies. The pages are written to be readable without the session cookie. The form may then be unable to keep a rate limit tied to a session. The server can still refuse a post that fails the other checks, such as the honeypot, the timing field, and validation of the name, email, and message. If blocking cookies causes a form post to fail, the person can email help@klaimlimited.business directly.

A person can block third-party cookies and still allow first-party cookies. That setting is a common way to reduce advertising cookies across the web. On this site it would not remove PHPSESSID, which is first-party, and it may affect whether a font host can set its own cookie. The typefaces may still load, or they may fall back, depending on the browser.

Private-browsing or incognito modes usually discard cookies when the window closes. They do not make a person anonymous to the server that receives a form. The email address typed into the form is still the email address.

Browser vendors publish their own instructions. Chrome, Safari, Firefox, and Edge each document cookie controls. Those documents are the current source for menu names. A corporate-managed browser may hide the controls. In that case the person’s organisation, not KLAIM LIMITED, decides the policy of the device.

Do Not Track and similar signals

Some browsers send a Do Not Track signal or a similar preference. There is no single legal rule that requires every UK site to respond to every such signal in the same way. This site does not need the signal in order to refrain from advertising cookies, because it does not set them. The site does not use the signal as a back door to set extra cookies.

Global Privacy Control and similar automated signals are aimed largely at sale and sharing of personal information in other legal systems. This site does not sell personal information and does not share it for cross-context advertising. The signal is not required to achieve that result here. The company will not describe the absence of a sale as a response that was “turned on” by a signal if the sale was never part of the site.

Mobile applications and email

There is no mobile application published as part of this website. An email client that opens a link to the site is just a browser session. The site does not place a cookie inside the person’s email program. Images in the company’s own pages are ordinary page images, not email tracking pixels. The company does not send a newsletter from this website.

If a person emails help@klaimlimited.business, their email provider may use cookies in the webmail interface. Those cookies are the provider’s. They are not set by klaimlimited.business.

Changes to the site’s cookies

This policy is part of the site published on 5 October 2026. If the company adds a cookie, it will name it here before relying on it, or at the same time it is introduced if it is strictly necessary and is described immediately. A non-essential cookie will not be added in silence.

A change of font host, or a decision to stop using a remote font host, will be reflected here if it changes the third-party request described above. Removing the font request would not require a person’s permission. Adding an analytics cookie would.

Older printed copies of this policy, if anyone makes them, can go out of date. The page on the website is the current version.

What a person can ask

A person can ask whether a particular cookie is in use, and the company will answer from the current site rather than from a generic list. The address is help@klaimlimited.business. The postal address is 9 Corbets Tey Road, Upminster, RM14 2AP, United Kingdom. The telephone number is +44 7520 619384.

A question about personal data in an enquiry, as opposed to the cookie itself, is handled under the privacy policy. The session cookie’s identifier is personal data in a thin sense if it can be tied to a person. On this site it is tied only for the life of the session and only to the rate limit, unless the same browser session is the one that submitted a form, in which case the enquiry itself is the richer record.

Complaints about cookies can be raised with the company and, where the matter is about personal data, with the Information Commissioner’s Office. The company does not publish an ICO registration number on this site.

Logs that are not cookies

A server may record an IP address and a user-agent when a page is requested. That record is a log, not a cookie, unless the server also asks the browser to store an identifier. This site’s pages do not add a tracking identifier to those logs. The privacy policy describes logs. Deleting cookies in a browser does not delete a log that the host already stored, and it does not delete an email already sent.

The company does not use log data to rebuild a browsing history for advertising. If a host’s default log is longer than the company needs, the practical control is the hosting arrangement, not a cookie setting in the visitor’s browser. The company does not publish the host’s log retention as a number of days, because that figure is not stated on this website and will not be invented here.

Relationship to the rest of the site

The contact forms on the home page and the contact page are the only features that need the session cookie. The services, portfolio, and about pages do not. A person who only reads those pages does not trigger PHPSESSID through the site’s own code.

The terms and conditions deal with commissioned work. They do not authorise a new cookie. A contract with a client does not turn this marketing site into an analytics product. If a client engagement includes a different website that the company builds for the client, that website’s cookies are the client’s responsibility to describe, unless the engagement says that KLAIM LIMITED will draft that description.

Nothing in this policy asks a person to accept a cookie as a condition of reading the company name, the address, or the telephone number. Those details are on the page in ordinary text.