Privacy, plainly.
What Media House handles while its owner prepares and publishes personal recordings.
Scope
Media House is a private application operated for its owner’s recordings and YouTube channel. It has no public registration or public login. This policy describes the planned and stated workflow; it does not claim that every recording has passed production review or that YouTube has approved public scheduling.
Two different sources: Camera and audio recordings are supplied by the owner from the owner’s computer. Channel details, video processing and publication status, and related records may be obtained or updated through YouTube APIs after the owner authorizes access.
Information handled
- Owner supplied media: original video and audio, selected frames for editing or thumbnails, and episode materials such as titles, descriptions, subtitles, and exported videos.
- Derived material: local transcripts, editorial notes, edit plans, subtitles, thumbnails, and technical or privacy review records created from the recordings.
- YouTube authorization and account data: OAuth credentials needed to act on the owner’s authorized channel, channel identification and metadata, upload identifiers, processing status, scheduling or publication state, and publication records.
The owner supplied footage is not YouTube API data. Information retrieved from YouTube is used for the authorized upload and publication workflow.
Where processing happens
Private cloud worker
The owner transfers recordings from a computer to a private cloud worker for editing. Transcription is performed locally within the private workflow. Media and selected frames may be used for editing, subtitle preparation, thumbnail selection, and quality or privacy review.
Microsoft Azure
Azure OpenAI assists with editorial planning using material supplied to that service for that task, such as transcript text or editorial context. It does not replace the owner’s editorial judgment. The exact fields sent for each task and Azure’s service-side handling have not been independently verified against the deployed implementation.
Google / YouTube
After owner authorization, the YouTube integration sends the finished episode and associated publication information to Google for private upload, processing verification, and, when eligible, scheduling or publication. Google processes that data under its own policies. See Google’s Privacy Policy.
Storage and deletion
Original recordings remain on the owner’s computer. The stated cloud-media rule is to remove cloud media files only after verified public publication. A private upload or completed render does not by itself trigger that removal. No fixed retention period is stated for unpublished media.
Retention and removal procedures for transcripts, selected frames, OAuth credentials, channel information, and publication records have not yet been verified from an implementation. No deletion timeline or automatic deletion process for those categories is promised here. Removing files from the private worker does not remove a video already uploaded to YouTube; that is controlled separately through YouTube.
Implementation details to verify: credential storage, access controls, the actual cleanup behavior for every data type, and how deletion requests are fulfilled. Send a request to the contact address below; it will be handled by the owner.
Access and controls
The application is intended for one authorized owner. OAuth credentials must be kept out of the public site and protected in the private application environment. Specific encryption, rotation, backup, and access-control measures have not been verified here and are not claimed.
The owner can withdraw the application’s Google Account authorization using Google Account third-party connections. Revocation stops future authorized API access, but does not automatically erase previously uploaded videos or locally held copies. Local credential removal after revocation needs to be verified in the implementation.
Contact and requests
For privacy questions or deletion requests, email games.princeraj@gmail.com. Identify the relevant recording or publication record without attaching private footage. This address is already published on the owner’s website; the owner handles requests directly.
Contact information ↗