Privacy Policy
Last updated November 6, 2026
The short version
Vidblast turns a topic into a narrated, captioned video using a mix of footage sources (a B-roll library, stock clips, real YouTube clips, or AI-generated visuals) and a handful of third-party services: an authentication provider, a payment processor, and a few AI/media APIs that do the actual generation work. This page lists exactly what we collect, which of those services see it, and why. We don't sell your data, and we don't run ads or ad trackers of any kind.
Who this covers
This policy covers vidblast.ai and the Vidblast dashboard, referred to here as "Vidblast," "we," or "us." It applies to anyone who creates an account, generates a video, or subscribes to a plan.
Information we collect
- Account information. When you sign up, our authentication provider, Clerk, collects your email address and, depending on how you sign in, your name and profile image. Clerk manages passwords and login sessions directly. Vidblast never sees or stores your raw password.
- Billing information. Subscriptions are handled by Stripe. We never see or store your full card number. Stripe processes payment and tells us your subscription plan, status, and renewal date. We store that status plus a Stripe customer ID so your dashboard reflects the right plan and credit balance.
- What you submit to generate a video. The topic or prompt you enter, and the settings you choose: length, tone, narrator voice, orientation, footage sources, caption style, and any style/template selection.
- No customer footage uploads. Vidblast doesn't currently accept footage uploads from customers. The B-roll and transition clips used in your videos come from a library Vidblast maintains. If that changes, this policy will be updated to cover it.
- Generated content. The script, narration audio, captions, footage selections, and finished video file produced from your request, plus the job's status and history.
- Usage and credit data. Which plan you're on, your credit balance and how it's been spent, and basic operational logs (timestamps, job status, error messages) used to run and debug the service.
What gets sent to third parties, and why
Generating a video is a pipeline with several steps. Here's what each one actually sends out:
- Script writing. Your topic and settings are sent to a hosted language-model API to write the script: kie.ai's model API (which proxies models such as GPT or Claude, depending on your plan). Only the topic, your settings, and the generated text are sent. The same API is also used to plan visuals from your script (search terms, image prompts, and footage matching).
- Narration. The finished script text is sent to a text-to-speech service to synthesize the voice-over: Fish Audio, or Microsoft's edge-tts when Fish Audio cannot narrate.
- Captions. Timed on our own server using faster-whisper against the narration audio we already produced; for Fish Audio narration, word timings come back from the narration service along with the audio itself. Either way, nothing extra is sent to a third party for this step.
- Footage. Depending on the sources your job enables: B-roll from Vidblast's own library is matched entirely on our servers (nothing sent out); a few stock clips per video are searched and downloaded from Pexels and blended in with it; real YouTube footage is located via YouTube search and, to confirm a clip actually matches your script, a low-resolution (360p) copy of each candidate video (up to its first 15 minutes) is downloaded, cut into shots on our servers with one small still frame of each shot described by kie.ai's model API, and then deleted from our servers, keeping only the few-second excerpts actually used in your video; AI-generated images and video clips are produced by kie.ai's image/video models from a text description derived from your script (or a prompt you type when regenerating a scene). No existing footage is used as an input to that generation.
- Storage and delivery. Finished videos and scene assets are stored on Cloudflare R2 so the dashboard can stream them quickly; job records live in a Postgres database we operate on Railway.
We don't sell your data to anyone, and none of these third parties are used to train a model on your content beyond what's inherent to generating your own video (e.g., an LLM processing your prompt to write your script).
Cookies and tracking
Vidblast doesn't run analytics, advertising, or third-party tracking scripts of any kind. The only cookies set are functional ones from Clerk (to keep you signed in) and Stripe (during checkout), both necessary for the product to work, neither used to track you across other sites.
Data retention and deletion
We keep your account data and generated videos for as long as your account exists, so your job history stays available. Canceling a subscription stops future billing and credit renewal, but doesn't delete your account or the videos you've already made. Those stay accessible until you ask us to remove them. If you want your account and associated data deleted outright, email us (below) and we'll delete it, generally within 30 days.
Your rights
Depending on where you live, you may have the right to access, correct, export, or delete the personal data we hold about you, or to object to certain processing. Most of this you can already do yourself from Settings in the dashboard (job history, billing details); for anything else, email us and we'll handle it directly.
Children's privacy
Vidblast isn't directed at children, and we don't knowingly collect personal information from anyone under 13. If you believe a child has created an account, contact us and we'll remove it.
International data transfers
Our infrastructure and the third-party services listed above (Clerk, Stripe, kie.ai, Fish Audio, Cloudflare, Railway) operate internationally, which means your data may be processed in countries other than the one you live in. Each of those providers maintains its own safeguards for cross-border data transfer under its own privacy policy.
Changes to this policy
We'll update the date at the top of this page whenever this policy changes in a meaningful way. This document describes the product's actual data flow as of that date. It's written to be accurate, not as reviewed legal advice. If you're relying on this for compliance purposes, especially across jurisdictions like the EU (GDPR) or California (CCPA), have it reviewed by a lawyer first.
Contact
Questions, deletion requests, or anything else privacy-related: carl.temming@gmail.com.