Privacy policy
Last updated 2026-11-11. This explains what Chenab (“we”) collects when you use this video studio, why, and the choices you have.
Who this service is for
The studio is a tool for adult creators and their teams to make and publish videos. It is not directed at children, and we do not knowingly collect personal information from anyone under 16. Channels may make content for children; the viewers of that content never use or sign in to this service.
What we collect
- Account details: your name, email address, password (stored as a secure hash) and optional passkeys or two-factor settings.
- Workspace content: channels, characters, scripts, footage, images, audio, renders and settings you create or upload.
- API keys you create so AI agents and apps can work in your workspace. Only a secure hash of each key is stored; the key itself is shown to you once.
- YouTube data, only if you connect a YouTube channel (see below).
- Billing details are handled by Stripe. We store your Stripe customer ID and the last four digits of a card, never full card numbers.
- Technical data: log entries, IP address and browser details needed to run and secure the service, and click counts on short links you create.
- Messages you send us through a contact page, or a request you choose to send us from the chat when the studio can't do something yet: your name, email address, the topic and what you wrote (for a chat request: what you asked, with email addresses and phone numbers removed, what the studio could not do and the nearest thing it could), and, if you are signed in, which account and workspace you sent it from.
- Error reports: when something breaks, a report of the error (what failed, the page or request, and your browser or device type). Reports do not include your name, email address or the content of forms, and we do not record your screen or sessions.
YouTube API Services
When you connect a YouTube channel, the studio uses YouTube API Services. By connecting, you also agree to the YouTube Terms of Service, and Google's use of data is covered by the Google Privacy Policy.
With your permission we access and store:
- your YouTube channel's ID, title, handle and picture, to show which channel is connected;
- an access token and refresh token (encrypted), to upload videos and thumbnails you choose to publish;
- comments on your videos, only when you ask the studio to read them, to turn viewers' requests into video ideas and to draft replies; a reply is posted to YouTube only after you approve it. Comments are deleted after 30 days, or when you disconnect YouTube;
- the details of videos you publish from the studio, and their public statistics and YouTube Analytics figures (views, watch time, subscribers, average view duration), to show you how your videos perform.
We only use this data to provide these features to you. We do not sell it or use it for advertising or to train AI models. Comments you ask the studio to read are sent to our AI writing provider to sort them and draft replies, routed only to model providers that do not store or train on them; no other YouTube data is sent to AI model providers. Analytics data that has not been refreshed from YouTube for 30 days is deleted.
YouTube data is shared or disclosed only with:
- the members of your workspace, who see the connected channel and how its videos are doing;
- AI agents and apps you connect with an API key from your workspace, which can read how its videos are doing (views, likes, comments, watch time and the channel's last 28 days). You choose which ones to connect, and revoking a key stops their access;
- our hosting providers, whose servers store it, and Cloudflare, which carries it to your browser and stores our backups, as service providers that may only use it to host the app for us;
- our AI writing provider, for comments you ask the studio to read;
- public authorities, only when the law requires it.
We do not transfer or disclose it to anyone else.
You can disconnect at any time with “Disconnect” on a channel's Publish tab, which revokes our access and deletes the stored tokens and analytics. You can also remove access from your Google account at myaccount.google.com/permissions.
Services we use
To run the studio we send data to these providers, only as needed for the feature you use:
- Hosting: our servers run with Hetzner in Germany.
- Cloudflare, which delivers the site, protects it from abuse (including a bot check on sign-up and the free tools) and stores your media and our backups (Cloudflare R2, in the EU).
- AI model providers, when you generate pictures, clips, voices, music or text. The prompts, reference pictures, scripts and transcripts needed for that step are sent to the provider that makes it. Which provider runs a step depends on the model and can change; we can tell you the current list on request.
- Pexels and Pixabay, for stock searches you make.
- BaniDB (Khalis Foundation), for Gurbani searches.
- Google (YouTube), and the social networks you connect, when you publish or sync analytics.
- Stripe, for payments.
- Resend, to send account and service emails.
- Sentry, which receives the error reports described above.
- Langfuse (in the EU), which receives the prompts and answers of the AI steps that make a video, with the models, timings and costs, so we can find faults and make videos better for less. It does not receive your name or email address, and nothing from videos made for children.
- Better Stack, which checks that the site is up. It does not receive your personal data.
We do not sell your data, and providers may only use it to do the work we send them.
Cookies and advertising
The site uses cookies it needs to work: keeping you signed in, protecting forms and remembering your theme, cookie choice and the account you last signed in with on that device. These are always on.
We advertise the studio on Google, Meta (Facebook and Instagram), TikTok, LinkedIn and Reddit. Only if you say yes on the cookie banner, their tags, loaded through Google Tag Manager, may set cookies to count visits (Google Analytics) and to measure which ads bring people here and show our ads to people likely to want them. They then receive the pages you visit and events such as signing up, starting a video or buying a plan or credits, with the amount, but never your name, email address, prompts or videos. Until you choose, and if you say no, these tags store nothing on your device and Google receives only anonymous signals without cookies. Each of these companies handles that data under its own privacy policy.
You can change your choice at any time with “Cookie settings” at the bottom of the site. These tags never run in the admin area or on the pages that show a video you shared.
How long we keep data
We keep your account and workspace content while your account is active. A deleted channel, episode or workspace disappears from the app straight away and is permanently erased, with its files, after 30 days (so mistakes can be undone). Deleting your account also deletes the workspaces only you belong to, the same way. Messages sent through a contact page, and requests sent from the chat, are deleted a year after we close them. Prompts we keep to look into faults are deleted after 14 days. Records we must keep for tax or legal reasons are kept as long as the law requires.
We keep backups so the service can be restored after a fault: the database is backed up daily and each backup is kept for 14 days, and media files are backed up weekly and removed from the backup 30 days after they are deleted from the app. So data you delete can stay in a backup for up to those periods before it is gone for good. Backups are encrypted, stored in the EU and only used to restore the service. Error reports are kept for up to 90 days.
Your choices and rights
You can view and change your details in Settings, download your videos at any time, disconnect YouTube, revoke API keys and delete channels or your account. Depending on where you live you may have further rights, such as access, correction or deletion; contact us to use them.
Security
Connections are encrypted in transit. Passwords and API keys are stored only as hashes, and YouTube and social tokens are encrypted at rest. No system is perfectly secure, so please use a strong password and two-factor authentication.
Contact
Questions or requests: [email protected]. We may update this policy and will change the date above when we do.