Privacy policy

scene-pilot (https://scene-pilot.minav.ru) is run by its owner, Sergey Minav, who is responsible for it and for this policy. “We” below means the owner. Contact: it.minav@gmail.com.

scene-pilot is a publishing service for video creators and teams, intended for external users as well as its owner. Access is currently provided by invitation; there is no public self-service sign-up yet.

The owner currently creates panel accounts. Users connect channels they are authorized to manage and publish only videos they own or have permission to use.

scene-pilot uses YouTube API Services. By connecting a YouTube channel you agree to the YouTube Terms of Service, and the Google Privacy Policy applies.

Panel accounts. We keep:

• your user name, role and when you were last active;
• your password only as a salted scrypt hash — never in plain text;
• a session cookie that keeps you signed in for up to 14 days;
• the IP address of each sign-in (you see it in your list of sessions) and of failed sign-in attempts (in the security journal);
• a journal of actions in the panel: who uploaded, changed, scheduled or deleted what;
• your Telegram chat ID, if you link Telegram for notifications.

Google user data. A YouTube channel is connected only through Google's consent screen. When you connect one, we receive and keep:

• the OAuth refresh token for that channel — stored encrypted;
• a short-lived access token, obtained when checking the connected channel or uploading and held only in memory — never stored;
• the authenticated channel ID and title, retrieved with your youtube.readonly consent and stored to display and confirm the upload destination; these are removed when you disconnect the account or its authorization is revoked;
• for each upload: the video ID YouTube returns and the link to the video, stored with the title, description, tags and time of the upload; while an upload is running, the address of its resumable upload session, so that an interrupted upload continues instead of starting over.

We request youtube.upload to upload the videos you schedule and youtube.readonly to retrieve the connected channel ID and title through channels.list(mine=true). We do not use read-only access to read your other videos, comments, subscribers or analytics.

Other platforms. If you connect accounts on other video platforms, their sign-in data is kept on our server — passwords, tokens and saved sessions encrypted — and used only to publish the posts you schedule there.

Your content. The videos you add to the library, with their audio and subtitle tracks; what is made from them — transcripts, scene lists, frame positions, plans, subtitles, titles, descriptions and tags; the music, banners and promo clips you add; and the post files the server assembles for publishing.

Cookies and browser storage. One session cookie keeps you signed in; one more cookie and your browser's local storage remember interface choices (theme, language, menu, editor settings). There are no advertising or analytics cookies and no third-party trackers.

Only to provide the features you use: signing in and access control; analysing your videos and preparing plans; assembling and uploading the posts you schedule; showing you what was published and notifying you about it; keeping the service secure.

Google user data is used only to identify and confirm the connected channel, upload the videos you schedule to it and show you the result.

scene-pilot's use and transfer of information received from Google APIs to any other app will adhere to Google API Services User Data Policy, including the Limited Use requirements.

• We use Google user data only to confirm your upload destination and provide the upload feature you asked for.
• We do not use it for advertising, and we do not sell it.
• We transfer it only as needed to provide that feature — to Google itself when checking the connected channel or uploading, and, if you linked Telegram, the title and link of your published post in a notification to your own Telegram chat — or when the law requires it.
• No person reads it, except the members of your workspace who see the connected channel and upload results in the panel, or where you have given consent, where it is needed for security or to investigate abuse, or where the law requires it.
• It is never sent to an AI model and never used to develop, improve or train AI or machine-learning models.

Speech recognition, scene detection and face and person detection run on the owner's own computer. Face detection only finds where faces are in a shot to place the vertical frame; it does not identify anyone, and nothing but frame positions is kept.

The language model that suggests cuts and drafts titles runs there too or, if the team chooses, at a hosted provider (OpenAI or Anthropic). It receives only text made from your videos — transcripts and scene lists — never Google user data, passwords or tokens.

• Google / YouTube — the videos you publish there, with their titles, descriptions and tags.
• Other video platforms you choose to connect — the posts you publish there.
• Telegram — notifications, if you linked it.
• OpenAI or Anthropic — transcripts, only if the team chose a hosted language model.

Uploads may pass through a network proxy or tunnel chosen for the account; the connection to the platform stays encrypted end to end (HTTPS). We do not sell any data.

• Data is kept on our own server and, for analysis, on the owner's own computer.
• Over the internet the panel is served only over HTTPS; connections to Google use HTTPS.
• OAuth refresh tokens, app secrets, and saved passwords and sign-in sessions for other platforms are encrypted at rest (Fernet: AES-128 with HMAC-SHA256). The key is kept only in the server's environment — not in the database and not in its backups.
• Passwords are stored only as salted scrypt hashes.
• The database is backed up daily, and each backup is kept for no more than 7 days. Expired backups are removed even if a new backup cannot be made.

• Our publication history (the title you supplied, schedule and outcome) is kept until you ask us to delete it. YouTube API responses, video identifiers, links, upload sessions and any saved statistics are removed from the live database within 21 days; remaining backup copies expire within 7 more days.
• Removing a connected YouTube account in scene-pilot first revokes its authorization with Google. Once Google confirms the revocation, we remove the existing shared database backups containing its data, immediately remove its stored token and YouTube API data, delete its settings and sign-in files, and cancel unfinished posts. Backup creation is paused during deletion so that a concurrent backup cannot preserve the deleted data. If revocation or deletion cannot be completed, we report the error and keep the account available to retry.
• Videos stay in the library until the team removes them — which deletes the file and everything made from it — or until you ask us to delete them. Assembled post files are kept as the record of what was published, until you ask us to delete them.
• To have your data deleted — the token, upload records, content or your panel account — write to it.minav@gmail.com; we delete your stored data, including database backup copies, within 7 days of receiving your request. When processing a request to delete YouTube data, we disconnect the account and remove the existing shared database backups containing that data. To automatically delete YouTube API data, revoke access as described below; no email is required.

Deleting data or disconnecting a channel in scene-pilot does not delete videos or other data held by YouTube. To delete a video on YouTube, use YouTube's own website or application. scene-pilot does not request permission to delete your YouTube videos.

You can revoke scene-pilot's access to your Google account at any time on the Google security settings page. We check authorization hourly, including for frozen accounts. When Google confirms that a refresh token is expired or revoked, we automatically delete that token and the YouTube API data stored under its authorization, and stop unfinished uploads. Remaining backup copies expire within 7 days of that cleanup. We delete associated YouTube API data, including backup copies, as soon as possible and no later than 30 calendar days after you revoke access through Google's security settings. The 21-day limit on API data in the live database and the 7-day limit on backups also apply while authorization checks are unavailable. Your source videos and editing plans remain in scene-pilot until you delete them.

scene-pilot is intended for adult video creators and teams. It is not directed to children under 16, and accounts are not created for them.

When this policy changes, we update this page and its effective date. We will not use Google user data in a new way without asking for your consent first.

Questions about this policy or your data: it.minav@gmail.com.