Privacy Policy — YouTube Community Search

Last updated: August 5, 2026

What the extension stores

Imported community post data (text, metrics, and related fields from YouTube Studio Analytics or a Studio zip) is stored locally in your browser using Chrome extension storage. Your Channel ID, if saved, is also stored locally so the extension can open the correct Studio Analytics page.

If you start a trial or purchase Pro, the extension may also store locally a license key and related entitlement timestamps (for example trial start / plan status) so Pro features unlock on that install. This data is not uploaded to the developer’s servers for normal use.

Payments (Lemon Squeezy)

Pro checkout and billing are processed by Lemon Squeezy (a third-party payment provider). When you choose Upgrade / Start trial, the extension opens Lemon Squeezy’s checkout in a normal browser tab. Payment card details are entered on Lemon Squeezy’s site — not inside the extension — and are handled under Lemon Squeezy’s own privacy policy.

After purchase, you paste a license key into the extension. To activate or re-check that key, the extension may send only the license key (and a short device label / instance id) to Lemon Squeezy’s License API (api.lemonsqueezy.com). It does not send your community post text, images, Channel ID, cookies, or Google credentials. A license key and local activation timestamps may be stored in the extension so Pro stays unlocked on that install.

Reliability diagnostics (Formspree)

On rare sync failures or unexpected Studio Analytics response shapes, the extension may send a small anonymous reliability report to Formspree so the developer can fix compatibility issues quickly.

That report may include:

It does not include:

Reports are rate-limited (at most once per error type per day on a given install).

Basic usage analytics

The extension may send anonymous product usage events (for example: extension opened, sync started, sync finished, upgrade button clicked) using Google Analytics Measurement Protocol. Events include only technical fields such as event name, extension version, and an anonymous install id. They do not include post text, Channel IDs, cookies, tokens, or email addresses.

Permissions (why they exist)

Contact

Questions or privacy requests: mike@lionhartweb.com