~/openloom/privacy

Privacy Policy

Last updated: March 7, 2026

Overview

OpenLoom is an open-source screen recorder available as a Chrome extension and desktop application. It is designed with a privacy-first approach: your recordings are stored on your own infrastructure, not on OpenLoom servers. We do not operate any centralized servers that collect, store, or process your video recordings or personal data.

Data We Collect

OpenLoom does not collect any personal data. The extension and desktop app run entirely on your device. Specifically:

  • No analytics or telemetry in the extension — the Chrome extension does not track usage, page views, or feature engagement. (The openloom.live marketing website uses privacy-friendly analytics — see below.)
  • No account system — OpenLoom does not require you to create an account or sign in to any OpenLoom service.
  • No advertising — there are no ads, trackers, or third-party marketing scripts.
  • No crash reporting — errors stay on your device.

Video Recordings

When you record your screen with OpenLoom, the recording is processed locally on your device. When you choose to upload a recording, it is sent directly from your browser or app to your own backend infrastructure — one of:

  • Firebase (Google Cloud) — your own Firebase project
  • Supabase — your own Supabase project
  • Convex — your own Convex deployment

OpenLoom never acts as an intermediary. Video data flows directly from your device to your chosen backend. You retain full ownership and control over your recordings, including the ability to delete them at any time through your backend provider's dashboard or through the OpenLoom interface.

Chrome Extension Permissions

The Chrome extension requests the following permissions, each for a specific functional purpose:

sidePanel

Opens the recording controls and video library in Chrome's side panel.

offscreen

Creates an offscreen document to handle screen capture and media recording. Chrome extensions cannot access media APIs directly from the service worker, so an offscreen document is required.

storage

Persists your settings and backend configuration locally in Chrome's extension storage.

unlimitedStorage

Allows IndexedDB to store video recordings locally before upload. Screen recordings can be large (hundreds of MBs), and the default 10 MB quota is insufficient.

alarms

Keeps the service worker alive during active recordings. Chrome's service worker can be terminated after 30 seconds of inactivity, which would interrupt an ongoing recording.

Host permissions (optional)

Network access to your chosen backend provider's APIs (Firebase, Supabase, or Convex). These permissions are requested only when you configure a specific backend provider during setup. The extension only communicates with the provider you select.

Shared Video Links

When you share a recording, OpenLoom generates a link pointing to openloom.live. The web viewer at this URL is a static site hosted on GitHub Pages. It does not have a server or database. When someone opens a shared link, the viewer fetches the video directly from your backend using credentials encoded in the URL. The openloom.live site itself does not store, log, or process any video data.

You may optionally enable password protection for shared links. Passwords are used to derive an AES-256-GCM encryption key client-side. The password is never transmitted or stored.

Website Analytics

The openloom.live marketing pages (home, technology, pricing, and this privacy page) use GoatCounter, an open-source, privacy-friendly analytics tool. GoatCounter:

  • Does not use cookies
  • Does not collect personal data or IP addresses
  • Does not require a consent banner
  • Is fully GDPR-compliant

Video player pages are excluded. When someone watches a shared recording at openloom.live/v/..., no analytics script runs. We do not track who watches your videos or how often they are viewed.

Third-Party Services

OpenLoom connects only to the backend provider you explicitly configure. Each provider has its own privacy policy:

Data Retention

Since all data is stored on your own infrastructure, data retention is entirely under your control. You can delete recordings at any time through the extension's library, the desktop app, or directly through your backend provider's dashboard. Uninstalling the extension removes all locally stored settings and cached data.

Open Source

OpenLoom is fully open source. You can review the complete source code, including all network requests and data handling, on GitHub.

Changes to This Policy

If we make changes to this privacy policy, the updated version will be posted on this page with a revised date. Since OpenLoom is open source, all changes are publicly visible in the commit history.

Contact

If you have questions about this privacy policy or OpenLoom's data practices, please open a GitHub issue.