Privacy Policy — Comment Exporter for YouTube™ — CSV
What the extension reads, and when
The extension runs only on YouTube watch pages (https://www.youtube.com/watch*). It reads the publicly visible comments already rendered on the page you are viewing — comment text, author handle, like counts, and timestamps — and only when you click the export button. It does not run in the background, does not read comments on pages you have not opened, does not access your YouTube account, private messages, subscriptions, or watch history, and does not call any YouTube or Google API.
Where comment data goes: it stays in your browser
Comment content is processed entirely locally and is never transmitted. The extension's only permitted network destination is extensionpay.com (payments/licensing, below). There is no other server, no analytics service, and no telemetry in the extension. We verified in the shipped code that no request carries comment content anywhere.
Exports are saved to your device
When an export finishes, the extension assembles the CSV (or JSON, on the Pro tier) in memory and hands it to your browser as a normal file download. The file is saved wherever your browser saves downloads. We never see it, receive it, or store a copy.
What is stored with chrome.storage
- Your preferences (e.g. export options) — stored in Chrome's extension storage, synced by Chrome if you use profile sync.
- A one-time UI flag (
ytce_nudged) — remembers that the upgrade hint was shown once, so it doesn't nag you. - License state — a cached copy of your ExtensionPay license/subscription status (
extensionpay_user,extensionpay_api_key,extensionpay_installed_at, and a short-lived license cache) so the extension does not need to check the network on every page.
No comment data, browsing history, or personal profile information is stored.
Payments: ExtensionPay and Stripe
The paid tier is handled by ExtensionPay, a payment service for browser extensions, with card processing by Stripe. When you buy, reactivate, or manage a plan, you do so on ExtensionPay/Stripe pages — not inside the extension. In that process ExtensionPay handles your email address (to identify your license and let you sign in on another machine) and Stripe handles your payment details (card number, billing information). The extension itself never sees your card details; it receives back only your license status. ExtensionPay's privacy policy and Stripe's privacy policy govern their handling of that data.
What we do not do
- We do not sell user data — to anyone, ever.
- We do not use any data for advertising, ad targeting, or ad measurement.
- We do not use any data to determine creditworthiness or for lending purposes.
- We do not transfer data to third parties except ExtensionPay/Stripe for the payments you initiate.
- We do not use data for any purpose unrelated to the extension's single function: exporting the comments of a video you are viewing.
Data retention and deletion
Everything the extension stores lives in your browser's extension storage and is deleted when you uninstall the extension (or clear extension data). Exported files are yours, on your device. Payment and email records held by ExtensionPay/Stripe persist per their policies for as long as you hold a license; you can request deletion of your ExtensionPay account data through them, or open an issue with us (below) and we will help route the request.
Limited Use
The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
Contact
Privacy questions or requests: open an issue at github.com/Jaxx-H/jaxx-h.github.io/issues — publicly answered, or mark it private-sensitive and we will arrange a direct channel. Changes to this policy will be posted at this URL with a new effective date.