Last updated: October 16, 2026
This Privacy Policy explains what information Reeliable ("we", "us") collects when you use the Reeliable application (the "Service"), and how that information is used, stored, and shared.
Account information. When you sign up, we collect your email address and authentication credentials through our authentication provider (Supabase). We never see or store your raw password.
Content you provide. Text prompts, article URLs, and audio files you upload to generate a video, along with any script edits you make.
Generated content. The scripts, narration audio, images, video clips, and final videos the Service generates on your behalf, stored so you can view, edit, and re-download them later.
Usage data. Which features you use, how many videos you generate, and estimated/actual cost per generation, used to enforce usage limits and show you your own usage.
Connected account tokens. If you connect YouTube, TikTok, or Instagram to publish videos directly from Reeliable, we store an OAuth refresh token for that connection. This token is stored securely on our servers, is never exposed to your browser, and is used solely to publish videos to the account you explicitly connected, at your explicit request.
We use the information above only to operate the Service: to generate and store your videos, to publish a video to a platform you've connected when you ask us to, to track and enforce usage limits, and to provide customer support. We do not use your content or account information for advertising, and we do not sell your information to third parties.
To generate a video, the content of your request (your prompt, script text, or uploaded audio) is sent to the AI providers we use for that step: OpenAI (script writing, narration voice, image generation, transcription), Google Gemini, Replicate and fal.ai (AI-generated video clips, songs and music, vocal separation, lip-sync and some images), ElevenLabs (additional narration voices and music), HeyGen (presenter avatar videos), and Pexels (licensed stock footage). Photos you upload for a character, avatar or performance are sent to the provider for that step too. Each provider processes this data under its own privacy policy and only for the duration needed to fulfil that request.
Rendering the final video is performed by Trigger.dev, a background-processing provider — it receives your video's scene images/audio and combines them into the final file, but never receives your account credentials.
Your account, generated content, and usage data are stored using Supabase (database, authentication, and file storage). The Reeliable web application itself runs on Railway. Account and notification emails are sent through Resend.
If you buy a plan or credits, payment is processed by Stripe. Stripe collects your card and billing details (and, where tax applies, your billing address) under its own privacy policy; we never receive or store your full card number. We keep only your Stripe customer reference, your plan, your billing period and a record of the credits you bought.
If you choose to connect a YouTube account, Reeliable uses the YouTube API Services for three things, each only for your own channel and only after you connect it:
We store the YouTube video IDs and these results with the matching project, and an access token so we can act on your behalf. We do not sell this data, use it for advertising, or show it to anyone else. The titles and results of your own videos may be sent to our AI provider only to generate topic suggestions for your own channel. You can disconnect YouTube at any time from Reeliable's Settings page, which deletes our stored access token, or revoke access directly from Google's security settings. Results already saved with a project stay until you delete that project, and you can ask us to delete everything at any time.
Reeliable's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
By using Reeliable's YouTube publishing feature, you also agree to be bound by the YouTube Terms of Service. Your use of YouTube API Services data is additionally subject to the Google Privacy Policy.
We retain your generated videos and account data for as long as your account is active, so you can continue to access and edit your work. You can delete an individual project at any time from your Projects page, which deletes its generated files from storage. You can also delete your whole account yourself, at any time, from your Account page ("Delete my account"): it permanently removes your account, videos and their files, saved decks, brand kits and logos, Auto Mode sequences, connected platforms and brands, and cancels any subscription. Brands you own are deleted with the account, so anyone you invited loses access. If you'd rather have us do it, or you can't sign in, contact us using the details below. Some records may be kept where the law requires it, for example payment records held by Stripe.
We use a single essential cookie set by our authentication provider to keep you signed in. We do not use advertising or third-party tracking cookies.
If we make a material change to what data we collect or how we use it, we'll update this page and change the "Last updated" date above.
Questions about this policy or your data can be sent to prasant.satpathy@tethik.com.
See also our Terms of Service.