Privacy & support

Yes — anonymous diagnostics, on by default, and you can turn them off.

Each diagnostic event carries:

• A random ID minted on your device
• The extension version
• Your browser and locale
• Which control you touched
• The bare domain of the site — youtube.com, never the full URL

One switch in Settings ends it.

No — Capo never uploads your audio or video.

Sound is reshaped right inside the page with a Web Audio worklet — the audio never leaves your machine, because there's nowhere for it to go.

The only things Capo ever sends out are diagnostic events (an ID, a version, a domain) and a one-time ping when you install. No audio. Ever.

No — the free features need no account at all.

Pro is the only reason to have an account. To unlock the Pro workspace you sign in and pay for Pro — signing in is simply how Capo ties those extra controls to your account. Nothing in the free tier ever asks you to sign up.

Because it can't know in advance where you'll play something.

Capo asks for access to all sites so it can slip its audio engine into whatever page you're on — YouTube, a lecture player, some tiny podcast site.

It also reads the track's title and artist to label your history, and that stays on your device.

Because pitch and speed can't be bent from outside the page.

Capo injects a small engine into the page itself, taps into its Web Audio graph, and reshapes the sound as it plays.

That's also why it only wakes up where there's media — on a page with nothing playing, there's simply nothing to hook into.

Mostly — with one wrinkle worth knowing.

• Your play history and per-track pitch, speed, and volume stay strictly local to that browser.
• Your preferences — language, ranges, skip interval — go to Chrome's synced storage, so they ride along to other devices on the same Chrome profile.

Neither ever reaches Capo's servers.

Four things worth knowing before you install.

• Audio is processed on your device and never uploaded.
• Diagnostics are on by default — opt-out, not opt-in. Switch them off in Settings.
• Capo asks for access to all sites, because media lives anywhere.
• Your history stays local; only bare domains ever travel.

The full policy lives at capotune.com/privacy.

Two ways: the in-extension feedback form, or email.

• Settings → Send feedback — no account needed, and you can leave your email out entirely.
• support@elyralabs.org — reaches the same people, and it's the address to use for privacy or data requests.

Settings → Support opens the FAQ.

Use Settings → Send feedback with category Bug.

1. Open Settings → Send feedback.
2. Pick Bug.
3. Put the site's domain — like youtube.com, not the full URL — in the "Site this happened on" field.

Your Capo version and browser attach themselves. And when Capo tells you a page won't work, there's a Report a bug link right on that screen.

Same route: Settings → Send feedback → Bug.

1. Describe what you did and what you heard.
2. Note the exact pitch, speed, and volume values.
3. Note the site and your Audio quality setting — crackle usually tracks the heavier engines.

Worth trying first: drop Audio quality a notch. If that fixes it, tell us that too.

Send it through Settings → Send feedback.

• Choose Idea if the site never worked, Bug if it used to.
• Drop the domain in the site field.

Leaving anonymous diagnostics on helps here too: domain-level site diagnostics are exactly how we spot places where Capo quietly fails.

The form asks for little, so your message does the work.

• The domain — there's a field for it
• What you tried, and what you saw or heard
• Your settings at the time: pitch, speed, volume, audio quality
• An email, if you want a reply — it's optional

Version and browser attach automatically.

Yes, please — use Settings → Send feedback.

1. Open Settings → Send feedback.
2. Pick Idea or Other.
3. Say which language you're running and quote the phrase that read wrong.

Wording notes are especially useful if you're running Capo in one of its ten non-English languages. Translation fixes ship like any other fix.