Privacy

Privacy Policy

YouTube Bookmark Pro

Last updated: 2026-04-20

YouTube Bookmark Pro is a Chrome extension for saving YouTube research, organizing a review library, and running creator workflows such as owner-video analytics, compare, transcript-first retrieval, packaging research, briefs, Comment Radar, monthly review, cloud sync, optional report email delivery, and paid overflow credits.

What data we access

1. Library and workspace data

When you save or organize items in the extension, we may store:

bookmarked URLs
video titles
thumbnails and preview assets
timestamps and durations
notes and tags
saved transcript snippets and snippet-derived notes, reasons, or bank entries
categories, projects, and watchlists
saved workflow artifacts such as reviews, compares, briefs, transcript exports, Comment Radar exports, and packaging results
extension preferences
UI theme preferences (Creator Calm Skin setting), stored locally on your device

This data is primarily stored on your device in extension storage.

2. Connected Google and YouTube data

If you choose Connect YouTube, the extension may access:

your Google account email address used for sign-in
your YouTube channel identity
channel metadata and video metadata
subscriptions and channel-management data used by the product
owner-only YouTube Analytics data for channels and videos you own and connect on this device

If you use transcript retrieval, the extension may also access public caption and transcript-track data for the specific YouTube video you select from:

the active watch page
a pasted YouTube URL
a saved video you reopen inside Creator

Full transcript bodies are fetched on demand for the selected video only. We do not sync or store full transcript bodies by default; only the snippets or derived saves you explicitly keep.

The extension requests the following Google scopes because they are required for shipped features:

youtube.readonly
youtube.force-ssl
yt-analytics.readonly

3. Billing, restore, and cloud-sync data

If you use paid features, we may process:

your billing email
entitlement and subscription status
purchased credit balances
cloud-sync snapshots of bookmarks, settings, projects, and subscriptions preferences
restore-session and verification metadata
Creator report-delivery settings such as whether email delivery is enabled and which recipient address you choose
delivery-log metadata for optional scheduled report emails, such as report type, source key, period key, recipient email, and delivery status

4. Feedback and optional bug telemetry

If you use the Feedback form, we receive the message you submit and the product context needed to investigate it.

This can include:

the active product surface
route and action context
a location label such as Creator > Briefs
an expected-behavior note describing what should have worked

If a Feedback submission clearly describes a bug or failure, we may also group it inside our internal bug monitoring so support and engineering can see it in the same issue inbox as runtime bug events.

Automatic bug telemetry is:

optional
redacted
off by default

If you opt in, we may collect limited technical diagnostics such as:

error messages
stack traces
feature surface
action name
route context
anonymized device and session identifiers
recent UI breadcrumbs
sanitized debug metadata

Passwords, payment card data, private messages, tokens, cookies, email addresses, and billing codes are filtered before upload.

How we use data

We use data only to provide and operate the extension features you ask for, including:

saving and reopening library items
rendering digests, recall, and privacy-mode behavior
comparing channels or videos
fetching transcript hits for the specific video you choose and saving only the snippets you keep
reviewing owned videos and surfacing owner analytics
generating user-requested creator outputs such as summaries, briefs, packaging research, strategist guidance, and Comment Radar exports
processing billing, restore, and cloud-sync flows
sending optional scheduled report emails when you turn that delivery path on
handling feedback and optional bug diagnostics

When data leaves your device

Data can leave your device only when a feature requires a connected service.

Google APIs

When you connect YouTube, the extension sends authorized requests to Google APIs to load YouTube and YouTube Analytics data needed for the connected features.

YouTube Bookmark Pro backend

We use our backend services to support:

account verification and restore
billing and entitlements
cloud sync
creator workflow caches
optional scheduled report delivery and delivery logging
feedback delivery
optional bug monitoring

AI service providers

When you explicitly run creator AI features, we may send the minimum necessary source context to our AI processing providers so they can generate the result you requested. This can include selected titles, notes, public or owner analytics snapshots, comment summaries, transcript snippets, compare context, strategist context, and other creator-workflow inputs needed to produce the feature output.

We do not use Google API data or creator-workflow content to build advertising profiles or to train generalized AI or machine-learning models.

Payments and email providers

We use service providers for:

checkout and billing portal flows
verification and transactional emails
optional scheduled report emails, billing reminders, and membership-end retention notices

These providers receive only the data needed to complete the payment or message flow.

Data sharing

We do not sell your data.

We share data only with service providers that are needed to operate the features above, such as:

Google, for authorized YouTube and YouTube Analytics requests
billing, sync, support, and backend infrastructure providers
AI processing providers, only when you explicitly use an AI feature
email providers, only for transactional, support-related, and optional report-delivery messages

Google API Services disclosure

YouTube Bookmark Pro's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

In particular:

Google API data is used only to provide or improve user-facing extension features requested by the user
Google API data is not sold
Google API data is not used for advertising
Google API data is not used to determine creditworthiness or for other prohibited purposes
Google API data is not used to train generalized AI or machine-learning models

Your choices and controls

You can:

choose whether to connect YouTube
disconnect YouTube at any time
choose the active Creator channel on this device
choose whether to enable optional report email delivery and set the recipient address
export, import, archive, hide, or delete saved items
control digest and recall settings
turn redacted bug reports on or off at any time
remove local extension data by clearing extension storage or uninstalling the extension

If you use paid cloud sync, you can also pause sync or restore data from the cloud through the extension settings.

Retention

Local library and settings data remain on your device until you change or delete them.
Full transcript fetches are treated as on-demand utility data and are not retained as synced transcript archives by default.
Saved transcript snippets, notes, reasons, bank entries, and workflow artifacts remain until you edit or delete them.
If a paid membership ends and there is no active paid access on the account, we may retain the cloud copy of synced workspace data and server-backed Creator artifacts for up to 1 year so the data can come back if you sign in again during that period.
You can request earlier deletion of that retained cloud copy from the membership-end retention email.
Deleting the retained cloud copy does not remotely wipe data that is already stored locally on one of your devices.
Cloud-synced data otherwise remains in our backend until you delete it or your account data is removed.
Optional report-delivery logs are retained only as needed to send, deduplicate, troubleshoot, and confirm report emails.
Optional bug telemetry is retained only for debugging, issue grouping, and operational monitoring.
Billing and transactional records are retained as needed for payments, fraud prevention, support, and legal compliance.

Contact

For privacy or support questions, contact:

info@youtubebookmarkpro.com