Episode Atlas
Privacy Notice
How Episode Atlas handles your data
This page is a maintainer draft describing how the product works today. It is not legal advice. If you need formal counsel for your situation, consult a qualified professional.
Data we collect
- Browsing (guests): You can browse episode guides, collections, and many public pages without signing in.
- Account identity: When you sign in via Azure Static Web Apps (for example Google, Microsoft, or GitHub), we receive the identity the provider shares with the app (typically a stable user id and display name; sometimes an email address).
- Watch history and lists: Episodes you mark watched, ratings/notes you choose to save, Watch Next queue items, and related captain’s-log data tied to your account.
- Public profile: Optional public handle, watch progress summaries, visit-streak / commendation displays, and community features you publish (for example public Top 5 lists).
- Preferences: Settings such as email preferences and browser-local choices (for example Do Not Track).
- Operations / security: Authenticated activity useful for audit and abuse prevention (for example sign-in related events), plus technical logs needed to run the service.
Why we use it
- Provide episode discovery, tracking, profiles, and community features you request.
- Remember preferences and improve reliability, performance, and security of the site.
- Send optional re-engagement email only when you opt in and provide a usable address.
- Understand aggregate product usage (see analytics below).
Public profiles
Public mission profiles and similar community surfaces are designed to show progress you share with others. Do not put information in public profile fields that you are not comfortable appearing on the open web. Private episode notes and personal ratings remain account-scoped and are not offered as a public feed.
Analytics, cookies, and Do Not Track
On production hosts we may use lightweight analytics (including Lite Analytics page and custom events) and first-party funnel telemetry to understand how the product is used. These paths are built to avoid dumping raw search text or other unnecessary PII into marketing dashboards.
You can exclude your browser from client-side analytics via
Tracking preferences, which stores a local flag
(lta_do_not_track). When enabled, client funnel posts and Lite Analytics custom events are skipped
for that browser. Visit streaks and core account features do not require analytics consent.
Email preferences
Re-engagement email is opt-in. Manage address and toggles on Email preferences when signed in. Campaigns may include streak-at-risk and inactive-account reminders. One-click unsubscribe links are included in those emails when sent. We do not auto-enable email without an explicit choice from you.
Retention, deletion, and contact
We keep account and operational data as long as needed to run Episode Atlas and comply with legitimate operational needs. To ask about correcting or deleting account data, use the site Feedback control in the footer or the channels listed on funkysi1701.com. Identity providers remain separate controllers for data they hold when you authenticate.
About this notice
Last reviewed: August 2026. Related: Terms of use, Tracking preferences, Support.