DeepHelp AI

Cookie Policy

Learn how DeepHelp AI uses cookies and local browser storage, why they are used, and how you can manage them.

Last updated: July 30, 2026

1. Overview

The public Guardian experience uses browser localStorage for an opaque session identifier and limited waitlist-prompt state. These values are not advertising cookies.

2. Browser localStorage

DeepHelp AI stores an opaque session identifier under deephelp.session.v1. The scanner may also store scan counters, prompt dismissal timing, and a waitlist-joined flag so the waitlist prompt behaves consistently in the same browser.

The waitlist email address itself is not stored in localStorage. Clearing site data removes these local values and disconnects that browser from its prior session-scoped history.

3. Essential admin cookie

The protected admin surface can set a signed, HTTP-only, SameSite=Lax cookie named deephelp_admin. It is used only to authenticate the admin session and expires after eight hours. It is secure in production.

4. Theme and analytics

DeepHelp AI stores deephelp-theme in browser localStorage only to remember your Dark or Light preference. It is not a cookie, contains only dark or light, and is not used for analytics, advertising, profiling, authentication, or tracking. It remains until you change the preference or clear browser storage.

5. Your choices

You can clear cookies and localStorage through your browser settings. Blocking essential storage may prevent session-owned history, waitlist-prompt suppression, or admin authentication from working as intended.

6. Contact

Questions about browser storage can be sent to [email protected].