Contact

Author: TubeDigest Team

Published: February 7, 2026

Last updated: February 7, 2026

Questions, bugs, or feature ideas are welcome. The fastest way to get help is to open a clear report with reproduction steps.

What to Include in a Report

Include the page URL, the action you took, what you expected, and what happened instead. If possible, include a screenshot, browser version, and relevant console or network errors. Specific details reduce back-and-forth and speed up fixes.

For summary quality issues, include the source video URL and a short note about what felt wrong or missing. This helps improve prompts and parsing logic over time.

You can also review the project README and deployment docs to solve common setup problems before filing an issue.

If you need GitHub issue templates, use GitHub Issues documentation as a starting point.

Response Expectations

Response time depends on issue severity and reproducibility. Security and data-loss reports are prioritized first, followed by production regressions, then general enhancements. Clear reports are addressed faster because they remove ambiguity during triage.

If your issue is blocking work, include that context and any temporary workaround you have already tried. That helps determine urgency and reduces duplicate investigation.

For collaboration requests, include your intended use case, expected volume, and whether you need custom integrations. This helps quickly determine fit and identify the right technical path without extra discovery rounds.

Please include your preferred follow-up channel and time zone so we can reply with concrete next steps that are easy to action.

Data handling details are available in the Privacy Policy.