Cookie notice
I use one small cookie to remember whether you want embedded maps to load. Nothing here is hidden behind jargon — this page explains exactly what happens when you accept, reject, or customise.
What cookies are
A cookie is a small text file your browser stores when a site asks it to remember something. On Note Nest, that "something" is your map preference — not a shopping basket, not a login session, and not an advertising profile.
I also mirror the same preference in local storage under the key cookie_consent_v1 so the site can read your choice quickly on the next page. The cookie and the local storage entry stay in sync whenever you accept, reject, or save custom choices.
The cookie name is sg_blog_consent. Its value is JSON, URL-encoded, containing which categories you allowed, a timestamp, and a version number. You can inspect it yourself in your browser's developer tools if you are curious — there are no secrets inside, only booleans and a date.
Three categories — only one does real work here
Essential
Essential storage remembers that you have made a cookie choice at all. Without it, the banner would return on every page load and you would never get a stable reading experience. This category is always on and cannot be switched off in the panel — not because I want to trap you, but because the alternative is a banner that never learns.
Essential does not mean "load everything." It means "remember what you decided." The essential flag in the stored JSON is always true when any choice has been saved.
Functional / embedded content
This category controls Google Maps iframes. Every page on Note Nest includes a neighbourhood map or a placeholder waiting for your permission. If functional cookies are off, you see a quiet box that says the map is hidden until you allow embedded content, with a button to load the map for that session by granting functional consent.
Functional is the only category that changes what you see on the page beyond the banner itself. Essential keeps the banner away; functional decides whether Google's iframe appears.
Analytics
Analytics is listed for honesty and future-proofing. I do not run Google Analytics, Matomo, Plausible, or any other analytics script on this site. The toggle defaults to off and nothing breaks if it stays off. If I ever add analytics — which I do not plan to — this page would be updated first.
Google Maps — what happens under Accept and Reject
Each map uses Google's standard embed URL inside an iframe. I do not use the Maps JavaScript API, and I do not pay for a Maps Platform billing account on this personal blog. When the iframe loads, Google may receive technical data such as your IP address and browser details under Google's own privacy policy — not mine.
If you click Accept all, functional consent is set to true, the banner hides, and maps load normally on every page. The choice persists for about six months across reloads and new pages in the same browser.
If you click Reject all, functional consent stays false. Maps do not load automatically. Instead, you see a styled placeholder with a "Load map" button. Clicking that button grants functional consent for the current choice and loads the map — the same mechanism as accepting functional cookies in the customise panel.
If you customise, you can flip functional on or off independently, save, and the banner will respect exactly what you picked. Re-open the panel anytime via the control below or through the banner's Customise button if it reappears after six months.
All maps are centred on the Marine Parade / Katong neighbourhood at a wide zoom. The pin is approximate — close enough to orient you to the east-coast corridor, not precise enough to identify a single flat.
How long choices are stored
Your consent record is stored in a cookie named sg_blog_consent with a maximum age of 180 days — about six months. The value is JSON containing which categories are on, a timestamp, and a version number so the site can ignore outdated formats.
After six months, the cookie expires and the banner may appear again so you can confirm or change your preference. I do not claim the choice lasts forever, and I do not silently renew it without your interaction.
The same record is mirrored in local storage for faster reads on repeat visits. Clearing cookies but not local storage may briefly show inconsistent behaviour until you make a fresh choice; clearing both resets everything cleanly.
Manage your choices now
If you already decided once and want to change your mind, use the button below. It re-opens the same panel as the banner's Customise option, with your saved toggles reflected accurately.
You can also clear site data through your browser settings. Clearing cookies removes the saved preference and the banner will return on your next visit as if it were your first.
The panel uses button toggles with aria-pressed states — not hidden form inputs — so the source stays free of form elements while remaining keyboard-operable. Essential stays locked on; functional and analytics move when you click their switches.
Clearing cookies in your browser
Every modern browser lets you delete cookies per site or globally. In Chrome, open Settings → Privacy and security → Delete browsing data, choose Cookies and site data, and limit the range to notevaultnest.life if you only want to reset this blog. Safari, Firefox, and Edge offer equivalent controls under their privacy menus.
Clearing cookies here does not clear Google's separate cookies if a map iframe had already loaded before you cleared — you may need to clear third-party data or use a fresh private window to see the placeholder state again.
Private browsing modes still show the banner on first visit because no prior consent exists in that session's isolated storage. That is expected behaviour, not a bug.
Questions
For broader privacy context — server logs, email, PDPA rights — read the Privacy notice. For cookie-specific questions, email [email protected]. Last updated: 11 August 2026.