Hadron Chrome Extension — Privacy Policy¶
Last updated: 2026-07-01
This policy explains how the Hadron Chrome Extension ("the extension") handles
your data. The extension is published by Baragaun and works with the Hadron
service at srv.hadronmemory.com.
The short version: the extension only accesses a page's data when you ask it to, sends that data only to Hadron to create the node you requested, and stores nothing about you beyond the sign-in token and OAuth client registration needed to talk to Hadron. It does not track your browsing, show ads, or sell data.
What the extension does¶
When you click the extension and choose to send a page, it captures either the page's URL or its HTML content and sends it to your Hadron account to create or update a memory node that you name and target. You can optionally ask a Hadron App task to process the captured content.
Data the extension accesses¶
- The active tab's URL, title, and — only if you choose "Full HTML" — its rendered HTML content. This is read only at the moment you click Send, on the tab you are actively viewing. The extension does not read pages in the background or on tabs you have not explicitly clipped.
- Your Hadron account resources (the list of your memories, apps, and tasks), fetched from Hadron to populate the extension's menus.
Data the extension stores¶
Stored locally on your device (via chrome.storage.local):
- Your Hadron access token (a
hdr_user_…bearer credential), used to authenticate API calls. - A cached OAuth client registration (a
client_id) created the first time you sign in.
The access token never leaves your device except within the Authorization header sent to
Hadron. Signing out removes the stored token. The extension keeps no other
history of the pages you clip.
Data the extension transmits, and to whom¶
The extension communicates only with the Hadron service
(srv.hadronmemory.com and its OAuth endpoints). It sends:
- The page URL and/or HTML you chose to clip, plus the node name, location (LOC/URN), and target memory you selected.
- Standard OAuth requests to sign you in.
Content you clip is stored in your Hadron memory and is subject to Hadron's handling of your account data. The extension sends nothing to any other third party, and includes no analytics, advertising, or tracking SDKs.
Authenticated pages¶
Because HTML is captured from the page you are already viewing, content behind a login you are signed into (for example, a discussion thread on a site where you are logged in) is read from the already-rendered page. The extension does not capture, store, or transmit your credentials for those third-party sites — only the page content you explicitly choose to send.
Permissions and why they are needed¶
identity— to run the OAuth sign-in flow with Hadron.activeTab+scripting— to read the current tab's URL/title/HTML at the moment you click Send.storage— to keep your sign-in token and client registration on your device.- Host access to
srv.hadronmemory.com— to send clips and OAuth requests to Hadron.
The extension requests no broad host access to other websites.
What the extension never does¶
- No selling or sharing of your data with third parties.
- No advertising, behavioral profiling, or cross-site tracking.
- No background collection of your browsing activity.
- No reading of page content without an explicit click from you.
Data retention and deletion¶
The token stored on your device is removed when you sign out or remove the extension. Content you have already clipped lives in your Hadron account; manage or delete it there.
Changes to this policy¶
We may update this policy as the extension gains new capabilities. Material changes will be reflected here with a new "Last updated" date.
Contact¶
Questions about this policy or your data: help@baragaun.com.