What we keep, and why.
This policy covers rollcut.dev and Rollcut Cloud at app.rollcut.dev. The short version: we store what it takes to record your trailers and bill you, we sell nothing, and you can have it all deleted by sending one email.
The marketing site
rollcut.dev is a static page served by Cloudflare. It sets no cookies. Cloudflare Web Analytics counts visits without cookies or fingerprinting. The playground on the page runs in your browser and sends nothing to us.
Your account
You sign in with a magic link sent to your email, or with GitHub. We store your email address, your name and avatar if GitHub provides them, and a session cookie that keeps you signed in. Magic-link emails are sent through Resend. We do not run advertising or analytics scripts inside the app.
Payments
Credit packs are sold through Dodo Payments, the merchant of record. Dodo collects your card and billing details under its own privacy policy; we never see your card number. We keep a ledger of credits bought, held and spent, with the Dodo payment reference, for as long as your account exists and as long as tax law requires.
Recordings
For each take we store the address you pointed Rollcut at, the steps or brief, your brand settings, and the files produced: video, GIF, poster, subtitles. Files live in an S3-compatible bucket (Tigris) and are private to your account unless you turn on a public share link. They stay until you ask us to delete them or the account. Workers that record takes keep the files only while they work on them.
Demo-account credentials
If you store a demo account so the recorder can sign in to your app, the password or token is encrypted with AES-256-GCM before it reaches our database, using a key that lives only in the recording service’s configuration, never in the database. It is decrypted on the recording machine for the seconds it takes to sign in, and the signed-in browser state is discarded when the take ends. Staff cannot read stored secrets through the app. Delete a stored account from Settings and the ciphertext is removed at once. Please use dedicated demo accounts with made-up data.
Language models
When you ask the planner to write steps, we send your brief, the address, and the text and structure the recorder observed on your app’s pages to a hosted language model (currently Google’s Gemini) to produce the steps and captions. We do not send stored credentials to the model. Narration is synthesised on our own machines. Model providers process this data under their API terms.
Public share pages
A share link exposes the trailer, the vertical cut, poster and GIF, your product name, tagline and site address to anyone who has the link. Share pages carry a no-index instruction for search engines. Turn sharing off and the link stops resolving.
Logs and email
Our servers on Fly.io keep request logs with IP addresses for up to 30 days for debugging and abuse prevention. We email you about your takes and account; we do not send marketing email. Mail you send to any rollcut.dev address is kept so we can answer it.
Who else sees data
Only the services needed to run Rollcut, each for its own part: Cloudflare (marketing site), Fly.io (app and recording workers), Neon (database), Tigris (file storage), Resend (email), Dodo Payments (billing), Google (planner model), GitHub (sign-in, if you choose it). We do not sell or rent personal data, and we do not share it with anyone else unless the law compels us.
Your rights
You can see your takes, settings and credit history in the app. Email legal@rollcut.dev from your account address to get a copy of your data, correct it, or have the account and everything attached to it deleted; we act within 30 days. Deleting removes your files, stored demo accounts, ledger and profile, except billing records we must keep for tax purposes. Depending on where you live, you may also have the right to complain to a data-protection authority.
Security
All traffic is encrypted in transit. Secrets are encrypted at rest as described above, and recording workers run in isolated machines that hold no persistent data. Found a problem? See security.txt or write to security@rollcut.dev.
Changes
If this policy changes in a way that matters, we email the address on your account before the change takes effect. The date at the top is always the current version. The controller is Syed Arshad Ali, trading as Rollcut, reachable at legal@rollcut.dev.