1. What this Cookie Policy covers
This Cookie Policy explains how ASHLAR TECHNOLOGIES LTD, operating from 22 William Street, Blackwood, Wales, NP12 1NW, uses cookies and similar technologies on https://ashlartechnologies.ink. It should be read with our Privacy Policy. Together they describe the thin technical layer that sits under a public brochure for CCTV app development, video security platforms and related digital surveillance software. This is not a shop. It is not a consumer snack brand. It is a United Kingdom software house explaining how a browser and a server shake hands.
A cookie is a small file stored on your device. Similar technologies include pixels, local storage keys, session storage keys, and tags that a browser sends with a request. Some are essential to deliver a page you asked for. Some remember a choice. Some measure traffic. We keep the set small because a candy-coloured interface is not an excuse for a surveillance stack pointed at our own visitors.
Questions: commercial@ashlartechnologies.ink, +44 7411 527577, or post to ASHLAR TECHNOLOGIES LTD, 22 William Street, Blackwood, Wales, NP12 1NW.
2. Who decides
ASHLAR TECHNOLOGIES LTD decides which cookies https://ashlartechnologies.ink sets for our own purposes. When an embedded map of 22 William Street, Blackwood, Wales, NP12 1NW loads, the map provider may set its own cookies or read identifiers as a separate controller. We do not control that provider’s stack. If you refuse third-party content, use browser blocking or skip the map and write to commercial@ashlartechnologies.ink instead.
We do not permit a hidden advertising auction on this site. We do not drop a forest of retargeting pixels because a visitor read about live video monitoring. If that ever changed, this policy would change first, and non-essential cookies would wait for a lawful permission where the law requires one.
3. Law
Cookies in the UK are regulated by the Privacy and Electronic Communications Regulations 2003 as amended, read with the UK GDPR where the cookie involves personal data. The Information Commissioner’s Office publishes guidance on consent, necessity, and transparency. We follow that frame. Strictly necessary cookies do not need consent. Other cookies do, unless another PECR exception genuinely applies, which we will not invent.
Consent, when required, must be informed, specific, freely given and as easy to withdraw as to give. A wall that blocks the whole site until you accept marketing cookies is not how we work, because we are not trying to fund the page with adverts. A banner that is honest about what is essential and what is optional is the correct wrap.
4. Strictly necessary cookies and similar items
Strictly necessary items include a session token that keeps a form from being submitted twice by a confused retry, a security token that helps reject a forged request, a load-balancer stickiness cookie if the host uses one, and a record that you opened or closed the mobile menu so the page does not fight you. They also include items required to remember that you refused optional cookies, because remembering a refusal is part of honouring it.
Without some of these items the site may still render static pages, but the batch request label may fail, the drawer may misbehave, or a security control may refuse a post. That is a technical consequence, not a punishment. You can still email {MAIL} with no cookies at all.
We treat a first-party preference key that stores ‘optional cookies off’ as necessary to provide the choice you made. We do not treat a marketing identifier as necessary merely because a vendor’s slide deck said so.
5. Functional cookies
Functional cookies remember non-essential conveniences: for example, that a legal page was last opened in a wide layout, or that a user asked not to see a decorative animation. They are not required to deliver the core information. Where we use them we will say so in the table below as updated from time to time on this page, and we will not set them until you allow them if the law requires that permission.
We do not currently use functional cookies to store your name, your telephone number, or the content of a CCTV brief. The form, when submitted, sends those fields as a POST to our thanks page workflow and then into ordinary business email or ticketing. That is correspondence, not a cookie profile.
6. Analytics cookies
We may use a lightweight analytics measurement to learn which pages are read: home, services, portfolio, contact, legal. The purpose is to see whether the flavour batch map is doing its job. It is not to rebuild your working day. If analytics cookies are not strictly necessary, they stay off until you opt in.
When analytics run, we prefer IP truncation or another coarsening where the tool allows it, a short retention, and a prohibition on sharing the measurement with advertising networks. If a tool cannot be configured that way, we will not use that tool. A glossy site can survive without a dossier on every visitor from Caerphilly.
You may also use browser add-ons that send a do-not-track or global-privacy-control signal. Where we can honour a recognised signal as a refusal of optional analytics, we will. Essential items may still operate.
7. Embedded map and third parties
The contact page and the homepage preview may embed a Google Map centred on 22 William Street, Blackwood, Wales, NP12 1NW. Loading that iframe is a request to Google’s infrastructure. Google may process IP address, browser data and interaction with the map under its own terms and privacy notice. That processing is not ASHLAR TECHNOLOGIES LTD’s cookie jar.
Fonts may be requested from a font delivery network so that the display face and the body face render as designed. A font request can expose your IP address to that network. If you block third-party fonts, the site falls back to a system sans and a mono. The legal meaning of the pages does not change.
We do not embed social posts, does-not-play video walls, or live camera demos on the public site. Those would be the wrong flavour of embed for a brochure.
8. Duration
Session cookies expire when you close the browser or after a short idle period. Persistent cookies have a named lifetime. We keep lifetimes short. A year is already long for a brochure site. Multi-year advertising identifiers are not part of this wrap.
Local storage can outlive a cookie. If we use it, we will treat it with the same honesty: purpose, necessity, and a way to clear it by using your browser’s site-data controls. Clearing site data may reset a cookie refusal flag; you may need to choose again. That is the browser’s model, not a trick.
9. How you control cookies
Every widely used browser lets you block or delete cookies, and to do so per site. Look for site settings for {SITE}. You can also use private browsing windows. These controls are more powerful than any button we could paint, and they work even if our page failed to load a banner.
If you block all cookies, some strictly necessary features may stop. If you block only third-party cookies, the map embed is the main thing that may degrade. The rest of the flavour system is first-party HTML, CSS and JavaScript that we host.
Mobile operating systems have additional tracking permissions. Those permissions govern apps, not this website. Our CCTV applications, when we wrap them for a client, have their own privacy disclosures inside the product and the client’s notices. Do not mix those product notices with this public Cookie Policy.
10. Table of current first-party items
Because implementations change with hosting, we describe categories rather than pretending a frozen vendor ID will never move. Category A: session integrity on forms and security, duration session or up to 24 hours, first party, strictly necessary. Category B: storage of optional-cookie choice, duration up to 12 months, first party, strictly necessary to remember the choice. Category C: coarse analytics, duration up to 13 months, first party or a named analytics host, optional, off until allowed. Category D: none for advertising.
If we add a named analytics host we will update this paragraph with the host’s name, the transfer tool if data leaves the UK, and a link to that host’s notice. Until a name appears, assume Category C is unused or limited to a first-party log that never leaves our processor.
11. Personal data and cookies
A cookie identifier can be personal data if it can be linked to a person. We treat it that way. Our Privacy Policy describes rights of access, deletion, objection and complaint to the ICO. A request to delete cookie data is often best performed by you clearing the browser, because we may never have seen a durable identifier in the first place.
Do not send us a screenshot of unrelated cookies from other sites and ask us to delete those. We cannot reach into another company’s jar. We can only speak to {SITE} and to our own processors.
12. Changes and contact
We will update this Cookie Policy when our technologies change. The date below is the wrap date of this version. Continued browsing after a change, with a fresh optional consent where needed, is the mechanism the web uses. We will not hide a new advertising pixel in a comma.
Contact ASHLAR TECHNOLOGIES LTD at commercial@ashlartechnologies.ink, +44 7411 527577, 22 William Street, Blackwood, Wales, NP12 1NW. Website https://ashlartechnologies.ink. Last updated 17 August 2026.
If a future version of the site uses a consent management prompt, the prompt will point back here. The legal substance is this page, not the colour of a button. Sour apple green means a call to action in our design system. It does not mean a cookie is healthy. It means the wrap is visible.
13. Server logs that are not cookies
Even with cookies blocked, a server will usually see an IP address and a user-agent string. Those are not cookies. They are described in the Privacy Policy. We mention them here so nobody is told that a cookie-off browser is invisible. It is less labelled. It is not a ghost.
Content delivery networks may also see requests. They are processors or separate controllers depending on the setup. We will not pretend a global CDN is a biscuit baked in Blackwood. We will name the arrangement in a processing record.
14. Why we avoid advertising cookies
Advertising cookies would fight our own thesis. We tell clients that messy input should be shaped into a chosen bite, not sprayed. Spraying our visitors into an auction would be hypocrisy with a tracking ID. We fund this site as a cost of doing CCTV app development in the United Kingdom, not as a media property.
If a partner ever asked us to host their pixel in exchange for a lead, we would refuse. Leads arrive through {MAIL} and the batch request label. That is enough sweetness.
15. Children
The site is not aimed at children. We do not knowingly set optional cookies to profile a child. If you are a parent and you believe a child used the form, write to {MAIL}. We will delete the enquiry as the Privacy Policy says.
16. Do not mix product telemetry with this policy
Applications we build for clients may include telemetry: crash reports, performance timings, camera-health pings. Those are product features governed by the client’s notices, the app stores’ rules, and the contract. They are not authorised by this Cookie Policy. A guard using a wrapped security camera app is not a visitor to {SITE}.
If you are testing a demo build we gave you, ask for that demo’s notice. Do not assume the brochure site’s cookie story covers a testflight binary. Different belt, different label.
17. Security cookies
Some hosts set cookies to distinguish humans from bots, to throttle abuse, or to pin a TLS session. Those are security measures. They are strictly necessary to keep a public form from becoming an open hose. Disabling them may cause a loop of challenges. That is inconvenient. It is still better than an unmoderated flood of false batch requests.
18. International aspect of cookie technologies
A cookie itself is a file on your device. The personal data question is who reads it and from where. If an analytics host is outside the UK, the Privacy Policy’s transfer rules apply. We would rather keep measurement in the UK. If we cannot, we will wrap the transfer in a recognised tool or we will drop the measurement.
19. Your practical checklist
Read this page. Read the Privacy Policy. Decide whether to allow optional items if a prompt appears. Use browser blocking if you want a harder line. Email {MAIL} if you want a human. Do not paste footage into a cookie banner. A banner cannot ingest a clip. The form should not ingest one either.
If you are procuring software for a public body in Wales, your own cookie rules for your own estate are your problem to wrap. We can help you design a product that honours them. This page only wraps {SITE}.
20. Closing
ASHLAR TECHNOLOGIES LTD uses cookies like a wrapper seam: thin, named, and not allowed to melt into a hidden layer of syrup. That is the entire commercial bite of this policy. Last updated 17 August 2026. https://ashlartechnologies.ink. 22 William Street, Blackwood, Wales, NP12 1NW. commercial@ashlartechnologies.ink.
If this policy and a banner disagree because of a deployment lag, this policy wins until the banner is fixed. Report the lag to {MAIL} and we will set the batch again.
21. How a batch request interacts with cookies
When you submit the public form, the browser sends fields as a POST. That POST is not a cookie. It is correspondence. A security cookie may ride along to prove the post came from a page we issued. If that security cookie is blocked, the form may fail and you should use commercial@ashlartechnologies.ink instead. We will not ask you to lower every browser defence merely to say hello.
After a successful post you arrive at a confirmation page. That page does not need to remember your message in a cookie. The message has already left the browser. Clearing cookies later will not unsend the enquiry, which is the correct behaviour. Enquiries are not shopping carts.
22. Caching, service workers and ‘similar technologies’
We do not currently install a service worker to make this brochure behave like an app. If that changes, a service worker is a similar technology and will be described here before it is used for anything other than a strictly necessary performance wrap. A cache that stores public CSS is not a profile of you. A cache that stored a form body would be a mistake and would be treated as an incident.
ETags and other HTTP validators can sometimes act as identifiers. We do not tune them to track people across sessions. Hosting defaults may still emit ordinary validators. That is how the web avoids re-downloading a logo on every click.
23. Office networks and shared devices
If you read this site from a shared control-room PC, the next person may inherit cookies left in that profile. That is an Estate hygiene issue. Use a guest profile or clear site data if the machine is communal. We cannot remotely wipe a browser we do not own.
Some corporate proxies rewrite cookies. If your IT department intercepts HTTPS, they are a controller of that interception. Our policy cannot see inside their box. Ask them, then ask us if a page looks broken.