Last updated 5 October 2026

Cookie policy

This policy explains how cookies relate to the website at https://tervra.xyz, operated by TERVRA LIMITED of 108 Fonthill Road, London, N4 3HT, United Kingdom. It should be read with the privacy policy. The short version is deliberate: the pages are built not to set a first-party cookie, there is no analytics cookie, and the only moment a third party may set a cookie is if you choose to load the map on the contact page.

What a cookie is

A cookie is a small piece of information that a website asks your browser to store and to send back later. Cookies were designed so that a site could remember a basket, a login, or a preference across requests that would otherwise be separate. A cookie has a name, a value, a domain, a path, an expiry, and flags that say whether it should travel only over an encrypted connection or whether browser scripts may read it.

A session cookie is meant to disappear when you close the browser. A persistent cookie remains until its expiry date or until you delete it. A first-party cookie is set by the site you are looking at. A third-party cookie is set by another domain, often because a page has embedded that other domain’s content. The distinction matters because browser makers have spent several years restricting third-party cookies, and because the privacy effect of a cookie depends on who can read it and what they join it to.

Cookies are not the only storage a browser has. Local storage, session storage, and indexed databases can hold information without using the cookie jar. This website’s pages do not use those stores to keep a visitor record. The contact form does not write your draft into local storage. If your browser or an extension stores form values for your own convenience, that is your browser’s feature, not a cookie set by TERVRA.

A server log is also not a cookie. A log is a line the server writes about a request. It can contain an IP address. It does not, by itself, leave a file in your browser. The privacy policy describes logs. This policy mentions them only so they are not confused with cookies.

The rule that applies

In the United Kingdom, the Privacy and Electronic Communications (EC Directive) Regulations 2003, usually called PECR, regulate cookies and similar technologies. Regulation 6 says that a person must not store information, or gain access to information stored, on a user’s terminal equipment unless the user is given clear and comprehensive information and has given consent. There is an exception where the storage or access is strictly necessary to provide a service the user has requested.

The Information Commissioner’s Office publishes guidance on this rule. The guidance treats analytics cookies, advertising cookies, and most preference cookies that are not essential to a service the user asked for as technologies that need consent. It treats a cookie that is needed to complete a request the user made, such as a cookie that remembers the goods in a basket the user is building, as capable of falling within the strictly necessary exception. Consent, where it is required, should be a real choice. A banner that cannot be refused, or a site that sets the cookie before the choice, does not meet that standard.

TERVRA’s approach on this site is to avoid the problem rather than to paper over it. The pages do not set a statistics cookie, a marketing cookie, or a preference cookie. There is therefore no consent banner asking you to accept a category that the site does not use. A banner that offered “accept analytics” when no analytics tool exists would be theatre. This policy is the information. The choice about the map is a button, described below, not a dark pattern in a corner.

What TERVRA’s own pages set

The HTML, CSS, and JavaScript of tervra.xyz are written not to call document.cookie, not to set a Set-Cookie header from the static pages, and not to start a PHP session when you only read a page. contact.php, which receives the form, does not start a session and does not send a session cookie. Abuse control for the form is done on the server, by checking the origin of the request and by counting recent attempts against an IP address in a temporary server file. That file is not a cookie. It does not live in your browser, and deleting your cookies does not delete it. It also does not identify you by name. It is a short list of timestamps used to slow a burst of posts.

Because no first-party cookie is set, there is no table of TERVRA cookie names, durations, and values to publish. Publishing invented cookie names would be less honest than saying the list is empty. If a future change introduces a strictly necessary cookie, for example because a later form needs a security token stored in a cookie, this policy should be updated with the name, the purpose, the duration, and the fact that it is strictly necessary. Until that change exists, the list stays empty.

A hosting provider can, in some configurations, add a cookie of its own in front of a site, for load balancing or for a security challenge. No such cookie is part of the site TERVRA publishes, and this policy does not name one. If you inspect the response headers and find a cookie the pages did not describe, write to general@tervra.xyz with the cookie’s name and the page you loaded. A cookie that appears should be explained or removed. It should not be ignored because the policy hoped it was absent.

Categories, and which ones are in use

It is usual to sort cookies into four conversations, even when some of the conversations are empty. Doing so makes the absence visible.

Strictly necessary cookies are those without which a service you asked for cannot be provided. A login session on a site that has accounts is the classic example. This website has no accounts and sets no strictly necessary cookie of its own. The rate-limit file described above is server-side and is not this category.

Preference cookies remember choices such as a language or a region. The site is in English and does not offer a switch that would need to be remembered. No preference cookie is set.

Statistics cookies count visits, measure scrolls, or record which buttons were pressed for the site operator’s dashboard. No statistics cookie is set. The site does not embed a product of that kind. Server logs, described in the privacy policy, are not a substitute analytics suite and are not cookies.

Marketing cookies follow a person or a browser across sites so that an advertisement can be chosen or measured. No marketing cookie is set by these pages. There is no advertising slot on the site. There is no social “like” button that would load another company’s script in the footer. Links to email and telephone are ordinary links. They do not include a tracking pixel.

The map

The contact page states the address in text: 108 Fonthill Road, London, N4 3HT, United Kingdom. Beside that text is a button labelled “Show the map”. The button does not load a map when the page first arrives. The embedded frame is created only after the button is used. The frame’s address is an OpenStreetMap export URL with a marker at the published coordinates of that address. OpenStreetMap is a third-party project. Its operators are not TERVRA LIMITED.

When the frame loads, your browser requests map tiles and the embed page from OpenStreetMap’s servers. A request of that kind carries the usual technical data: IP address, user agent, and the address of the resource. OpenStreetMap may set cookies on its own domain. TERVRA does not choose the names or the lifetimes of those cookies, does not read them, and does not receive a report of them. Their purpose, so far as a map embed ordinarily has one, is to operate the map service, which can include remembering a setting of that service. Because they are not TERVRA’s cookies, this policy will not invent a duration such as “thirteen months” for them. OpenStreetMap publishes its own privacy information, and that information, not this page, is the source for how that project handles data.

You do not have to load the map. Every practical contact method works without it: the postal address is on the page, the email is general@tervra.xyz, and the telephone number is +44 7399 204815. If you have already loaded the map and you want the third-party cookies gone, delete them in your browser. Blocking third-party cookies in the browser will also reduce what an embed can store. The rest of tervra.xyz does not depend on those cookies.

The button is the information and the choice together. It is specific. It says what will load. It is not a condition of reading the contact details. If you use a browser that blocks third-party cookies by default, the map may still appear while the cookies are refused. That is a good outcome. The map is a convenience, not an access test.

How to control cookies in a browser

Every current major browser can show you the cookies stored for a site and can delete them. The labels move between versions, so the following is a description of the control rather than a screenshot that will date. In each case you can also block third-party cookies as a standing setting, and you can block all cookies if you are willing to break sites that truly need them. Blocking all cookies will not break the reading of tervra.xyz as it is published, because the pages do not need a cookie to render. It may affect the map embed. It will not stop you sending the form.

In Chrome, cookie controls sit in Settings, under Privacy and security, then Third-party cookies or Cookies and other site data, depending on the version. From that area you can block third-party cookies, delete cookies for a particular site, and see what is stored. Chrome also offers a way to send a “Do Not Track” style signal in some versions, but the more reliable control is the cookie setting itself. An extension can add further blocking. TERVRA does not require you to install an extension to use the site.

In Firefox, the controls are under Settings, Privacy and Security. Enhanced Tracking Protection, in its standard setting, already blocks many third-party cookies. You can choose strict protection, and you can manage data for individual sites, including clearing cookies and site data. Firefox separates cookies from the rest of site data in its site-information panel, which is useful if you want to remove a map cookie without clearing a password the browser saved for a different site.

In Safari on Apple systems, the control is under Settings or System Settings, then Privacy, or under Safari’s settings, Prevent Cross-Site Tracking. Safari has limited third-party cookies for some time. You can also manage website data and remove it for a chosen period or for all sites. On iOS the same ideas appear inside Settings, Safari. Blocking all cookies is available and, as noted, is not required for this site.

In Microsoft Edge, the path is Settings, Cookies and site permissions, then Manage and delete cookies and site data. Edge can block third-party cookies and can clear cookies when you close the browser. If you use tracking prevention, its strict level blocks more third-party storage. That setting does not change the text of TERVRA’s pages.

Other browsers, including Brave, DuckDuckGo’s browser, and older engines still found in some organisations, have equivalent panels. The pattern is the same: find site data, find cookies, delete the ones you do not want, and decide whether third-party cookies are allowed. If a browser is managed by an employer, the employer’s policy may lock these settings. That lock is the employer’s, not TERVRA’s.

What the controls do and do not do here

Deleting cookies, or blocking them, does not delete an enquiry you have already sent. The enquiry, if the mail function accepted it, is an email. Removing a cookie does not pull an email out of a mailbox. To deal with the email, use the rights in the privacy policy and write to general@tervra.xyz.

Blocking cookies does not stop the server from seeing the IP address of a request you choose to make. That is how the web works. The privacy policy explains logs and the IP address that is copied into an enquiry email. Cookie settings are the wrong tool for that fact. Not sending the form is the tool for the enquiry. Not pressing the map button is the tool for the map.

A private-browsing or incognito window starts without the ordinary cookie jar and usually discards new cookies when the window closes. It does not make you anonymous to the site you are requesting, and it does not hide your IP address from the server or from OpenStreetMap if you load the map. It is still a useful way to avoid leaving a third-party cookie in your main profile.

Signals that are not cookies

Some browsers offer a “Do Not Track” header or a newer preference such as Global Privacy Control. This website does not run a tracker that would change its behaviour when it sees those headers, because it does not run a tracker. Honouring a signal matters when a site would otherwise track. Here, the published behaviour is already not to track with cookies. The header is not ignored out of indifference. It is unnecessary for a page that does not set the cookie the signal is worried about. If a tracking tool were ever added, the tool should not be switched on in the face of a legally relevant opt-out signal, and this policy would have to say so in plain text.

Email pixels are another non-cookie technique: a tiny image in a message that reports when the message was opened. TERVRA’s website form does not add a pixel to the email it sends to its own mailbox. A reply you receive should be judged by its content. If a reply ever contained an unexpected tracking image, that would be a mistake to be corrected, not a feature described here.

Links to other sites

The site links to its own pages, to a telephone number, to an email address, and, if you ask, to OpenStreetMap inside a frame. It does not link out to advertising networks. If a future page links to a third-party article or a standards body, that other site has its own cookies. Following the link is a request to that site. Read its policy if you want to know what it stores. TERVRA’s policy stops at the edge of tervra.xyz, plus the specific warning about the map embed.

Changes

This policy is dated 5 October 2026 and describes the site as published. If the site begins to set a cookie, the policy should name it before the cookie is part of ordinary browsing, or at the same time, with enough detail to decide. A change that only clarifies wording will still change the date. Keeping an empty cookie list accurate is part of the point. An empty list that has quietly become a full list is a failure of this document.

Contact

Questions about cookies on this website go to general@tervra.xyz, or by post to TERVRA LIMITED, 108 Fonthill Road, London, N4 3HT, United Kingdom, or by telephone on +44 7399 204815. If you are writing about a cookie you observed, include the cookie’s name, the domain, and the page. If you are writing about the map, say whether you loaded it. The Information Commissioner’s Office is the UK regulator for PECR as well as for data protection. Its public site is https://ico.org.uk and its public postal address is Wycliffe House, Water Lane, Wilmslow, Cheshire, SK9 5AF. You can read the privacy policy for how personal data, as distinct from the cookie mechanism, is handled.