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 website has no registration, Google sign-in, advertising, or analytics scripts. Its only form is the project inquiry form described under Website project inquiries. Cloudflare hosts this website and processes website requests, including IP addresses and technical request information, to deliver and protect the site. See the Cloudflare Privacy Policy.
Website project inquiries
If you send a project inquiry through our Contact page, we receive the details you enter: your name, email address, project type and project description, plus your business name, existing website, approximate budget and timeline if you choose to share them. We use this information to review your request, reply to you and, where appropriate, prepare a written quote. Please don’t include passwords, payment details or other sensitive information.
The form also sends technical values used only to protect it and to recognize repeated submissions: an empty spam-trap field, the time the page was opened and how long the form was open, and a random reference created in your browser. To limit abuse, our website code keeps your IP address in temporary memory to count recent inquiries from the same connection, and stores with your inquiry a short coded value derived from your connection’s network address and the date, created with a private key and used only to limit repeated submissions; that value is erased about two days after the inquiry. Your IP address itself is not written to the inquiry database or included in the notification email. We store the random reference, or a one-way fingerprint of the inquiry if JavaScript is turned off, with your inquiry so that a repeated submission is not recorded twice.
If you send an inquiry while a website offer is running, we record with your inquiry that it arrived during the offer, which offer and offer period it was, and whether you reached the form from the offer’s button, and we include this in the notification email, so that the offer can be considered in your proposal.
When you send an inquiry, it is stored in a database that Cloudflare operates for us (Cloudflare D1), and a notification containing your inquiry is emailed to a Yurei Studios business mailbox through Microsoft 365, which also delivers a copy to the founder’s Yurei Studios mailbox. If the notification cannot be sent straight away, your inquiry stays in the database and the notification is tried again. Our website code does not log inquiry contents; it records only status codes and the short inquiry reference. Cloudflare processes website request and platform data under its own policies, and Microsoft 365 email is governed by the Microsoft Privacy Statement.
The owner reads and answers inquiries. Access to the inquiry database and our mailboxes is limited to Yurei Studios personnel who need it to respond to inquiries, and to the service providers named in this notice. We do not add you to a mailing list, use your inquiry for advertising, or sell it.
Cloudflare and Microsoft may process and store inquiry information in Canada, the United States or other countries. While it is outside Canada, it is subject to the laws of those countries and may be accessible to their courts, law enforcement and national security authorities.
If an inquiry does not lead to a project, we delete it from the inquiry database and our mailboxes about 12 months after we receive it. If it leads to a project, we keep the inquiry and related project correspondence for the duration of the project and afterwards for as long as we need them to meet legal, tax and accounting requirements. Deleting an inquiry removes it from the database and our mailboxes but does not guarantee immediate removal from Cloudflare’s or Microsoft’s internal backup and recovery systems. To ask about, correct or delete an inquiry, email privacy@yureistudios.com.
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 are delivered through Microsoft 365 to Yurei Studios business mailboxes that the owner reads. 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.