DocuClip.studio

Privacy Policy

Last updated 17 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 run no advertising and no analytics trackers.

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, the finished video files and your autosaved project (kept in your browser’s local storage) are not sent to us.

2. What we store

DataWhyKept for
E-mail addressYour account and sign-in codesUntil you delete the account
One-time sign-in codes (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 3 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 in your browser from the project (its places, wording or data). They show whether two exports are the same project and cannot be turned back into the content. The text, data and images themselves are not sent.Counting projects for the pace of exports during the refund window, so that a corrected or restyled version of a project is not counted twiceWhile the account exists
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 the Founding 50 CharterSignals 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 the Founding 50 Charter, 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.

3. Cookies and local storage

We set only strictly necessary cookies: a session cookie that keeps you signed in and a guest cookie that lets the Free Sandbox work without an account. Both are HttpOnly, Secure and SameSite=Strict, and neither is used for advertising or tracking. Your browser’s local storage holds your preferences and autosaved project 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.

4. Who processes data for us

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

5. Legal bases (Art. 6 GDPR / DSGVO)

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 docuclip.support@gmail.com 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 · docuclip.support@gmail.com · Contact page