Local-first privacy boundary

What the website receives

The website handles your account, subscription, Billing Portal, extension token metadata, and plan status. It does not need prompt text, answer text, local file paths, export filenames, raw DOM, cookies, tokens, or sensitive screenshots.

What stays local

Browser captures and exported files stay in your browser or on your device, unless you explicitly send an export to another destination.

Local workflow boundary

RecallBase is not a cloud upload path for raw conversations. Any local bridge or desktop workflow follows the same rule: account and billing systems never receive conversation content.

• Save or export only from a supported conversation page.

• Keep exported files in a folder you control.

• Send content to Notion, Obsidian, clipboard, or another app only when you choose that destination.

• Do not include raw chats, tokens, cookies, or local files in support requests.

Practical support boundary

Support can help from the symptom, browser, extension version, export type, and account state. Do not send raw AI conversations, prompt or answer text, cookies, access tokens, local database files, raw DOM dumps, or screenshots that reveal sensitive work. If a screenshot is genuinely necessary, crop it to the RecallBase control or error message before sharing.

Where exports go

Exports go to the destination you choose: a browser download, the clipboard, the browser PDF dialog, Notion, Obsidian, or another local workflow. RecallBase does not back up exported chats to a cloud account.