Privacy policy
What we store, why, who handles it for us, and your choices.
This is a draft that has not been reviewed by a lawyer. Words in dashed boxes are placeholders the owner sets before launch.
This policy explains what Entity name: placeholder, set by the owner (“we”) stores about you when you use Clipwright, and who handles it for us.
What we store
- Your account: email address, how you sign in, your plan and credit balance.
To sign you in, run the service and bill you.
- Your projects: the files of each film, its versions and each version’s one-line summary.
To draw, review and render your films, and keep their history.
- Your films and renders: the finished files, their progress and their history.
To deliver them to you and to estimate and charge renders.
- Your notes: what you write on the review page and what your agent answers.
So your agent can fix them and you can see what changed.
- Your channels: identities, fonts you bring with their licence statements, languages and approvals.
To make films in your own look.
- Your keys and connections: API keys (we keep only what is needed to check them), connected agents, and machines with their measured speeds.
To authenticate your agent and estimate renders on your machine.
- Reusable rendering code generated in your sessions (shaders, procedural geometry, camera paths, sound generators), which is part of your project’s files.
To generalise the useful techniques into Clipwright’s shared component library, under the library licence in the terms. The library carries no name or film of yours.
- Voice recordings, once voices open: the takes you record and the lines we speak for you.
To make the film’s sound. We will say here before we start.
- Billing records: what you bought and when. We do not see or keep your card number.
To give you your credits and a record.
- Technical logs: requests, errors and timings, with network addresses for a short time.
To keep the service safe and working.
| What | Why |
|---|---|
| Your account: email address, how you sign in, your plan and credit balance. | To sign you in, run the service and bill you. |
| Your projects: the files of each film, its versions and each version’s one-line summary. | To draw, review and render your films, and keep their history. |
| Your films and renders: the finished files, their progress and their history. | To deliver them to you and to estimate and charge renders. |
| Your notes: what you write on the review page and what your agent answers. | So your agent can fix them and you can see what changed. |
| Your channels: identities, fonts you bring with their licence statements, languages and approvals. | To make films in your own look. |
| Your keys and connections: API keys (we keep only what is needed to check them), connected agents, and machines with their measured speeds. | To authenticate your agent and estimate renders on your machine. |
| Reusable rendering code generated in your sessions (shaders, procedural geometry, camera paths, sound generators), which is part of your project’s files. | To generalise the useful techniques into Clipwright’s shared component library, under the library licence in the terms. The library carries no name or film of yours. |
| Voice recordings, once voices open: the takes you record and the lines we speak for you. | To make the film’s sound. We will say here before we start. |
| Billing records: what you bought and when. We do not see or keep your card number. | To give you your credits and a record. |
| Technical logs: requests, errors and timings, with network addresses for a short time. | To keep the service safe and working. |
We keep each kind for as long as you have an account, and for retention period after deletion: placeholder, set by the owner afterwards unless the law requires longer.
Who handles it for us
- Supabase
Our database and sign-in, including the emails that carry sign-in codes.
- Cloudflare
Hosting, delivery, and storage of your files.
- Dodo Payments
Payments. It is the merchant of record: it takes your payment and holds your payment details, under its own privacy policy.
- GPU and sandbox providers
Companies that run our rendering and the checks on library components. They process your film’s files while a render or check runs, and are not given your account details.
- The affiliate programme
When you arrive through a partner’s link, it records the referral with a cookie so the partner can be paid.
| Processor | What it does |
|---|---|
| Supabase | Our database and sign-in, including the emails that carry sign-in codes. |
| Cloudflare | Hosting, delivery, and storage of your files. |
| Dodo Payments | Payments. It is the merchant of record: it takes your payment and holds your payment details, under its own privacy policy. |
| GPU and sandbox providers | Companies that run our rendering and the checks on library components. They process your film’s files while a render or check runs, and are not given your account details. |
| The affiliate programme | When you arrive through a partner’s link, it records the referral with a cookie so the partner can be paid. |
We do not sell your data and we do not use your films to advertise to you or others.
Cookies and storage
The public pages set no tracking cookies. They remember your theme choice, light or dark, in your browser. The app keeps you signed in with a session. The affiliate programme’s cookie, above, is set only if you arrive through a partner’s link.
Your choices
- See and download your data, correct it, or ask us to delete your account.
- Delete a project, a film or a channel yourself in the app.
- Object to or limit how we use your data where the law gives you that right.
Write to support@clipwright.studio: placeholder address, set by the owner and we will answer within answer time: placeholder, set by the owner.
Children
Clipwright is not for children under 16 age: placeholder, set by the owner.
Changes
If we change this policy in a way that matters, we will tell you in the app before it starts.