What stays local, and what does not

Current storage model

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

If you clear browser site data, reset Chrome, delete the browser profile, or do a full cleanup without exporting first, the local workspace may be deleted.

Backup and portability

Use Last backup in the top bar, then choose Export library to save a full copy outside the browser. A good low-friction habit is to export once a week, after important work, and before a browser cleanup, profile change, or big reorganization.

If you are restoring a full exported root library, keep rootpad.json with the exported note files. The note files hold the content, and rootpad.json helps root recognize the full export cleanly.

Delete moves items into Trash first. Trashed items can be restored or deleted forever, and the current public Chrome package keeps them for 30 days before cleanup.

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.

If you want the exact permission-level explanation, read Security & Permissions.

Photo Text

When Photo Text is available in private testing, root processes the selected or captured image to extract text. root saves the recognized text, not the source image.

Browser AI and shared tabs

Browser AI features are separate from root. Different browsers handle that context differently. In some cases an assistant may only see tab titles and URLs by default. In other cases, if you enable browser features such as shared tab context, page-content access, or similar privacy settings, that assistant may be able to read the current root page.

If a root tab is visible and you choose to give a browser AI feature access to that page, the browser may be able to use the notes on it. That is browser behavior, not a background transfer initiated by root, and it can vary by browser and by the privacy controls you turn on.

Workspace size

root works best as an active work surface, not a giant permanent archive. Very large libraries, lots of long notes, or mass text storage can make the browser do more work than root is meant to carry. If something no longer feels active, export it or move it out.

Context Handoff and export

Context Handoff, 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 copy, paste, or export it yourself.

Accounts, analytics, and remote storage

The current Web Store package does not require an account to use the workspace, does not use analytics, and does not store workspace content on a root server.

Cloud sync is not part of the current Web Store package. If you save an export to a cloud folder or another location outside the browser, that is a manual file backup you chose outside root.

If root adds accounts, 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].