Cookie notice

This cookie notice describes how wordnest.pro uses cookies and similar storage. Read it alongside the privacy notice at /privacy.php. I keep the language direct because cookie banners are annoying enough without extra fog.

What cookies are. Cookies are small text files a site places on your device through your browser. Local storage is a related browser feature that can hold a little data without expiring as quickly. Word Nest uses both sparingly and only for purposes listed here.

Strictly necessary. The consent cookie wn_consent records whether you accepted, rejected, or customised categories. It is first-party — set by wordnest.pro, not by advertisers. It exists so the banner does not reappear on every page once you decide. This category is always active because without it the consent system cannot remember your choice.

Preferences. If you enable Preferences in the customise panel, the site may remember small display choices — for example, whether you prefer the map placeholder collapsed a certain way. These are not used to track you across other websites. If you leave Preferences off, defaults apply.

Embedded content. Google Maps iframes on every content page load only when you accept Embedded content. Until then, a styled placeholder with a "Show the map" button appears. Accepting this category may allow Google to set its own cookies or process data under Google's policies. I do not receive that data directly.

What I do not use. No analytics cookies. No advertising cookies. No social media pixels. No A/B testing frameworks. No heatmaps. Word Nest is a reading site, not a surveillance product.

Cookie table (summary). Name: wn_consent. Purpose: store consent choice. Duration: up to twelve months unless cleared. Provider: wordnest.pro (first party). Category: strictly necessary once you interact with the banner.

Local storage keys. The main script may mirror consent JSON in localStorage under the same logical name for faster reads on repeat page loads within a session. Clearing cookies but not storage could desynchronise until you choose again — clearing both restores a first-visit state.

How to change your mind. Use "Cookie settings" in the footer on any page. The panel reopens with your current choices visible. Save to update. You may also clear cookies through your browser settings; the banner will return on your next visit so you can choose again.

Browser controls. Most browsers let you block third-party cookies, delete stored data, or browse in private modes. Blocking all cookies may prevent the consent system from remembering your choice — the banner may keep returning, which is inconvenient but safe.

JavaScript disabled. The site remains readable without JavaScript. The banner may not appear; maps stay as placeholders unless you enable scripts. Consent storage depends on JavaScript for the full experience described above.

Interaction with maps. Rejecting embedded content means the iframe never loads and Google should not receive map requests from your browser on my pages. Accepting loads the iframe from maps.google.com with the neighbourhood query defined in my template. You can accept once and later reject via settings if you change your mind.

Third-party cookies from Google. If you accept maps, Google may set its own cookies or use similar technologies. I do not control that behaviour. Consult Google's documentation if you need detail beyond what a personal blogger can reasonably maintain.

Consent records. I do not maintain a server-side database of your choices. The record lives on your device until you clear it or until it expires. That keeps the blog small and avoids collecting visitor identifiers I do not need.

Children. The banner language is written for adults managing their own browser. Parents should supervise minors' choices about embedded maps on any site, including this one.

Updates. If I add a category — unlikely — I will update this notice and ask for consent again before activating it. No silent expansion.

Testing your choice. After saving, reload any page: the banner should stay hidden if you accepted or rejected decisively. Open Cookie settings from the footer: toggles should reflect saved state, not factory defaults. If they do not, try clearing site data once and choosing again — browsers occasionally cache aggressively.

Contact. Questions about cookies: [email protected]. I will answer in plain language.

Last updated: 8 August 2026.