Really appreciate this question privacy is something we take seriously, not just as a checkbox.

Here's the transparent breakdown:

• No tracking of videos watched we don't know or care what you're watching

• No browsing history collection your site visits are yours alone

• No data sold to third parties ever

• Privacy-first analytics only aggregated, anonymous usage patterns (like "how many users use speed control") to improve the product

• Manifest V3 compliant built on the latest extension standard which itself has stricter privacy boundaries

• Minimal permissions we only request what's needed to interact with HTML5 video elements on the page

• Cloud sync is opt-in only if you choose to sign in with Google; works fully offline otherwise

The extension needs page-level access to detect <video> elements that's the permission you see. But it doesn't read page content, form data, or anything else.

Totally valid concern nobody wants an extension that turns their browser into a space heater.

Here's why Video Controls Plus stays light:

• Activates only on video pages the extension doesn't inject anything on tabs without HTML5 video elements

• Minimal background processing no persistent background scripts eating resources when you're not using it

• Manifest V3 architecture built on the modern extension standard that enforces better resource management by design

• Clean memory footprint controls attach to the video element directly, not running heavy scripts on the entire page

• CSS-based filters visual filters use GPU-accelerated CSS, not CPU-heavy canvas manipulation

• 932 automated tests we test not just features but also that things don't break or bloat unexpectedly

In practical terms: with 15+ tabs open, you should see no measurable difference in memory usage compared to not having the extension installed unless a tab actually has a video you're actively controlling.

This means the world coming from an educator thank you!

You've actually identified the exact workflow we designed for:

For watching educational content:

• Speed control blast through familiar material at 3x 4x, slow down to 0.8x for complex derivations

• A-B Loop replay a key explanation or demonstration until it clicks

• Screenshot capture diagrams, equations, key slides at full resolution for your notes

• Keyboard shortcuts navigate your learning without breaking focus

Love that you're thinking about accessibility it's something we care about deeply. Here's a glimpse of what's ahead:

What's live today:

• Full speed control suite (0.1x 16x)

• A-B looping, audio boost, filters, screenshots

• Customizable keyboard shortcuts

• Cloud sync via Google sign-in

• Chrome, Firefox, and Edge support

What's on the horizon:

Absolutely and this is a more common need than most people realize!

The video filters in Video Controls Plus include:

• Brightness crank up those dimly-shot lecture videos

• Contrast make text overlays and subtitles pop more clearly

• Grayscale reduce visual noise when you just need to focus on content

• Saturation adjust color intensity for comfort during long sessions

• More filter options fine-tune the video display to your eyes' comfort level

For language learners specifically:

Yes cloud sync is built in! This was a priority feature because we knew power users don't just use one machine.

Here's how it works:

• Google sign-in quick, secure authentication

• Settings sync across devices your keyboard shortcuts, speed presets, and preferences travel with you

• Cross-machine, cross-browser set it up on Chrome at work, find the same config on Firefox at home

• Automatic changes sync in the background, no manual export/import needed

• Firebase-powered reliable, fast, and secure backend

The idea is simple: your video workflow should follow you, not the other way around. Configure once, use everywhere.

Good news for creators yes, all filters apply in real-time with zero perceptible lag!

Here's why it's smooth:

• CSS/Canvas-based processing filters are applied at the rendering layer, not by re-encoding video

• No buffering interruption the video keeps playing as you adjust filters

• Live adjustment slide brightness up, see the change instantly, fine-tune on the fly

• Lightweight on resources no heavy CPU usage, no frame drops

• What you see is real-time perfect for quick visual checks before downloading content for editing

For creators reviewing their own uploads:

YouTube's native speed control is honestly fine for casual use but if you're a power user, here's where Video Controls Plus levels up your experience:

The killer combo is speed + looping + keyboard shortcuts. Imagine watching a 3-hour lecture at 3x, hitting a complex topic, instantly slowing to 1x, setting an A-B loop, reviewing it twice, then jumping back to 3x all without touching your mouse.

"YouTube gave us 2x. We said: 'Those are rookie numbers.'"

Shortcut conflicts are the worst we totally hear you on that. Here's the good news:

• Fully customizable keyboard shortcuts rebind any action to your preferred key combos

• Covers all major actions speed up/down, A-B loop set/clear, screenshot, filters, audio boost

• Conflict-friendly since you can remap everything, you can dodge conflicts with other extensions

• Instant response shortcuts trigger actions without any popup or menu interaction

• Persistent settings your shortcut configuration saves and stays across sessions

The keyboard shortcut system was designed to be highly customizable and lightweight because when you're in the middle of a 2-hour lecture at 2x speed, you don't want to break flow reaching for your mouse.

"A keyboard shortcut saved is a thought preserved."

Thanks for noticing this is genuinely one of the hardest parts of building a browser extension!

Here's a peek behind the curtain:

• Built with WXT framework a modern extension framework that handles a lot of cross-browser plumbing

• React 19 + TypeScript single codebase for all UI surfaces, strongly typed to catch platform-edge cases early

• 932 automated tests our test suite runs across the extension to catch regressions before they hit any store

• Manifest V3 compliant built natively for MV3 from the start, not ported from MV2

• One codebase, three builds platform-specific quirks are handled at the build layer, not in feature code

The goal was always: you install it on your browser of choice, and it just works the same way. No "Firefox version is behind" or "Edge is missing features" situations.