1. What are cookies?
Cookies are small browser files used to remember or measure something.
Cookies are small text files stored in a browser when someone visits a website. Some are essential for a site to work; others measure performance, remember preferences, or — on some websites — support advertising.
Lightly Coded keeps the list short on purpose and describes only the cookies and browser storage the site actually uses.
2. How Lightly Coded uses cookies
Cookies support consent, preferences, and optional analytics.
- Necessary: required for site function and consent storage.
- Analytics: anonymous usage insight, set only after consent.
- Marketing: not currently used by this site.
3. Necessary cookies
The consent system needs one essential cookie to remember choices.
| Cookie | Purpose | Duration | Type |
|---|
lightlycoded_consent | Stores your cookie consent preferences. | 1 year | 1st party |
4. Analytics cookies
Google Analytics cookies are only set when you consent.
Analytics help us understand how visitors interact with the site. These cookies only run after consent through the banner or the Cookie Preferences modal.
| Cookie | Purpose | Duration | Type |
|---|
_ga | Google Analytics — distinguishes unique users. | 2 years | 3rd party |
_ga_* | Google Analytics — maintains session state. | 2 years | 3rd party |
_gid | Google Analytics — distinguishes users. | 24 hours | 3rd party |
_gat | Google Analytics — throttles the request rate. | 1 minute | 3rd party |
Vercel Analytics is listed for transparency because it measures page views and Core Web Vitals, but it's cookieless and doesn't appear in the cookie table.
5. Marketing cookies
No advertising or retargeting cookies are currently used.
Lightly Coded doesn't currently set marketing or advertising cookies. There's no retargeting pixel, no social-media tracking pixel, and no third-party advertising network embedded on the site.
The Marketing toggle exists for forward compatibility. If marketing tooling is added later, the existing preference will be respected.
6. Lead attribution
One stored ID connects an enquiry to the page that prompted it.
When you send a message, request an audit by email, or create an account, we record which page you arrived on and which pages you read before doing it. That is the whole purpose: it lets us tell a client “this article produced this job” instead of guessing.
This is not a cookie and it is not Google. It is our own software, on our own domain. It stores one randomly generated ID in your browser, sends nothing to a third party, never reads what you type into a form, and identifies nothing about you — the ID is a random string with no meaning anywhere else. Because it sets no cookies it is not covered by the banner above; it is listed here instead so it is disclosed by name rather than buried in a toggle.
| Stored item | Purpose | Duration | Type |
|---|
fa_session | A random ID connecting your visit to an enquiry you send. | 30 minutes of inactivity | 1st party (localStorage) |
Recorded alongside it: the page you arrived on, the pages you view, the site that referred you, any campaign tags in the link, whether you are on a phone or a desktop, and whether a phone number on the page was tapped. Your IP address is kept for spam correlation and deleted automatically after 90 days.
To clear it, clear this site's data in your browser, or browse in a private window. Enquiries and audits work exactly the same either way — an enquiry we cannot connect to a page is simply recorded as unattributed.
7. Third-party services
Only a small number of services are listed.
- Google Analytics: anonymous traffic analysis, only when consented.
- Vercel Analytics: cookieless page-view and performance measurement.
- Vercel hosting: serves the site and may log basic request metadata.
8. Updates to this notice
The notice changes when the cookie setup changes.
If our cookie use changes, this Cookie Notice will be updated and the date at the top moved forward — especially if marketing tools, ad pixels, or new third-party scripts are added later.