Privacy

Who handles privacy questions

The Echo Archives is operated as a Continental project.

For privacy, legal, or copyright requests, use the public contact route at contact.continental-hub.com. For factual archive corrections, the faster route is usually Submit or correct.

The current data categories

• Browsing and Ask the Archivist

  General page requests reach the site like any normal web request. Ask the Archivist sends the chat messages you submit to the same-origin chat API, and recent conversation history is also stored in browser session storage under echo-archives-chat-v3.

• Community ratings

  Show pages can create an anonymous rating profile using the HTTP-only voter cookie echo-community-voter plus the linked localStorage key echo-community-profile-id. Rating actions can also send the rating value and a Cloudflare Turnstile token when that protection is enabled.

• Submissions and contact details

  When you send a show submission, correction, listener review, or creator verification request, the server receives the request body you send. That can include titles, links, notes, review text, proof URLs, and any contact email you choose or are required to provide for that submission type.

• Technical and moderation data

  The site receives IP address and user-agent data with requests. Community rating flows use hashed abuse signals for rate limiting and bot defense, and submission records currently store source IP and user agent for moderation follow-up. The live public site can also send privacy-focused Plausible pageview events without cross-site advertising cookies.

Plain-language legal basis

• To run the archive features you asked to use

  The site needs to process page requests, chat prompts, and rating actions to deliver the archive, Ask the Archivist, and community rating features you actively use.

• To review and respond to submissions

  Submission content and any contact details are used because you asked the archive to review a correction, review, verification request, or new-show suggestion and it needs enough context to handle that request.

• To keep ratings and submissions safe from abuse

  Rate limits, hashed abuse signals, technical request data, and Turnstile checks are used to reduce spam, automated voting, and moderation abuse. That is part of the archive’s legitimate interest in keeping the system trustworthy.

• To follow up when you ask for it

  If you provide a contact email, the archive uses it to respond to your submission or legal request. You can stop that follow-up by asking for deletion of the contact detail where the archive no longer needs it.

How long data is kept

• Ask the Archivist session history

  Browser session storage lasts until the browser session ends or you clear site data. The public site does not provide saved account-based chat history.

• Community rating identifiers

  The voter cookie currently has a maximum lifetime of about 400 days after it is set. The linked local profile id stays in localStorage until you clear it. Backend rating records may be kept as long as needed to preserve rating state, summaries, moderation context, and audit history.

• Abuse-prevention signals

  Community rating abuse hashes are retained on a rolling window that defaults to 30 days in the current backend configuration.

• Submission records and contact details

  Submission content, moderation notes, contact email, source IP, and user agent are kept in the moderation database until the request is handled and may be retained longer where needed for archive history, audit, dispute handling, or follow-up.

• Maintainer session access

  The protected maintainer session cookie currently lasts up to 12 hours after sign-in unless it is cleared earlier by logout or browser controls.

See the cookies and browser storage page for the storage-by-storage list.

What you can ask for

Depending on the law that applies to you and the archive, you may be able to ask for access to the personal data held about you, correction of inaccurate data, deletion, restriction, objection to certain processing, or withdrawal of consent where processing depends on consent.

Where GDPR applies, the archive aims to respond to valid privacy-rights requests without undue delay and normally within one month of receipt.

• You can clear browser session storage, localStorage, and cookies through your own browser controls at any time.
• You can ask for a submission-related contact detail or moderation record to be corrected or deleted when it is no longer needed.
• If Swedish or EU data-protection law applies, you may also complain to the Swedish Authority for Privacy Protection, Integritetsskyddsmyndigheten (IMY).

Services outside the archive

Community rating requests may use Cloudflare Turnstile when that protection is enabled, which means the browser can contact Cloudflare for human-verification checks during rating actions.

The site also links out to official show sites, listening platforms, Patreon, GitHub, and the external Continental contact route. If you open those destinations, your browser connects to them directly and their own terms and privacy rules apply.

The live public site can use Plausible for privacy-focused pageview analytics. It does not use advertising trackers or cross-site marketing cookies. If additional processors such as newsletters or other named vendors are introduced later, this page should be updated to match the live behavior.