Report a bug
A good bug report is the URL, what you expected, what you saw, and what you already tried. Debug mode sends diagnostic logs to our servers when we need them.
We read every bug report. Please send them.
A good one is four short lines:
- The URL of the page or video.
- What you expected to happen.
- What you saw instead.
- What you already tried (reload, reinstall, a different page).
Send it through contact support — the one entry point. Screenshots help.
Debug mode (when we ask for it)
For intermittent or race-condition bugs, our support team may ask you to enable debug mode. Debug mode records extra diagnostic logs and sends them to our servers so we can see exactly what happened. It is always opt-in — you confirm a consent prompt before it turns on.
The simplest place to control it is the support page, which has a debug toggle you can switch on and off:
- Open contact support and turn on the debug toggle. Confirm the consent prompt.
- Reproduce the bug.
- Send your report — our team will have the diagnostic logs on our end.
- Turn the toggle back off when you are done.
You can also enable debug mode from inside the extension: when you send a support message from the extension, check Enable debug mode on the consent step before sending.
Security reports
If you found a security issue — a data leak, an auth bypass, exposure of someone else's content — start your message with "security" so it routes correctly. We prioritize security reports.
What is next
- Contact support — the entry point for every bug report.
- No overlay appears — the most common bug, with a self-serve fix.