Where data lives
| Storage | Typical contents |
|---|---|
| chrome.storage.local | Workspaces, settings, snapshots, API key, long-lived preferences |
| chrome.storage.session | Short-lived UI state, per-window workspace map, the rolling list of recently-visited domains for the bill-capture nudge, and your per-conversation “always allow” AI permissions (all cleared when Chrome closes) |
| Service worker memory | Tab activity timestamps for discard heuristics (cleared when the worker stops) |
Protected domains
In Protected Domains, enter host fragments (for examplemail.google.com or docs.google.com). Tabs whose hostname matches those entries are never discarded by Performance mode sweeps or Free RAM now (substring match — be specific to avoid over-broad rules).
Themes
The extension supports light and dark themes using design tokens. Toggle from the in-product Settings or dashboard header where available.Auto-save tabs
When Auto-save tabs is on, tab navigations in the active workspace update saved tab lists through a debounced path in the background worker — this avoids writing storage on every single event and reduces UI flicker.Open Tabs view
The Open Tabs view is off by default. Turn it on in Settings, then choose its layout, sort order, and whether tabs are grouped by window. It reads your open tabs’ titles and addresses to build the list — nothing leaves your computer.The “capture any bills?” nudge
To offer the occasional bill-capture suggestion, the extension keeps a short, rolling list of website names you’ve visited recently (just the domain, likesupplier.com). This list lives only in memory for the current browser session — it’s wiped when you close Chrome and is never sent anywhere. It’s used purely to decide whether to show the chip.
eggz account
Settings → eggz account shows whether the extension is connected to your eggz account, with Sign in / Sign out. One login is shared with the web app. Privacy notes for the connected mode:- The extension never stores tokens or passwords — your session is a secure, httpOnly browser cookie on
app.eggz.ai, the same one the web app uses. - While you use the AI, it’s sent names and addresses only by default — your open tabs’ titles and URLs, your saved workspace/folder/link names, and the current page’s title and URL. The actual contents of a page are sent only after you approve the permission card (see below). Other browsing is not sent anywhere.
- Documents you upload go to your eggz organization and follow the web app’s data handling.
Asking permission before reading a page
When the AI wants to read what’s on a page (or look at one of your records), it shows a permission card first — Allow once, Always allow (for the current conversation), or Deny. Until you approve, no page or record content leaves your browser — the AI only ever has names and addresses. Your “Always allow” choices are remembered per conversation and clear when you start a new chat or close Chrome.AI and network
There’s now one AI chat — no modes to flip between. It just picks the right helper for you (see AI assistant & search):- No eggz server is required for core workspace features — they all work offline-ish, on your computer.
- Signed in to eggz: the chat talks to eggz (your organisation’s assistant) — no API key needed.
- Using your own key: Anthropic is only contacted when you use AI features and a valid API key is set (signed out, or as a backup when your eggz credits run out).
- To answer questions about your tabs, the chat sends your open tabs’ titles and web addresses (names only) — and the contents of a page only after you approve the permission card. This only happens when you actually use the AI.
- Review Anthropic’s policies for data processing when you enable AI.