At Reframe, we respect your privacy and are committed to protecting your personal data. Reframe is designed as a fully local-first application, meaning all processing happens directly on your device and no media is ever transmitted to external servers.

1. Data Collection

Reframe does not collect, transmit, or process any personal data on external servers. All video processing is performed entirely on-device using FFmpeg.wasm. No raw video, audio, metadata, or derived content ever leaves your browser.

Reframe embeds Datadog Real User Monitoring (RUM) to collect anonymous performance and error metrics — page views, load times, and JavaScript errors. Session replay is disabled. This telemetry never includes your video files, audio, filenames, exported content, or any other media you work with in the app. See Telemetry & Diagnostics below for details. Reframe does not embed advertising scripts.

2. File Handling

All files remain in your browser’s runtime memory or local processing context only. Reframe does not upload, store, or persist files on any server.

Files are only temporarily accessible while you are actively using the application. Any persistence (such as downloads or exports) is explicitly initiated by you. Temporary browser caching may occur as part of standard browser behavior and is not controlled by Reframe.

3. Telemetry & Diagnostics

Reframe uses Datadog RUM to collect anonymous, aggregate telemetry: page views, load performance, and JavaScript errors. This helps us catch bugs and performance regressions across browsers we don't personally test on.

Session replay is explicitly disabled — Datadog never records or reconstructs what the editor looked like during your session. Telemetry is limited to metrics and error events; it does not and cannot include your video or audio files, filenames, export settings, or any content you create or edit in the app, since that data never leaves your browser in the first place (see Data Collection above).

4. Third-Party Dependencies

Reframe uses FFmpeg.wasm to perform local media processing within the browser. This library runs entirely on your device and does not send data externally.

Any additional dependencies (such as CDNs for initial asset delivery) are used solely for application loading and do not receive user media or personal data.

5. Security Model

Reframe operates entirely within the browser sandbox. All processing is isolated to the client environment and requires no server communication for core functionality.

This design ensures that your media never leaves your device, and security is enforced by the browser’s built-in execution boundaries.

6. Browser Storage Usage

Reframe does not use persistent storage mechanisms such as localStorage or IndexedDB for storing user media.

If your browser temporarily caches assets or processing data, this is handled entirely by the browser and can be cleared through standard browser settings.

7. User Rights & Control

Because Reframe does not store or transmit user data, there are no server-side records to access, modify, or delete. Users retain full control of their data at all times, as all processing occurs locally.

8. Open Source Verification

Reframe is open source and publicly verifiable. The entire codebase, including processing logic, dependency usage, and exactly what telemetry is collected and how, can be audited on GitHub to confirm its local-first architecture.

9. Policy Updates

This Privacy Policy may be updated as Reframe evolves. Changes will be reflected in the public repository, and the latest version will always be available on this page.