CARS & GAMES

AI Content Engine / Privacy

Privacy Policy

Last updated: 4 November 2026. This policy explains how Jaymak's AI Content Engine accesses, uses, stores, and shares information from Google and YouTube when the channel owner authorizes it.

Application: AI Content Engine, used with the Cars and Games YouTube channels.
Operator and privacy contact: Jaymak, gloomblue100@gmail.com.

About the application and this website

AI Content Engine is a locally operated tool used by its owner to prepare video drafts and, after the owner authorizes an upload, send a selected video to one of the owner's YouTube channels. It is not a public account service, does not let members of the public sign in, and does not offer visitors a form to submit personal information. The Cars & Games website describes the channels and the tool; it does not receive the tool's OAuth credentials, video files, or upload records.

The website consists of static pages hosted on Cloudflare. It has no visitor accounts, analytics, advertising pixels, embedded video players, or custom tracking cookies. Cloudflare may process technical information needed to deliver and protect website requests, such as connection, browser, and request data, under Cloudflare's Privacy Policy. This website hosting data is separate from the YouTube API data handled by the local tool.

Google and YouTube data and permissions

The owner authorizes the tool through Google's OAuth consent flow and chooses the Google account and YouTube channel for that authorization. The tool does not ask for or collect the account password. The configured YouTube API permissions are:

In connection with those actions, the tool handles the OAuth authorization response and resulting access and refresh tokens; the selected local video; the title, description, category, visibility and other upload settings entered or selected by the owner; the selected playlist identifier; and YouTube's response, including video or playlist identifiers and action status. The owner selects the account and channel by completing authorization in that account. The tool does not use the API to collect unrelated Google account profile information.

How the data is used

The tool uses the authorization tokens to make the upload and playlist insertion requested by the owner, and uses the API response to report and record whether those actions succeeded. The current engine sets uploaded videos to Private. It also records the owner's per-video choice for YouTube's synthetic or altered content disclosure. It does not automatically publish or schedule uploads.

The tool may keep a local operational record containing the video title, file hash, upload time, result, YouTube video ID, privacy status, and playlist result. These records support upload tracking and help prevent an uncertain upload from being repeated. Newly uploaded videos are added to their configured playlist; existing videos are not automatically added.

How data is shared or transferred

The selected video, the metadata needed for the upload, the authorization token needed for the API request, and the playlist insertion request are transmitted to Google/YouTube through YouTube API Services to perform the actions the owner requested. Google and YouTube process that data under their own terms and privacy policies. The local tool does not send OAuth tokens, video files, or upload records to the Cars & Games website or to advertisers, data brokers, or AI model providers.

Google/YouTube API data is not sold, used for targeted advertising, or used to train or improve AI or machine-learning models. It is not shared with another party except as needed to provide the owner-requested YouTube API functionality or where required by law. The website host may separately process technical website request data as described above.

Use of YouTube API Services is subject to the YouTube Terms of Service and YouTube API Services Terms of Service. Google's Privacy Policy explains Google's handling of information.

Storage and security

The tool runs locally on the operator's computer. An access token is held in the tool process while needed. When background authorization is enabled, the refresh token is stored in the current Windows user's Credential Manager, with separate entries for Cars and Games. The OAuth client configuration is kept outside the project repository. Prepared media, manifests, and upload records are kept in local project files. The website does not receive or store these items.

These arrangements keep the tool's credentials and working records on the operator's computer rather than on a Jaymak upload server. Access to the local data depends on the security of that computer and its Windows user account. No separate server-side copy or additional encryption system is operated by the tool.

Retention, deletion, and revoking access

Local project files and upload records remain on the operator's computer until the operator deletes them. A refresh token remains in Windows Credential Manager until it is removed or the Google authorization is revoked. The owner can revoke the tool's access in Google Account third-party connections and remove the corresponding local Credential Manager entry.

For a privacy question or request to delete locally stored API-related information, contact gloomblue100@gmail.com. The operator will remove the relevant local API records and stored authorization within seven calendar days. This local deletion does not delete a video or metadata already uploaded to YouTube; the owner manages those separately in YouTube Studio.

Changes and contact

This policy will be updated if the application's Google or YouTube data handling changes. For questions about this policy or a deletion request, contact Jaymak at gloomblue100@gmail.com.