Parsec Files Factory

Parsec Files Factory Privacy Policy

Last updated: 3 October 2026

Application: Parsec Files Factory
Operated by: Caio Martins (individual), owner of the Parsec Files YouTube channel
Contact: ccaio43gsd@gmail.com

Parsec Files Factory ("the application") is an internal, owner-operated system used to produce content for and manage the Parsec Files YouTube channel. This policy explains what Google user data the application accesses, how it is used, stored, shared and deleted.

YouTube API Services

Parsec Files Factory uses YouTube API Services (the YouTube Data API v3). By using the application you agree to be bound by the YouTube Terms of Service. Google's handling of your data is described in the Google Privacy Policy.

Google and YouTube data we access

When the owner authorizes the application through Google OAuth (scope: https://www.googleapis.com/auth/youtube.force-ssl), the YouTube Data API v3 provides access to the authorized YouTube channel's information, such as:

The application does not access Gmail, Google Drive, contacts or any other Google service, and does not access other YouTube channels' private data. It does not collect the owner's Google password: sign-in happens on Google's own pages.

How the data is used

Google user data is used only to:

Data storage and retention

Data sharing

Google user data is not sold, not rented, not shared with advertisers, and not used to build advertising profiles or for any purpose unrelated to managing the owner's channel. It is not shown to anyone other than the owner, and not transferred to third parties except to comply with applicable law.

Cookies, device information and third-party content

This website and the application do not use cookies, do not store or access information on users' devices for tracking, and do not allow third parties to serve content or advertising.

Limited Use

The application's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Security

All API traffic uses HTTPS (TLS). OAuth credentials are stored in the macOS Keychain and are accessible only to the owner.

Revoking access and deleting data

Videos already published on YouTube remain on YouTube and can be managed or deleted in YouTube Studio.

Changes

This policy may be updated when the application changes. The date above shows the latest revision.

Contact

Privacy questions or complaints: ccaio43gsd@gmail.com