Loop Page Markdown

Privacy policy

Last updated: 2026-06-19

This extension does not collect, store, or transmit any personal data or telemetry. There are no analytics, no remote endpoints owned by the author, and no third-party services involved in its operation.

What the extension does with data

Page content (only when you click Capture)

Reads the current tab's rendered DOM — the Loop page body and, if the comments pane is open, its comment threads. This content has already been fetched and rendered by your browser; the extension reads it from the DOM. All processing happens entirely in your browser. The resulting Markdown is written directly to your local machine via the OS Save As dialog. No copy of the content is sent anywhere else.

Downloads (chrome.downloads)

Saves the captured Markdown through the browser's standard download manager, which opens the OS Save As dialog. The extension does not enumerate or access any other downloads; it only acts on the file it just created.

Permissions

The extension requests:

Permission Why
activeTab Access to the current tab when the user clicks the extension's toolbar icon. No background access to any site.
scripting Required by Manifest V3 to inject the capture script on demand via chrome.scripting.executeScript. No persistent content scripts are registered.
downloads Save the captured Markdown via the browser's download manager (opens the OS Save As dialog).
https://loop.cloud.microsoft/* Host permission required to inject the capture script into Loop pages on the primary Loop domain.
https://*.sharepoint.com/contentstorage/* Host permission for Loop pages embedded in SharePoint Embedded containers — these URLs follow the /contentstorage/ path pattern.

The extension runs no background service worker and makes no network requests beyond what your browser was already sending to the Loop page you're viewing.

Host permissions

Unlike the related Teams Transcript to Markdown extension (which uses activeTab with no host permissions), this extension declares host permissions for loop.cloud.microsoft and *.sharepoint.com/contentstorage/*. These are required because Loop pages use authenticated session state; Manifest V3 requires explicit host permissions for executeScript on pages with specific origins. The extension only injects its capture script when the user actively clicks Capture — there is no background activity on these hosts.

Contact

Issues and questions: please file an issue on the project's GitHub repository.

← Back to home