Plume — Privacy Policy

Last updated: 2026-05-19

Plume is a Chrome extension that records your screen and microphone, uploads the resulting video to Google Drive, and copies a shareable link to your clipboard. It is developed and maintained by Bolt IoT for internal team use.

What Plume accesses

  • Your Google account identity. Plume reads your name, email, and profile picture once at sign-in (via Google's userinfo endpoint). Your email is used to label your uploads (each user gets a Drive subfolder named after their email) and to verify that you belong to an allowed domain.
  • Your screen and microphone. Captured only while you are actively recording, and only after you explicitly start a recording in Plume. Recording stops as soon as you click stop or revoke the share via Chrome's banner.
  • Your Google Drive. Plume operates under the https://www.googleapis.com/auth/drive.file OAuth scope, which is the most restricted Drive scope. Plume can see and modify only the files it has created itself (your Plume recordings, and the per-user folder Plume creates inside the configured parent). Plume cannot read your other Drive files, your photos, your documents, or anything else in your Google account.

What Plume sends to third parties

  • Recordings are uploaded to Google Drive — your own Google account, or the Shared Drive your team's Plume deployment is configured to use. Plume does not send video data anywhere else.
  • Authentication is handled by Google's standard OAuth 2.0 flow. Plume does not see your password.
  • No analytics, no tracking, no telemetry. There is no Plume backend. There is no third-party service in the data path other than Google.

What Plume stores

  • On our servers: nothing. Plume has no backend.
  • In your browser: a small amount of session data in chrome.storage.local — your signed-in email/name, the ID of the Drive folder Plume created for you, the rotating-tip index, and the version-gate cache. This data never leaves your machine.
  • In your Google Drive: your recordings, in a folder named after your email.

Data retention

Your recordings remain in your Google Drive until you delete them. Plume keeps no copies, no metadata, no backup. Uninstalling Plume from your browser does not delete the recordings you have already made — they remain in Drive under your control.

Sharing

When a recording is uploaded, Plume sets the file's permissions to "anyone with the link can view" so you can paste the link in chat. If your Workspace administrator has disabled anyone-with-link sharing, the file is still uploaded but is viewable only by people who already have access to the parent Drive folder. Plume tells you which case happened.

Permissions Plume requests, and why

  • identity — sign in with Google.
  • storage — remember your session locally.
  • offscreen — host the chunked Drive upload (MV3 service workers don't have XHR).
  • desktopCapture — show the screen / window / tab picker.
  • tabs — present a picker for tab capture.
  • notifications — tell you "link copied" when upload finishes.
  • clipboardWrite — copy the Drive link to your clipboard automatically.
  • downloads — used in TEST_MODE only, to save a recording locally instead of uploading.
  • host permissions for googleapis.com and oauth2.googleapis.com — talk to Google's auth and Drive endpoints.

Contact

Questions about Plume's data handling: ppv@boltiot.com.