Zero data collection
Privacy Policy
OpenScreenShot collects nothing. There are no servers, no accounts, and no analytics.
Last updated: August 2026
Zero data collection. OpenScreenShot does not collect, store, transmit, or share any personal data, usage data, or any other information from its users.
How it works
Every part of the extension runs locally in your browser: page capture, image compositing, annotation editing, screen recording, and export. No data ever leaves your device. The extension makes no network requests of its own and declares no standing host permissions, so it has no background access to any website you visit.
Permissions
Each permission the extension requests has one narrow purpose.
| Permission | Why it is needed |
|---|---|
activeTab
|
Capture the tab you are looking at, when you click the toolbar button, press a keyboard shortcut, or pick a capture from the right-click menu. Access is granted for that one tab, for that one capture. |
scripting
|
Inject small, self-contained functions into the captured tab: measure the page height and scroll it during a full-page capture, draw the drag-to-select overlay for a region capture, and write an image to the clipboard in quick mode. Every script ships inside the package. No remote code is loaded. |
storage and unlimitedStorage
|
Keep your settings on the device, hold the capture the editor page loads, remember the last region rectangle so it can be repeated, and save an in-progress editing draft so a closed or crashed tab does not lose your annotations. A full-page screenshot can exceed the default storage quota, which is what unlimitedStorage raises. |
downloads
|
Save an export from the editor, or a quick-mode capture, to your downloads folder. The extension never reads, searches, or opens your download history. |
contextMenus
|
Add one OpenScreenShot submenu to the page right-click menu, as a second way to start a capture. The extension reads only which menu item you clicked. |
clipboardWrite
|
Copy a screenshot to your clipboard, from the editor’s Copy button or from quick mode. The extension only ever writes the screenshot you just captured or exported. It never reads what is already on your clipboard. |
offscreen
|
Run the screen-recording engine in a hidden document. MediaRecorder capture and the crash-safe IndexedDB chunk writes need a page context a service worker does not have. Always present; it adds no install-time warning. |
Screen recording
Recordings, cursor logs, and microphone or webcam streams are handled the same way as screenshots: entirely on your device. Video chunks, the cursor log, and any audio are written to IndexedDB as you record and stay there until you delete the session; nothing is ever uploaded. Recording uses two further permissions, both optional and requested only when you use the recorder.
| Permission | Why it is needed | When it is requested |
|---|---|---|
tabCapture
|
Captures the current tab’s video, and its audio if you enable the tab-audio track, for recording. | Once, the first time you click Record — a single Chrome permission prompt. |
<all_urls>
|
The optional host permission. It keeps the in-page cursor overlay and control bar alive when a recording’s tab navigates to a different origin. | Only if you turn on “Record across sites” in settings. |
The microphone and camera, when you enable them, are opened directly by your browser’s own permission prompt. The extension never sees a stream until you grant it, and the stream never leaves your device.
Third-party services
OpenScreenShot uses no third-party analytics, advertising, or data-processing services. PDF export is handled by a small writer built into the extension, so exporting a PDF makes no network request either.
Changes to this policy
If this policy changes, the updated version is published on this page with a new Last updated date.
Contact
For questions about this policy, open an issue on the GitHub repository.