Noble Medical Group Español

Privacy Policy — Noble Guides

Last updated: 08/03/2026 · Contact: info@noblemedicalgroup.com

Noble Guides is an internal browser extension used by Noble Medical Group. It captures a workflow in the browser and turns it into a step-by-step guide with screenshots.

This document states exactly what data the extension touches, what leaves the browser and what does not.

What stays in your browser and is never sent anywhere

All of the following lives only in the user's own browser, in local storage on their machine:

Noble Guides has no user accounts, requires no sign-up, and sends nothing to a Noble server for storage. If the user uninstalls the extension or clears browser data, the guides go with it.

What leaves the browser, and only if you enable AI descriptions

The AI description feature is optional. If no API key is configured, no data leaves the browser.

When enabled, for each captured step a text summary of the element you interacted with is sent to the AI provider you selected. That summary includes:

Screenshots are not sent to the AI provider. Only text is transmitted.

Important notice about field values

If you type into a text, email, phone or number field, that content may be part of the text sent to the AI provider.

Usage rule at Noble Medical Group: do not capture guides on screens containing patient data or personally identifiable information while AI descriptions are enabled. To document those screens, turn AI off in Settings before recording, or select the local model.

Who receives that data

The AI provider the user selects in Settings. By default, Noble Guides points to Noble's own gateway, which in turn routes the request to the chosen model. Among the available options there is a local model hosted on Noble's own server, with which the data never leaves the company's infrastructure. If the user configures a different provider, the data goes to that provider under its own terms.

Permissions the extension requests, and why

PermissionWhy
Access to all sitesThe extension must be able to record a workflow on any internal or external site the team uses. Which ones cannot be known in advance.
activeTab, tabs, webNavigationTo know which tab is being recorded and detect page changes, so steps can be separated.
scriptingTo inject the click detector and the blur overlay into the page being recorded.
storage, unlimitedStorageTo store guides and screenshots on the machine. Screenshots are large, hence the expanded storage.
sidePanelTo show the side panel used for recording and browsing guides.

The extension does not collect browsing data for analytics, does not track users across sites, and does not sell or share data with anyone.

Changes to this policy

Any change will be published at this same address with an updated date.