PhishNet
ProductPricingSecurityEnterpriseBlog
Sign inAdd to Chrome — Free
LEGAL · COOKIES

Cookies & Local Storage

What PhishNet stores on your device, why, and how to clear or block it. We don't use tracking cookies — but we do use browser storage to keep you signed in and to cache scans.

Last updatedMay 28, 2026EffectiveMay 28, 2026
Contents
  1. Overview
  2. What we store
  3. What we do not store
  4. Third-party services
  5. How to clear or block
  6. Changes to this policy
  7. Contact

01Overview

This page explains what PhishNet stores on your device, why we store it, and how to clear or block it. It covers both traditional cookies and other browser-storage technologies (localStorage, sessionStorage, chrome.storage), because the privacy considerations are the same whether the data lives in a cookie or somewhere else.

Short version: PhishNet uses a small number of HTTP cookies for security purposes — specifically to store your refresh token and to protect OAuth sign-in flows against CSRF attacks. We also use localStorage in the web app and chrome.storage in the extension. We do not use any advertising, tracking, or analytics cookies.

02What we store

HTTP Cookies

Cookie namePurposeAttributesLifetime
refresh_tokenKeeps you signed in. The server reads this cookie to issue a new access token when your session expires, without requiring you to log in again.HttpOnly · Secure · SameSite=Strict · first-party onlyUntil you sign out, or the token expires (set per session).
oauth_stateCSRF protection during Google OAuth sign-in. A one-time nonce set before you are redirected to Google and verified when Google redirects back.HttpOnly · Secure · SameSite=Lax · first-party only10 minutes (cleared immediately after use).
workos_oauth_stateSame CSRF protection as above, for enterprise SSO (SAML / WorkOS) sign-in flows.HttpOnly · Secure · SameSite=Lax · first-party only10 minutes (cleared immediately after use).

Browser storage (non-cookie)

WhereKeyPurposeLifetime
localStorage
(web app)
phishnet_access_tokenShort-lived access token used to authenticate API requests. The refresh token (in the cookie above) is used to renew it.Until you sign out or clear browser storage.
localStoragephishnet:themeRemember your light/dark mode preference.Until you change it or clear browser storage.
chrome.storage
(extension)
Scan cache, sensitivity, trusted-senders allowlist, panel state.Avoid re-scanning the same email twice; remember your in-product preferences.Per your scan-cache TTL setting (default 10 minutes for scans; preferences persist).
sessionStorageTransient UI state (e.g. OAuth redirect destination).Preserve where to send you after sign-in completes.Until you close the tab.

03What we do not store

PhishNet does not use:

  • Third-party advertising or marketing cookies.
  • Cross-site tracking pixels.
  • Analytics that profile individual users (we use server-side, aggregated metrics only).
  • Social-media share/embed cookies.

All cookies we set are strictly necessary for authentication and security — they are not used for advertising, analytics, or personalisation. Under ePrivacy rules, strictly-necessary cookies do not require consent. If we ever introduce non-essential cookies we will request your consent before setting them and update this page first.

04Third-party services

Some pages of the marketing site embed resources from third parties. These providers may set their own cookies on your device, governed by their own policies:

  • Google Fonts — serves the Space Grotesk, DM Sans, and DM Mono typefaces. Google's policy: policies.google.com/privacy.
  • Stripe — sets cookies on the checkout and billing-portal pages. Stripe's cookie notice: stripe.com/cookie-settings.

We never share your PhishNet identity with these providers. They see only the embed itself (font request, payment session) — not your email content or account details.

05How to clear or block

You can clear what PhishNet stores on your device at any time:

  • Auth cookies — sign out from your profile dropdown. This clears the refresh_token cookie server-side immediately.
  • Web app storage — open browser settings → "Clear browsing data" → select "Cookies and other site data" → choose "phishnet.ai". This will sign you out.
  • Extension storage — visit chrome://extensions, find PhishNet, click "Details" → "Extension options" → "Reset". Or remove the extension entirely.

You can also block all storage for our domain at the browser level. The web app and extension will not function without their essential storage — there is no usable fallback for an unauthenticated session.

06Changes to this policy

If we ever start using new storage technologies — particularly if any of them become non-essential or third-party — we will update this page and notify you in-product before the change takes effect.

07Contact

Questions about what we store on your device: privacy@phishnet.ai. See also our Privacy Policy.

← Back to home
PhishNet
AI-powered email security built into Gmail. Stop phishing before it stops you.
Product
FeaturesHow it worksPricingChangelogRoadmap
Company
AboutBlogSecurityPressCareers
Support
DocsStatusPrivacyTermsContact
© 2026 PhishNet, Inc. All rights reserved.
Privacy PolicyTerms of ServiceCookie Policy