Privacy practices

10xTube Privacy

10xTube is distributed by Obsessive Coders, Inc. It runs locally in the user's browser and does not run a backend server operated by Obsessive Coders, Inc.

Data Access

10xTube can access YouTube pages where it is installed because it needs to:

• Add Summary buttons and panels.
• Read YouTube page data needed to find the native Ask summary request.
• Request the selected video's Ask summary from YouTube.
• Seek the active video when the user clicks timestamp links.

Data Transmission

10xTube sends summary requests from the user's browser session to YouTube.

If the user clicks Listen, 10xTube sends generated speech synthesis input to Azure Speech using the user's configured Azure Speech key and region.

10xTube does not send summary text, Azure settings, or YouTube page data to a server operated by Obsessive Coders, Inc.

Data Storage

10xTube stores narration settings in browser extension storage:

• Chosen voice engine (browser built-in or Azure) and voice selection mode.
• Voice selections, including per-language voice choices.
• Shared speaking rate.
• Narration timing calibration (millisecond latency averages; no content).
• Azure Speech key, region, language, and voice — only if the user configures the optional Azure engine.

Summary text and generated audio are cached only in the current page's extension runtime state to support the active summary surface and reload behavior.

Diagnostics

Store builds of 10xTube ship with diagnostics disabled: no console logging, no page attributes, no version badge. Development builds used for testing write diagnostic events to the browser console and a page attribute; even there, diagnostics are designed to exclude raw cookies, authorization headers, Azure keys, full InnerTube payloads, and raw continuation tokens.

Third Parties

10xTube interacts with YouTube for the native Ask summary flow and Azure Speech only when the user enables and uses Listen.

10xTube is not affiliated with YouTube, Google, Microsoft, or Azure.