Cookies
What does this site actually store?
Lorikeet Lanes keeps its website simple: two small entries saved in a visitor's browser, and nothing tracking beyond that.
The approach
Why so little gets stored at all
This website doesn't run advertising campaigns, so there's little reason to track a visitor beyond the two checks it actually needs: an age confirmation, and a record that the cookie notice has been seen.
Both live in the browser's own storage rather than travelling back to any server, and neither carries a name or any personal detail.
What's stored
Two small entries, that's all
- The entry age18au40 saves an age confirmation once given, so the question doesn't pop up again on every page opened afterwards.
- The entry ckau40 saves the fact that this notice has already been seen, so the banner along the bottom doesn't keep reappearing.
- Neither one identifies a visitor by name, and neither is passed on to an advertiser.
What isn't stored
No other trackers, and how to clear these two
- There's no ad network plugged into this site, no third-party platform pixel, and nothing quietly logging visits for marketing elsewhere.
- Clearing the site's data through browser settings removes both entries at once — the age check will simply ask again next time.
- Nothing breaks by clearing them; the cookie banner and the age gate just reappear on the next visit.