Privacy

Last reviewed: November 3, 2026.

About this policy

Yurei Studios creates independent software and creative projects. This policy covers this website, privacy enquiries, and Content Factory. Future products may have their own notices.

This static website has no registration, Google sign-in, forms, advertising, or analytics scripts. For the planned Cloudflare deployment, Cloudflare processes website requests. See the Cloudflare Privacy Policy.

Content Factory

Content Factory is an owner-operated desktop application for preparing and reviewing video content. It uses YouTube API Services and is not offered as a public upload service.

It requests permission to read YouTube account information (youtube.readonly) and upload videos (youtube.upload). It checks the connected channel’s ID, name, and handle. Its current upload workflow supports separately approved private uploads; connecting an account does not approve an upload.

Data and storage

Local project records can contain channel details, authorization status and expiry, upload-related video IDs, API responses, publishing receipts, and account history. Exports and database backups can contain copies alongside original media. These records support channel verification, publishing and troubleshooting.

On Windows, OAuth tokens and temporary authorization material are stored in Windows Credential Manager, together with application client credentials. Project databases hold references to those credentials. Tokens are used to authenticate requests to Google; the project export process does not export the credential vault.

Retention and current limitations

Existing account records and historical copies have not been migrated to the new privacy controls. Some records have uncertain origins, and external backups have not all been identified. We cannot yet confirm complete deletion across every copy or automatic enforcement of retention limits for existing data.

New deletion, retention and restore protections have been tested offline but are not active for existing projects. Tests do not establish that real data has been cleaned up. Independently created media must be distinguished from API-derived records during cleanup.

The owner checks privacy email daily, including when Content Factory is closed, and handles verified requests within applicable deadlines. Cleanup is manual while the application is offline; it does not happen automatically. Receiving a request does not mean deletion is complete. Unresolved work must be tracked and reported rather than described as successful.

Disconnect, revoke or request deletion

Email privacy@yureistudios.com with privacy questions or deletion requests. Identify the application and affected account or channel. We may ask for proportionate ownership evidence. Never send passwords, tokens, API keys or authorization codes.

• Local disconnect stops the local publishing route. It does not revoke Google authorization or erase project records.
• Google revocation removes the application’s Google-side access. You can do this through Google account security settings.
• Stored-data deletion addresses application records and relevant copies. It is separate from disconnecting or revoking access, and remains subject to the limitations above.

Deleting application data does not delete videos or other data held by YouTube. Manage that information through YouTube. Removing local tokens alone does not prove Google-side revocation.

External services

Google and YouTube receive authorization requests, API requests and approved upload content. Optional AI features can send supplied creative context and research evidence to OpenRouter, Groq or NVIDIA. OpenRouter may pass requests to the selected model provider. Their terms and settings govern their processing; we do not promise that these providers retain no data or never use it for training.

Available history does not establish whether YouTube-derived data was included in past AI requests. Safeguards restricting such inputs have been tested but are not active for existing projects. We cannot claim that no YouTube data was shared. Exchanges between the owner’s tools can also copy research and publishing evidence and must be included in deletion review.

Privacy correspondence

Privacy emails pass through Cloudflare Email Routing to the owner’s Gmail inbox. They include your email address and the information you supply. They are used to respond, verify ownership, handle requests and record the outcome.

No fixed correspondence-retention schedule or automatic email-deletion process is currently in operation. Requests and related correspondence are handled manually, subject to applicable legal requirements and the deletion limitations described above. Removing a message from the owner’s mailbox does not guarantee immediate removal from the email provider’s internal backup systems.

Related policies

Read the Content Factory terms, Google Privacy Policy and YouTube Terms of Service. This notice describes current practices and limitations. Material changes will be dated here.