Cookies and localStorage are different
Cookies are small values a browser can send with requests to a website. LocalStorage is browser-held data that website scripts can read for the same origin; it is not automatically attached to every request. Both deserve clear explanation when used.
The supplied site scripts do not set cookies, load analytics, activate advertising trackers or embed third-party media. Serving infrastructure may have its own technical behaviour, which is not determined by these static files. This page describes the storage implemented by the journal's own supplied code.
The optional preference
If you choose Save Essential-Only Preference, the site writes essential-only to the localStorage key fjordtalesbriz-privacy-preference. Its sole purpose is to remember that choice in this browser. It contains no name, email, message or advertising identifier.
The value has no built-in expiry and remains until you clear it, clear site data or use a browser mode that removes it. It does not follow you to another browser or device. The site does not activate optional tracking whether you save a preference or leave storage empty.
Checking browser storage…
What is not stored
The navigation menu and scroll animations do not save a browsing profile. The contact composer does not put your draft in cookies or localStorage. Copying a draft uses your device clipboard; downloading creates a local file. Those copies are separate from the preference described here.
Managing your browser
You can clear site data, block storage or use private browsing through your browser settings. Blocking this optional preference does not prevent reading the journal. Some browser settings, extensions or private modes may make storage unavailable; the site then continues without saving the preference.
Removing the preference does not delete downloaded files, clipboard contents, email or infrastructure logs. Read Privacy Information for the distinctions between these activities.
Questions and future changes
If the site introduces optional analytics, embedded services or other storage, those features should be assessed and this notice updated before their use. For questions about the behaviour described here, contact [email protected].