What stays local, and what does not

Current storage model

The current root prototype stores workspace content locally in the browser. That includes items, tags, snippets, pinned state, and local version history.

Current page capture

The current Chrome build uses the active tab only when you open Quick Capture and choose Current page. In that moment, root reads the active page title and URL so it can append them into your workspace. That information is not sent anywhere automatically.

Browser AI and shared tabs

Browser AI features are separate from root. If you use something like Gemini in Chrome or Atlas and allow it to use page content, those tools may be able to read the current page or other tabs you share with them. If a root tab is visible and shared with a browser AI feature, that browser may be able to use the notes on that page. That is browser behavior, not a background transfer initiated by root.

Copy Context and export

Copy Context, export, and import are all user-triggered. root prepares a preview or a file set, and you decide what leaves the local workspace. Nothing is sent to an assistant, model, or external service unless you intentionally paste or export it yourself.

Accounts, analytics, and remote storage

The current beta does not require an account to use the workspace, and it does not use server sync for workspace content.

If root adds accounts, sync, analytics, or server-backed features later, this page should be updated before those features launch so it clearly explains what changes, what data moves, and what remains local.

Privacy questions

For privacy questions, contact [email protected].