Tjikko Network Privacy Policy

Effective date: 2026-09-24

This Privacy Policy explains how the Tjikko Network production application (the Application) accesses, uses, stores, shares, retains, and deletes information when it operates the Tjikko Network YouTube channel.

This policy applies to the Application operated by Old Tjikko and is not a general privacy policy for Google, YouTube, or unrelated third-party services. Those services have their own policies.

1. Operator and contact

Application: Tjikko Network
Operator: Old Tjikko
Contact: oldtjikko365@gmail.com
YouTube channel: https://www.youtube.com/@Tjikko-Network

The Application's homepage links to this policy and its Terms of Service. The operator will provide an updated notice if the Application materially changes how it handles Google user data.

2. Google user data the Application accesses

The Application uses Google OAuth and the YouTube Data API. The user chooses whether to authorize access and sees the requested permissions on Google's consent screen.

With the current authorization configuration, the Application may access:

• the authorized YouTube channel's channel ID, title, description, thumbnails, and related channel metadata;
• the authorized user's YouTube video and channel data that the granted YouTube API permissions make available;
• video metadata, including titles, descriptions, tags, category, privacy status, processing status, publication details, and identifiers;
• video files selected by the operator for upload to the channel;
• thumbnails, captions, playlists, and related metadata when a specific production operation requires them;
• access and refresh tokens needed to maintain the authorized connection.

The Application does not request or store the Google account password. It does not request Google Gmail, Google Drive, Contacts, Calendar, payment, location, or advertising-profile data. It does not request a Google profile email or name through a separate profile scope unless the consent configuration is explicitly changed.

If the requested OAuth scopes change, this policy and the consent-screen disclosures will be updated before the changed access is used.

3. How Google user data is used

Google user data is used only to provide and improve the Application's user-facing YouTube channel functionality, including:

• inspecting the authorized channel and its current content;
• uploading video files selected by the operator;
• preparing or updating titles, descriptions, thumbnails, captions, playlists, and related video metadata;
• checking upload processing status and confirming that an upload is playable;
• organizing the Tjikko Network production workflow and its approved outputs;
• maintaining authorization, security, error handling, and service reliability;
• responding to a request from the authorized channel operator;
• complying with law or responding to a valid security or legal request.

The Application does not use Google user data for targeted, personalized, retargeted, interest-based, or other advertising. It does not sell Google user data, provide it to data brokers or information resellers, use it to determine creditworthiness or lending decisions, or create unrelated databases about users.

The Application does not use Google user data to train, fine-tune, validate, or improve generalized or non-personalized artificial-intelligence or machine-learning models. Google user data is not provided to an AI model for model training.

4. Sharing, transfer, and disclosure

The Application does not sell, rent, or disclose Google user data to advertising networks, data brokers, information resellers, or unrelated third parties.

Google user data may be transmitted to or processed by:

1. Google and YouTube, as necessary to authenticate the user and perform the YouTube API operations the user authorized;
2. The operator's local production system, where OAuth tokens and production workflow data are stored and processed;
3. A service provider explicitly enabled for a particular operation, only when necessary to provide that user-facing operation and only according to that service's documented handling terms;
4. Authorities or professional advisers, only when required by law, valid legal process, or necessary to protect the Application, channel, operator, or public from fraud, abuse, or security threats.

The Application does not send Google user data to local or hosted AI services for training. Video files and production assets may be sent to an explicitly selected processing service only when the operator intentionally enables that service for the relevant operation. Google account credentials and OAuth refresh tokens are not sent to AI-generation services.

5. Local production data and generated content

The production workflow may create and store scripts, research notes, source and rights records, generated images, generated audio, narration, video renders, subtitles, thumbnails, metadata, quality-assurance reports, and logs.

These production files are stored in the TV Network project workspace or in an explicitly selected service. Production assets are separate from Google OAuth credentials. External source media is tracked with source URLs and license information when applicable.

The Application may use local AI models to generate or transform production assets. Google user data is not used to train those models. The operator reviews generated content, factual claims, licensing, and platform compliance before publication.

6. Storage and security

OAuth client files and access tokens are stored in a profile-specific local secrets directory with filesystem permissions restricted to the channel operator. The Application does not place credentials in the public project files, generated videos, public web pages, or source-control repositories.

Data transmitted to Google and YouTube uses Google's HTTPS/TLS endpoints. Local access is limited through operating-system permissions and the operator's machine security controls. The operator does not claim that any internet-connected or local system is perfectly secure.

If unauthorized access or credential exposure is suspected, the operator will disable or revoke the affected OAuth credentials where practical, remove the affected local token, investigate the incident, and create replacement credentials when necessary.

7. Retention

The Application retains data according to the following rules:

• OAuth client files and refresh tokens: retained only while the authorized channel connection is needed. When access is revoked or no longer needed, the local token is deleted within 30 days, subject to security investigation or backup-retention requirements.
• Temporary API responses, caches, and processing files: retained only as long as needed for the operation and normally removed within 30 days.
• Production records: scripts, source records, rights records, manifests, and approved project files may be retained while needed for channel operation, attribution, auditability, legal records, or historical production records.
• Uploaded YouTube content: retained on YouTube until the channel operator changes or deletes it. Local deletion does not automatically delete content already uploaded to YouTube.
• Backups: may retain deleted local data for the limited backup lifecycle used by the operator. Deleted data is removed from active systems first and expires from backups according to that lifecycle.

8. Deletion and access requests

The authorized channel operator may request deletion of Application-held Google user data by contacting:

oldtjikko365@gmail.com

A deletion request should identify the relevant account or data without sending passwords or OAuth tokens. The operator will acknowledge the request and normally complete deletion of data under the operator's control within 30 days, unless retention is required for legal obligations, security investigation, dispute resolution, attribution, or a surviving backup lifecycle.

The operator cannot delete data held directly by Google or YouTube through this Application. To remove YouTube content, the channel operator must delete it through YouTube. To revoke the Application's Google access, the operator may remove the Application from the Google Account's third-party connections. Revoking access prevents future API operations but does not by itself delete content already uploaded to YouTube.

9. User choices and consent

Authorization is voluntary. The user may decline consent, revoke access through Google Account settings, or contact the operator to request deletion. The Application will not attempt to bypass Google's consent screen or retain a new authorization after the user has revoked it.

The Application uses private or unlisted uploads during production and verification when configured to do so. Public publication is a separate operator-controlled action.

10. Children's privacy

The Application is a production and channel-management tool. It does not provide child account registration and is not designed to knowingly collect personal information directly from children. It does not knowingly request Google user data from children.

11. Changes to this policy

This policy may be updated when the Application, YouTube API permissions, data handling, services, or legal requirements change. The effective date will be updated when a material revision is published. The current version will remain available at this page, and material changes will be identified in the published update where practical.

12. Contact

Privacy questions, access requests, and deletion requests should be sent to:

Old Tjikko
oldtjikko365@gmail.com