Privacy Policy
Last updated: 12 October 2026
1. Controller
Droidtech e.K., owner Michael Rauen, Auf der Eichelsbach 19, 54533 Hasborn, Germany. Phone +49 6574 227 0937, e-mail mail@castfold.com. No data protection officer has been appointed because the legal requirements for one are not met.
This policy covers the website castfold.com and the Castfold application (app). The legal bases are the GDPR, the German Federal Data Protection Act (BDSG) and the German Telecommunications Digital Services Data Protection Act (TDDDG).
2. Website and app: hosting, cookies and storage on your device
Server logs. When you visit the website or the app, the hosting provider processes technically necessary data (IP address, time, page requested, browser, referrer) to deliver and secure the service (Art. 6(1)(f) GDPR). Logs are deleted after 14 days at the latest. The hosting provider is Host Europe GmbH, Hansestraße 111, 51149 Cologne, Germany, with a data centre in Germany; it is bound as a processor by contract (Art. 28 GDPR).
Cookies and similar technologies – what Castfold stores on your device. Castfold (website castfold.com and app app.castfold.com) sets no cookies of its own and uses no analytics, advertising or tracking cookies or scripts. To work, Castfold does store and read information on your device using your browser’s local storage (localStorage and sessionStorage), a technology similar to cookies:
- Website: your choice in the consent banner (
castfold.consent), whether the language hint has already been shown (castfold.langhint) and – only when you arrive through a referral link – the referrer’s code and the time of that first visit (castfold.ref,castfold.refAt, see below). - App – sign-in: your login session (access token and refresh token,
ytm.auth) so that you stay signed in. The app sends the access token with every request to our server to authenticate you; it contains no YouTube data. - App – settings and convenience: language, light or dark display, the chosen date range and table columns, hints you have dismissed, the last top-up amount, your consent choice and, if you came through a referral link, the referrer’s code.
- App – temporary state (sessionStorage, deleted when you close the tab): the page to return to after the Google sign-in or a payment, and unfinished input in the channel wizard.
This storage is strictly necessary to provide the service you requested (Section 25(2) no. 2 TDDDG; Art. 6(1)(b) and (f) GDPR). Apart from the sign-in token it is not transmitted to us. Signing out deletes the login session; you can delete all entries at any time through your browser’s site data for castfold.com and app.castfold.com.
Third parties that may place or read cookies on your device. Some features take you to or embed services of other providers, which then set and read their own cookies and similar technologies under their own responsibility:
- Google: the Google sign-in and consent pages (accounts.google.com) when you connect a YouTube channel, and the YouTube player (see “External media” below). Google’s privacy policy: https://policies.google.com/privacy.
- Stripe: the payment pages hosted by Stripe when you top up credit or subscribe, including device data for fraud prevention (see section 8). Stripe’s privacy and cookie policy: https://stripe.com/privacy and https://stripe.com/cookies-policy/legal.
- Cloudflare: when your browser uploads a video file or loads a preview directly from our object storage, Cloudflare receives your IP address and browser identifier (see section 6); Cloudflare sets no cookies for this.
Referral link (?ref=). If you arrive through a partner’s referral link, the website remembers that partner’s code and the time of that first visit on your device and appends both to the links to registration, so the referral can still be attributed if you sign up later. A later visit through a different referral link does not overwrite the remembered code or time. The code belongs to the partner, not to you, and says nothing about your person. We set no cookie for it, and as long as you do not register, nothing is transmitted to us (Art. 6(1)(f) GDPR). You can delete the entry at any time through your browser’s site data.
External media (YouTube embeds). YouTube videos on the website are loaded only after you consent to the “External media” category or load a video individually; in the app, the YouTube player for one of your videos is loaded only when you click play (Art. 6(1)(a) GDPR, Section 25(1) TDDDG). On loading, Google LLC receives your IP address and sets its own cookies; we use the domain youtube-nocookie.com. Google’s privacy policy: https://policies.google.com/privacy. You can withdraw consent at any time via “Cookie settings” in the footer.
Fonts. Fonts are served from our own server; no connection to Google Fonts is made.
3. Registration and account (app)
On registration we process your e-mail address, display name, account name, time and a confirmation code. Optionally you can add billing details (company, address, VAT ID). The purpose is to provide the account and perform the contract (Art. 6(1)(b) GDPR). If your account is created through a partner link, we store the partner id and the time to settle the partner commission (Art. 6(1)(f) GDPR); the partner receives no personal data, only anonymised figures.
Login sessions do not expire automatically; you end them by logging out. For this we store a refresh token (hashed) with the time of last use.
4. Google sign-in and YouTube API Services
To connect a YouTube channel you sign in with Google (OAuth 2.0) and grant Castfold permissions for the selected channel. Castfold uses YouTube API Services. By connecting you agree to the YouTube Terms of Service; the Google Privacy Policy also applies.
Castfold only works with the channel you connect yourself. It reads data of that channel only, never data of other users’ channels, and it does not search YouTube (no search.list).
Which user information and API Data Castfold accesses. With your permission Castfold accesses, through the YouTube Data API and the YouTube Analytics API, only data of the channel you connected:
- Channel data: channel id, title, handle, description, keywords, country, default language, translations of title and description, profile picture and banner, subscriber, view and video counts.
- Data of your own videos: video id, title, description, tags, category, language and translations, thumbnail, duration, visibility (public, unlisted, private), scheduled publication time, upload and processing status, view, like and comment counts, and the list of your caption tracks.
- Analytics of your channel (YouTube Analytics with
ids=channel==MINE): views, watch time, average view duration, subscribers gained and lost, likes, comments and shares per day, per video and per country; estimated revenue only if your channel is monetised. - Google sign-in: access and refresh tokens for the permissions you grant. Castfold does not read your Google contacts, e-mail, files or other Google account data.
Which data Castfold collects and stores. We store the data listed above in our database so that the app can show it to you and work with it, together with the analytics history of your channel. OAuth access and refresh tokens are stored only in encrypted form. Video files, thumbnails and captions that you upload through Castfold are stored as described in sections 6 and 10.
How Castfold uses this data – and what it writes to YouTube. Only for the functions you use in Castfold: showing your channel, videos and analytics in the app, insights and AI suggestions for your channel, uploading and scheduling videos (videos.insert, always private first, with your chosen publication time), setting thumbnails (thumbnails.set), uploading captions, keeping title, description, tags and translations of your videos up to date (videos.update), and transferring your channel branding (channels.update, channelBanners.insert). Castfold only writes to YouTube what you created or confirmed in the app.
Who else processes this data. We do not sell, rent or share YouTube API Data with third parties and do not use it for advertising. It is processed only by service providers acting on our behalf under a data processing agreement: our hosting provider (section 2), and Google Cloud Vertex AI when you use an AI feature, which then receives excerpts of your channel data and analytics as context (section 5) and does not use them to train models. Video files go to Cloudflare R2 as described in section 6.
Confirmation before transfer: After the Google sign-in we first retrieve only the channel id, title, handle, profile picture and the subscriber and video counts of the channel found and show them to you. Only when you confirm that it is your channel do we transfer your branding and retrieve further data. If you choose “Choose another channel”, we revoke the permission with Google immediately and delete the retrieved details.
Refresh and deletion (30-day rule): Data retrieved through the API is refreshed regularly; stored API data older than 30 days is retrieved again or deleted, except for the historical daily values of your analytics, which you expressly keep for evaluation and can delete at any time. If you disconnect a channel or delete your account, we delete the associated tokens immediately and the retrieved data within 30 days.
Revocation: You can revoke Castfold’s access at any time in the app (“Disconnect”) or in your Google security settings at https://myaccount.google.com/permissions.
Processing by Google: When data is retrieved through the API, Google LLC (or Google Ireland Limited for the EEA) processes data under its own responsibility. Google may collect data through the YouTube API for security and abuse-prevention purposes.
Handling of Google user data: Castfold’s use and transfer of information received from the YouTube API Services adheres to the Google API Services User Data Policy, including the Limited Use requirements. This data is used only for the purposes described in this section, is not used to train AI models, and is not shared with or sold to third parties.
How we protect your Google user data: We protect data received through the YouTube API Services with the following technical and organisational measures (Art. 32 GDPR):
- Encryption in transit: All connections between your browser, Castfold and Google use HTTPS (TLS) exclusively. Unencrypted requests are redirected to HTTPS.
- Encrypted access tokens: We store Google OAuth access and refresh tokens only in encrypted form (AES-256). The encryption keys are kept separately from the database. Tokens never appear in the interface, in logs or in data exports.
- Protected servers: The database is not reachable from the internet. Server administration is only possible via SSH with personal keys and is restricted to the operator.
- Access for authorised users only: Within Castfold only your account can see your channel data, and only members with the corresponding permissions. Castfold staff access it only when you ask for support, when it is necessary for security purposes (such as investigating abuse), or when required by law.
- Protected files: Video files are stored encrypted in object storage (see section 6) and can only be retrieved through short-lived signed links.
- Encrypted backups: Database backups leave the server only in encrypted form (AES-256); the key is kept separately.
- Data minimisation and deletion: We request only the permissions needed for the functions described. When you disconnect a channel or delete your account, we revoke the permission with Google and delete the tokens immediately; other data is deleted as described in section 10.
- Security incidents: If data is disclosed without authorisation despite these measures, we notify the competent supervisory authority and the affected persons in accordance with Art. 33 and 34 GDPR.
5. AI features: Google Cloud and Vertex AI as processor
Castfold generates channel concepts, metadata, translations, advice, images, videos, narration and music with Google models (Gemini, Veo, Imagen, Lyria) through Google Cloud Vertex AI. The contracting party and processor (Art. 28 GDPR) is Google Cloud EMEA Limited, 70 Sir John Rogerson’s Quay, Dublin 2, Ireland, under the Google Cloud Data Processing Addendum; the data is not used to train the models.
What is transmitted: the text you enter (keywords, hints, scripts, questions), excerpts of your channel data and analytics as context, and image prompts. You should not enter personal data of third parties.
Processing location and third countries: We call the models through the global endpoint of Vertex AI, video models through the us-central1 location (USA). With the global endpoint, Google selects the data centre that processes the request; we cannot determine the location, and processing may take place outside the European Union, in particular in the USA. These transfers rely on the European Commission’s adequacy decision on the EU-US Data Privacy Framework (Google LLC and its US subsidiaries are certified; Art. 45 GDPR) and, in addition, on the EU standard contractual clauses in the Cloud Data Processing Addendum (Art. 46(2)(c) GDPR). Google’s sub-processors are listed at https://cloud.google.com/terms/subprocessors. The legal basis is performance of the contract (Art. 6(1)(b) GDPR).
Every AI call is logged with time, model, tokens and cost so that we can show and bill your usage.
6. Video files and object storage: Cloudflare R2 as processor
Video files you upload, deliver by address or create in the video studio, raw thumbnail files, and intermediate and result files from the video studio (raw clips, stills, narration tracks, music bed, final cut) are stored in the object storage Cloudflare R2 operated by Cloudflare, Inc., 101 Townsend St., San Francisco, CA 94107, USA (European contact: Cloudflare Germany GmbH, Rosental 7, 80331 Munich, Germany; data protection officer: dpo@cloudflare.com). Cloudflare acts as a processor (Art. 28 GDPR) under the Cloudflare Data Processing Addendum, which forms part of our contract with Cloudflare, and does not use the files for its own purposes.
What Cloudflare processes: the files named above plus technical details of each object (an internal identifier of the account, video or project as the file name, size, time, file type) – no names, titles or e-mail addresses. When you upload a video file in the browser, your browser transfers the file in parts directly to Cloudflare without passing through our server; Cloudflare thereby receives your IP address, the time, the browser identifier and the size of the parts and processes these access data for delivery, security and billing according to its own retention periods. The same applies when your browser loads a preview directly from Cloudflare. We do not store these access data ourselves. Access to the files happens exclusively through signed, short-lived URLs; the storage itself is not publicly reachable, and the files are stored there encrypted.
Storage location and third countries: The storage bucket is pinned to the EU jurisdiction; Cloudflare guarantees that the files themselves are stored exclusively in data centres in the European Union. The technical object details, access data and usage metrics, by contrast, may be processed by Cloudflare in its core data centres worldwide, including the USA; and because Cloudflare, Inc. is a US company, access from the USA or by Cloudflare affiliates in other countries (for example by support or operations staff) cannot be ruled out. These transfers rely on the European Commission’s adequacy decision on the EU-US Data Privacy Framework (Cloudflare, Inc. is certified; Art. 45 GDPR) and, in addition, on the EU standard contractual clauses in the Data Processing Addendum (Art. 46(2)(c) GDPR). Cloudflare’s sub-processors are listed at https://www.cloudflare.com/gdpr/subprocessors/; Cloudflare’s privacy policy is at https://www.cloudflare.com/privacypolicy/.
Legal basis: performance of the contract (Art. 6(1)(b) GDPR); for the access data during direct upload and previews, our legitimate interest in a fast, secure transfer that does not pass through our server (Art. 6(1)(f) GDPR).
Deletion: The retention periods for these files are set out in section 10; deletion is triggered by our application. Cancelled or unconfirmed uploads are removed by us after 24 hours without progress; after two days at the latest Cloudflare deletes them itself according to our rule. Images, voice samples and music, by contrast, continue to reside in our database on our own server.
7. E-mail delivery
We send sign-in codes, invitations and notifications through the e-mail service of ALL-INKL.COM – Neue Medien Münnich, owner René Münnich, Hauptstraße 68, 02742 Friedersdorf, Germany (processor, data centres in Dresden, Germany). E-mail address, subject and message content are processed.
Log of outgoing e-mails: When we send you an e-mail (for example a sign-in code, an order confirmation or a notice about your account), we store the recipient address, subject, type of e-mail, time, delivery status (sent or failed, including the mail server’s error message) and the link to your account – but not the content of the e-mail; we never store sign-in codes or links. The purpose is to prove that and when an e-mail was sent and to troubleshoot delivery problems; the legal basis is our legitimate interest (Art. 6(1)(f) GDPR). Entries are deleted automatically after 90 days.
8. Payment processing, invoices, fraud prevention
Payments are processed by Stripe Payments Europe, Ltd., 1 Grand Canal Street Lower, Dublin 2, Ireland (“Stripe”), as an independent controller. Stripe receives name, e-mail address, billing address, VAT identification number where applicable, amount and payment method; we do not receive full card details, only confirmation, amount, time, the last digits and a technical identifier of the payment method (Art. 6(1)(b) GDPR). Stripe issues invoices on our behalf; we retain them for eight years (§ 14b UStG, § 147 AO). Stripe screens payments for fraud (Stripe Radar) and may process device data and the IP address for this; Stripe’s privacy policy: https://stripe.com/privacy. To prevent multiple starter credits and chargeback fraud we store the technical identifier of the payment method and the IP address at registration and match them against other accounts (Art. 6(1)(f) GDPR); a block after a chargeback is reviewed by a person before it remains in place for more than 30 days. If we store a card for automatic top-up, this happens only with your consent in the purchase flow; you can remove it in the customer portal at any time.
Partner payouts. For commissions Stripe sets up a payout account (Stripe Connect) and verifies identity and bank details as an independent controller under anti-money-laundering rules. We transmit to Stripe your name or company name, address, e-mail address, country, language, your website if you provide one, and the payout amounts, and retain the credit notes for eight years.
9. Contact, partner applications, support
If you write to us by e-mail or through the contact or partner form on the website, we process your details (name, e-mail address, message, for the partner form also website and reach, plus the chosen language) to handle the request (Art. 6(1)(b) or (f) GDPR). Form submissions are stored on our server and additionally delivered to us by e-mail. To keep automated submissions out, the form checks a hidden field and the time between display and sending; we use neither a captcha nor tracking. We delete the details once the request is settled and no retention obligation applies.
10. Retention, deleting your account
We keep account data until you delete your account. You start the deletion in the application and confirm it with a code sent by e-mail; we then remove channels, video details, analytics, studio projects, memberships and access keys without undue delay, revoke the YouTube permissions with Google and anonymise the account. Restoration is not possible. You can export your data beforehand (section 12).
After deletion we keep only what the law requires or what we need to defend claims (Art. 17(3)(b) and (e) GDPR), counted from the end of the calendar year:
- Invoices, credit notes, partner credit notes, billing details (country, business status, VAT ID, identifiers at the payment provider): eight years (§ 14b UStG, § 147 AO, § 257 HGB).
- Credit bookings, top-ups and usage with time, type and amount (without AI inputs and outputs): ten years (§ 147 AO, § 257 HGB).
- Order confirmations with billing address, your consents in the purchase flow and in the studio, cancellations, block notes and the record of the deletion with your e-mail address: six years (§ 257 HGB, § 147 AO); afterwards we remove address and e-mail address from them.
- Payment-method identifier and registration IP address against multiple starter credits: twelve months after deletion (Art. 6(1)(f) GDPR).
- At the payment provider we immediately detach all stored payment methods and have the customer record deleted 180 days after the last payment or refund; invoices remain there for the period stated.
Video files you upload yourself that are not scheduled for publication are deleted 30 days after the upload or after a schedule is cancelled, with a reminder by email seven days beforehand; video files of scheduled or published videos are deleted as soon as YouTube has processed them, at the latest 48 hours after the transfer to YouTube. The related entries with title, description, thumbnail and analytics remain until you delete the video or the account. Export files are deleted 48 hours after they are made available. Server logs: 14 days. Log of outgoing e-mails (without content): 90 days. AI call logs with inputs and outputs: 24 months for billing and cost control.
11. Recipients and international transfers
Recipients are the processors named above (Host Europe, ALL-INKL.COM, Google Cloud, Cloudflare, payment service provider) and Google LLC in the context of the YouTube API. Transfers to the USA rely on the European Commission’s adequacy decision on the EU-US Data Privacy Framework (Art. 45 GDPR) for the recipients certified there and, in addition, on the EU standard contractual clauses (Art. 46(2)(c) GDPR).
12. Your rights
You have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and to object to processing based on legitimate interests (Art. 21). You may withdraw consent at any time with effect for the future. You can lodge a complaint with a supervisory authority; the competent authority is the State Commissioner for Data Protection and Freedom of Information of Rhineland-Palatinate, Germany. Requests to mail@castfold.com.
You obtain your data export (Art. 20 GDPR) yourself in the application under Account: we provide a ZIP with your account, channel, video, analytics and studio data and, for the account owner, invoices and credit history, and send you a link valid for 48 hours. Credentials, keys and video files are not included.
13. Changes
We update this policy when features or the legal situation change. The current version is always at castfold.com/privacy/.