Privacy Policy
01. Overview
LagSync is built with a "Privacy First" philosophy. We believe that a utility tool for your browser should do exactly what it says—sync your audio—and nothing else. Everything runs on your device. Nothing is collected automatically, ever. The single exception is a bug report that you personally compose, review, and send (see section 03).
02. Data Collection
LagSync does not track your browsing history, does not use cookies, does not include analytics, and never transmits anything in normal use. There is no background reporting of any kind.
03. Optional Bug Reports
Since version 1.4.0 (Chrome and Edge), you can send a bug report from inside the extension. This is entirely optional and only ever happens when you press Send. A report contains:
- The hostname of the video site the report is about (for example
www.youtube.com)—never the full address, page title, or any page content. - Technical state of the extension itself: version, browser, your delay settings, and the delay engine's own diagnostic counters.
- Your optional comment, and an optional email address if you would like a reply. The email is used solely to answer your report.
The exact data is shown to you before sending—what you see in the preview is byte-for-byte what is transmitted. Reports are stored in a private issue tracker accessible only to the developer and are used only to diagnose and fix problems.
04. Permissions
To function, LagSync requires the following permissions:
storage: Used strictly to remember your delay presets and settings.scripting+ a curated list of video sites: Used to inject the delay engine into supported video platforms. Since 1.3.0 LagSync no longer asks for access to every website—it ships with access to a fixed list of major video sites, and anything else is yours to allow one site at a time. We only interact with HTML5 media elements.activeTab: Lets the popup show which site you are on and offer to enable LagSync there. No tab content is read.
05. Local Storage
All configuration data (your custom offsets, toggles, and preferences) is stored within your browser's extension storage. This data never leaves your device, other than syncing between your own browsers via your browser vendor's built-in settings sync.
06. Third Parties
We do not sell or share data with third parties. Bug reports (section 03) are transported via Cloudflare and stored on GitHub in a private repository; both act purely as infrastructure providers and the data is used for nothing except handling your report. If you click a donation link provided within the extension (e.g., Ko-fi or PayPal), you will be subject to that specific platform's privacy policy.
Last Updated: August 2026
← Back to Home