Privacy Policy
Last updated: July 29, 2026
ScreenKit (“the Extension”) is a free Chrome extension for screen recording, screenshots, annotation, and local export. This policy explains what data the Extension handles and how, including its optional YouTube and Google Drive upload features.
Summary
ScreenKit works entirely on your device by default. We do not operate servers that receive your recordings, screenshots, or personal information. The Extension does not require an account to use its core capture features.
The Extension includes an optional, opt-in feature to upload recordings directly from your browser to your own YouTube or Google Drive account. Uploads go directly to Google — ScreenKit has no backend and never receives your recording content.
Information the Extension processes locally
When you use ScreenKit, the following data may be processed only on your computerinside Chrome:
- Screen, window, tab, or camera content you choose to record or capture
- Audio from your microphone and/or system audio, if you enable those options
- Annotations you draw (shapes, text, arrows, etc.)
- Settings such as theme, default quality, and selected camera/microphone devices
- Temporary recording buffers stored in browser storage while a recording is in progress
Exported files are saved to your computer via Chrome’s download mechanism, or copied to your clipboard when you choose that export option. All recording, encoding, and annotation happen locally before any data ever leaves your device.
Optional cloud uploads — YouTube and Google Drive
ScreenKit includes an opt-in feature to upload finished recordings to your own YouTube channel or Google Drive. This feature is entirely optional — the Extension works fully without it.
Uploads are initiated only by you and only when you explicitly click the upload button in the preview screen. Your recording bytes travel directly from your browser to Google’s servers via HTTPS. ScreenKit operates no intermediate server and never receives your recording content.
YouTube uploads
- OAuth scope:
https://www.googleapis.com/auth/youtube - Your recording is uploaded to your own YouTube channel as an Unlisted video (not publicly searchable).
- It is added to a playlist named my-screen-record (also Unlisted), created automatically on first use.
- We read your YouTube channel name and channel ID solely to label the connected account in the Extension UI.
Google Drive uploads
- OAuth scope:
https://www.googleapis.com/auth/drive.file(access limited to files the Extension itself creates — not your entire Drive) - Your recording is uploaded to a folder named my-screen-record in your own Google Drive.
- The file is set to “anyone with the link can view” — shareable by link, not publicly listed.
- We read your Google account email address and display name solely to label the connected account in the Extension UI.
Sharing and disclosure of Google user data
When you use the optional upload feature, your recording is transferred toGoogle LLC (YouTube Data API v3 or Google Drive API v3) using your own Google account credentials. This transfer is subject toGoogle’s Privacy Policy.
ScreenKit does not:
- Transfer your Google account data or recordings to any party other than Google
- Store your recordings, OAuth access tokens, or Google account information on ScreenKit servers (no such servers exist)
- Share your Google user data with advertisers, analytics services, or any other third parties
- Use your Google account data for any purpose other than completing the upload you explicitly requested
Data that is shared with Google when you choose to upload:
- The recording video file you select for upload
- A title and description for the video (defaulting to “Recorded with ScreenKit.”)
- OAuth access tokens, which are sent directly to Google’s API endpoints from your browser and are never routed through ScreenKit
OAuth tokens are stored only in Chrome local storage on your device and used solely to authenticate upload requests to Google APIs on your behalf.
Data protection mechanisms
We apply the following technical measures to protect your data, including any sensitive Google user data accessed through OAuth:
- Encryption in transit: All communications with Google APIs (YouTube, Google Drive, and OAuth token endpoints) use HTTPS (TLS), ensuring data is encrypted in transit.
- Minimal OAuth scopes: The Extension requests only the scopes strictly necessary for each feature. The
drive.filescope limits Drive access to files the Extension created — not your full Drive contents. - Isolated credential storage: OAuth tokens are stored exclusively in Chrome’s
chrome.storage.local, which is sandboxed to the Extension and inaccessible to web pages or other extensions. - User-controlled revocation: You can disconnect your Google account at any time from the Extension settings. Disconnecting revokes the token with Google and removes it from local storage.
- No server-side storage: ScreenKit has no backend servers. No recording content, OAuth tokens, or account information are ever transmitted to or stored on ScreenKit infrastructure.
- Local-first processing: All recording, encoding, and annotation happen entirely in your browser before any data leaves your device. Only the final file is uploaded, and only when you explicitly choose to.
What we do not collect
ScreenKit does not:
- Upload recordings or screenshots to ScreenKit servers (we operate no such servers)
- Collect your name, email, or Google account information for purposes other than labeling your connected upload account in the Extension UI
- Track browsing history for advertising or analytics
- Sell or share your data with any third party other than Google (when you explicitly initiate an upload)
- Retain Google user data beyond what Chrome local storage holds for your connected upload session
Permissions
Chrome permissions used by the Extension:
| Permission | Purpose |
|---|---|
activeTab | Capture the tab you are using when you start a screenshot or recording |
clipboardWrite | Copy exported images to your clipboard when you request it |
downloads | Save video and image files to your device |
identity | Authenticate with your Google account via OAuth for optional YouTube and Google Drive uploads |
offscreen | Run media capture and image processing (required by Chrome MV3) |
scripting | Show the in-page overlay for region select, full-page capture, and live annotation |
storage | Save your preferences, in-progress recording data, and upload connection state locally |
tabCapture | Record screen/tab/window audio and video when you start recording |
Host access (http, https, file) | Enable capture overlays and screenshots on pages you visit |
Data retention
- Settings persist in Chrome local storage until you uninstall the Extension or reset settings.
- In-progress recordings are stored temporarily in IndexedDB during capture and removed after you finish or cancel.
- Exported files remain wherever you save them on your device; ScreenKit does not delete them.
- OAuth tokens (if you connect YouTube or Google Drive) persist in Chrome local storage until you disconnect the account from the Extension settings or uninstall the Extension.
- Upload history (video IDs, Drive file IDs, account labels) is stored locally in Chrome storage for display in the Extension UI and is never sent to ScreenKit.
Children’s privacy
ScreenKit is not directed at children under 13. We do not knowingly collect personal information from anyone.
Changes
We may update this policy if the Extension changes. The “Last updated” date at the top will reflect the revision.