Raccoon Factory
Privacy Policy
Effective date: September 14, 2026
Raccoon Factory is a single-owner application for creating original animated videos and uploading them to the owner's authorized YouTube channel.
1. Scope and operator
The application is operated by the individual owner of the «Еноты на нервах» YouTube channel. It runs on the owner's private infrastructure and is not offered as a service for connecting other users' accounts. This policy covers that application and this informational website.
Contact for privacy matters: rybalko.nikita@gmail.com.
2. Data and Google permissions
Authorization takes place through Google OAuth, not through this website. Raccoon Factory does not receive or store the owner's Google password. The application requests:
youtube.upload: to upload the owner's finished videos and their titles, descriptions, tags and selected upload settings.youtube.readonly: to identify the authorized channel and check the processing and privacy status of uploaded videos.
Locally stored Google API data can include the authorized channel ID and title, uploaded video IDs, processing and privacy status, failure details and status-check timestamps. OAuth access and refresh tokens are stored to maintain the authorized connection. The application does not use this connection to read Gmail, contacts or Google Drive files.
Original scripts, generated speech, images, final videos and owner-created upload metadata are production assets. They are separate from data retrieved through the YouTube API.
3. Use and sharing
Google API data is used only to operate and troubleshoot the owner's requested YouTube connection and uploads. It is not sold, used for advertising or audience profiling, or used to train or improve artificial intelligence models.
Raccoon Factory's use and transfer of Google API data is subject to the Google API Services User Data Policy, including its Limited Use requirements.
Google/YouTube receives the uploaded video, metadata and API requests needed to provide its service. Independently of the YouTube connection, original production prompts and scripts are sent to OpenAI for text generation, and dialogue text is sent to ElevenLabs for speech generation. The application does not send Google OAuth tokens or data retrieved from the YouTube API to these generation providers.
The owner has access to the locally stored data for operation and troubleshooting. Data may also be disclosed where necessary to comply with a binding legal obligation. Provider processing is described in the Google Privacy Policy, OpenAI Privacy Policy and ElevenLabs Privacy Policy.
4. Storage, security and retention
Application records and production assets are stored on the owner's private computer infrastructure. OAuth credentials are held in access-restricted local files, separately from the public website and source repository. Requests to Google use HTTPS. The site does not host credentials, a production database or an upload console.
The following retention rules apply to the owner-operated application:
- Retain API-derived metadata only while needed for the authorized upload workflow; review it and refresh or delete it within 30 days, as required by the applicable YouTube API policies.
- Delete locally stored OAuth tokens when the connection is removed. Following a verified data-deletion request or an in-app revocation, remove the associated API-derived records within seven days.
- After access is revoked through Google, stop using the authorization and remove the associated stored API data within the applicable 30-day period, or sooner when the owner requests deletion.
- Local operational backups have a seven-day retention window. Deleted data must not be restored into active use; if recovery is necessary, the deletion must be reapplied.
Retention reviews and deletion requests are the owner's responsibility. This informational website does not perform them. Original production assets are retained separately until the owner removes them. Deleting local records does not delete an already uploaded video from YouTube.
5. Revoke access, correct or delete data
- Open your Google Account third-party connections, select Raccoon Factory, and remove its access. This prevents the application from continuing to use that authorization.
- To remove local data as well, use the application's owner-operated revoke procedure or send a request to the contact below. Specify Raccoon Factory and the relevant channel URL. Do not send a password, token or verification code.
- To change visibility or delete videos already on YouTube, use YouTube Studio. Removing app access alone does not delete uploaded videos.
You may also contact the owner to request access to or correction of application-held data. Requests are verified using only information necessary to establish control of the relevant account.
6. Website visitors
This static website has no sign-in, forms, embedded video player, advertising pixels or application analytics scripts. It does not set its own cookies or store browser preferences. Following an external link takes you to a separate service governed by that service's policies.
Cloudflare Pages hosts and delivers the website. Cloudflare may process technical request information, such as an IP address, request time and browser information, to deliver and secure the site. See Cloudflare's Privacy Policy.
The application is an owner-operated production tool, not a service directed to children. It does not offer accounts for children.
7. Contact and updates
Privacy and support contact: rybalko.nikita@gmail.com.
Updates to this policy will appear on this page with a revised effective date. Material changes in how Google data is used require an updated disclosure and, where required, renewed consent before that use.
Коротко: доступ нужен для загрузки собственных видео и проверки их состояния. Пароль Google не сохраняется; данные YouTube не передаются моделям генерации. Отозвать доступ можно в настройках Google, а удаление локальных данных запросить у владельца проекта.