How Curious Engine handles Google and YouTube data

Effective: October 26, 2026

1. Overview

Curious Engine is a private automation system used by authorized YouTube channel operators to prepare, validate and publish video content. This policy explains how Curious Engine accesses, uses, stores, shares and deletes information obtained through Google APIs and YouTube API Services.

2. Google user data we access

When an authorized operator connects a YouTube account through Google OAuth, Curious Engine may access:

basic YouTube channel identity needed to confirm that the expected channel was authorized;
video and upload metadata for the authorized channel, such as video IDs, titles, descriptions, tags, thumbnails, privacy status and upload information;
authorization credentials, including OAuth access and refresh tokens, required to make authorized API requests; and
API responses needed to confirm upload or update results.

Curious Engine does not request access to Gmail, Google Drive, Contacts, Calendar, or other unrelated Google services.

3. Permissions and how we use them

Curious Engine currently uses YouTube permissions for the following purposes:

YouTube read access: verify the authorized channel, inspect relevant uploads and reduce accidental duplicate publishing.
YouTube upload access: upload videos selected by the authorized operator.
YouTube management access: manage publishing-related video metadata and status for authorized videos.

Google user data is used only to provide and maintain these user-facing publishing features. Curious Engine does not use Google user data for advertising, credit decisions, surveillance, data brokerage, or unrelated profiling.

4. Storage and security

OAuth credentials used by the automation are stored in protected automation configuration, such as encrypted workflow secrets, and are not intentionally written to public repositories or public logs. During an authorized workflow, credentials may be made available to the secure execution environment only for the time needed to call Google/YouTube APIs.

Operational records may retain non-secret information such as video IDs, titles, timestamps, publishing status, error summaries and workflow results so the operator can audit publishing activity and prevent duplicates.

5. Sharing and transfers

Curious Engine does not sell Google user data. It does not share Google user data with advertising networks or data brokers. Data may be processed by infrastructure providers used to operate the authorized automation, such as GitHub Actions, solely to execute the requested workflow, and by Google/YouTube as necessary to provide the API service.

Any use or transfer of information received from Google APIs is limited to providing the disclosed functionality and is handled in accordance with the Google API Services User Data Policy, including its Limited Use requirements.

6. Retention and deletion

OAuth credentials are retained only while the operator wants the account connected. They may be replaced or deleted when access is revoked or the automation is disconnected. Operational publishing records may be retained for audit, reliability and duplicate-prevention purposes. An authorized operator can request deletion of stored application data by contacting the address below.

7. Revoking Google access

You can revoke Curious Engine's Google account access at any time from your Google Account permissions page: Google Account third-party access. Revocation prevents future API access once existing authorization is no longer valid.

8. YouTube API Services

Curious Engine uses YouTube API Services. Use of those services is also subject to the YouTube Terms of Service and the Google Privacy Policy.

9. Changes to this policy

If Curious Engine materially changes how it accesses or uses Google user data, this policy will be updated before the new use is introduced. Where required, users will be asked to provide new consent.

10. Contact

Privacy or deletion requests: thecuriousloop.ai@gmail.com