01Overview

This Privacy Policy applies to the iteach4u YouTube Shorts publishing automation system (the "Service"), a backend application operated by the iteach4u.kr team for the sole purpose of publishing short-form video content to a small set of YouTube channels owned and operated by the same team.

The Service is not publicly accessible. It does not have end users, does not provide any user-facing interface, and does not process data on behalf of third parties. This policy is published to comply with the YouTube API Services Terms of Service and Google's Privacy Policy.

02Information we access

The Service uses the YouTube Data API v3 to publish and manage videos on YouTube channels owned by the operator. The specific YouTube API methods invoked are:

• videos.insert — Upload new video files with title, description, tags, category, and language metadata, including multilingual localizations for global audiences.
• videos.update — Occasional metadata edits on previously uploaded videos owned by the operator.
• videos.list — Confirm upload status and retrieve video IDs after insertion.
• thumbnails.set — Apply custom thumbnails generated by the operator's own automation.
• captions.insert — Upload caption files generated by the operator.
• commentThreads.insert — Post pinned comments on the operator's own videos only. No automated commenting on third-party content.
• channels.list — One-time verification of channel ownership during OAuth setup.

03Information we do not collect

To remove ambiguity, the Service explicitly does not access, collect, store, or process the following categories of information:

• Personal data of viewers, subscribers, or commenters on YouTube
• Watch history, playlists, or recommendations of any YouTube user
• Engagement data (likes, dislikes, subscriptions) from third parties
• Email addresses or contact information of any YouTube user
• Search history or browsing behavior
• Demographic or location data of viewers
• Content owned by anyone other than the operator

The Service performs no search.list queries, no scraping, no harvesting, no surveillance, and no engagement automation.

04OAuth 2.0 authorization tokens

To upload videos to YouTube channels, the Service obtains and stores OAuth 2.0 refresh tokens issued by Google. These tokens grant the Service permission to upload content to specific channels owned by the operator.

How tokens are handled:

• One token per managed channel — never shared across channels or projects
• Stored on a private server in restricted-access directories with strict file permissions
• Never transmitted to third parties, never logged in plaintext, never exposed via any network endpoint
• Used only for the YouTube scopes explicitly granted during OAuth consent (youtube.upload, youtube)
• Revocable at any time via Google Account permissions, which immediately disables Service access

Users (the operator) can revoke the Service's access at any time by visiting Google Account Permissions.

05How we use accessed information

All data accessed via the YouTube API is used solely for publishing video content to the operator's own YouTube channels. Specifically:

• Uploading video files with metadata in multiple languages
• Setting custom thumbnails generated by the Service
• Reading the upload status to confirm publication success
• Pinning informational comments authored by the operator on the operator's own videos

The Service does not use accessed data for advertising, profiling, personalization, analytics on third parties, model training, or any purpose unrelated to publishing the operator's own content.

06Data storage and security

The Service runs on a private virtual machine controlled by the operator. Data handled by the Service is stored as follows:

• OAuth refresh tokens: Encrypted at rest in restricted server directories. Access limited to the operator's account.
• Video metadata logs: Stored locally on the private server for audit and debugging purposes only.
• Generated content files (videos, thumbnails, scripts): Stored locally on the operator's infrastructure.
• No cloud database or third-party storage is used for any data obtained from the YouTube API.

Security measures include firewall protection, key-based SSH authentication, fail2ban intrusion prevention, regular security updates, and physical access controls on infrastructure operated by Synology DSM and Proxmox VE.

07Third-party services

The Service uses the following third-party services strictly for content generation, none of which receive YouTube user data:

• DeepSeek — Text generation for video scripts and metadata
• OpenAI — Image generation for video thumbnails
• ElevenLabs — Text-to-speech for video narration on selected channels
• Pexels and Pixabay — Stock footage and music with permissive licenses
• YouTube Audio Library — Royalty-free background music

These services receive only generic content prompts authored by the operator (e.g., "cute kittens playing"). They do not receive any data obtained from the YouTube API, no OAuth tokens, and no information about specific YouTube users.

08Data retention and deletion

The Service retains data only as long as necessary for its operation:

• OAuth tokens: Retained while the Service is active. Deleted upon revocation or when the channel is no longer managed by the operator.
• Upload logs: Retained for up to 12 months for audit purposes, then deleted.
• Generated content files: Retained on local storage at the operator's discretion.

To request deletion of any data associated with this Service, contact the operator at the address below. The operator will also delete data accessed from YouTube's APIs upon Google's request, per the YouTube API Services Terms of Service.

09User rights

Since the Service has no public users, traditional data-subject rights apply only to the operator. However, in accordance with applicable privacy laws (including GDPR and CCPA where relevant), any individual who believes their data has been improperly accessed may:

• Request information about what data, if any, has been processed
• Request correction or deletion of such data
• Lodge a complaint with a supervisory authority
• Contact Google to report concerns regarding the use of YouTube APIs

10Children's privacy

The Service is not directed at children under 13 (under 14 in South Korea per PIPA). The Service does not knowingly collect any data from children. Content published by the Service complies with YouTube's "Made for Kids" disclosure requirements; videos directed at general audiences are appropriately labeled in YouTube Studio.

11International data transfers

The operator is based in South Korea. The YouTube API is operated globally by Google. Limited metadata (video titles, descriptions, tags, language codes) is transmitted to Google's servers as part of normal API operations. No data is transferred to other third parties.

12Compliance with YouTube API Services

The operator agrees to comply with the YouTube API Services Terms of Service, the YouTube API Services Developer Policies, and Google's Privacy Policy. The Service does not modify, replace, or interfere with YouTube's user-facing features. All AI-assisted or synthetic media is disclosed via YouTube Studio's "Altered or synthetic content" toggle on each affected video.

13Changes to this policy

This policy may be updated periodically to reflect changes in the Service or in applicable regulations. The "Last updated" date at the top of this page reflects the most recent revision. Material changes will be noted with a clear revision summary.

14Contact

For questions or requests regarding this Privacy Policy, please contact:

• Email: www.iteach4u.kr@gmail.com
• Operator: iteach4u.kr
• Location: South Korea