DASHH uses the minimum number of cookies and browser-storage keys needed to make the app work. This page lists every one.
1. Strictly necessary
These are required for the platform to function. You cannot turn them off — without them, the app can't log you in or remember what page you were on.
dashh_session— HMAC-signed cookie storing your authenticated wallet address (only after you complete SIWS). 30 days. HttpOnly.dashh_wallet(localStorage) — mirrors the connected wallet address client-side so we don't re-prompt on every page.dashh_mode(localStorage) — whether you're in Explore (creator) or Create (brand) mode.
2. Functional
dashh_onboarded(localStorage) — flag set totrueafter you complete the onboarding wizard, so we don't show it again.dashh_demo_mode(sessionStorage) — only set when you click “Try the live demo”. Cleared when you exit demo mode.
3. Analytics (opt-in)
Disabled by default. If you accept analytics in the cookie banner, we initialise PostHog to track aggregate page views and feature usage. No personal information is captured — just anonymous events scoped to your wallet address (which is already public).
ph_*— PostHog session and distinct-id cookies.
4. Error monitoring (opt-in)
Disabled by default. If you accept, runtime errors are captured by Sentry. Stack traces may include a truncated wallet address (for debugging) but never private keys, signatures, or content you haven't already submitted to the platform.
5. Controlling cookies
You can:
- Clear all DASHH storage via your browser's site-data settings.
- Disable analytics + error tracking via the cookie banner that appears on first visit.
- Block all third-party cookies in your browser — the strictly-necessary cookies above are first-party and will keep working.
6. Updates
When we add or remove cookies, we'll update the table above and bump the “Last updated” date at the top of this page.