No ad-tech layer
The current public deployment does not load Plausible analytics. It does not use advertising cookies or cross-site marketing trackers.
Cookies and browser storage
The site currently relies on browser storage more than marketing-style cookies. This page lists the current storage items and related server-side identifiers used by the live repo.
Browser-scoped memory
the show-page rating widget uses publicly anonymous, pseudonymous browser identifiers.
Maintainer-only auth
Protected moderation routes can set a short-lived session cookie, but public browsing does not require a login.
What this page covers
The legal operator and data controller is Charlie Arnerstål. The Echo Archives is a Continental project, not a separate legal entity, and the controller is established in Sweden. Privacy questions can be sent to [email protected].
This page covers first-party cookies, sessionStorage, localStorage, and the small number of related server-side identifiers that matter for the current community-rating flow. For broader personal-data handling, see Privacy.
Current storage list
| Name or key | Type | Purpose | Duration | When it is set |
|---|---|---|---|---|
echo-scroll:… |
sessionStorage |
Remembers the current page’s scroll position so returning from a show or collection restores the browse position. | Until the browser session ends or site data is cleared. | While you scroll a page; the suffix identifies the route and active query or filter state. |
echo-community-profile-id |
localStorage |
Stores the linked publicly anonymous, pseudonymous community profile id used by the frontend to fetch and update your rating state. | Until you clear site data or remove it manually. | After you submit or clear a community rating or mark a listener review helpful; passive show-page browsing does not create a profile. |
echo-community-voter |
HTTP-only cookie | Stores a pseudonymous device token used by the server to keep one device tied to one community-rating profile without a public account. | Up to about 400 days after it is set, unless the browser clears it first. | After you submit or clear a community rating or mark a listener review helpful and the server needs a voter token; passive show-page browsing does not set it. |
cf_clearance |
Cloudflare security cookie | Stores proof that Cloudflare’s browser or challenge checks were passed so the visitor is not repeatedly challenged. | For the zone’s configured Challenge Passage period and any security-driven refresh. The exact production-zone setting is not visible from an ordinary public response. | Cloudflare may set or refresh it when its challenge or JavaScript-detection protections evaluate a visit. |
echo-maintainer-reviewed-by |
localStorage |
Remembers the maintainer’s “Reviewed by” value inside the protected submission queue UI. | Until it is cleared or overwritten. | When a maintainer saves or reuses a reviewer name in the protected moderation tools. |
echo-maintainer-session |
HTTP-only cookie | Keeps a maintainer signed in to the protected moderation routes. | Up to about 12 hours after sign-in, or until logout/clear. | After a successful maintainer sign-in. |
community-rating abuse hash |
Server-side abuse signal | Stores a hashed abuse-prevention signal used for rate limiting and community-rating moderation. | Rolling 30-day cleanup by default; an active rating’s stored hash is redacted after 30 days without a rating update. | When a community rating is submitted or removed, or a listener review is marked helpful or unmarked. |
What kind of storage this is
The current storage items are functional or security-related. They support chat and scroll continuity, publicly anonymous ratings, Cloudflare challenge protection, and maintainer authentication.
The current public deployment does not load Plausible analytics and does not use optional advertising cookies, analytics cookies, or cross-site marketing cookies. No separate preference-cookie layer is implemented today.
We use Cloudflare Real User Monitoring (RUM) to collect anonymous website performance metrics, such as page loading and responsiveness information. Cloudflare RUM does not use cookies or local storage to track visitors and is not used to identify individual users.
What happens on show pages
Opening a show page reads the public rating summary and can read an existing rating profile, but it does not create a profile or set the archive’s voter cookie. The publicly anonymous, pseudonymous rating identifiers are created only when you submit or clear a score or mark a listener review helpful.
In practical terms, the rating system currently uses both the HTTP-only voter cookie and the linked local profile id. The cookie is not readable from frontend JavaScript, while the local profile id is used by the browser-side rating UI.
How to clear or limit storage
- Clearing site data in your browser removes session storage, localStorage, and first-party cookies for the archive.
- Blocking the archive’s cookies can interfere with publicly anonymous community rating behavior.
- Logging out of protected maintainer routes clears the maintainer session cookie.
What happens if storage changes later
If optional analytics cookies, advertising cookies, or preference cookies are introduced later, this page should be updated with the purpose, duration, and whether that storage is essential or optional. The privacy page should be updated at the same time.
The current implementation does not add a cookie banner because the public deployment does not use optional analytics, advertising, or marketing cookies. If that changes, this page and the consent flow must be updated before the change is deployed.