Privacy policy
Last updated: November 2, 2026
This policy explains what VideoToBlog (“we”, “us”) collects when you use https://videotoblog.com, the blogs we host on our subdomains, and any custom domain you point at us. Using the service means you accept it.
What we collect
Your account
Your email address, and your name and profile picture if you sign in with Google. You can sign in with a one-time code sent to your email instead, in which case we only ever have your email address.
Your YouTube channel
When you connect a channel we store its public details (channel ID, title, handle and avatar) along with the videos we sync: titles, descriptions, publish dates, thumbnails and transcripts.
For each video we write an AI summary and topic tags, so we can link your posts together and give you a brief of your whole channel. If you add a channel by pasting its URL instead of signing in with Google, we only ever read its public data.
We also store a Google OAuth refresh token so we can keep syncing new uploads without asking you to reconnect. It is encrypted before it reaches our database and is never sent to your browser. Disconnecting the channel deletes it. You can also revoke our access at any time from your Google account security settings.
Your content
The posts we generate, plus any edits you make and the settings for your publication: name, logo, custom domain, links and SEO fields. When our post agent changes a published post, we keep the previous version so you can undo it.
Free articles in your browser
Free-converter articles are not saved to your account. You can opt into a temporary copy in your browser on this device. Recovery expires after 24 hours, and expired storage is removed the next time you visit the converter. You can delete it sooner using Delete temporary copy. The personal blog preview stays in your browser and does not publish a site.
Your team
If you invite teammates to help manage a channel, we store the email addresses you invite so we can grant them access when they sign in.
Billing
Whether you're on a paid plan, your renewal date, and identifiers from Stripe. Card numbers go to Stripe directly and never touch our servers.
Usage
How many posts you've generated in the current period, so we can apply plan limits.
What we do with it
We use it to run the product: sync your videos, generate and host your posts, keep published posts linked and up to date, apply your plan's limits, and email you about your account (a welcome message, a note when a post is published, and sign-in codes). We do not sell your data, and we do not share it for advertising.
Who else processes your data
Running the service means sending data to a few companies, each for one job:
| Convex | our database and backend |
|---|---|
| Vercel | hosting for the site and your published blogs |
| Google / YouTube | sign-in, and reading your channel and videos |
| ScrapeCreators | fetching video transcripts |
| OpenAI | writing and maintaining your posts, reached via Vercel AI Gateway |
| Perplexity | web searches our post agent runs to check facts in your published posts, reached via Vercel AI Gateway |
| Stripe | subscriptions and payments |
| Bento | product usage analytics and signed-in account identification |
| Simple Analytics | cookieless marketing-site traffic analytics |
| Resend | account and sign-in emails |
Video transcripts and post text are sent to OpenAI to write and maintain your posts. We do not use your content to train our own models.
Analytics
Our app and marketing pages use Bento to understand product use, such as conversions, exports, plan selection and setup progress. Signed-in accounts are identified by their email address. Funnel events contain named actions and limited choices such as billing period; they do not include article text, video URLs or article titles. Customer-hosted blogs do not receive these app analytics.
Our marketing site uses Simple Analytics, which is cookieless and does not track individuals across sites.
The blogs we host for you count page views so you can see what gets read: a total per page per day, and a total per day of where visits came from (just the referring site's name, like Google or YouTube, never the address), with no cookies, no IP addresses and nothing that identifies a reader. They carry no other analytics by default. If you add your own Plausible, Google Analytics or Fathom ID in your publication settings, that provider's script runs on your blog and their privacy policy applies to your readers. That's your choice to make and yours to disclose.
Anything you publish is public
Posts you publish, and the pages of your publication, are on the public internet by design, indexed by search engines and readable by anyone. Please don't put anything in them you wouldn't want public. Drafts stay private.
Keeping and deleting data
We keep your data while your account is open. Disconnecting a channel removes its OAuth token; its blog, posts and videos stay so you can add it again. Deleting a blog removes its pages and uploaded images. To delete your account and everything attached to it, use Delete your account at the bottom of the Billing page in your dashboard (it cancels your subscription too), or email us at the address below. You can download all your posts from the Posts page first.
Your rights
Depending on where you live you may have the right to see, correct, export or delete the personal data we hold about you. Email us and we'll help. We won't ask you to justify the request.
Children
VideoToBlog isn't intended for anyone under 13, and we don't knowingly collect their data. If you believe a child has given us personal information, contact us and we'll delete it.
Changes
We may update this policy. Material changes will be announced by email or in the app, and the date at the top will change.
Contact
Questions, requests, or anything else: andy@videotoblog.com