Private beta30 seats for the $9 test film.Check a niche

Privacy Policy

What personal data VidSwarm processes, why, with whom, for how long, and your rights under the GDPR.

Last updated 13 November 2026 (draft)

Draft — needs legal review. This text is a working version and not yet binding.

This policy explains what personal data VidSwarm (vidswarm.app, website and app) processes, why, with whom, for how long, and what your rights are under the EU General Data Protection Regulation (GDPR).

1. Controller

Julian Schiederer (sole proprietor, trading as VidSwarm)
[ADDRESS]
[EMAIL]

We have not appointed a data protection officer because the law does not require one for a business of our size (Art. 37 GDPR, § 38 BDSG).

DataPurposeLegal basis (GDPR)How long
Account data: email address, name (optional), login method (email link or Google sign-in), workspace, team members, plancreate and run your accountArt. 6(1)(b) contractwhile the account exists, then deleted within 30 days
Billing data from Paddle: plan, amount, country, invoice number, subscription status (never card details)grant access, apply minutes, answer billing questionsArt. 6(1)(b) contract; Art. 6(1)(c) legal obligation for accounting recordsaccounting records up to 10 years (§ 147 AO, § 257 HGB)
Project data: channel settings, reference video links, topics, scripts, storyboards, films, thumbnails, upload packages, production records, your comments and approvalsmake your filmsArt. 6(1)(b) contractwhile the account exists; after cancellation 90 days for export, then deleted within 30 days
Your uploads: footage, images, logos, fonts — they may show peopleuse them in your filmsArt. 6(1)(b) contract. If the uploads contain other people, you are responsible for having a legal basis; we process them on your behalf (section 7)as project data
Your voice (only if you clone it): voice sample, verification recording, voice model at our voice providermake narration in your own voiceArt. 6(1)(a) and, as a precaution, Art. 9(2)(a) explicit consent. You can withdraw at any time in Settingsuntil you delete the voice or your account; deleted at us and the provider within 30 days
YouTube data (only if you connect a channel) — see section 4upload approved films, show results, plan next filmsArt. 6(1)(b) contractsee section 4
Public YouTube data about other channels (channel names, public statistics, video titles) in the niche check and radarshow niches and comparable channelsArt. 6(1)(f) legitimate interest in showing market data; YouTube API data rulesrefreshed or deleted within 30 days
Client review links: the name or email a reviewer enters, their commentslet your clients review a film without an accountArt. 6(1)(b) contract with you; Art. 6(1)(f) towards the revieweras project data
Support emailsanswer youArt. 6(1)(b) or (f)3 years after the last message
Waitlist and newsletter: email, answers to "How many channels do you run?" and "What format?", sign-up pageinvite you to the beta, send updatesArt. 6(1)(a) consent; unsubscribe link in every emailuntil you unsubscribe, or 12 months after public launch if you never sign up
Server logs: IP address, time, URL, browser, error messagesrun and secure the service, detect abuseArt. 6(1)(f) legitimate interest in a secure serviceup to 14 days
Product analytics (PostHog), only after you allow it — see section 6understand which features help, find errorsArt. 6(1)(a) consent; § 25(1) TDDDG12 months

We do not sell personal data and do not use it for advertising. We do not make decisions about you that are based solely on automated processing and have legal or similarly significant effects (Art. 22 GDPR). Our automatic quality checks judge scenes in your films, not you.

3. AI processing

To make a film, VidSwarm sends the content of your project — the brief, script, sources, voice text, storyboard descriptions and, where you use it, your voice sample — to AI providers (section 5). They process it only to return the result to us. Under our contracts they may not use it to train their models. They do not receive your account or billing data. We do not use your projects or your voice to train AI models ourselves.

4. YouTube API Services and Google user data

This section applies if you connect a YouTube channel or sign in with Google.

What we access and why

Permission (scope)What we do with it
Sign in with Google (openid, email, profile)log you in; we store your email address and Google account ID
youtube.uploadupload the films you approved for publishing with title, description, tags, privacy status, publish time and the "altered or synthetic content" flag, and set the thumbnail you chose
youtube.force-sslmanage your channel's videos over a secure connection: read your channel's name, ID, avatar and subscriber count; add captions made from the film's script; list your playlists so you can pick one, and add new uploads to it; apply the title, description, tags and visibility you change after publishing; read the newest public comments on films published through VidSwarm and show them to you (read-only: we never post, reply, edit or delete)
yt-analytics.readonlyread views, watch time, average view duration, audience retention, traffic sources, impressions and click-through rate (YouTube Analytics and Reporting APIs), to show results per film and suggest topics and edits for your next films
yt-analytics-monetary.readonlyread estimated revenue and playback-based CPM per film (only channels in the YouTube Partner Program have them), to show revenue and RPM next to each film's results

We ask for these permissions together when you connect a channel. A channel connected earlier keeps working with the permissions it granted; features that need a newer one ask you to reconnect. We do not read messages, other users' playlists, comments on videos not published through VidSwarm, payment information or your Google account content outside YouTube.

Storage and sharing. Tokens are stored encrypted in our database (Supabase, EU region). Analytics numbers, revenue estimates and the newest comments are stored with the film they belong to and only shown to your workspace. Comments include the commenter's public display name; we keep the 20 newest per film and replace them on every refresh. We share Google user data only with the processors in section 5 that we need to provide the feature you use (for example, sending your retention numbers to our AI provider to suggest edits for your next film). We do not sell it, do not use it for advertising and do not transfer it to data brokers.

Limited Use. VidSwarm'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. In particular:

  • we use Google user data only to provide and improve the user-facing features described above;
  • we do not transfer it except as needed to provide those features, to comply with the law, for security, or as part of a merger or acquisition with your notice;
  • we do not use it for advertising, retargeting or interest-based ads;
  • no human reads it unless you ask us to (for example in a support request), it is needed for security or legal reasons, or it is aggregated and anonymised for internal operations;
  • we do not use Google user data to develop, improve or train generalised AI or machine-learning models.

YouTube and Google terms. By connecting YouTube you agree to the YouTube Terms of Service (youtube.com/t/terms). Google's processing is governed by the Google Privacy Policy (policies.google.com/privacy).

Revoking access and deletion. You can disconnect your channel in VidSwarm (Channels → Disconnect) or revoke access at security.google.com/settings/security/permissions. We then delete the stored tokens immediately and other data we received through the YouTube API within 7 days, except films and metadata you created in VidSwarm. Public data obtained through the YouTube API is refreshed or deleted within 30 days.

5. Processors and other recipients

We use the following service providers. Processors act only on our instructions under a data processing agreement (Art. 28 GDPR).

ProviderRoleWhat they processWhereTransfer safeguard
Vercel Inc.website and app hostingall web requests, logsUSA; functions in [EU region, e.g. Frankfurt]EU-US Data Privacy Framework (DPF) + SCCs
Supabase Inc.database, login, file metadataaccount, project and YouTube dataEU region ([Frankfurt]); support access from USASCCs
Cloudflare Inc. (R2)storage of films, uploads, voice samplesfiles[EU jurisdiction bucket]DPF + SCCs
Amazon Web Services EMEA SARL (Lambda)rendering filmsproject files during renderingregionDPF + SCCs
Trigger.devrunning background jobsjob data incl. project content
Anthropic (PBC, USA / Anthropic Ireland Ltd.)language model for research, scripts, checksproject content, YouTube analytics numbersUSASCCs
ElevenLabsAI voices and voice cloningnarration text, your voice sample and voice modelUSASCCs
[Image or video model provider, if used]thumbnails or generated stillsprompts, reference images
PostHog Inc. (EU Cloud)product analytics, only with consentusage events, device dataEU (Frankfurt)not needed for hosting; SCCs for support access
Resendsending login and service emailsemail address, email contentUSADPF/SCCs

Independent controllers (not our processors):

  • Paddle.com Market Limited (UK), merchant of record: processes your payment and billing data under its own privacy policy. The UK has an EU adequacy decision.
  • Google / YouTube when you connect a channel or sign in with Google.
  • Content sources such as Pexels, Wikimedia Commons and other archives: we send them search terms from your script, not personal data about you.

Authorities and advisers, where the law requires it or to defend legal claims (Art. 6(1)(c), (f)).

6. Website, cookies and analytics

The website uses only necessary storage by default. PostHog analytics loads only after you click "Allow analytics" in the cookie banner; before that, no analytics script runs. You can withdraw consent at any time via "Cookie settings" in the footer. Embedded YouTube players on our site load only after you click them. Details: Cookie Policy. Fonts are served from our own domain.

7. When we process data on your behalf

If your uploads, scripts or client review links contain personal data of other people (for example people visible in your footage), we process that data on your behalf as your processor. Business customers can request our data processing agreement at [EMAIL].

8. International transfers

Some providers are in the USA. Transfers rely on the EU-US Data Privacy Framework where the provider is certified, and otherwise on the EU Standard Contractual Clauses (Commission Decision 2021/914) with additional measures where needed. You can request a copy of the safeguards at [EMAIL].

9. Security

Data is encrypted in transit (TLS). Access to the database is restricted per workspace (row-level security). Files are stored in private buckets and shared only through time-limited links, except client review links you create, which anyone with the link can open until you revoke them.

10. Your rights

You have the right to access (Art. 15), correction (Art. 16), deletion (Art. 17), restriction (Art. 18), data portability (Art. 20) and to object to processing based on legitimate interest (Art. 21). You can withdraw consent at any time with effect for the future (Art. 7(3)). Write to [EMAIL]; we answer within one month.

You can also complain to a data protection authority, for example the one where you live or the one responsible for us: [supervisory authority of the German federal state of ADDRESS].

11. Children

VidSwarm is not for people under 18. We do not knowingly collect data from children.

12. Changes

We update this policy when our processing changes and show the date at the top. We email account holders about material changes.