1. Browser storage we use (no cookies)
| Item | Type | What it holds | Lifetime |
|---|---|---|---|
| naamdhara (IndexedDB) | Essential | Your jap events, counters and sessions, so counting works offline and nothing is lost | Until you clear it or use Delete all local data |
| naamdhara.settings.v1 | Essential | Mantra, mala size, language, sound, vibration, theme, analytics toggle | Until cleared |
| naamdhara.reminders.v1, routines.v1, meditation.v1, prayer-bookmarks.v1, practicePlan.v1, tracks.v1 | Functional | Reminder and timer preferences (including the one-time location reading if you enabled sunrise mode), routines, bookmarks, your practice plan, downloaded track list | Until cleared |
| naamdhara.sessions.since.v1 | Essential | Sync cursor, so only new history is fetched | Until cleared |
| naamdhara.analytics.id.v1 | Analytics | A random id for usage statistics while signed out. Not set when the analytics toggle is off. | Until cleared |
| Supabase auth session | Essential | Your login token, only after you sign in | Until you sign out |
| Service worker cache | Essential | Copies of pages, sounds and wallpapers so the counter opens offline | Managed by the browser |
The mobile apps keep the same kinds of data in their own SQLite database and settings store; app stores call this "app data". Clearing the app's storage or uninstalling removes it.
2. Advertising cookies and identifiers
On the website, Google AdSense loads on content pages (home, mantra list, festivals, prayers, help, wallpapers) for free users and sets cookies such as IDE, test_cookie and __gads to serve and measure ads. Google explains them at How Google uses cookies. Ads and their cookies never load on the counter, Pure Counter, timer, mantra counting pages or routine runners, and never for Ad-free or Plus users.
In the mobile apps Google AdMob uses the device advertising identifier. Google's consent form appears on first launch and can be reopened from Settings → Ads → Privacy options.
3. Analytics and crash reporting
Usage statistics (PostHog) and crash reports (Sentry) are sent directly from the app code; they do not set cookies. They are off in development builds, and usage statistics can be turned off in Settings → Privacy → Share anonymous usage statistics.
4. How to control them
- Local data: Settings → Delete all local data in the app or on the dashboard, or clear site data in your browser. Export first if you want to keep your history.
- Ads: choose non-personalised ads or withdraw consent in Google's consent form; manage Google ad personalisation at Google Ad Settings; block third-party cookies in your browser; or buy Ad-free or Plus.
- Analytics: Settings → Privacy toggle.
- Login: sign out to remove the session token.
Blocking essential storage stops the counter from saving between visits; the site will still load but history will not persist.
5. Questions
hello@naamdhara.com. The Privacy Policy has the full picture of data handling.