Privacy Policy
What personal data Draft2Cut processes, why, for how long, who it is shared with, and the rights of the people it belongs to.
Last updated 9 November 2026
1.Who is responsible
The data controller is Alcalambra S.r.l., registered at Via Chopin 37, 20141 Milano, Italia (P. IVA IT04629320963). For anything concerning personal data, including the rights described below, write to [email protected].
Draft2Cut has two roles, and it helps to keep them apart. For account, billing, security and usage data, Alcalambra is the data controller. For the production content an organisation uploads or generates — texts, images, recordings, and the data of the people who appear in them — the controller is the customer organisation, and Alcalambra acts as processor (Article 28 of the Regulation), processing it only to provide the service and on the customer's instructions. That relationship is governed by a data processing agreement, which can be requested at [email protected] and applies to customers who sign it.
No data protection officer has been appointed: this processing does not fall within the cases that make one mandatory under Article 37 of the Regulation. Requests go to the address above.
The controller could change in the future, through a corporate reorganisation, a merger, or a transfer of business — the same possibility already provided for in the Terms of Service, under «Changes and assignment». A change of this kind may include a transfer to a company established outside the European Union, including the United States. If it happens: the new controller remains bound by this same policy until it publishes its own; the transfer of personal data relies on whichever legal basis for a transfer outside the EEA is valid at that time — standard contractual clauses, an adequacy decision, or an equivalent mechanism, whichever applies when it happens; and none of the rights described further on are reduced. A change of this kind is announced with the same notice already promised for material changes to this policy.
2.Where the data lives
The application and the database run on Fly.io in the Francoforte (Germania) region. Generated files — images, audio, video, documents — are stored on Cloudflare R2, in a bucket bound to the Unione Europea jurisdiction.
Account and project data therefore does not leave the European Economic Area, with one exception — the most important one in this policy: content sent to an AI provider to be processed. That exception has a section of its own.
3.What we process
| Category | What it covers |
|---|---|
| Account | Email address, first and last name, password (stored only as a bcrypt hash, never in clear), preferred language, the role held in each organisation, activation and terms-acceptance dates. |
| Production content | Everything written or generated: treatments, screenplays, characters, environments, shots, images, audio, video, music, and the prompts that produced them. |
| Images and voices of people | Photographs and recordings uploaded as a reference for a character. When used to make a face speak or move they become biometric data: see the dedicated section. |
| Usage and cost | A record of each generation: which activity, which model, how many tokens or minutes, the estimated cost, the time and the IP address of the request. |
| Activity log | Who did what and when, for operations that change an organisation: creations, deletions, configuration changes, invitations, role changes. |
| Billing | Company name, address, VAT number and invoice history, for paid plans. Of payment methods we keep only the last four digits and the card brand. |
| Access and security | Confirmation and sign-in links sent by email, stored as a fingerprint and valid for fifteen minutes; a log of sign-in and registration attempts, which holds only keyed fingerprints of the email address and the IP address, used to limit attempts; the date the email address was confirmed; when the app is used, the start and end of each session and the organization open at the time, with no IP address or browser, to protect accounts and give support; the country given at registration. |
| Visit statistics | Page views, visits and visitors, with the country they come from and the time spent, collected with two first-party cookies (a random code for the browser, thirteen months; one for the visit, thirty minutes). The IP address, the account and the organisation are not stored: the path is recorded as a pattern (/projects/[id]/script). For the first page of a visit the name of the referring site (not its full address) and the campaign labels of the link (utm_source, utm_medium, utm_campaign) are stored. Sending a beta request or a guide request, or registering, is also counted, without a name or an email, tied to that origin. A page viewed while a member of the Draft2Cut team is signed in carries only a yes/no mark, to leave the team's own visits out. See the cookies page. |
| Beta requests | The details of the form on the public site: name, work email, company or studio, role, country (chosen from a list), type of organization and, if the person writes them, the project in development and its deadline, the AI tools they use, the languages they need, how they heard about Draft2Cut and what they would like to do first; the date of the consent and the version of this policy; whether they asked to receive news. Two keyed fingerprints are also kept, of the email address and of the IP address, to limit repeated submissions: the IP address itself is not kept in clear. Every request is also notified by email to the Draft2Cut team. A person who is invited receives a personal link, valid thirty days and kept only as a fingerprint; we record when the link is opened (and how many times), whether the welcome video was watched to the end, the answer (interest or decline), the acceptance of the beta tester terms with their version, and the registration. |
| Guide requests | The details of the form used to ask for a free guide (for example the legal guide to AI models): name and surname, email and, if the person writes them, studio or company and role; the date of the consent and the version of this policy; whether they agreed, with the optional checkbox, to be contacted about the service; the language of the page; where the request came from (the campaign labels of the link that opened the page, or the page of the site the person came from, or the name of the referring site); how many times the download link was opened. The link sent by email is valid for 24 hours and only a fingerprint of it is kept. Two keyed fingerprints are also kept, of the email address and of the IP address, to limit repeated submissions. |
| Staff access | At a customer's request, or to resolve a problem or abuse, a Draft2Cut staff member can enter an organisation and see what its users see. Every such access leaves a trace in the activity log. |
| Technical | IP address and browser information in server logs, for diagnostics and security. |
4.Why, and on what legal basis
| Purpose | Legal basis |
|---|---|
| Running the service: accounts, projects, generations, file storage. | Performance of the contract (Art. 6(1)(b)). |
| Answering a request to take part in the beta and deciding whom to invite, by contacting the person by email. | Pre-contractual steps taken at the data subject's request (Art. 6(1)(b)) and consent (Art. 6(1)(a)) to be contacted about the beta, given with the checkbox on the form. |
| During the beta, analysing what beta testers do on the platform to find problems and study their workflows, in order to improve the product, as the beta tester terms accepted before registration say. | Performance of the beta participation agreement (Art. 6(1)(b)) and legitimate interest in fixing and improving the service (Art. 6(1)(f)). |
| Sending the requested guide by email, and understanding which channel (a video, a page of the site) the requests come from. | Consent (Art. 6(1)(a)), given with the checkbox on the form. Asking for a guide does not subscribe anyone to a list. |
| Contacting someone who asked for a guide to present the Draft2Cut service, only if they agreed with the optional checkbox on the form. | Consent (Art. 6(1)(a)), separate from the one to receive the guide, not needed to receive it and revocable at any time by writing to [email protected]. |
| Sending news about Draft2Cut to whoever asked for it with the optional checkbox on the form. | Consent (Art. 6(1)(a)), separate from the previous one and revocable at any time by writing to [email protected]. |
| Invoicing and meeting accounting and tax obligations. | Legal obligation (Art. 6(1)(c)). |
| Keeping the activity and usage logs, preventing abuse, measuring cost. | Legitimate interest (Art. 6(1)(f)): being able to reconstruct who did what inside a shared organisation, and to attribute costs to whoever incurs them. |
| Sending service messages: invitations, email address confirmation, sign-in links, notice that a job has finished, security notices (for example to someone who already has an account when somebody tries to register with their address). | Performance of the contract (Art. 6(1)(b)). |
| Protecting accounts: confirming that an email address belongs to whoever registers it, limiting sign-in and registration attempts, spotting unusual access. | Legitimate interest (Art. 6(1)(f)): preventing anyone from entering an account that is not theirs or using the service in someone else's name. |
| Understanding how the site is used: visit statistics, including the count of beta request forms sent, of guide requests and of registrations (with no data about the person), only in aggregate form, identifying no one and with no third-party tools. | Legitimate interest (Art. 6(1)(f)): improving the service and seeing which pages are needed. If the browser sends «Do Not Track» or «Global Privacy Control», nothing is counted. |
| Support and service security: staff access to an organisation at the customer's request or to resolve an abuse. | Performance of the contract (Art. 6(1)(b)) and legitimate interest (Art. 6(1)(f)), with a trace of every access. |
| Processing real people's faces and voices for animation and lip sync. | Explicit consent of the person depicted (Art. 9(2)(a)), which whoever uploads the material must have obtained. |
| Preventing and countering abuse and unlawful content, including child sexual abuse material; responding to reports and to requests from authorities. | Legal obligation (Art. 6(1)(c)) and legitimate interest (Art. 6(1)(f)): keeping the service safe and not letting it become a tool for wrongdoing. |
| Complying with sanctions and embargoes: checking the country declared at registration, at subscription and in the beta request (excluded countries are not in the list), and the country the connection comes from. | Legal obligation (Art. 6(1)(c)) and legitimate interest (Art. 6(1)(f)). |
We do not profile, we make no automated decisions producing legal effects on individuals, and we sell data to no one.
5.Faces and voices: biometric data
Uploading a real person's photograph or voice to build a character means processing a special category of personal data. Draft2Cut does not use it to identify anyone, but transmits it to providers that derive face and voice models from it.
Whoever uploads that material acts as controller of their own processing and answers for it: they must hold a written release from the person depicted, with a defined scope of use and duration, and must have it, and have informed the person, before uploading. Draft2Cut does not collect that consent on behalf of whoever uploads and cannot verify it. Facial-animation providers require this expressly in their contracts — they do not grant those rights, they demand them from whoever uploads.
The notice to hand to the person depicted, the public retention and destruction policy, and the release form are at /likeness-release. For each character, whoever uploads must declare whether it depicts a real person and record the consent before images can be uploaded. Anyone who would rather not process biometric data has two routes: fully generated characters, which depict nobody, or the engines that run on your own infrastructure, where the material never leaves your perimeter.
6.Who we share it with
To generate something, the text or image needed to produce it is sent to the provider chosen for that craft, and to that one only. The choice is made per project and is visible on every screen that generates anything.
- Language model providers, for screenwriting and text analysis.
- Image generation providers, for characters, environments, props and storyboards.
- Speech synthesis and video generation providers, for dialogue, animation and lip sync.
- Infrastructure providers: hosting, file storage, transactional email, DNS and network protection (Cloudflare).
A named list of the active providers, with each one's country and transfer basis, is published at /subprocessors and is kept current because it changes more often than this document. We choose providers and configurations that do not train their own models on transmitted content; where a provider's terms say something different, the list says so.
Cloudflare, besides hosting the file storage, runs the domain's DNS and, in front of the application, provides attack protection and the check of the country a request comes from: it therefore sees the IP address of anyone visiting the site, and uses it to protect the site and to apply the country blocks described in the Terms of Service.
Several providers are established outside the European Economic Area, notably in the United States: transfers rely on the European Commission's standard contractual clauses or on an adequacy decision, depending on the provider.
Anyone who supplies their own API keys sends content under their own contract with that provider: the relationship is direct and governed by that contract. Anyone using the local engines — Ollama, ComfyUI, Piper and the others that run on your own machine — transmits nothing to anyone.
7.How long we keep it
| Data | Retention |
|---|---|
| Account and production content | For as long as the account exists. |
| Deleted projects and files | Removed on deletion; the archive of a project you set aside stays for as long as you keep it. |
| Activity and usage logs | Twenty-four months: what it takes to reconstruct a disputed charge or an unusual access. |
| Invoices and accounting records | Ten years, as Italian law requires. |
| Server technical logs | Ninety days. |
| Confirmation and sign-in links | Valid fifteen minutes; the row is deleted seven days after it expires. |
| Log of sign-in and registration attempts | Twenty-four hours. |
| Session log (start and end of each use of the app) | Twenty-four months, after which the row is no longer linked to any person or organization: only dates, length and country remain. If the account is erased sooner, until then the sessions stay attached to the anonymised account, with no name or email. |
| Visit statistics | Fourteen months, then deleted. |
| Beta requests | 12 months from the day they are sent, then deleted. Someone who is accepted has an account, which follows the account rules; consent to news can be withdrawn at any time. |
| Guide requests | 12 months from the day they are sent, then deleted. The download link stops working after 24 hours; consent to be contacted can be withdrawn at any time. |
| If the service is discontinued | Biometric data and release forms: immediately; content and account data: within thirty days of shutdown; backup copies: within ninety days. See «If the service closes». |
| Content reports and moderation decisions | For as long as needed to establish, exercise or defend a right, or as the law requires. |
When an organisation is closed, its files are removed from storage in a single operation: they are filed under a path that belongs to that organisation and to no other. Only the records the law requires us to keep remain.
8.How we protect it
- Passwords are stored as bcrypt hashes: not readable even by whoever administers the system.
- API keys entered by customers are encrypted at rest (AES-256-GCM, key derived with PBKDF2).
- Invitation tokens are stored as a fingerprint: reading the database does not let anyone sign in as someone else.
- Every query is scoped to the organisation it belongs to, and each organisation's files live under a separate path.
- Traffic is encrypted in transit; session cookies are httpOnly and not readable from JavaScript.
- Whoever registers must confirm their email address with a link sent to the inbox before the password gives access.
- Sign-in and registration attempts are limited; the log that counts them holds only fingerprints, not the addresses, and is deleted within twenty-four hours.
- Private files — restore archives, release forms, packages waiting to be imported — are handed only to people working in the organisation that owns them.
- Requests the system makes to addresses customers provide, for example a local model server, are checked before they go out, so that they cannot reach the internal network.
- The site's security headers limit where a page can load content from and prevent other sites from framing it.
If a personal data breach occurs that presents a risk to individuals, we notify the data protection authority within seventy-two hours of becoming aware of it, and inform the individuals concerned without delay when the risk is high. For content we process as a processor we notify the customer organisation, which is its controller, without delay so that it can meet its own obligations. No measure makes a system impossible to breach: this list says what we do, it does not promise an absence of incidents.
9.Your rights
Anyone may ask to access their data, correct it, erase it, restrict its processing, receive it in a machine-readable format, and object to processing based on legitimate interest. Where processing rests on consent, consent may be withdrawn at any time without affecting what was done before.
Requests go to [email protected] and are answered within one month. Anyone who believes the processing breaches the Regulation may complain to the Italian supervisory authority (Garante per la protezione dei dati personali, www.garanteprivacy.it) or to the authority of their country of residence.
If you are part of someone else's crew and want your account deleted, note that the content produced stays with the organisation that commissioned it: what disappears is the person's identity, not work done on another's behalf.
Anyone in a jurisdiction that grants further rights sees them honoured the same way — for example in California, where the California Consumer Privacy Act guarantees the right to know what data is processed, to correct it, to delete it, and to opt out of its sale: Draft2Cut does not sell or share personal data with third parties for advertising purposes, so that particular right is already met by how the service is built. For any other right recognised under your country's law, the request goes to the same address above.
10.If your data is in a customer's content
If you appear in a project — as a person depicted, a voice, the author of a text — and your data is in the content an organisation has uploaded, that organisation is the controller and your requests about your rights should go to it. If you write to [email protected] we will tell you whom to contact and, as far as the service is concerned, help the customer respond: we cannot decide the fate of that content in its place.
11.If the service closes
If Draft2Cut discontinues the service, we announce it with at least sixty days' notice (see «Service discontinuation» in the terms of service). Until shutdown anyone can export their data. At shutdown we destroy biometric data and release forms immediately; production content, account data and files within thirty days; backup copies within ninety. We ask the providers that process data on our behalf to delete it in turn.
Only the documents the law requires us to keep remain — in particular invoices, for ten years — and the records needed to defend or assert a right, for as long as necessary. Even after closure the controller remains reachable at [email protected] for at least twelve months, for data subjects' rights and for any data breach.
12.Changes
If this policy changes materially, account holders are notified before the changes take effect. The date at the foot of the page always says which version you are reading.

