Use Privacy choices in the app footer to accept, reject, or manage optional preferences. Google's applicable Privacy & Messaging message is the intended certified advertising consent mechanism, not the custom preference banner. Advertising stays disabled until that published setup is verified. Unknown or rejected regional consent keeps the ad SDK off.
| Storage | Purpose | Duration |
|---|---|---|
tg_consent | Versioned optional preferences; accepts legacy md_consent. | Until changed or cleared. |
tg_lang, md_lang | Language compatibility across the app and articles. | Until cleared. |
tg_journal, legacy md_journal | Guest entries, questions, card IDs, and reflection notes. | Until deleted or cleared. |
tg_account_owner, tg_account_cache, tg_account_pending | Account-specific entries and unsynced changes. These are private journal data, not credentials. | Until account switch or sign-out; pending changes require export/discard. |
tg_device_id, tg_guest_imports | Stable device and acknowledged guest-entry IDs prevent repeated imports. No Google credential is stored here. | Until cleared. |
tg_daily, tg_streak, tg_deck_theme, tg_persona, tg_ritual | Daily card, chosen deck, reader voice, and ritual preferences. | Until cleared. |
tg_visits, tg_pwa_dismiss, remaining md_* interface flags | Install reminders, study progress, and dismissed interface tips. Not every legacy key is renamed. | Until cleared. |
tg_license, tg_ent, legacy license keys | Compatibility with earlier licensing and its separate journal API; no checkout is offered. | Until cleared. |
__Host-tg_login cookie | Secure, HttpOnly binding for the one-time Google login nonce. | Five minutes. |
__Host-tg_session cookie | Secure, HttpOnly, host-only, revocable account session. | Seven days or logout/deletion. |
| Service-worker caches | Public application shell and previously viewed card artwork. API responses are not cached. | Until cache upgrade or site-data clearing. |
Legacy email markers may contain a previously entered email address. Private backups contain journal information. Neither is used as a Google credential. The cookie names prefixed tg_dev_ exist only in explicitly opted-in localhost development, not the HTTPS production session.
Optional Google Analytics 4 is configured and loads only after your explicit analytics consent. Google Analytics 4 or Plausible requires separately verified access with no added cost and analytics consent, and is blocked by Global Privacy Control. Google Analytics is loaded only after consent; a previous Plausible choice does not authorize its cookies. With consent, tg_analytics_day stores only the latest measured UTC date in this browser to recognize a return on a later day. It is removed when consent is refused, revoked, or site data is cleared; it contains no unique identifier. A subscription-confirmation timestamp is created only with prior analytics consent and Global Privacy Control off, and remains until consumed on an eligible app visit or cleared. It is counted only within 24 hours and when confirmation occurred during the current analytics consent grant. Our events exclude query values, fragments, referrers and account identifiers. Plausible requests do not use cookies. If Google Analytics 4 is enabled, its tg_ga4_ga and tg_ga4_ga_* cookies contain pseudonymous browser/session information. We configure a 30-day expiry without renewal on every visit; browser limits may shorten it. Withdrawing analytics consent removes these cookies where accessible and disables collection. Accepting again on that page takes effect after navigation or reload. Advertising storage remains denied for this analytics integration. Google advertising requires the project's verified publication gate and applicable consent data; the custom advertising toggle can block but cannot independently authorize Google ads. Google sign-in and Turnstile load when you deliberately request their configured features. Their provider-controlled storage depends on their own services.
No automatic ad refresh runs. Advertising is restricted to editorial pages and completed readings, not account, journal, policy, confirmation, or error screens. Global Privacy Control blocks the ad loader in this version.
Clearing browser storage removes local guest records and preferences and can remove unsynced account changes. Export a backup first if you want to keep them. Signing out clears the account cache while preserving guest data. Cloud account deletion and email unsubscribe are separate actions.
Contact johnny.bulker@gmail.com. See the Privacy Policy and project and editorial information.