Last updated: September 2, 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 and Replicate and fal.ai (AI-generated video clips), ElevenLabs (additional narration voices), and Pexels (licensed stock footage). 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), hosted on infrastructure provided by Railway.
If you choose to connect a YouTube account, Reeliable uses the YouTube API Services to upload videos to that account on your behalf, only when you explicitly click publish. We request only the permission needed to upload a video (we cannot read your existing videos, comments, subscriptions, or any other YouTube data). You can revoke this access at any time from Reeliable's Settings page, or directly from Google's security settings.
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. If you'd like your entire account and all associated data deleted, contact us using the details below.
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.