FramedShot processes screenshot and tab recording data locally in your browser to provide capture, editing, trimming, and export features. FramedShot does not sell user data and does not send screenshot or recording content to external servers.
1. Data we process
- Visible-tab screenshot image data captured when you trigger the extension.
- Visible-tab video and tab audio data captured when you start a recording.
- Optional area-selection coordinates when you use area capture.
- User preferences (for example: colors, padding, shadow, format, export settings).
- Optional local UI state (for example: dismissed tips or saved defaults).
- Email address — only if you opt in via the Supporter Badge form in the extension popup. See section 8.
2. How data is used
- To render and edit screenshots inside the extension editor.
- To record, preview, trim, and export a tab recording after explicit user action.
- To preserve your selected settings between sessions.
- To support user-initiated area selection via a temporary page overlay.
3. Storage and transfer
- Screenshot handoff data, editor preferences, saved defaults, and feature settings are stored locally using Chrome extension storage on your device.
- Tab recordings are written as local recording metadata and video chunks in browser IndexedDB while you preview, trim, frame, or export the recording.
- Exporting or discarding a recording from the recording editor removes that local recording entry from FramedShot's IndexedDB storage.
- No remote code is executed.
- No screenshot content, recording content, tab audio, or page text is transmitted to FramedShot servers.
- The Supporter Badge form transmits only your email address (opt-in). See section 8.
4. Third-party sharing
FramedShot does not sell, rent, or share user data with third parties.
5. Permissions used
- activeTab — capture the current visible tab only after explicit user action.
- scripting — inject a temporary local overlay for user-initiated area selection capture.
- storage — save preferences and temporary screenshot/editor state locally.
- tabCapture — record the current tab only after you press Record Tab.
- offscreen — run the hidden local recorder document required by Chrome Manifest V3.
6. Retention and control
- You can reset saved settings from inside the extension.
- You can export or discard a tab recording from the recording editor. Discard removes the local recording data.
- Uninstalling the extension removes extension data according to Chrome behavior.
7. Video recording
Tab video recording is user-initiated. FramedShot captures the current browser tab only after you choose Record Tab. While recording is active, Chrome provides a tab capture stream to FramedShot's local recorder document using the tabCapture and offscreen extension permissions.
Recording metadata, WebM chunks, and tab audio, when present, are stored locally in browser storage/IndexedDB while you preview, trim, frame, export, or discard the recording. FramedShot does not upload tab recordings, recording chunks, tab audio, or page text to FramedShot servers. Exported WebM files are saved locally by you through the browser's download flow.
8. Supporter Badge email collection
If you submit your email via the Supporter Badge form in the extension popup, we store that address in a MongoDB database to send your badge and occasional product updates ahead of our Product Hunt launch. This is entirely opt-in.
- We store your email address and the timestamp of submission only. Nothing else is included — no screenshot data, no browsing activity, no device identifiers.
- Your email is sent to our backend, which writes it to the database. The database credentials are never shipped in the extension, so the email list cannot be read, modified, or deleted from the browser.
- We will not sell or share your email with third parties.
- To be removed from the list, email andrei.projects@proton.me with the subject "Remove my email".
9. Contact
For privacy questions, contact andrei.projects@proton.me.