1. Who we are
Synthvids ("Synthvids", "we", "us", "our") operates the website and service at https://synthvids.ai (the "Service"). Synthvids is an AI video production tool that helps creators research topics, generate scripts, synthesize voiceover, render video, and — at the creator's direction — publish the resulting videos to their own connected channels.
This Privacy Policy explains what information we collect, why we collect it, how we use and share it, and the choices you have.
Controller / operator: JB Malcolm LLC
Mailing address: c/o Northwest Registered Agent, 2108 N St, Ste N, Sacramento, CA 95816
Contact: [email protected]
If you have questions or complaints about our privacy practices, contact us at [email protected]. We respond to privacy requests within 30 days.
2. Information we collect
We collect only what we need to run the Service, and we are direct about what happens to it. In short: your account is private, your content is yours, and we do not sell any of it. The detail follows, and Section 2.5 states plainly how we treat the material you create.
2.1 Information you give us
- Account information. Your name, email address, and profile image. If you sign in with Google, we receive this from your Google Account (see Section 3).
- Billing information. Subscription tier and billing status. Card details are collected and stored by Stripe, our payment processor — we never receive or store full card numbers.
- Free sample videos. We keep a normalized form of your account's email address (lower-cased, with any "+tag" removed and, for Gmail addresses, the dots in the name removed) so each person gets the free sample videos only once. These keys are deleted within 30 days after the offer ends.
- Free render trial (closed to new accounts since October 13, 2026). For an account whose free render trial started before then, we keep a normalized form of your account's email address (lower-cased, with any "+tag" removed and, for Gmail addresses, the dots in the name removed, since Gmail ignores them), a hashed identifier of the device you sign up from (a random id stored in a first-party cookie on that browser), and a hashed form of your network address (for IPv6, of its /64 network). For the free trial we keep only these one-way hashes, never the raw device id or network address. We use them only to make sure each person, device and network starts a limited number of trials, including after an account is deleted.
- Free trial card check (until October 11, 2026). We no longer ask for a card for the free trial. Accounts that verified a card before then were never charged; from that check we keep only a one-way card fingerprint provided by Stripe (it cannot be turned back into a card number), used only so each card starts one trial.
- Content and configuration. Channel settings, topic sources, prompts, voice selections, uploaded reference images, and any other input you provide to configure a video.
- Third-party API keys you choose to provide. If you supply your own keys for optional providers (for example, a voice provider), we store them encrypted and use them only to make requests on your behalf. These encrypted values are never read by a human reviewer, and are decrypted only at the moment we make the specific request you authorized — never for any other purpose.
- A Reddit session cookie, if you choose to provide one. If you use the Reddit research source, you may optionally copy your own Reddit login session cookie from your browser and paste it into your channel settings. This lets Synthvids fetch Reddit content as your logged-in session instead of as an anonymous visitor, which Reddit blocks after a few requests. The cookie is stored encrypted, is never shown in logs, and is used only to fetch content on your behalf when that channel's Reddit source runs.
- Support communications. Messages you send us.
2.2 Information we generate
- Generated media. Scripts, voiceover audio, images, and rendered video files produced from your inputs, along with associated metadata (titles, descriptions, thumbnails).
- Usage and job records. Render jobs, timestamps, credit consumption, error and status logs, and diagnostic information about failed jobs.
2.3 Information collected automatically
- Technical data. IP address, browser and device type, referring pages, and pages viewed.
- Cookies and similar technologies. We use cookies that are strictly necessary to keep you signed in and to secure your session. If you arrive from one of our own ads or campaign links, a first-party cookie keeps the campaign labels on that link (for example
utm_sourceandutm_campaign), the page you landed on, the site that referred you, and when, for up to 90 days. When you sign up we send those labels to Klaviyo with your account so we can see which of our campaigns bring sign-ups; the cookie is then cleared. That cookie holds no identifier. If you arrive by clicking one of our ads in ChatGPT, a second first-party cookie keeps the click reference OpenAI adds to the link, for up to 30 days. If you then sign up, we tell OpenAI that this click led to a sign-up, sending only that click reference (not your email address, name, account id or IP address), so OpenAI can count our ad's sign-ups; the cookie is then cleared. Nothing is sent to OpenAI for sign-ups that did not come from a ChatGPT ad. We do not sell advertising on the Service. - Meta Pixel and Conversions API. We use the Meta Pixel and Meta's Conversions API to measure our ads on Facebook and Instagram. The Pixel runs on every page of our website except inside the app (your dashboard and our admin pages) and tells Meta which pages you visit. If you arrive by clicking one of our Meta ads, a first-party cookie keeps Meta's click id for up to 90 days. When you sign up, we tell Meta that it happened, with the Meta click id, Meta's browser id (its
_fbpcookie), your IP address and your browser. When you start a paid plan, we tell Meta that too, with the plan's price and the same click id, browser id, IP address and browser, recorded when you open the checkout. When you open a plan checkout, we report that to Meta too. For sign-ups, opened checkouts and paid plans we also send a hashed (SHA-256) form of your email address and of your account id. We never send Meta your email address itself or your name. On pages where the Pixel runs, Meta's Pixel may also read the email address you type into a form, such as the sign-up form, turn it into a hash (SHA-256) in your browser and send Meta only that hash, so Meta can match the visit to a Meta account. Meta may use this to measure and improve our ads. None of this happens for visitors in the EU, the EEA, the UK or Switzerland, or in our Android app. To opt out, use the "Do not share my information for ads" link at the bottom of any public page, including the sign-in and sign-up pages: it sets a cookie on that browser and the Pixel and these reports stop. - TikTok Pixel and Events API. We use the TikTok Pixel and TikTok's Events API to measure our ads on TikTok, in the same way and under the same rules as Meta's. The Pixel runs on every page of our website except inside the app (your dashboard and our admin pages) and tells TikTok which pages you visit, including which plans you look at on our pricing pages and which plan's button you press. If you arrive by clicking one of our TikTok ads, a first-party cookie keeps TikTok's click id (
ttclid) for up to 90 days. When you sign up, open a checkout or start a paid plan, we tell TikTok that it happened, with the TikTok click id, TikTok's browser id (its_ttpcookie), your IP address, your browser, and a hashed (SHA-256) form of your email address and of your account id; for a checkout or a paid plan, also which plan it is and its price. We never send TikTok your email address itself or your name. TikTok may use this to measure and improve our ads. None of this happens for visitors in the EU, the EEA, the UK or Switzerland, in our Android app, or after you use the "Do not share my information for ads" link. - Google Ads tag. We use Google's tag (gtag.js) to measure our ads on Google. It runs on every page of our website except inside the app (your dashboard and our admin pages) and tells Google which pages you visit; Google may set its own cookies to recognise that you arrived from one of our Google ads. When you start a paid plan, the tag tells Google that it happened, with the plan's price and the checkout's reference number. We never send Google your email address, your name or your account id for ads. This is separate from Google sign-in and the YouTube connection (Section 3): no Google user data is used for ads. Google may use this to measure and improve our ads. None of this happens for visitors in the EU, the EEA, the UK or Switzerland, in our Android app, or after you use the "Do not share my information for ads" link.
2.4 Discover (research)
Synthvids includes a research feature called Discover. When you select a topic or a source, Discover retrieves publicly available material and analyses it to identify subjects, facts, and themes worth covering. That material is used as research input: it informs what a script is about and how it is structured. Scripts are then newly written by a language model rather than assembled from the retrieved text.
Retrieved material that becomes part of a script or a rendered video is held as part of your channel's research state for as long as that story, its channel, or your account exists, and is removed when you delete any of those.
Retrieved material that is never turned into a script or a render is deleted automatically 90 days after it was discovered, regardless of whether you take any action — unused research material does not accumulate indefinitely.
Retained material — used or unused, while it exists — helps the Service track what you have already covered and avoid suggesting the same subject twice. It is never published to your channel, is not shown to other users, and is not sold or shared with third parties.
When a channel turns on the "Real photos where they fit" setting, the render also fetches public archive photos (from sources such as Wikimedia Commons (including Wikipedia's article photos), Openverse, The Metropolitan Museum of Art, the Art Institute of Chicago, The Cleveland Museum of Art and the Library of Congress) for that channel's videos. To find them, the render sends short search words written from your story's title and script (never your account details) to those services' public search tools. Only photos marked public domain, CC0, CC BY, CC BY-SA, or the Library of Congress's "no known restrictions" are used, and each is credited in the video description. On a drawn look the render may also send the same short search words to Pixabay, a stock image library, to find illustrations; those are used under the Pixabay Content License and credited in the same way.
Discover retrieves material; it does not grant you rights in it. Determining whether a given source may be used for your project remains your responsibility — see our Terms of Service.
2.5 How we treat what you create
The scripts, audio, images, and videos you generate are yours. We hold them to operate the Service for you, and we commit to the following:
- Your content is private to your account by default. Generated media is stored in access-controlled storage and is not listed publicly, indexed by search engines, or browsable by other users. Playback and download links issued by the Service are time-limited and specific to your session. Content becomes public only when you choose to publish it to a channel you have connected.
- We do not sell your content or your personal information. Not to advertisers, not to data brokers, not to anyone. We have no advertising business. To measure our own ads we share limited data with Meta, TikTok and Google, described in Section 2.3, and you can opt out of it.
- We do not use your content to train our own AI models, and we select model providers whose commercial terms exclude training on API inputs. This applies to your prompts, your source material, your generated Output, and your Google user data. The one exception outside our control is ElevenLabs — see Section 6.
- We do not showcase your work without asking. We will not feature your videos, thumbnails, or channel in marketing, demos, or public examples unless you give us separate, express permission.
- Staff access is limited and purposeful. Our personnel do not browse user content. Access happens only where necessary to investigate a fault you have reported, to respond to a legal obligation, or to investigate a credible report of abuse — and is limited to what that purpose requires.
- You can take it with you, and you can take it down. You may download your generated media at any time, and delete it from your account. Deletion removes the file from our storage; see Section 7 for backup retention.
The one thing we cannot do is reach into a platform you have already published to. Once a video is live on your YouTube channel, you control it there.
3. Google user data
This section describes how Synthvids accesses, uses, stores, and shares data from Google APIs, including YouTube API Services. It applies in addition to the rest of this policy.
3.1 Sign-in with Google
If you choose to sign in with Google, we request the following scopes:
openid,.../auth/userinfo.email,.../auth/userinfo.profile
We use this to create and authenticate your Synthvids account. We receive your Google account email address, name, and profile picture. We do not receive your Google password.
3.2 YouTube channel connection
Publishing to YouTube is optional. You are never required to connect a YouTube channel to use Synthvids. If you choose to connect one, we request the following scopes:
| Scope | Why we request it |
|---|---|
https://www.googleapis.com/auth/youtube.upload | To upload videos you have created in Synthvids to the YouTube channel you select. |
https://www.googleapis.com/auth/youtube | To display your available YouTube channels including Brand Accounts, so you can select which channel to publish to, and to confirm the status of videos we uploaded on your behalf. The full scope is required for reliable Brand Account discovery; we do not read, modify, or delete existing channel content, comments, or subscriber data. |
What we access and store. When you connect a channel, we store an OAuth access token and refresh token, your YouTube channel ID, and channel title. We store the refresh token so that scheduled uploads can run at the time you selected, without requiring you to be signed in at that moment.
How we use it. We use this data solely to (a) show you which channel you are publishing to, (b) upload videos at your explicit direction, including on a schedule you set, and (c) report back the status and link of an upload we performed. We do not read, download, analyze, or index your existing YouTube videos, comments, subscriber data, or analytics beyond what is described here.
How we share it. We do not sell, rent, or transfer Google user data to third parties. We do not share it with advertisers, data brokers, or analytics providers. Google user data is transmitted only between your browser, our infrastructure providers listed in Section 5, and Google's own APIs.
We do not use Google user data to train AI models. Google user data is never used to develop, improve, or train any machine learning or artificial intelligence model, whether ours or a third party's.
Limited Use. Synthvids' use and transfer of information received from Google APIs to any other app adheres to the Google API Services User Data Policy, including the Limited Use requirements.
3.3 Your control and revocation
- You may disconnect a YouTube channel at any time from your Synthvids account settings. Doing so deletes the stored tokens for that channel from our systems.
- In addition to our normal deletion procedure, you may revoke Synthvids' access to your Google data at any time via the Google security settings page at https://security.google.com/settings/security/permissions.
- Revoking access does not delete videos already uploaded to your YouTube channel. You control those directly through YouTube Studio.
3.4 Google and YouTube terms
By connecting a YouTube channel, you are also agreeing to the YouTube Terms of Service. Data handled by Google and YouTube is governed by the Google Privacy Policy.
3A. TikTok user data
This section describes how Synthvids accesses, uses, stores, and shares data from TikTok's APIs. It applies in addition to the rest of this policy.
Publishing to TikTok is optional. You are never required to connect a TikTok account to use Synthvids. If you choose to connect one, we request access to your TikTok account through TikTok's official API to enable the publishing features you choose to use.
3A.1 Scopes
| Scope | What it grants | Why it is there | What we do with it |
|---|---|---|---|
video.upload | Permission to deliver a video to your TikTok inbox as a draft | Lets Synthvids send a finished video to your TikTok account for you to review and post yourself | The video is transferred to TikTok at your request. Synthvids does not publish it on your behalf under this scope. |
video.publish | Permission to publish a video directly to your TikTok profile | Lets Synthvids publish, at your explicit request, a video you publish now or schedule | Used only when you click Publish or Schedule for a TikTok destination. You select the post's privacy setting and complete any required content disclosures before publishing. |
user.info.basic | Your TikTok display name and profile photo | TikTok includes this scope with Login Kit, which its Content Posting API requires | Synthvids does not currently request it when you connect. If that changes, it will be used only to show which TikTok account is connected. |
Our TikTok app is registered for the three scopes above. When you connect, Synthvids requests only video.upload and video.publish. It does not currently request user.info.basic, and it requests no other TikTok scope. If that changes, user.info.basic will be used only to show which TikTok account is connected.
3A.2 What we access and store
When you connect a TikTok account, we store:
- your TikTok account identifier (TikTok's per-app open ID);
- an OAuth access token and refresh token, encrypted at rest, and their expiry times;
- the scopes you actually granted; and
- the creator information TikTok returns when you connect and when you open the TikTok publish form: your display name, username and profile photo link, and your account's posting settings (the privacy options available to you, whether comments, duets and stitches are allowed, and the maximum video length).
We show your display name in your Synthvids channel settings so you can see which TikTok account is connected, and we use the posting settings to show only the publishing options your account allows. We store the refresh token so that scheduled posts can go out at the time you selected, without requiring you to be signed in at that moment.
We do not store the video content itself beyond what is needed to complete the requested upload or publish action. We do not read, download, or analyze your existing TikTok videos, followers, comments, or analytics.
3A.3 How we share it
We do not sell, rent, or transfer TikTok user data to third parties. We do not use any data obtained through TikTok's API for advertising, and we do not share it with advertisers, data brokers, or analytics providers, consistent with TikTok's Developer Terms of Service. TikTok user data is transmitted only between your browser, our infrastructure providers listed in Section 5, and TikTok's own APIs. We do not use TikTok user data to train AI models.
3A.4 Your control and revocation
- You may disconnect a TikTok account at any time from Channel setup. Doing so revokes Synthvids' access through TikTok's own authorization system and deletes the stored connection, including its tokens, from our systems.
- Deleting your Synthvids account also revokes Synthvids' access to your TikTok account through TikTok's own authorization system, not just locally.
- You may also remove Synthvids' access at any time from the security and permissions settings of your TikTok account.
- Revoking access does not delete videos already posted to your TikTok account. You control those directly in TikTok.
3A.5 TikTok's own terms
Your use of TikTok remains governed by TikTok's Terms of Service and Privacy Policy, separate from this policy.
3B. Facebook (Meta) user data
This section describes how Synthvids accesses, uses, stores, and shares data from Meta's APIs. It applies in addition to the rest of this policy.
Publishing to a Facebook Page is optional. You are never required to connect Facebook to use Synthvids. If you choose to connect, we request access through Meta's official API to enable the publishing features you choose to use.
3B.1 Permissions
| Permission | Why we request it |
|---|---|
pages_show_list | Lists the Pages you manage so you can pick one |
pages_read_engagement | Reads the Page you chose and obtains its Page access token |
pages_manage_posts | Publishes the videos you publish or schedule to that Page |
business_management | Reaches Pages owned through a Meta business portfolio |
public_profile | Identifies the connecting account; Meta grants it to every app |
We request no other Meta permission.
3B.2 What we access and store
When you connect a Facebook Page, we store your Meta app-scoped user ID, the chosen Page's ID and name, and access tokens, encrypted at rest. We use them only to list your Pages when you connect, to publish when you click Publish or schedule a post to that Page, and to revoke access when you disconnect or delete your account. We do not read your existing posts, followers, comments, or insights.
3B.3 How we share it
We do not sell, rent, or transfer Facebook user data. We do not use any data obtained through Meta's API for advertising, and we do not use it to train AI models. It moves only between your browser, our infrastructure providers listed in Section 5, and Meta's own APIs.
3B.4 Your control, revocation, and deletion
- You may disconnect Facebook at any time from Channel setup. Doing so revokes Synthvids' access through Meta's own authorization system and deletes the stored connection, including its tokens, from our systems.
- You may also remove Synthvids in Facebook Settings → Business integrations.
- Disconnecting, deleting your Synthvids account, or sending a data deletion request through Meta deletes the stored IDs, Page name, and tokens.
- Revoking access does not delete videos already posted to your Page.
3B.5 Meta's own terms
Your use of Facebook remains governed by Meta's Terms of Service, Privacy Policy and Platform Terms.
4. How we use information
We use the information described above to:
- provide, operate, and maintain the Service;
- authenticate you and secure your account;
- generate the scripts, audio, images, and video you request;
- publish videos to channels you have connected, at your direction;
- process payments, enforce usage limits, and prevent abuse;
- diagnose failures, monitor performance, and improve reliability;
- communicate with you about your account, billing, and service changes; and
- comply with legal obligations.
We do not sell your personal information. To measure our own ads we share limited data with Meta and TikTok (Section 2.3); you can opt out with the "Do not share my information for ads" link at the bottom of any public page.
5. Service providers
We use the following providers to operate the Service. Each receives only the data needed for its function.
| Provider | Function | Data involved |
|---|---|---|
| Supabase | Database, authentication, file storage | Account data, job records, generated media, encrypted tokens |
| Vercel | Website hosting | Technical/request data |
| Render.com | Backend API and job workers | Job data, request data |
| Upstash | Job queue | Job identifiers and parameters |
| RunPod | GPU compute for video rendering and voice synthesis | Scripts, prompts, and media for the duration of a render |
| Stripe | Payments, subscriptions, and the free trial card check | Name, email, billing details; the card you verify for the free trial |
| Anthropic | Script and text generation | Prompts and topic material you supply |
| ElevenLabs | Optional voice synthesis | Script text |
| OpenAI | Image generation when Meta's image model cannot draw a picture; counting sign-ups from our ChatGPT ads | Prompt text and reference pictures; for a sign-up from a ChatGPT ad, the ad click reference only |
| Meta (AI models) | Drawing the pictures for your videos and thumbnails; choosing archive photos for a channel that turns on "Real photos where they fit"; checking finished AI scenes for visible defects, when we run that check | Picture prompts and reference pictures; for archive photos, the story's title and script and the candidate photos; for scene checks, each AI scene clip and its narration line; an anonymous account code, never your email or name |
| xAI / Grok | Optional image generation | Prompt text |
| Meta (ads) | Measuring our Facebook and Instagram ads | Pages visited, the Meta click id, Meta's browser id, IP address, browser, a hashed (SHA-256) email address and account id, that you signed up, opened a checkout, and started a paid plan with its price; never your email itself or your name |
| TikTok (ads) | Measuring our TikTok ads | Pages visited, the plans you looked at or picked, the TikTok click id, TikTok's browser id, IP address, browser, a hashed (SHA-256) email address and account id, that you signed up, opened a checkout, and started a paid plan, with which plan and its price; never your email itself or your name |
| Google (ads) | Measuring our Google ads | Pages visited, Google's own ad cookies, IP address, browser, and that you started a paid plan with its price and checkout reference; never your email, name or account id |
| Klaviyo | Signup notification and account email list | Email address, signup date, plan tier, the campaign that brought you (if any) |
| Email delivery provider | Transactional email | Email address |
| Google / YouTube | Publishing to your channel | See Section 3 |
| TikTok | Publishing to your TikTok account | See Section 3A |
| Meta (Facebook) | Publishing to your Facebook Page | See Section 3B |
We may add or change providers; we will update this list when we do. No provider in this list receives Google user data except Google itself and the infrastructure providers that store or transmit it on our behalf (Supabase, Vercel, Render.com, Upstash).
We may also disclose information if required by law, subpoena, or valid legal process, or where necessary to protect our rights, users, or the public.
6. AI processing and your content
Content you create with Synthvids belongs to you, subject to our Terms of Service. We process it to render your videos and to operate the Service.
We do not use your content or your Google user data to train AI models. Our model providers process your prompts under their own commercial terms; we select providers whose terms exclude training on API inputs.
ElevenLabs is the one exception we cannot guarantee. Voice synthesis through ElevenLabs requires you to connect your own ElevenLabs account and API key — Synthvids does not operate a shared ElevenLabs account on your behalf, and your script text is sent to ElevenLabs under your account, not ours. Zero-retention (no training on submitted audio or text) is ElevenLabs' default account setting, but it is a setting the account holder controls and can change at any time. Because the account is yours, Synthvids has no way to verify or guarantee which retention or training setting is active on it. If this matters to you, check the setting directly in your ElevenLabs account.
7. Data storage, location, and retention
Our primary database and file storage are hosted in Canada. Rendering compute may be performed in the United States. If you are located outside these countries, your information will be transferred to and processed there.
We retain:
- Account data for as long as your account is active, and for 90 days after deletion to allow recovery and to meet legal and accounting obligations.
- Generated media for 90 days following the most recent sign-in. Where an account belongs to an organization with more than one member, the most recent sign-in by any member counts. Signing in renews that period; after 90 days with no sign-in, generated media may be deleted. An account with no recorded sign-in is not deleted on this schedule.
- Google OAuth tokens until you disconnect the channel, revoke access, or delete your account, whichever comes first.
- TikTok OAuth tokens and connection data until you disconnect the TikTok account, revoke access, or delete your account, whichever comes first.
- Facebook access tokens and connection data until you disconnect Facebook, revoke access, or delete your account, whichever comes first.
- Render logs for 30 days. After that, the console log of a render that has finished, failed, or been cancelled is cleared. A short failure message is kept with the render's own record for as long as that record exists, so we can still tell you why a render did not succeed.
- Free trial records — normalized trial emails, hashed device identifiers, hashed network addresses and card fingerprints — until the free trial offer ends, then deleted within 30 days. They are kept after an account is deleted until then, because their only purpose is to stop the same email, device, network or card from starting another trial.
Billing records are retained as long as required by tax and accounting law.
8. Security
We protect information using encryption in transit (TLS), strict access controls limiting who and what can read sensitive data, and row-level security isolation so that one account cannot access another's data. Credentials and tokens are isolated to service-role database access only and are not readable by other users. Stored OAuth tokens and user-supplied API keys are additionally protected with column-level AES-256-GCM encryption, decrypted only in-process at the moment a request is made to the provider it belongs to. No system is perfectly secure, and we cannot guarantee absolute security. If we become aware of a breach affecting your personal information, we will notify you and any applicable regulator as required by law.
9. Your rights
Depending on where you live, you may have the right to:
- access the personal information we hold about you;
- correct inaccurate information;
- delete your information;
- obtain a portable copy of your information;
- object to or restrict certain processing; and
- withdraw consent at any time, without affecting prior processing.
California residents have the rights described above under the CCPA/CPRA, including the right not to be discriminated against for exercising them. We do not sell personal information. Measuring our ads with Meta and TikTok (Section 2.3) may count as "sharing" under the CCPA; you can opt out with the "Do not share my information for ads" link at the bottom of any public page.
EEA/UK residents may also lodge a complaint with their local supervisory authority.
To exercise any of these rights, email [email protected] or use the account deletion option in your account settings. We may ask you to verify your identity before acting on a request.
10. Children
The Service is not directed to children and is not intended for anyone under 18. We do not knowingly collect personal information from anyone under 18. If you believe someone under 18 has provided us information, contact [email protected] and we will delete it.
11. Changes to this policy
We may update this policy from time to time. If we make material changes to how we handle Google user data or other personal information, we will notify you by email or through the Service before the change takes effect. The "Last updated" date above reflects the most recent revision.
12. Contact
JB Malcolm LLC
c/o Northwest Registered Agent, 2108 N St, Ste N, Sacramento, CA 95816
