Privacy Policy — Blossom Screenshot & Screen Recorder
Last updated: 13 September 2026 · Published at <https://blossom-screenshot.loudhost.net/privacy.html>, which is generated from this file by scripts/build-site.mjs.
Blossom Screenshot & Screen Recorder captures, annotates and records what is on your screen. This policy describes exactly what the extension does with that material.
The short version: everything stays on your computer unless you press Share.
What the extension stores, and where
Captures and recordings are written to your browser's own storage on your machine — the image and video data in IndexedDB, the list that describes them (names, sizes, dimensions, dates, and the page a capture came from) in chrome.storage.local. None of it is sent anywhere as a consequence of being captured.
Your settings are kept in chrome.storage.sync. If you are signed into Chrome this is synchronised across your own devices by Chrome itself, under your own Google account; the extension's authors cannot read it. If you would rather it did not sync, sign out of Chrome or disable extension sync in Chrome's settings.
Deleting an item from the library removes both its data and its entry. Clearing the library, or uninstalling the extension, removes everything.
What leaves your computer
Nothing, until you choose to share something.
The upload takes one of two routes:
- If you have entered your own API key in Options, the file goes directly from your browser to YourImageShare, using your key and your account. Nothing passes through any server belonging to this extension.
- If you have not, the file is sent through
blossom-screenshot.loudhost.net, which holds a shared API key and forwards the upload. It keeps counters of how many uploads have been made, per address and in total, to stop the shared account being abused. It does not log the contents of what passes through.
through that server is sent in pieces, so that a dropped connection does not mean starting a long upload over again. The pieces are written to a working file on the server until the upload is complete, at which point it is forwarded to YourImageShare and the working file is deleted immediately — including when the upload is refused or fails. An upload abandoned part-way leaves its pieces behind; those are deleted automatically after 24 hours. Uploads of 8 MB or less are forwarded in a single request and are never written to disk there. If you use your own API key none of this applies, because nothing passes through that server at all.
its link, and offers no private upload. The extension asks you to confirm this before the first upload, and that confirmation can be turned back on in Options if you dismissed it.
once to check the upload still exists, and forgets the link if the host reports that it is gone. This request carries no cookies and no identifying information.
What the extension does not do
- No analytics, telemetry, crash reporting or usage tracking of any kind.
- No accounts, sign-in or user identifiers.
- Nothing is sold, shared or transferred to anyone, for any purpose.
- Page content is not read, collected or transmitted. The extension runs code in pages in order to measure them, scroll them and draw its own overlay while capturing; it does not inspect or send what is on them. The one exception is described below, and happens only when you ask for it.
- Browsing history is not read. A capture records the URL and title of the page it came from, so the library can show where it came from — that is stored locally with the capture and is never transmitted.
Connecting your account
If you press Connect my YourImageShare account, the extension opens yourimageshare.com in a tab, waits for you to sign in if you are not already, and reads your API key from your account page so you do not have to copy it by hand. The key is saved in your settings, exactly as if you had pasted it.
This is the only time the extension reads the contents of a page. It happens only when you press that button, only on that one page of that one site, and it reads only the key. Nothing is injected into any page until you press it, and nothing at all for anyone who never does.
You are signed in on YourImageShare's own page. The extension never sees, fills or stores your email or password, and nothing about the sign-in is sent anywhere. Copying the key yourself remains available, and is the fallback whenever this cannot find it.
Removing something you have shared
Deleting a shared item from your library also removes the uploaded copy, through YourImageShare's own delete endpoint. If you have your own key the request goes directly from your browser; if the upload was made with the shared key, only that key can remove it, so the request goes through blossom-screenshot.loudhost.net.
The host serves uploads through a CDN, and a copy already cached at an edge can still answer for a short time after the original is gone — a measured deletion returned 410 at the host while the cached file was still served for another minute or so. The deletion itself is immediate; the cache is not ours to clear.
If you delete an upload from the host's side instead, the extension notices the next time you open that item and removes the dead link.
Permissions, and why each is needed
| Permission | Why |
|---|---|
<all_urls> | To capture and annotate any page you choose. A screenshot tool cannot know in advance which sites you will use it on. |
tabs, activeTab, scripting | To measure the page, scroll it while stitching a full-page capture, and draw the selection and recording overlays. |
tabCapture, desktopCapture, offscreen | To record a tab, a window or a screen. |
downloads | To save a capture to your Downloads folder. |
storage, unlimitedStorage | To keep your library and settings on your machine. Screenshots and recordings are large. |
clipboardWrite | To copy a capture to the clipboard when you ask. |
contextMenus, alarms | The right-click capture menu, and stopping a recording after a set time. |
Pages opened from your computer (file://) are not captured, and the extension does not request access to your filesystem.
Children
The extension is not directed at children and collects no personal information from anyone.
Changes
If this policy changes materially, the updated version will be published here with a new date before the change takes effect.
Contact
Questions about this policy, requests about data the extension holds, or anything else, can be raised through the contact form at <https://forms.gle/jFfTbjMuc58pfX3z8>. The extension's Chrome Web Store listing also carries a support link.