Cookie Policy

The service currently uses the following first-party or service-provider storage for requested features, continuity, and security.

• Theme preference. localStorage remembers light, dark, or system mode until you change it or clear site data.
• Authentication. Firebase may use IndexedDB and related browser storage to keep you signed in and refresh authentication state securely.
• Sign-in handoff. Temporary localStorage values support Google redirect state and email-link sign-in, and are removed or replaced as the flow completes.
• Visitor identity. A random first-party visitor key lets public readers keep preferences and meaningful reader actions associated with the same browser.
• Reader preferences. localStorage may hold onboarding choices, ranking objectives, follows, and a preference profile.
• Reader memory. localStorage may hold saved stories, reading history, search memory, recommendation feedback, guardrails, and recent front-page exposure state.
• Operational storage. Hosting, security, or interface components may use strictly necessary state to route requests, protect the service, or remember a control you asked us to preserve.

We do not currently use advertising cookies. We do not currently use analytics cookies. We do not use browser storage to follow you across unrelated websites or to build an advertising profile.

If we introduce non-essential analytics, advertising, or cross-site tracking, we will update this policy and add consent controls before activating that use where required by law.

You can clear or block site storage through your browser settings. You can also sign out, remove reader items through product controls, and change the theme or recommendation settings in the service.

Blocking or clearing storage may sign you out, reset theme and onboarding choices, create a new visitor key, remove local saves or history, and make personalization less consistent. Account-linked records may remain on the server until removed through product controls or a verified request.

Some values last only for a sign-in flow or browser session. Preference and reader-memory values can remain until you remove them, the application expires stale entries, or you clear site data. Firebase controls the lifetime of authentication persistence needed to keep you signed in.

We will update this page when browser storage practices materially change. The effective date at the top identifies the current version.