Privacy policy
How YouCraft Studio handles your content and Google / YouTube connection.
Last updated: 22 October 2026
YouCraft Studio is a privately operated, self-hosted creator workspace. This public website explains the service. The working Studio, its projects and its account connections require authorized access.
1. Who this policy covers
This policy covers these public YouCraft pages and the connected self-hosted YouCraft Studio installation. The operator of that installation controls the workspace, its storage and its configured service providers. It applies when you visit these pages, use the Studio, or connect a Google / YouTube account.
2. Information the Studio handles
- Your projects: channel profiles, scripts, research references, uploaded images and audio, generated media, final video exports, thumbnails and upload metadata.
- Google connection: the authorized YouTube channel’s ID and name, permission tokens, token expiry information and the application credentials used for the connection. We do not collect your Google password.
- Upload state: the file and metadata you confirm, audience and altered-content choices, progress, resumable session information, resulting YouTube video ID and any upload error.
- Public YouTube data: channel and video information such as public titles, descriptions, thumbnails, tags and statistics, when research and channel features request it.
- Operational data: sign-in sessions, application errors, task status and service logs. Hosting and security providers may process IP addresses, request headers and connection information.
3. Why Google access is requested
The youtube.readonly permission lets Studio identify the channel you authorized and check that it matches the intended Studio profile. The youtube.upload permission lets Studio upload the finished video you select, with its saved title, description, tags, audience settings and selected thumbnail.
Each Google account gives its own permission. One channel’s approval does not give Studio access to channels on another account. Google connection is optional for script creation and local video production; it is needed for uploading directly to YouTube.
4. How data is used and shared
We use content and account data to provide the actions you request: research, writing, media generation, rendering, file management, channel identification and confirmed uploads. Finished videos and their upload details are sent to YouTube when you start an upload. Studio requests Unlisted visibility; YouTube controls processing and any visibility restrictions it imposes.
When you request AI writing, image, voice or video generation, the relevant content and references can be sent to the providers configured by the Studio operator. Google OAuth client secrets, access tokens and refresh tokens are not included in AI prompts. Google account authorization data is used for the connection and upload features, not to train general-purpose AI models or target advertising.
Storage, hosting, security and requested generation services process only the information needed for their roles. We do not sell Google user data or use it for advertising. We follow the Google API Services User Data Policy, including its Limited Use requirements.
5. Storage and protection
Project content is stored on the operator’s server and configured object storage, with local working copies when tasks need them. Google app credentials, tokens and resumable upload sessions are held separately in restricted server files, outside project archives and MinIO object storage. Access to the working Studio requires sign-in.
The operator may retain protected backups for recovery. Hosting and configured service providers have their own security and data-handling practices. No system can guarantee absolute security.
6. Retention, disconnection and deletion
Saved projects and connection data remain available while needed for the workspace and its user-requested operations, subject to applicable service policies and deletion requests. You can use Studio’s project and storage controls to delete saved work, and Disconnect to remove the channel’s locally stored Google access and refresh tokens.
You can separately revoke the app’s Google permission at Google Account permissions. Revoking permission prevents further authorized access but does not by itself remove saved project files. Contact the operator to request removal of saved Google / YouTube account data or copies requiring administrator access. Requests to delete Google / YouTube API data are handled within seven days, including applicable recovery copies under the operator’s control.
Deleting a local project or disconnecting an account does not delete a video already uploaded to YouTube. Manage those videos in YouTube Studio. Keep your own copy of any files you wish to retain before requesting deletion.
7. Cookies and external services
The public pages do not add advertising trackers, analytics scripts or browser storage. Cloudflare can use security-related processing or cookies under its own policies. The separate Studio uses sign-in session cookies. If the operator supplies a YouTube cookies.txt file for downloads or transcripts, it is kept privately on the server; it is separate from OAuth upload authorization.
YouCraft uses YouTube API Services. See Google’s Privacy Policy and Cloudflare’s Privacy Policy for their practices.
8. Changes to this policy
Material changes to how Google user data is accessed or used will be disclosed before that new use. Additional permission will be requested where required. This page’s update date records the latest version.
9. Contact and privacy requests
For support, privacy questions or data-deletion requests, contact the operator who provided access to your Studio. For Google-connected users, the operator’s support email is also displayed on the Google permission screen. Include your channel ID and describe your request; never send passwords, client secrets or Google tokens.