Back to HolyTL;DR

Cookie & Storage Policy

TL;DR

We don't use cookies. Seriously, zero. We use localStorage to remember your preferences and cache verses for speed. No Google Analytics, no Facebook Pixel, no third-party trackers. Your browser, your data. You can clear it all from your browser settings anytime.

1. No Cookies

HolyTL;DR does not set or read any browser cookies — not first-party, not third-party, not tracking cookies, not analytics cookies. None.

This means there is no cookie banner, no consent dialog for cookies, and no cookie-based tracking of any kind.

2. What We Use Instead: localStorage

We use your browser's localStorage to store small pieces of data that make the app work smoothly. localStorage is a browser feature that keeps data on your device only — it is never automatically sent to our servers (unlike cookies).

Here is what we store:

KeyPurposeContains
Theme preferenceRemember your light/dark mode choiceString ("light" or "dark")
LocaleRemember your language selectionLanguage code (e.g., "en", "es")
Onboarding statusTrack whether you completed setupBoolean flag
Verse cacheStore recent verses for faster loadingVerse data (JSON)
Referral codeCredit the person who referred youReferral code string
Streak dataTrack your daily reading streak locallyDate and count values
Promo dismissalRemember if you dismissed a promotionBoolean flag

All localStorage data stays on your device. We do not transmit it to third parties.

3. Authentication Tokens

When you sign in with a magic link, Supabase (our authentication provider) stores session tokens in your browser's localStorage. These tokens are used to keep you signed in and authenticate your requests to our servers. They are managed entirely by the Supabase client library and are not shared with any other service.

4. Push Notifications

If you enable push notifications, HolyTL;DR uses the Web Push API — a browser-native feature. This requires your explicit browser permission. When granted, a push subscription token is generated by your browser and sent to our server so we can deliver notifications to your device.

You can revoke notification permission at any time through your browser settings. When revoked, we stop sending notifications and delete your push token from our servers.

5. Service Worker & Offline Cache

HolyTL;DR uses a service worker to cache application files (HTML, CSS, JavaScript, fonts, icons) for offline use and faster loading. This is a standard Progressive Web App (PWA) feature.

The service worker cache stores only application assets — not your personal data. You can clear this cache at any time through your browser's developer tools or by clearing site data in your browser settings.

6. What We Do NOT Use

To be explicit, HolyTL;DR does not use any of the following:

7. How to Clear localStorage

You can clear all HolyTL;DR data stored in your browser at any time. Here's how:

Chrome

  1. Open Settings > Privacy and Security > Site Settings
  2. Search for holytldr.com
  3. Click Clear Data

Safari

  1. Open Settings > Safari > Advanced > Website Data
  2. Find holytldr.com
  3. Swipe to delete

Firefox

  1. Open Settings > Privacy & Security > Cookies and Site Data > Manage Data
  2. Search for holytldr.com
  3. Select and click Remove Selected

Clearing localStorage will sign you out and reset your local preferences, but your account data on our servers remains intact. Simply sign in again to restore your experience.

8. Changes to This Policy

If we change our storage practices (for example, if we ever introduce cookies or analytics), we will update this policy and notify you via the app. Your continued use after changes constitutes acceptance.

9. Contact Us

Questions about our storage practices?

Berry App Labs
Email: hello@holytldr.com

For full details on how we handle your personal data, see our Privacy Policy.