Privacy Policy

1.1 Recordings

All video and audio recordings are created and stored locally on your device. We do not upload, access, transmit, or store your recordings on any external servers. Your recordings remain completely private and under your control at all times.

1.2 Extension Settings

We store your extension preferences (such as selected camera, microphone, and recording mode) locally in your browser using Chrome's storage API. This data never leaves your device.

1.3 Technical Data

The Extension uses standard Chrome Extension APIs for functionality. No personal information, browsing history, or usage analytics are collected or transmitted.

Your information is used exclusively to provide the screen recording functionality:

• To capture and process your screen, camera, and audio recordings
• To store recordings locally on your device
• To convert recordings between video formats (WebM to MP4)
• To remember your device and quality preferences
• To manage storage and cleanup old recordings when needed

We do not use your information for advertising, marketing, analytics, or any other purpose beyond providing the core functionality of the Extension.

All recordings and data are stored locally on your device using:

• Chrome Storage API: For extension settings and recording metadata
• Local Storage: For temporary processing and preview functionality
• Downloads Folder: For saved video files you choose to download

Automatic Cleanup: To prevent storage issues, the Extension automatically removes old recordings when storage usage reaches 85% (keeps 5 most recent) or 95% (keeps 2 most recent). You can manually delete recordings at any time.

We do not share, sell, rent, or transmit your data to any third parties.

The Extension operates entirely on your device. No recordings, personal information, or usage data are sent to external servers, analytics services, or third-party companies.

Third-Party Libraries: The Extension uses FFmpeg.js for video conversion, which runs entirely in your browser without any external connections.

The Extension requires certain Chrome permissions to function:

We only request permissions that are absolutely necessary for the Extension's functionality. No permission is used for tracking, advertising, or data collection purposes.

Since all data processing happens locally on your device, your recordings benefit from the security measures provided by your operating system and browser:

• Recordings are stored in your browser's secure storage area
• No data transmission over the internet
• Shadow DOM isolation prevents conflicts with other extensions
• Chrome's extension security sandbox protects your data

Your Responsibility: Since recordings are stored locally, we recommend:

• Regularly backing up important recordings
• Using device encryption for sensitive content
• Keeping your browser and operating system updated
• Deleting recordings you no longer need

You have complete control over your data:

• Access: All your recordings are accessible through the Extension's recordings page
• Delete: You can delete any recording at any time from the recordings page
• Export: Download recordings in WebM or MP4 format
• Revoke Permissions: Manage permissions in Chrome settings at any time
• Uninstall: Removing the Extension will delete all stored data

The Extension is not directed at children under the age of 13. We do not knowingly collect information from children. If you believe a child has used the Extension, please contact us.

We may update this Privacy Policy from time to time. Any changes will be reflected in the “Last updated” date at the top of this page. Continued use of the Extension after changes constitutes acceptance of the updated policy.

Material changes will be communicated through the Extension's release notes system.

On our marketing site (including the guides at /blog), you may optionally sign in with Google to post a comment. Comments are stored in Google Firebase (Authentication + Cloud Firestore) in project showesome-recorder: comment text, your Firebase user id, display name, submission time, and moderation fields (for example whether a comment is approved for public display).

This is separate from the Chrome extension's optional cloud connections (for example Google Drive). Drive authorization uses the extension's own OAuth client and scopes; blog comments use Firebase Authentication on the website.

You can request deletion of your comment content by contacting us at the email below. Deleting your Firebase Auth account for the site may limit future sign-ins; moderation and legal retention may still apply where required.

If you have any questions, concerns, or feedback about this Privacy Policy or the Extension's data practices, please contact us: