Current Video Clipper 1.12.1 — local helper 1.8.1. Updated 26 October 2026.

The interface language preference stays in local storage. English/Italian catalogs are included in the extension; no text is sent to a translation service. First installation opens a local guided setup page. The separate Windows installer embeds the verified helper 1.8.1 binary. On your Install action, if missing tools are allowed, it downloads the fixed FFmpeg 8.1.2 archive from gyan.dev and verifies its size and SHA-256 before use. The vendor receives an ordinary download request (IP address and installer user-agent), never your videos, page addresses or browser cookies. Installed tools and licenses stay on this computer. The extension does not start the installer or download tools automatically.

When activated, Video Clipper reads the chosen tab's accessible HTML5 players: source addresses, title, duration, playback position and geometry. It uses active-tab access; optional access to embedded-player domains is requested through your actions. Persistent access to all websites is not granted by default.

Saving sends the selected page/frame/media addresses, title, intervals, output settings and destination to the native helper on your own computer. yt-dlp contacts source websites and media/CDN servers; FFmpeg/ffprobe processes media locally. Those servers receive normal network information such as your IP address and applicable request headers. The full source may be downloaded before trimming. Video Clipper has no publisher-operated video upload, cloud editing or analytics service and requires no Video Clipper account.

Browser-session access is optional, initially disabled, site-scoped and revocable in settings. Only cookies applicable to authorized addresses and the selected tab's cookie store, partition and first-party context may be sent to the local job. Another browser profile is not read. Advanced discovery has separate consent: it temporarily observes relevant requests in the selected tab/frames and keeps candidates in memory for selection. It does not collect arbitrary authorization headers or other tabs' browsing history. Revocation prevents future collection; it cannot retract session data already handed to a running local job.

Cookie values/session tokens are not stored in preferences, history or diagnostic reports. The helper may use a temporary cookie jar, scoped to authorized requests and redirects. Temporary data is cleaned after completion, error or cancellation; cleanup failures are reported. Exported videos remain in your chosen destination. This policy concerns the current extension/helper pair, not older releases' legacy protocols.

Local extension storage holds preferences, consented domains, output profiles/site associations, watermark images, projects and recent-result history. Projects retain clip names, hashed source/page identifiers, intervals and output settings so they can resume when the same video is available. History contains result names, intervals, status and local output paths, with configurable retention; clearing it removes references, not exported files. Private-window projects and jobs are not added to persistent projects/history. An exported file is still written to disk when you save from a private window.

Watermark images are converted locally to bounded PNG data, kept in local extension storage and sent only to the local export job that uses them. Diagnostic exports omit the image. Removing the current image does not remove copies retained in an existing project/profile or a settings backup you previously exported. Settings backups are user-requested JSON files and may include local paths, names, site associations and images; review them before sharing.

Diagnostic reports omit cookie values, source addresses, titles and local paths. They can contain versions, platform/browser information, configuration flags, anonymized event/error codes, durations and permission/check results. Reports remain local unless you choose to share them. Copying file paths or exporting a settings backup is a separate explicit action.

Settings → Updates makes an optional, user-requested HTTPS call to the GitHub releases API after host permission is granted. It sends no cookie/session credentials, video addresses, titles or local paths; GitHub receives ordinary connection information such as your IP address. It compares published versions with the installed extension/helper and offers links. It neither downloads nor installs updates automatically. Visiting GitHub/Mozilla download pages is subject to those services' privacy practices.

Firefox's theme palette, or native browser light/dark colors, is used locally. Browser vendors, Mozilla Add-ons, GitHub, dependency distributors and source websites operate independently under their own policies. The extension is not a browser-wide privacy or anonymity tool.

Earlier releases — original policy retained for reference

Video Clipper 1.3.1 and Windows helper 1.3.0 — data handling

When you activate the extension, it reads the selected tab's accessible HTML5 players: source URLs, title, duration, current time and geometry. It uses activeTab access and, only when you request it, optional host access for displayed embedded-player domains. It does not request persistent access to every website by default.

When you save a clip, the selected page/frame/media URLs, title, timestamps and export preferences are sent to the separately installed native helper on your own computer. yt-dlp contacts the source page, video hosts and related media-delivery servers; FFmpeg/ffprobe processes media locally. Those hosts receive normal request information including your IP address and applicable headers such as the referrer. Video Clipper does not upload video to a publisher-operated editing service and has no analytics or telemetry service.

Use Firefox session for this site is optional and off by default. Its separate consent window identifies the authorized site/media domains and requests cookies plus the relevant host permissions. The background reads only cookies applicable to authorized URLs, explicitly limiting the query to this tab's cookie store and to unpartitioned cookies or the top-level site's partition. Cookies from other stores, unrelated partitions or nonempty legacy firstPartyDomain isolation are not used. The scope can be revoked in extension settings; removing browser permissions also invalidates the related consent. Revocation prevents future jobs and collection still in progress; it does not retroactively remove a session already passed to a running job.

Only the consent/domain list is saved in extension preferences. Cookie values are sent only to the local export job, written to its temporary yt-dlp cookie jar and used for matching-domain media requests. They are not stored in clip history, UI views or diagnostic records. Cleanup is attempted after success, failure and cancellation; a cleanup failure is reported. The 1.3.x extension's new protocol does not read Firefox profile files. For compatibility, the helper's legacy protocol used by older extensions retains the previously documented limited X/FapFolder profile-cookie behavior.

Destination, quality, layout and panel geometry stay in local Firefox storage. Clip history stores up to 30 recent results for up to 30 days, including title, interval, completion status and local output path. Source URLs and cookies are not stored in history. Clearing history removes references, not saved videos. Exported files remain in your chosen folder. Temporary media is created on the destination volume and cleaned after the job, with cleanup failures reported.

No Video Clipper account is required. Firefox, Mozilla Add-ons, GitHub, dependency distributors and source websites apply their own privacy practices. This policy describes the extension and local helper, not those independent services.