Effective and last updated: June 15, 2026

Cookie and Local Storage Notice

Cruxl uses a small set of device-storage technologies for login, preferences, drafts, and core application features.

1. Technologies we use

  • Authentication storage: Supabase authentication tokens and session data used to keep you signed in and protect account access.
  • Functional cookie: a sidebar-state cookie named sidebar:state, retained for up to seven days.
  • Local storage: theme, contrast, reduced-motion, onboarding, and other interface preferences.
  • Draft storage: locally stored text used to preserve unfinished captures.
  • IndexedDB or mobile storage: recordings you explicitly save for later processing and other offline-capable app data.
  • Provider logs: hosting and infrastructure providers may receive IP address, user-agent, request, and security data when serving the application.

2. What we do not currently use

Cruxl does not currently use third-party advertising cookies, cross-site behavioral tracking, or third-party behavioral analytics cookies. If that changes, we will update this Notice and request consent where required.

3. Your controls

Browser and device settings can block or delete cookies, local storage, and site data. Clearing authentication storage signs you out. Blocking required storage may prevent login, saved preferences, offline recordings, or other core features from working.

Saved recordings and drafts can be deleted in the relevant Cruxl screen or by clearing Cruxl's app or browser storage on your device.

4. Contact

Questions may be sent to contact@cruxl.app.