DocuClip Studio

Privacy Policy

Last updated 19 November 2026

This policy explains what John Bishara (“we”), the controller of your personal data for DocuClip Studio, collects, why, and what your rights are under the EU General Data Protection Regulation (GDPR, in German: DSGVO), the UK GDPR and similar laws.

The short version. Your videos are rendered in your own browser with WebCodecs. The images, screenshots and footage you use never leave your device. We keep the minimum needed to run an account: your e-mail address, your sessions and devices, your subscription status and whatever you choose to save. We use Google Analytics 4 to learn which pages and features lead people to try and to buy the studio (see section 4). We run no advertising.

1. What stays on your device

Rendering and encoding happen on your device (WebGL, Canvas and WebCodecs). Uploaded images, newspaper screenshots, logos used in a preview, a voiceover you record or import, the finished video files, your autosaved project and the projects, timelines and export list of the studio’s library (kept in your browser’s own storage) are not sent to us.

2. What we store

DataWhyKept for
E-mail addressYour account, sign-in codes and the e-mails about your subscription (see section 4)Until you delete the account
If you ask on a phone for the link that opens a preset on your desktop: the e-mail address you type there (no sign-in is asked for)Sending you that one e-mail. The address is not added to any list and is not stored; a one-way hash of it is counted so that an address gets one link a day (the rate-limit counters below)The address: not kept. The hash: up to 48 hours
If you continue with Google: the identifier of your Google account and your e-mail address, read from the sign-in token Google gives your browser (Google confirms that the address is verified). We never see your Google password, contacts or files.Signing you in with GoogleUntil you delete the account
One-time sign-in codes and the browser that asked for each (both stored only as a keyed hash)Passwordless sign-in10 minutes, then expired
Sessions and devices: a keyed hash of a browser fingerprint, browser family and operating system, a readable label such as “Chrome on Windows”, last-seen timeKeeping you signed in; the two-device limit of a subscriptionUntil sign-out or 30 days of inactivity
Subscription status mirrored from Paddle: plan, billing period, status, Paddle customer and subscription identifiers, whether a payment was refundedGiving you what your plan includes; preventing abuse of the refund guaranteeWhile the account exists, and as long as tax and accounting law requires
Fair-use counters: a one-way hash of each project exported at paid quality during the first 14 days of a subscription, with the time. The project itself is not stored.Pacing exports during the refund windowWhile the account exists
Brand kits and projects you choose to save (text, colours, a logo you upload to a kit; embedded images are stripped from saved projects)So that you can open them again on another deviceUntil you delete them or the account
Rate-limit counters keyed by account, session, mailbox or the network part of the IP address (/24 for IPv4, /48 for IPv6)Security and abuse preventionUp to 48 hours
Device key: the public half of a signing key that your browser creates and keeps (the private half never leaves your browser and cannot be exported), and a log of when a subscription moved to another deviceProving that a request comes from the browser that signed in, so that a copied session cookie is useless; the limit of 2 device changes in 30 days on a paid seatUntil sign-out or 30 days of inactivity; the change log for 30 days
Coarse location of your connection as reported by our host: country, coordinates rounded to about 11 km, and whether the network is a home/mobile network, a datacenter/VPN or a privacy relay. We do not store your IP address for this.Ending a session that is used from two places no one could travel between (a sign of a copied session); comparing the country with the billing countryThe last position of each session and account, overwritten as you move; until sign-out
Payment-method fingerprint: a keyed one-way hash (HMAC-SHA256) computed from the card brand, last four digits and expiry date (or the PayPal payer reference) together with the billing country and postcode, as reported by Paddle. The hash cannot be turned back into those details, and we never receive or store a full card number.Recognising when a payment method that was refunded or charged back is used again on another accountWhile the account exists, and up to 24 months after its last payment
Browser integrity signals, on paid plans, at sign-in and export: whether the browser alters canvas read-backs (a sign of fingerprint-spoofing software), and keyed hashes of the graphics renderer name and of a test audio rendering, the screen ratio, the number of processor cores, the time zone and the language. These are not used to track you across sites or for advertising.Weighing the risk of refund abuse together with other signals; never used on its own to block anyoneThe latest value per device; risk signals for 30 days
Content signatures, on paid plans: keyed one-way hashes of a brand kit’s logo, palette and fonts, and of a narration script sent to Script-to-B-Roll. The script and the logo themselves are not kept for this purpose.Recognising a refunded customer who returns under a new account with the same materialWhile the account exists
Project similarity sketch, on paid plans, when you export during the first 14 days of a subscription: 16 numbers computed from the project (its places, wording or data): in your browser for newspapers and charts, and by our server from the scene the studio already sends for rendering for maps, evidence boards and forensics scenes. At the standard pace they show whether two exports are the same project; they cannot be turned back into the content. For maps, evidence boards and forensics scenes our server also keeps a keyed one-way hash (HMAC-SHA256) of the places and wording, used only to recognise an unchanged re-export. The text, data and images themselves are not sent.Counting projects for the pace of exports during the refund window, so that at the standard pace a corrected or restyled version of a project is not counted twice, and at a reduced pace an unchanged re-export is not counted againWhile the account exists
Free prompt trial: a keyed hash of each distinct custom AI prompt a free account has run (running one again is free; the prompt itself is not stored here), and a keyed hash of the network of your request (the first three parts of an IPv4 address, or the first three groups of an IPv6 address), to count the trial prompts that came from itKeeping the free trial to 3 prompts per account and 9 per network a day, so that it cannot be farmed with new accountsThe account’s trial record while the account exists; the network count 24 hours
Answers of the language model that reads a prompt our own rules cannot parse, stored under a SHA-256 hash of the normalised prompt and not linked to your account. The prompt itself is not stored.Answering the same prompt again without asking the model a second time30 days
Place lookups: when you press Enter on a place the built-in list of places does not know, the text you typed is sent by our server to OpenStreetMap’s geocoder, and its answer is kept under a SHA-256 hash of that text (the text itself is not stored). We count lookups per account and per network (a keyed hash of the network, as above) for each day, never what was looked up.Finding streets and places the built-in list lacks, no more than once a second for the whole site, as OpenStreetMap’s usage policy asks; keeping lookups to a fair number a dayAnswers 30 days (1 day when nothing was found); the daily counts until the next day is over
Delivery record, on paid plans: how many short test exports and production exports each subscription has made; the time you accepted the test notice and the time you confirmed the production acknowledgement, each with the country your connection came from at that moment and the version of the text you were shown; the time, kind (video or timeline pack), class (test or production), clip length and manifest id of each watermark-free delivery; and the signed licence tag written into each exported fileShowing where a subscription stands under the 14-day compatibility guarantee when a refund is asked for, answering payment disputes, and tracing a file to the licence it was made underWhile the account exists, and up to 3 years after the last payment
Risk signals and standing: dated entries such as “datacenter network” or “device-change limit reached”, a score from 0 to 100, and a link between accounts that share a payment-method fingerprint or content signatureSetting the pace of exports during the first 14 days of a subscription (see the Refund policy); eligibility for a Founding 50 seatSignals for 30 days; links between accounts while the accounts exist

No automated bans. None of these signals closes an account, refuses a payment or changes your right to a refund. Their only effects are the pace of paid-quality exports during the first 14 days of a subscription, eligibility for a Founding 50 seat, and ending a session that appears to be used from two places at once (signing in again restores it). If you think a signal is wrong, write to us and a person will review it.

We normalise e-mail addresses to recognise one mailbox under different spellings (for Gmail, dots and “+tags” are ignored), and we do not accept addresses from temporary-inbox services.

We do not store your card details: payment data is collected by Paddle. We do not store the scripts you send to Script-to-B-Roll or the scene descriptions (places, timings) your browser sends to plan a shot; they are processed in memory to produce the answer and then discarded, apart from the hashes and cached model answers described above.

3. Cookies and local storage

Outside the EEA, the UK and Switzerland, Google Analytics sets two first-party cookies (_ga and _ga_<id>, kept for up to 13 months) that recognise a returning browser; in those regions it sets them only after you press Accept on the analytics bar, and none if you decline or do not answer (see section 4).

Apart from these, we set only strictly necessary cookies: a session cookie that keeps you signed in; for a browser that has passed the bot check but is not signed in, a guest session cookie; and, for the 10 minutes a sign-in code is valid, a cookie that lets only the browser that asked for the code enter it. All three are HttpOnly, Secure and SameSite=Strict, and none is used for advertising or tracking. Your browser’s own storage (local storage and IndexedDB) holds your preferences, your autosaved project, the projects and timelines you save in the studio’s library, the list of your recent exports, your answer to the analytics bar and, if you arrived through a partner’s link, the referral code of that link for up to 60 days so that the partner can be credited at checkout. None of it is sent to us.

4. Who processes data for us

  • Cloudflare, Inc. hosts the site, runs our server code and database (Cloudflare Pages, Workers and D1) and provides Cloudflare Turnstile, which checks that sign-in and session requests come from a real browser without showing a puzzle and without advertising cookies. Cloudflare Web Analytics counts page views and page load times without cookies, without local storage and without fingerprinting. Cloudflare processes your IP address and technical request data for this.
  • Paddle.com Market Limited and its affiliates sell the subscriptions as Merchant of Record and are an independent controller of your payment and billing data. See Paddle’s privacy policy.
  • Resend delivers the e-mails we send, and receives the address and the text of each one: the e-mail that carries your sign-in code; the e-mails about a subscription (the welcome after a purchase, a payment that did not go through, a cancellation that was scheduled, a plan that was replaced by another, and a refund or chargeback, with the notice that the licence of that billing period has ended); and, if you ask for it on a phone, the link that opens a preset on your desktop.
  • Google signs you in when you choose “Continue with Google” and tells us your e-mail address and account identifier; see Google’s privacy policy.
  • Language models. When our own rules cannot read a prompt or a line of a script, its text (never your files) is sent to a language model that turns it into a scene plan: Cloudflare Workers AI or, where this service is set up for them, OpenAI or Google’s Gemini API.
  • Map data services. Your browser requests map tiles directly from OpenFreeMap (streets, land and water), Mapterhorn and the AWS Open Data terrain tiles (elevation), and NASA Earthdata GIBS and USGS The National Map (satellite imagery, when a scene shows it), so those services see your IP address and which part of the map you are viewing.
  • OpenStreetMap Foundation runs Nominatim, the geocoder that finds a place the built-in list does not know when you press Enter in the place search. Our server sends it only the text you typed, never your account, e-mail or IP address.

Google Analytics 4 (product analytics). To learn which pages and features lead people to try and to buy DocuClip Studio, our pages load Google Analytics 4, provided by Google Ireland Limited. It records the pages you view and these steps: opening the homepage or a guide, pointing at or opening a sample, opening the studio or a template, the sign-in prompt, creating an account, a sample loading, building a scene from a typed prompt, running Script-to-B-Roll, an upgrade banner, an export that needs a paid plan, downloading the sample pack, opening the plans, starting a checkout and a verified purchase (plan, value, currency and Paddle transaction id). It never receives your e-mail address, your projects, your scripts or your exports. Google signals and ad personalisation are switched off. In the EEA, the UK and Switzerland the tag starts with all analytics and advertising storage denied, so it sets no cookies there and sends cookieless measurements only. If your browser sends Global Privacy Control or Do Not Track, no Google script loads at all, and any content blocker stops it without losing anything.

Your analytics choice. If the time zone or the language of your browser suggests that you are in the EEA, the UK or Switzerland, a bar at the bottom of the page asks once whether Google Analytics may set cookies. That check is made inside your browser; nothing is looked up or sent anywhere for it, and when it cannot tell, the bar is shown. Accept allows the analytics cookies and the measurement of a purchase (Google’s analytics_storage, ad_storage and ad_user_data). Decline keeps all three denied: no cookies are set and only cookieless measurements are sent. Until you answer, they stay denied in those regions; elsewhere they start allowed, and you can decline in the same way. Personalised advertising (ad_personalization) stays denied whatever you answer. Your answer and the time you gave it are kept in your browser’s local storage, not on our servers, and hold for these pages and for the studio. To change it, press “Privacy choices” in the footer of any page, or beside the legal links in the studio, and answer again; clearing this site’s data in your browser also resets it. With Global Privacy Control or Do Not Track the bar never appears, because no Google script loads at all.

We do not sell personal data and we do not share it with advertisers.

  • Performance of a contract (Art. 6(1)(b)): your account, sign-in (including sign-in with Google), the free prompt trial, your subscription and saved content.
  • Legitimate interests (Art. 6(1)(f)): keeping the service secure, the device limit and device key, rate limiting, bot protection, and preventing abuse of the refund guarantee (payment-method fingerprints, browser integrity signals, content signatures, coarse location and the risk signals built from them). You can object to this processing at any time; see “Your rights”.
  • Legal obligation (Art. 6(1)(c)): records we must keep for tax and accounting.

6. International transfers

Our providers operate globally. Where personal data is transferred outside the European Economic Area or the United Kingdom, it is protected by the European Commission’s Standard Contractual Clauses or an adequacy decision, as described in each provider’s data processing terms.

7. Your rights

You have the right to access your data, to have it corrected or erased, to restrict or object to processing, to receive it in a portable format and to withdraw any consent you have given. To use any of these rights, write to [email protected] from the address of your account; we answer within one month. You also have the right to lodge a complaint with the data protection authority of your country (in Germany: the Aufsichtsbehörde of your federal state).

8. Children

The service is not directed at children under 16, and we do not knowingly collect their data.

9. Changes

We update this policy when the service changes. The date at the top shows the latest version.

10. Contact

John Bishara · [email protected] · Contact page