1. What this policy covers
This cookie policy explains how STARLIGHT PORTER LTD uses cookies and similar storage on https://starlightporter.wiki. It should be read with the privacy policy. The company is established at 911 Green Lanes, London, United Kingdom, N21 2QP. Questions: tech@starlightporter.wiki or +44 7411 527869.
Cookies are small files stored on a device. Similar technologies include local storage, session storage, pixels and scripts that recognise a returning browser. This policy uses “cookies” to cover that family unless a distinction matters legally.
2. Why the yard uses cookies
Strictly necessary cookies keep the public site readable, remember a cookie banner choice, protect forms from crude automated abuse, and load assets. They are not used to build an advertising profile. Functional cookies, if enabled, remember a preference such as reduced motion. Analytics cookies, if enabled after a choice, help us see which fraction pages are actually read so we can screen wasted content.
We do not operate a retail storefront and we do not run third-party advertising networks on this domain as a default commercial model. If that ever changes, this policy will be updated before any advertising cookie is set.
3. Legal bases
United Kingdom law, including the Privacy and Electronic Communications Regulations and UK GDPR, requires consent for non-essential cookies. Strictly necessary cookies rely on legitimate interests in delivering a service requested by the visitor, namely loading the page that was typed or tapped. Consent is not buried in this long document. Where a banner or comparable control is presented, the choice is recorded.
Continuing to scroll is not treated as consent. Closing a banner without a choice is not treated as consent for analytics. A refusal leaves the strictly necessary layer in place so the legal pages and intake ticket still work.
4. Cookie inventory
A strictly necessary cookie may record that a cookie preference was set, with a typical lifetime of six to twelve months. A session cookie may keep a form from losing its place if the stack requires it; the current intake form is validated in the browser and then routed to a confirmation page, so a durable identity cookie is not required for that path.
If a content delivery or font provider sets a cookie, it is identified in the banner when that provider is active. Map embeds from Google Maps on the contact page may set cookies from Google when the iframe loads. That embed is offered because the address {ADDR} must be locatable. A visitor who does not want map cookies should not load the contact map iframe; the address is also printed as plain text.
Analytics cookies, when consented, typically last between twenty-four hours and twenty-four months depending on the tool. They collect approximate location, device class, and path. They are not used to sell a list of visitors.
5. Google Maps and third-party frames
The contact page includes a Google Maps iframe whose query matches 911 Green Lanes, London, United Kingdom, N21 2QP. Google may process device data under Google’s own terms. That processing is not a sale of data by us. If you wish to avoid Google cookies, use the printed address and a map tool of your choice instead of the embed.
6. Fonts and assets
Typography may be delivered from a font network. That network may see the IP address that requested the font file. This is a common web pattern, not a hidden advertising exchange. A visitor using a browser that blocks third-party requests will still receive the local layout, with fallback system fonts if the network file never arrives.
7. How to control cookies
Browser settings can block or delete cookies. Blocking all cookies may break the preference record so the banner reappears. Device-level tracking controls on mobile operating systems should be respected by any SDK we later ship inside an intelligent mobile application; those applications are not this website and carry their own notices when distributed.
To withdraw analytics consent, use the same control that granted it or write to the published email asking us to stop analytics association with your device. We will not be able to identify a device from an email alone if no identifier was ever stored.
8. Duration and refresh
Consent is refreshed when the purpose changes, when the cookie set changes in a material way, or when the recorded consent expires. A new analytics vendor is a material change. A patch to a strictly necessary security cookie is not.
9. Do not track and global privacy controls
Where a widely adopted browser signal indicates a wish to opt out of sale or share of personal information, we honour it for this site by not enabling advertising cookies, which we do not use as a default in any event. We do not currently sell personal information.
10. Children
The site is not directed at children. We do not configure cookies to profile children. Parents who believe a child submitted the intake form should write to the published email so the ticket can be deleted.
11. Changes
This policy was last updated on 18 August 2026. Material changes will be published on this page. The privacy policy, terms of service and terms and conditions remain available through the yard directory.
12. Detailed commentary on similar technologies
Local storage can hold larger strings than a classic cookie. We do not use local storage to fingerprint a visitor across unrelated sites. Session storage clears when the tab closes and may be used only if a future interactive grade tool needs a scratch pad.
Pixels are tiny requests that can record that an email was opened. Transactional mail about a live contract may use a delivery log. Marketing mail, if sent, includes an unsubscribe path and is not the default result of submitting an intake ticket.
Fingerprinting through canvas, audio or font enumeration is not part of the public site design. If a security provider later uses limited device signals to stop abuse of the form, that use will be necessary for security and described here.
13. Processor list for cookie-related vendors
Possible categories include hosting, DNS, content delivery, font delivery, mapping, and consented analytics. Named vendors change. A current list can be requested from tech@starlightporter.wiki. Each vendor is reviewed for location, subprocessor chain, and deletion.
14. Contact
STARLIGHT PORTER LTD, 911 Green Lanes, London, United Kingdom, N21 2QP. tech@starlightporter.wiki. +44 7411 527869. Website https://starlightporter.wiki.
This cookie policy does not authorise placing cookies on a client’s own users inside software we build. Those cookies, if any, are specified in the product design and in the client’s notices.
15. Browser-level controls in more detail
On common desktop browsers you can block third-party cookies, delete existing cookies, and in some cases send extra privacy signals. Blocking all cookies may prevent the site from remembering that you already refused analytics, so a banner may reappear. That repetition is an inconvenience, not a new consent. Mobile browsers have similar settings under privacy menus. If you use a private window, cookies often die when the window closes. That is a good way to visit legal pages without leaving a durable identifier, with the trade-off that any preference record will not persist.
Enterprise devices may enforce cookie policies through management software. If your employer blocks Google domains, the map iframe on contact.html may fail while the rest of the yard still loads. That is expected. The address 911 Green Lanes, London, United Kingdom, N21 2QP remains printed as text so you are not forced to accept a map cookie to know where the company is.
16. What we store if you refuse non-essential cookies
We still need to deliver HTML, CSS, JavaScript, images, and a favicon. Those requests produce ordinary server logs. A strictly necessary preference cookie may record that you refused, so we do not keep asking in a loop during the same period. Form fields you type exist in your browser until you submit or leave. After a successful submit, the confirmation page does not need to remember your message. We do not rebuild a marketing profile from a refusal. Refusal is not recorded as a character judgement; it is a legal choice.
17. Analytics, if switched on after a choice
If we enable an analytics tool, it will run only after a positive choice. It may record approximate city, device class, landing page, and whether a legal page was opened. It will not be used to decide whether to offer you a job or a contract. IP addresses, if collected by the tool, should be truncated where the tool allows. We will not merge analytics identifiers with intake tickets as a default join. If a vendor changes its cookie behaviour, we treat that as a material change and seek consent again if the purpose widened.
Heatmaps, session replays, and keylogging-style recordings are not part of this site’s design. If that ever changed, it would require a very clear consent because message fields on the intake ticket could otherwise be captured. We do not want that risk and we do not want that theatre.
18. Local storage, session storage and service workers
The current yard front end does not rely on a service worker to run offline. If a service worker is added later to speed repeat visits, this policy will say so, because a service worker can cache pages on the device. Session storage might be used in a future interactive grade calculator; it would clear with the tab. Local storage would only hold a preference or a draft if we built that feature and explained it. We will not use local storage as a hidden super-cookie to stitch visits across sites we do not control, which we could not do lawfully in any event without a surprising identifier scheme.
19. Fonts, images and cache
Images of crushed stone, belts, tickets and desks are loaded from this domain’s asset path. Your browser cache may keep them so the next page is lighter. Caching is a performance behaviour, not a marketing profile. Fonts requested from a font network cause a request that includes your IP and the referrer. If you block that network, fallback fonts still keep the legal text readable, which is the priority on these pages. We accept that the visual universe is slightly less stamped if fonts fail, provided the words remain clear.
20. Embedded maps as a cookie source
Google Maps is embedded with a query that matches 911 Green Lanes, London, United Kingdom, N21 2QP. Loading that iframe is a decision to talk to Google’s servers. Google may set cookies and process location data under its terms. We include the embed because the technical brief requires a map that matches the address exactly. If you want zero map cookies, do not load that iframe; print the address; use a map you already trust. We will not hide the embed behind a fake button that still loads Google in the background.
21. Duration table in sentences
A session cookie dies when the browser session ends, subject to the browser’s own restore behaviour. A preference cookie of six to twelve months is typical for remembering a consent or refusal. An analytics cookie of up to twenty-four months is typical in the industry if analytics is on; we prefer the shorter end if we use analytics at all. Server logs of ninety days are not cookies but they are similar in spirit: they fade unless an investigation holds them. Invoice records are not cookies. Recruitment files are not cookies. Do not confuse a legal retention period for contracts with a cookie lifetime on this domain.
22. Children, pupils and schools
This corporate site is not a children’s service. We do not configure cookies to track pupils. If a school later becomes a client of an intelligent mobile application, that application will carry its own notice. A child who submits the public form should have that ticket deleted when a parent or guardian writes to tech@starlightporter.wiki. We will not knowingly use a child’s device identifier for analytics.
23. Changes, contact and relationship to other notices
This cookie policy can change when vendors change. The date on the page is the version date. Read it with the privacy policy, which explains lawful bases and rights, and with the terms of service, which explain acceptable use of the site. Commercial processing inside a paid load is not controlled by a website cookie; it is controlled by the contract and the privacy allocation. Questions: STARLIGHT PORTER LTD, 911 Green Lanes, London, United Kingdom, N21 2QP, tech@starlightporter.wiki, +44 7411 527869.
If you remember only one operational fact, remember this: refusing non-essential cookies still lets you read the method, the fractions, the outputs and the legal bins, and still lets you send a load ticket. The yard is not a retail checkout that withholds the product until you accept advertising. Heavy clarity includes leaving the belt usable when the dust of tracking is screened out.
24. First-party versus third-party cookies
A first-party cookie is set by starlightporter.wiki. A third-party cookie is set by another domain, such as a map or font host. We prefer first-party storage for any preference we control. Third-party cookies appear only when a page actually calls that third party. Legal pages that do not include a map iframe should not need Google cookies. The homepage does not include a live advertising exchange. If your browser’s privacy report shows unexpected third parties, it may be an extension on your device rather than our page; we cannot control extensions.
We will not disguise a third-party cookie as a first-party cookie by reverse-proxying an advertising identifier through this domain. That technique is used by some commercial stacks to evade browser rules. It is incompatible with the yard’s method. If a future tool requires it, we will not adopt that tool.
25. Cookies in emails and in software we later build
Transactional email about a live contract may include a delivery log at the mail provider. That is not a website cookie, but it is similar tracking of whether a message moved. Marketing email, if you asked for it, will include an unsubscribe path. Applications we build for clients may set their own cookies on the client’s domain; those are described in the client’s notices, not here. This policy is only for https://starlightporter.wiki and for embeds it loads.
26. Record of this policy’s purpose
United Kingdom visitors are entitled to know what is stored on their device and why. This long form exists so that a person who cares can read the actual pattern: necessary delivery, optional analytics only with a choice, a map that is honest about Google, fonts that may phone a network, and no advertising pile hidden in the dust. If you wanted a three-line cookie policy, you still received the usable fraction: refuse non-essential cookies and the yard remains readable. The rest is the weighbridge ticket for people who audit these things professionally. STARLIGHT PORTER LTD, 911 Green Lanes, London, N21 2QP, tech@starlightporter.wiki, +44 7411 527869.