Skip to content

Instantly share code, notes, and snippets.

@tutecode
Created March 23, 2026 21:15
Show Gist options
  • Select an option

  • Save tutecode/ae4a01c0212344a61d359ae3bb44ded8 to your computer and use it in GitHub Desktop.

Select an option

Save tutecode/ae4a01c0212344a61d359ae3bb44ded8 to your computer and use it in GitHub Desktop.
Privacy Policy — Video Player Chrome Extension

Privacy Policy — Video Player Extension

Last updated: March 23, 2026

Overview

Video Player ("the Extension") is a Chrome browser extension that helps users compare AI-generated video pairs side by side and write pairwise evaluations with scorecard ratings, justifications, and feedback.

This privacy policy describes how the Extension collects, uses, and protects user data.

Data Collection

Personally identifiable information

  • Evaluator name: Collected once on first submission and stored locally using Chrome's storage.local API. This name is included when submitting evaluations to the user's own Supabase database instance (see Third-Party Services below). It is not shared with any other party.

Website content

  • Video URLs, evaluation criteria, and task instructions are extracted from the active evaluation platform page to populate the extension's comparison viewer. This data is stored locally and is not shared with any third party.

What is stored locally

  • Evaluator name for tagging evaluation submissions
  • Pairwise evaluation scores and justifications you enter while comparing videos
  • Feedback text you write for each model
  • Video rating checklist state for per-item scoring
  • Evaluation history with autosave snapshots
  • UI preferences such as settings and view state
  • Temporary sync data used to keep multiple extension windows in sync (e.g., the Text View and Eval View)

What is NOT collected

  • No authentication credentials or passwords
  • No browsing history or web activity outside of the active tab
  • No location data
  • No financial, health, or payment information
  • No analytics, telemetry, or usage tracking
  • No personal communications

Permissions Justification

Permission Purpose
activeTab Extract evaluation data (video URLs, criteria, instructions) from the currently active tab and inject autofill scripts to populate evaluation forms with scores and feedback
tabs Find open evaluation platform tabs for autofill injection and open new tabs for the viewer, text-view, and eval-view windows
scripting Inject content scripts into evaluation platform tabs to extract form data and autofill evaluation scores and written feedback
storage Persist evaluation state (scores, justifications, feedback, settings, history) across sessions and synchronize data between the viewer, text-view, and eval-view windows
declarativeNetRequest Modify response headers (CORS) on video file requests so cross-origin videos can be loaded and analyzed in the extension's video player
Host permissions (<all_urls>) Fetch and play video files hosted on various content delivery domains, and inject autofill scripts into the evaluation platform tab

Remote Code

The Extension does not use any remote code. All JavaScript and resources are bundled within the extension package. ML inference runs locally via bundled ONNX Runtime WebAssembly binaries and Transformers.js.

Third-Party Services

The Extension can optionally submit evaluations to a Supabase database instance configured by the user. This is an opt-in feature that requires the user to set up their own Supabase project and provide their own API credentials. Data submitted includes: evaluator name, evaluation scores, justifications, feedback, video URLs, and task instructions. No data is sent to any Supabase instance unless the user explicitly configures one and clicks Submit.

No other third-party services, APIs, or servers are contacted by the Extension.

Data Sharing

The Extension does not sell, transfer, or share any user data with third parties for any purpose. The optional Supabase submission sends data only to the user's own self-managed database.

Changes to This Policy

If this privacy policy is updated, the changes will be reflected in this document with an updated date.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment