Cookie Policy
This Cookie Policy explains how DayZero Payments, Inc. (“DayZero,” “we,” “us,” or “our”) uses cookies and similar technologies when you use the DayZero platform and website (the “Service”). This policy should be read alongside our Privacy Policy.
1. What Are Cookies
Cookies are small text files stored on your device by your web browser when you visit a website. They are widely used to make websites work efficiently and to provide information to site operators. “Similar technologies” include localStorage, sessionStorage, and other browser storage mechanisms that serve comparable purposes.
2. Cookies We Use
Authentication cookies (essential)
Our authentication provider, Clerk, sets cookies to manage your login session. These are strictly necessary for the Service to function and cannot be disabled.
- Session cookies — HttpOnly cookies set by Clerk to maintain your authenticated session. These identify you to the Service after login and expire when you sign out or after a set period.
- CSRF protection cookies — Used to prevent cross-site request forgery attacks during authentication flows.
These cookies are first-party (set under our domain) and do not track you across other websites. DayZero does not set any cookies directly from our own application code; all cookies are managed by Clerk for authentication purposes.
Admin session cookies (essential)
For internal administrative sessions, the backend may set HttpOnly cookies during certain authentication flows. These are automatically cleared by the application when not needed.
3. Local Storage & Session Storage
In addition to cookies, the Service uses your browser's localStorage and sessionStorage to store preferences and application state. Unlike cookies, this data is not sent to our servers with each request — it remains on your device.
Preferences (localStorage)
- Theme settings (
dz-pref-theme,dz-pref-font,dz-pref-color-blind) — Your visual theme, font, and accessibility preferences. Used to render the correct appearance immediately on page load.
Application state (localStorage)
- Active business context (
dz_active_business_id) — Remembers which business you were last working with. - Portal context (
dz_portal_firm_id,dz_portal_business_id, etc.) — Remembers your advisory firm and business selections. - Client portal context (
dz_client_business_id,dz_client_business_name) — Remembers client portal selections. - Dashboard tab (
dz:dashboard-tab) — Remembers your last selected dashboard view. - Sidebar state (
dz_sidebar_view) — Remembers your sidebar preference (expanded/collapsed). - Navigation shortcuts (
dz:page-visits) — Tracks which pages you visit most frequently to personalize navigation shortcuts. This data stays in your browser and is not sent to our servers.
AI chat state (localStorage)
- Chat drafts and context (
ai_chat_*keys) — Preserves your current chat draft, message queue, and conversation context so you don't lose work if you navigate away. - Microphone preference (
ai_chat_mic_device_id) — Remembers your selected audio input device for voice features. - Tutorial completion — Tracks whether you have completed the chat and workflow tutorials so they are not shown again.
Session storage
- Admin authentication tokens (
dz_admin_access,dz_admin_refresh) — Temporary Bearer tokens for admin sessions. Cleared when the browser tab is closed. - Conversation identifiers — Temporary references to your current AI chat session.
4. Third-Party Technologies
Sentry (error monitoring)
When enabled, Sentry collects error reports and may record session replays for debugging purposes. Sentry may use its own cookies or local storage to track error sessions. This is configured as follows:
- Session replay is sampled at a low rate (configured via environment variables) and captures only error-related sessions by default.
- Personally identifiable information (PII) is not sent to Sentry by default. This is configurable and disabled unless explicitly enabled.
- Sentry is not active in development environments unless explicitly enabled.
Google Fonts
The Service loads fonts from Google Fonts (fonts.googleapis.com / fonts.gstatic.com). This results in your browser making requests to Google's servers, which may log your IP address per Google's Privacy Policy. Google Fonts does not set cookies, but font files may be cached by your browser.
Clerk
As described in Section 2, Clerk manages authentication cookies. For details on Clerk's data practices, see Clerk's Privacy Policy.
5. What We Do Not Use
DayZero does not use:
- Marketing or advertising cookies — No Google Analytics, Facebook Pixel, LinkedIn Insight Tag, or similar.
- Third-party tracking pixels — No cross-site tracking of any kind.
- Behavioral advertising — We do not build advertising profiles or serve targeted ads.
- Social media tracking — Our LinkedIn link is a standard outbound link with no embedded tracking.
6. Managing Your Preferences
Browser settings
Most browsers allow you to control cookies through their settings. You can typically:
- View what cookies are stored and delete specific ones.
- Block all cookies or only third-party cookies.
- Clear all cookies when you close your browser.
Note that blocking essential authentication cookies will prevent you from signing in to the Service.
Local storage
You can clear localStorage and sessionStorage through your browser's developer tools or settings. Clearing this data will reset your theme preferences, active business selections, and chat drafts.
Sentry opt-out
Sentry error monitoring can be blocked using browser extensions that block requests to sentry.io domains. This will not affect the core functionality of the Service.
7. Changes to This Policy
We may update this Cookie Policy to reflect changes in our practices or for legal, operational, or regulatory reasons. We will post any changes on this page and update the “Effective” date.
8. Contact Us
If you have questions about our use of cookies, contact us at:
DayZero Payments, Inc.
legal@ondayzero.com
This Cookie Policy was last updated on April 7, 2026.