This policy covers the Longhand Agent browser extension. For the Longhand website and desktop product, see the site-wide
Privacy Policy.
The Longhand Agent browser extension lets the Longhand desktop app act on the websites you are already signed into, on your explicit instruction. This policy describes exactly what the extension does and does not do with your data.
The short version
- The extension is off by default. It reads nothing until you turn on the master "cloud reading" switch and add a specific site to your allowlist.
- It talks only to the Longhand desktop app on your own computer, over a loopback connection (
127.0.0.1). It has no server of its own and sends nothing to any Longhand-operated server. - Page contents leave your machine only when you have allowlisted that exact site and only to the AI provider you configured in the desktop app, using your API key.
What the extension accesses
When — and only when — a site is on your allowlist and the master switch is on:
- The active tab's page content (DOM) of that allowlisted site, so the agent can understand the page to complete the task you asked for.
- The ability to perform in-page actions (click, fill, navigate, select, scroll) on that site, each one shown to you for approval before it runs.
The extension does not read other tabs, does not run on non-allowlisted sites, and requests no broad host permissions (host_permissions is empty; it uses activeTab + scripting only on the site you allowlisted).
Where your data goes
- To your desktop app only. The extension connects to the Longhand desktop app over a local loopback WebSocket. The connection is paired with a one-time 6-digit code and authenticated per message; a random web page or another extension cannot drive it.
- To your chosen AI provider, by your desktop app. If you have enabled cloud reading for a site, the desktop app sends that site's relevant page content to the AI provider you selected (e.g. Anthropic), authenticated with the API key you entered. This is the same provider and key you already use in Longhand.
- Nowhere else. The extension operators do not collect, store, sell, or share your browsing data. There is no analytics beacon in the extension that transmits page content.
What is stored, and where
- Locally, in your browser: your consent settings (master switch, the list of sites you allowlisted) and the pairing token for the local connection, kept in
chrome.storage.local on your device.
- Locally, on your computer: the desktop app records which sites you allowlisted and an audit of approved actions, stored on-device. The pairing token is encrypted at rest in the desktop app's vault.
- Domain identifiers in optional product telemetry (if you opted into Longhand telemetry) are one-way hashed (
sha256(domain)[..16]) — never the full URL, never page content.
Your controls
- Turn the master cloud-reading switch off at any time → the extension reads nothing, everywhere.
- Remove a site from the allowlist → the extension stops reading that site.
- Unpair the extension in the desktop app → the local connection is revoked.
- Uninstall the extension → all locally stored extension settings are removed by the browser.
Permissions, explained
-
activeTab / scripting — read and act on the current tab only on a site you allowlisted, when you trigger the agent.
-
storage — save your consent settings and the local pairing token on your device.
-
tabGroups — put the tab the agent is working into a labelled, coloured tab group (Longhand · …) so you can always see, at a glance, which tab the agent acted on. It only ever groups the active tab you already consented to — it does not read your tabs, your tab titles, or your URLs across the browser, and a grouping failure never affects the task.
- No
host_permissions, no background network access to any remote server.
Contact
Questions about this policy:
support@longhand.app
Looking for the extension itself? See the
Longhand Agent extension page.