Addwell Chrome Extension — Privacy Policy
Last updated: May 18, 2026
What the extension does
The Addwell Chrome extension lets a builder, designer, or other authorized team member read product information from a webpage they are currently looking at — typically a manufacturer or retailer product page — and send it into their Addwell Selections project. It is a workflow tool tied to an Addwell account; it does not function without one.
What the extension reads
- The active browser tab's rendered HTML, but only when you explicitly click the extension's Extract this page button. The extension does not read pages in the background, does not read pages you have not opened, and does not run on a schedule.
- The URL and title of the active tab, used to show you which page you are about to extract from.
- Your Addwell API token, which you paste once during first-run setup. It is stored locally in your browser via
chrome.storage.local.
What the extension sends
- The rendered HTML of the page you chose to extract from, along with your API token and the project/item you picked, to your Addwell instance (typically
app.addwell.design) over HTTPS. Your Addwell backend then parses the page to populate item fields. - Any product URL you paste, screenshot, or PDF you upload via the in-app version of the same wizard, to the same backend.
Nothing is sent to third parties. Page contents are not retained beyond the extraction call except where you choose to save fields or attach documents to a project item.
What the extension stores locally
- Your API token (so you don't have to paste it every time the popup opens).
- Your Addwell instance URL (so the popup knows where to send extractions).
- Your name and organization as returned by the token-verify response, used to label the popup header ("Connected: Josh · Delta Design Build").
All of this is stored using chrome.storage.local, which means it stays on your device and is cleared if you uninstall the extension or explicitly disconnect via the gear icon in the popup.
What the extension does NOT do
- It does not track your browsing history.
- It does not read pages without an explicit click.
- It does not send data to third-party advertising or analytics services.
- It does not store credit-card or payment information.
- It does not have access to data on pages outside the active tab you are extracting from.
Permissions the extension declares
activeTab+scripting— required to read the active tab's HTML when you click Extract.tabs— required for the optional "pop-out window" mode, which lets the popup stay open while you switch tabs. Used to look up the URL of the tab the standalone window is associated with.storage— to remember your API token + instance URL across browser sessions.<all_urls>host permission — so the extension works on any product page, regardless of which retailer or manufacturer. The extension does not read pages on its own; the host permission is checked only when you click Extract on the currently active tab.
Who has access to what you save
Items, photos, and documents you save through the extension land in your Addwell organization's project, subject to the same role-based access rules as anything created from the web app. Other people in your organization may see what you save according to their assigned role. People outside your organization cannot see it.
Revoking access
You can revoke a token at any time from Settings → Extension in the Addwell app. Revoked tokens stop working immediately; the extension will prompt you to paste a new one on its next request.
Uninstalling the extension from Chrome removes all locally stored data (your token + instance URL). It does not delete anything you have already saved to your Addwell account.
Contact
Questions about this policy or how the extension handles your data? joshua@addwell.design.