Canopy Clipper Privacy Policy

Page access and information handled

Canopy Clipper requires HTTP(S) host access so it can index images on eligible pages and provide the image picker and hover-save control. It does not run on non-HTTP(S) pages or on the configured Canopy application origin.

The extension handles detected image URLs and dimensions, the source page URL, and information you choose to add, such as a title, description, collection, or event. These details stay in page memory unless you request a save. Image previews may load from their original detected source URL.

How information is used

This information is used only to show image choices, authenticate your Canopy account, and complete saves that you request. The extension does not include analytics and makes no unrelated third-party requests.

When information leaves your browser

When you save an image, its metadata is sent to the configured Canopy API. Canopy normally retrieves HTTP(S) image bytes from the source URL. If that is not possible, the extension sends bounded image bytes to the configured Canopy API. The extension never writes to R2 directly.

Local storage and credentials

Detected image details and unsaved form values are not persisted by the extension. chrome.storage.local stores only Canopy account credentials and temporary authorization, refresh, and sign-out state. Credentials remain in extension-owned storage and are used only by the extension's background service worker.

Your controls and deletion

You can review or revoke browser extension sessions under Connected Apps. Removing Canopy Clipper from Chrome deletes extension-owned local data. It does not delete images already saved to Canopy; manage those in the Media Library.

Policy scope and changes

This policy covers the Canopy Clipper extension. Canopy may update it when the extension's behavior or legal requirements change. Material updates will be published on this page with a revised effective date.