PacketSafari

Cookies and Local Storage

Effective date: April 3, 2026

This page explains how PacketSafari uses browser cookies, local storage, and session storage.

For broader information about how we handle personal data, see our Privacy Policy.

1. Overview

PacketSafari uses browser-side storage for a small number of practical reasons:

  • keeping sign-in and authenticated API flows working;
  • protecting authenticated requests with CSRF tokens;
  • remembering consent and interface preferences; and
  • preserving short-lived workflow state in the browser.

The exact storage used may vary by deployment mode, browser, and enabled features.

2. Cookies

PacketSafari uses cookies that are necessary for authentication and security, including cookies used with sign-in flows and CSRF protection.

Examples visible in the current frontend integration include CSRF cookie names such as:

  • csrf_access_token
  • csrf_refresh_token

Depending on deployment and authentication mode, additional session or authentication cookies may also be set by the backend.

These cookies are used to:

  • keep authenticated requests working;
  • refresh sessions securely;
  • protect against cross-site request forgery; and
  • support normal operation of the application.

If you block strictly necessary cookies, login and other authenticated features may not work correctly.

3. Analytics Consent

PacketSafari shows a consent banner for cookies and analytics preferences. The current frontend stores the consent choice in browser local storage under:

  • google-analytics

This stored value is used to remember whether you accepted or declined analytics consent in that browser.

4. Local Storage

PacketSafari currently uses browser local storage for a mix of authentication fallbacks, preferences, and user interface state.

Examples visible in the frontend code include:

  • access_token
  • refresh_token
  • theme
  • google-analytics
  • UI preference and workflow state keys used by analyzer, Copilot, Agent, tours, and view settings

These entries may be used to:

  • preserve sign-in state in some flows;
  • remember theme or display preferences;
  • remember whether onboarding or help prompts were dismissed; and
  • save temporary client-side preferences for analysis screens.

5. Session Storage

PacketSafari also uses session storage for short-lived browser state that should normally disappear when the browser tab or session ends.

Examples visible in the frontend code include temporary workflow state for analysis and agent views.

6. Third-Party Services

PacketSafari may rely on third-party infrastructure or analytics services depending on deployment, configuration, or future product changes. Where those services are enabled, their own cookies or storage mechanisms may also apply.

7. Managing Browser Storage

You can usually manage cookies, local storage, and site data through your browser settings. Please note:

  • disabling necessary cookies can break login and authenticated requests;
  • clearing local or session storage may reset preferences and client-side workflow state; and
  • declining analytics consent does not disable storage that is necessary for security or core application behavior.

8. Contact

If you have questions about cookies or browser storage in PacketSafari, contact PacketSafari support or email contact@packetsafari.com.