Privacy Policy

Scope of this policy

This policy applies to Petmeister Video Publisher, the local-first video production and publishing application associated with the Petmeister project. It covers the current production YouTube Data API integration and the informational website at petmeister.com.tr.

The application runs on a device controlled by its operator. This website does not provide a hosted application account, collect form submissions, initiate Google OAuth, or store application data.

Google and YouTube data the application accesses

The production client requests the Google OAuth scope https://www.googleapis.com/auth/youtube.upload. The current implementation uses this permission only to upload a video chosen by the operator.

For that workflow, the application handles:

• OAuth access credentials, including a refresh token when Google issues one, together with scope and expiry metadata;
• the MP4 file selected for upload;
• the video title, description, tags, category, visibility, made-for-kids setting, and synthetic-media disclosure supplied with the upload; and
• the video identifier returned by YouTube after a successful upload.

The production client does not request Google profile, email, contacts, Gmail, Drive, YouTube Analytics, channel-membership, or YouTube read-only scopes.

How that data is used

Google authorization is used only to:

• authenticate an operator-authorized YouTube upload;
• send the selected video and its publishing metadata to the official YouTube Data API v3;
• resume or safely retry an interrupted upload when the API permits; and
• record the returned video ID and local publication state so the application can avoid accidental duplicate uploads.

Petmeister does not use Google user data for advertising, user profiling, credit decisions, or model training.

Local storage and security practices

OAuth credentials are stored on the operator’s own machine in a configured token file. The default paths are secrets/youtube_token.json for the OAuth token and secrets/client_secret.json for the OAuth client configuration. The token file is replaced atomically when updated.

The returned YouTube video ID and publication state are stored in the application’s local SQLite data. Credential and token paths are excluded from the production source repository. The public website does not receive or store those files.

The application uses Google’s OAuth client libraries and the official YouTube Data API. Device access control, filesystem permissions, backups, and deletion remain the operator’s responsibility. Local credential files are not represented as having application-level encryption at rest.

Sharing and sale

The application sends OAuth credentials to Google’s OAuth services and sends the selected video and metadata to YouTube as required to complete the authorized upload. It does not sell Google user data or share it with advertisers, data brokers, or unrelated third parties.

The application can use an operator-selected language-model provider to help create content before rendering. The current YouTube integration does not send Google OAuth tokens or Google user data to those model providers.

Retention and deletion

This website retains no Google user data. On the operator’s device, the OAuth token remains until it is revoked, deleted, or replaced. The local video ID and publication record remain until the operator removes the related application data or database.

To remove local authorization and records, the operator can close the application, delete the configured OAuth token file, optionally delete the locally stored OAuth client file, and delete the relevant publication records or local SQLite data.

Deleting local files does not delete a video already stored by YouTube. The operator must manage or delete that video in YouTube. If another person administers the local installation, the user should ask that operator to remove the local data.

Revoking Google access

A user can revoke Petmeister Video Publisher’s access at any time from the connections page in their Google Account. Revocation prevents the stored authorization from being used; deleting the local token file removes the application’s local copy.

Google API Services User Data Policy

Petmeister Video Publisher’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

The application is also operated subject to the YouTube API Services Developer Policies.

Informational website and hosting

The site’s source contains no analytics, advertising, tracking pixels, cookies, forms, login system, or application JavaScript. The static hosting provider may process ordinary network information, such as IP addresses and request logs, to deliver and secure the site under its own privacy terms. That hosting data is not Google user data obtained by Petmeister through the YouTube API.

See the GitHub General Privacy Statement for information about the hosting provider’s practices.

Policy updates and contact

This policy will be updated when the production application’s use of Google user data changes. The effective date above identifies the current version. Where required, affected users will be informed and asked to consent before Google user data is used for a newly disclosed purpose.

For privacy or OAuth support, contact the project owner through the public GitHub profile. Never include an access token, refresh token, client secret, or credential file in a public message.