Turbinio Privacy Policy

Effective date: 22 September 2026.

Turbinio assembles short vertical videos from the takes you record and, when you tell it to, publishes the finished video to your YouTube channel.

This policy is short and plain. We collect little, and saying so does not require convoluted language.

Who we are

Turbinio is operated by Broutonlab Technologies, at Bar Rav David 30, Haifa 3559203, Israel ("Turbinio", "we", "us"). We are the controller of the personal data described in this policy. Website: turbinio.com. Privacy and support contact: support@turbinio.com.

What we receive from you

Your account. Sign-in runs through Clerk. All we keep is the user identifier Clerk issues and the authentication information needed to maintain your session. Clerk processes the account information you give it, which may include your name, email address and credentials. We do not receive or store your password.

Your footage. The video files you upload, and everything you say about them: names, trim boundaries, scene order, dubbing languages.

Your settings — what each video is made of, the publishing schedule, titles.

Service and security data. Our server may record the time of a request, the requested route, response status, account identifier, IP address, browser or device information, and diagnostic information. We use these records to operate, secure and troubleshoot the service; not for advertising or cross-service tracking.

The speech in your takes. We transcribe it in order to fit the dubbing to the original pauses and to suggest titles. Speech recognition runs on our own server, and no audio is sent to an external provider for transcription. If you ask us to clone a voice, selected voice samples do go to the speech provider — see "Who we share it with" below.

What we deliberately do not receive. A video file usually hides details the person filming never thinks about: the coordinates of the place, the device model, the date and time. We strip them on intake, at the same moment we bring the file to a single technical shape. Neither location nor device information stays with us — not in storage, not in backups, not in what goes to the platform.

What we receive from YouTube

We contact YouTube only with the permission you grant through Google's consent screen, and what we receive is exactly this:

Permission to access your channel. Technically a long-lived key that proves your consent to YouTube. We store it because without it we cannot publish your video at the hour you chose.

Your channel's id and title. Only so we can show you which channel is connected, so you never confuse yours with someone else's.

Data about videos published through Turbinio. We receive and store their YouTube video IDs, upload and visibility status, any rejection or failure reason, and the view, like and comment counts returned by YouTube. We use these data to show publication status and analytics to the channel owner and to help evaluate which takes perform better.

We do not request your YouTube password, subscriptions, viewing history, the text or authors of comments, or data about videos that were not published through Turbinio.

What we use it for

We use the data to provide the features you request: authenticate you, process and store your takes, assemble, subtitle and dub videos, generate and translate text, publish at the time and with the visibility you select, show publication status and analytics, provide support, prevent abuse and maintain security.

Where applicable, our legal bases are performance of our agreement with you, our legitimate interests in operating and securing Turbinio, your consent (including Google OAuth and voice-cloning consent), and compliance with law. You may withdraw consent at any time without affecting processing already carried out lawfully.

We do not sell your data. To anyone, under any circumstances.

We do not show you advertising and do not pass your data to ad networks.

We do not use your footage or Google user data to train our own models. Third-party AI providers process only the inputs needed to provide the feature you request, subject to their applicable business/API terms and our configuration with them.

Who we share it with

Only those without whom the service does not work, and only as much as needed. We name them, because "trusted partners" tells you nothing:

• Google / YouTube — the video itself, its title and its description, when you tell us to publish it;
• Clerk — sign-in and accounts;
• OpenAI — four things, and nothing else. When you ask for a suggested title or description: six still frames from the take and the transcript of its speech. When you publish to a channel in another language: the title and the description, for translation. When you order a dubbed track: the transcript of the speech, for translation into the language you chose. When you ask us to pick keywords for your project: the transcripts of its takes and what you wrote about the channel, to turn into search phrases;
• DataForSEO — only the search phrases themselves, to ask how much they are searched for on YouTube. Nothing of your footage, your text or your account goes with them;
• HeyGen or Inworld, when the configured external speech provider is used — the text to synthesise and, for voice cloning, selected voice samples;
• an object storage provider — a backup copy of your prepared take files;
• the hosting provider running Turbinio.

These providers process data to supply their services to us. They may process data in countries other than yours, subject to contractual safeguards and applicable law. We do not disclose Google API data to advertising platforms, data brokers or information resellers, and do not use it for advertising, credit decisions or surveillance.

How long we keep it

As long as needed for your account and the service. Delete a project and we delete its associated working files, subject to the limited time needed to remove backup copies. Disconnect a channel and we delete its access token and stored YouTube API data.

Assembled videos are a cache, not a store. A video is put together the moment it is needed and is evicted once the cache fills up; it can always be rebuilt from your takes.

Your channel's data, once a day. We ask YouTube afresh for your channel's id and title every 24 hours — which is also how we confirm each time that we still have your permission. If that fails for 30 days running, we erase the channel data YouTube gave us. What is yours — the channel's language, your schedule — stays: you did not lose it.

Delete your account and we delete your account data: footage, settings, channel permissions and stored YouTube API data, except information that we must retain for legal, security or dispute-resolution purposes. We delete data requested by you as soon as possible and no later than seven calendar days; backup deletion may follow the backup provider's normal rotation cycle.

How to revoke access

With us — disconnect the channel in the Publishing section.

With Google, independently of us — go to Google security settings, find Turbinio and revoke access. After that we cannot reach your channel even if we wanted to.

Delete your account or exercise a privacy right — write to the privacy contact above. Depending on the law where you live, you may have rights to access, correct, erase, restrict or object to processing, obtain a portable copy, withdraw consent, and complain to your data-protection authority. We may need to verify your identity before acting on a request.

YouTube data: required notices

By using Turbinio's YouTube features you agree to the YouTube Terms of Service: YouTube Terms of Service.

Turbinio uses YouTube API Services. Google's handling of data is described in the Google Privacy Policy: Google Privacy Policy.

We keep YouTube data no longer than the service requires. We delete it the moment you disconnect a channel or delete your account, and in any case within seven days of your asking. Data received from YouTube that we do keep is re-confirmed with YouTube every 24 hours, and never held for more than 30 days without such confirmation.

Compliance with Google's policy. Turbinio's use and transfer of any information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Security

OAuth tokens are stored server-side and are transmitted only to Google's OAuth and YouTube API endpoints, when a request to your channel requires it. They are never exposed to the browser, never returned by our interface and never deliberately written to our logs. Traffic to the service runs over an encrypted connection. Access to the server is limited to those who need it for their work.

Nobody can promise complete invulnerability, and we will not either.

Cookies and local storage

Turbinio and Clerk use cookies or equivalent browser storage necessary for sign-in, session security, language preference and operation of the service. Turbinio does not use advertising cookies. If optional analytics or marketing technology is introduced, this policy and any legally required consent mechanism will be updated before it is enabled.

Children

Turbinio is not intended for anyone under 16, and we do not knowingly collect their data.

Changes

We may change this policy. Material changes will be shown inside the service or otherwise communicated to you. If a change materially expands our use of YouTube API data, we will ask you to accept the updated policy before that use begins. The effective date is at the top.

Questions

Write to us: support@turbinio.com or Bar Rav David 30, Haifa 3559203, Israel.