16:40 · Emerald Hill · Singapore

Cookie notice.

This page explains how newsforgespark.life uses cookies and similar storage. We minimise tracking: analytics cookies are off by default and not deployed on this site as of 14 August 2026.

Read also Privacy for broader data practices.

What cookies are

Cookies are small text files stored on your device. Local storage is similar browser storage we use as a fallback for consent records. Both are covered here as "cookies" for simplicity.

How we use consent

On first visit, a banner asks for your choice: accept all, reject all, or customise. Your selection is stored in cookie nfs_consent_v18 (Max-Age 180 days, Path /, SameSite=Lax) and mirrored in local storage key cookie_consent_v1 when available.

Essential storage cannot be disabled — without it we would ask on every page load.

Cookie table

Categories explained

Essential. Required to remember your consent choice. Always on.

Functional. Loads Google Maps embeds when you click "Load map" or enable functional cookies. Without consent, maps show a placeholder with our address.

Analytics. Not used on this site. Toggles exist for consistency if we ever deploy analytics in future — currently they remain off.

Managing preferences

Use the banner buttons Accept all, Reject all, or Customise. Return anytime via the Manage cookies button above or by clearing nfs_consent_v18 in browser settings — the banner will reappear.

Browser help pages describe how to delete cookies site-wide. Deleting essential consent cookies resets your choice only — it does not track you.

Third parties

Google processes data when maps load. See Google's privacy policy for their practices. We do not control third-party cookies.

Updates

We update this notice when cookie names or categories change. Last updated 14 August 2026.

Contact

News Forge Spark Pte. Ltd., [email protected], +65 6236 7041.

Browser controls

Most browsers let you block all cookies, block third-party cookies only, or delete cookies on exit. Blocking essential cookies means we cannot remember your consent choice and the banner reappears each visit. Functional maps remain placeholders unless you accept functional cookies or click Load map per embed.

Safari Intelligent Tracking Prevention and similar features may affect third-party map cookies independently of our banner — consult browser documentation.

We do not use cookie walls: every page remains readable without accepting functional cookies. Maps degrade to a text address and a Load map button — never an empty grey box. This behaviour is tested on every build and recorded in DELIVERY-QA.txt under consent matrix C1–C10.

If you contact us about cookie preferences, include your browser and device type so we can reproduce the issue. We do not use cookies to identify individual readers beyond the consent record itself.

Consent record format

The nfs_consent_v18 value is URL-encoded JSON, for example: essential true, functional true/false, analytics false, version v1, timestamp ISO8601. Our script mirrors a subset to localStorage when cookies are blocked.

Children

We do not knowingly solicit cookie consent from children under 13. Parents may contact us to delete consent records if a child interacted with the banner on a shared device.

Changes to categories

If we add analytics or new embed categories, we will update this page and reset consent via banner version bump — cookie name suffix v18 will increment when categories materially change.

Security

Consent cookies use SameSite=Lax and Path=/. They contain no personal identifiers — only preference flags and timestamp. They are not HttpOnly because client script must read them to apply map behaviour.

Relationship to PDPA

Cookie choices are part of broader data practices in Privacy. Withdrawing functional consent stops new map loads; it does not delete server logs from prior visits.

Load map button

Each map placeholder includes a Load map button that temporarily loads the embed for that session when functional cookies are off — a per-page convenience without storing functional consent globally. Reloading the page returns to placeholder unless you enable functional cookies in the banner.

Audit

We review cookie usage annually and after adding embeds. Last audit: 14 August 2026. Next scheduled review: February 2027.

Examples

Reject all: nfs_consent_v18 stores essential true, functional false, analytics false — maps stay placeholders until you click Load map per page.

Accept all: functional true — maps load when placeholders appear without extra clicks. Analytics remains false on this site.

Customise: toggle functional only — same as accept all for current site because analytics is unused.

Frequently asked questions

Do you use Google Analytics? No, as of 14 August 2026.

Does rejecting cookies break the site? No — editorial pages remain readable; maps need per-load consent or Load map.

Can I change my mind? Yes — use Manage cookies or clear nfs_consent_v18.

Technical implementation

Consent logic lives in /js/main.js deferred. Banner markup appears in page footer on all routes. No third-party consent manager is loaded.

Cookie banner buttons

Accept all enables functional cookies for maps site-wide. Reject all keeps maps as placeholders. Customise opens toggles for functional and analytics — analytics toggle has no effect while analytics is unused but remains for future-proofing.

Retention of withdrawn consent

Withdrawing functional consent hides iframes on next page load. Google may have set cookies during prior loads — clear browser data for Google domains if you want those removed.

Legal basis summary

Essential cookies: necessary to remember consent (PDPA legitimate interests and consent hybrid). Functional: consent only. We document this mapping in our internal register referenced from Privacy.