Information We Collect
OBSB collects minimal information to function:
- Google account profile — your name and email address, only if you sign in with Google. Used to identify your session and label uploads.
- Recording metadata — file names, sizes, and timestamps stored locally in the extension's storage to display your recording history.
- No analytics or tracking — we do not embed third-party analytics, telemetry SDKs, or ad networks in the extension.
How Recordings Are Processed
All screen, microphone, and camera capture happens locally in your browser using the standard Web APIs (MediaRecorder, getDisplayMedia). Video data is never sent to OBSB servers.
If you choose to upload a recording, it is sent directly to your own Google Drive account via Google's APIs. OBSB does not receive, proxy, or store a copy of the video file.
Google Drive Access
When you sign in with Google, OBSB requests the drive.file OAuth scope. This grants OBSB permission to:
- Create new files in your Google Drive (recordings you upload).
- Read and delete only the files OBSB itself created — not your other Drive content.
You can revoke this access at any time in your Google Account permissions or by signing out inside OBSB.
Data Sharing
We do not sell, rent, or trade your personal data. The only third-party service involved is Google (for sign-in and Drive uploads), which is governed by Google's Privacy Policy.
Shareable links you generate point to files in your Google Drive. You control who has access to those links.
Local Storage
OBSB uses Chrome's chrome.storage.local API to store your preferences and recording history on your device. This data stays on your machine and is not transmitted to us.
Children's Privacy
OBSB is not directed at children under 13. We do not knowingly collect personal information from children.
Changes to This Policy
We may update this policy occasionally. The "Last updated" date at the top will reflect any changes. Continued use of OBSB after changes constitutes acceptance of the updated policy.
Contact
Questions about this policy? Open an issue in the GitHub repository or email us at je.biniyam@gmail.com.