Current hosted policy: https://app.devboy.pro/meet-extension/privacy


Last updated: 2026-08-10

DevBoy / Codenik Meet Recorder records a meeting only after you press the start
button. This policy covers the Chrome, Firefox and Safari packages and explains
where their behavior differs.

• Meeting audio. Chrome captures tab audio and can add your microphone.
  Firefox captures audio tracks exposed by Google Meet media elements and can
  add your microphone. Safari connects Google Meet media elements to a Web
  Audio recording destination and can add your microphone. Microphone access
  is controlled by the browser.
• Screen video. Each browser can record a screen, window, or browser tab
  selected in its system picker. Firefox and Safari start this capture only
  from their persistent recorder UI after a direct button click. The browser
  may return video without system audio.
• Meeting metadata. The extension reads the meeting URL, page title, and
  visible participant names from the supported meeting page.
• Workspace authentication. Requests use the existing session cookie for
  the selected DevBoy or Codenik instance. The extension does not read or store
  your password.

The Firefox manifest classifies this transmission as authenticationInfo,
browsingActivity, personalCommunications, personallyIdentifyingInfo, and
websiteContent.


Nothing is recorded before an explicit start action. A successful start also
requires an authenticated workspace and an organization. Google Meet audio
recording requires a live media-element audio track. Screen recording requires
a live video track from the browser picker and any audio source selected in
Settings. If a required track is absent, Firefox and Safari stop before
creating a server-side recording. Safari also requires a direct confirmation
inside the Google Meet page before it starts meeting-audio capture.

The extension attempts to post a recording notice in the meeting chat. This is
best effort and may fail if the chat is unavailable. You remain responsible for
obtaining any consent required by your jurisdiction or organization.


The background extension context creates a recording in the selected DevBoy or
Codenik workspace. Audio or video chunks are uploaded through presigned URLs to
that workspace's configured object storage. The workspace processes the data
for transcription and meeting notes and applies its own access and retention
settings.

The Firefox and Safari capture owners do not send network requests to the
workspace or object storage. They pass chunks to the extension background
context, which validates the recording owner and performs authenticated
requests.


All packages store extension settings and current recording state in browser
storage.

• Chrome can buffer interrupted chunks in IndexedDB for the Recovery page.
• Firefox keeps pending chunks in memory for the active session. It does not
  promise recovery after the tab or browser closes.
• Safari keeps pending chunks in memory for the active session. It does not
  promise recovery after the capture page or browser closes.

The Chrome package can send error diagnostics to Meteora's self-hosted Sentry
service at sentry.meteora.pro when that instance supplies a Sentry
configuration. Diagnostics can include the error message and stack, extension
component, build release, distribution channel, and product brand. They are
used to investigate extension failures and not for advertising.

The Firefox and Safari packages do not initialize Sentry or request the Sentry
host. Recording in these packages works without diagnostic telemetry.

• No advertising identifiers or data brokers.
• No sale of meeting data.
• No capture of pages outside the supported meeting page.
• No keystroke logging.
• No hidden background recording.

The extension uses meeting data only to record a meeting into the selected
workspace, upload it, transcribe it, produce meeting notes, show recording
state, and recover supported interrupted uploads.

• DevBoy: support@devboy.pro
• Codenik: support@codenik.ru