What we hold, and who else touches it.

ReelDouble is run by Reeldouble LLC, an Arizona LLC, and that company is responsible for the data described here. Questions go to [email protected].

• Your name and email address, from the Google account you sign in with. That is the whole of the sign-in, and there is no password for us to hold.
• What you write into the studio: scripts, beats, character descriptions, project and part titles, and anything you type into the writing assistant.
• What the studio makes for you: rendered videos, character reference sheets, posters, filmstrips and the edits you assemble from them.
• Billing metadata from Stripe: which plan you are on, the state of the subscription, the last four digits and brand of the card, and a record of charges. Not the card number.
• Your credit ledger: what you were given, what you spent, and on which render.
• Usage and technical logs: pages and API routes you hit, the time, the IP address the request came from, the browser's user agent, and the outcome, including errors.
• What you do on our own pages: which page, which button you pressed, how much of a video you watched, and whether a purchase followed. It is tied to a random visitor id rather than to you, and clause 07 says what that is. We store no IP address and no browser user agent against it — only a keyed hash of the address, never the address itself — and no advertising network is involved in any of it.
• Cookies that keep you signed in, described in clause 07.

We do not ask for a date of birth, a phone number, a postal address, or anything about you that the studio does not need to run.

To give you an account and keep you in it. To render what you ask for and show you the result. To charge the right number of credits and take the right payment. To answer you when you write to support. To keep the service up and find out why it broke when it does, which is what the logs are for. And to spot abuse: somebody hammering the render queue, or making the kind of content the terms forbid.

These are the companies we use to run the service. Each one gets only what its job needs, and each is bound by its own contract with us.

Google

Signs you in. Google tells us the email address and name on the account you chose, and nothing else. We never see your Google password.

Stripe

Takes the payments and holds the card. Stripe sends us back the state of your subscription, the last charge, and which plan you are on. Card numbers never reach our servers.

fal.ai

Runs the video, image and voice models. Your prompts, your character reference images and the parameters of the render go there, and the finished file comes back.

Anthropic

Powers the writing assistant. When you ask it for help with a script, what you have written in that form is sent to Anthropic's API to get a suggestion back. It is not sent anywhere when you are not using it.

Cloudflare

Stores the files. Renders, character sheets, posters and filmstrips live in Cloudflare R2, and are served from there by links that expire.

Railway

Hosts the application and the database it keeps your account and projects in.

Beyond those, we share something only when the law requires it, when we have to in order to defend a legal claim, or if the business is ever sold, in which case you would be told before anything moved.

• We do not sell your personal information, and we do not share it for cross-context behavioural advertising. There is no advertising on ReelDouble and no ad network in the page.
• We do not use your scripts or your renders to train our own models, and we do not hand them to anybody to train theirs.
• We do not put your videos in marketing without asking you first.
• We do not watch your library. Support looks at an account only when you have written to us about it, or when abuse is being investigated.

Your projects, characters and renders stay until you delete them or until the account is closed. Delete a render and the video file is removed from storage, along with the filmstrip made from it for the editor.

When an account is closed we delete its content within 30 days. Two things outlive that: the record of what was charged, because tax and accounting rules require it, and technical logs, which are kept for up to 90 days and then rotate away. Backups are overwritten on their own cycle, so a deleted thing can sit in a backup for a short while after it is gone from the app.

We set the session cookies that keep you signed in and protect the sign-in from being forged, and two others. Both are first-party, both are set by this site and read by nobody else, and there is no third-party cookie, no tracking pixel, no advertising network and no analytics company anywhere on these pages.

The first is rd_vid, a visitor cookie. It holds a random identifier — a number with nothing of you in it — for 395 days, so that the pages you open on this site can be counted as one visit rather than as strangers. It is set by our own server and marked so that no script on the page can read it, it is never sent anywhere else, and it is used for one thing: knowing which parts of this site work and which do not. What we record against it is the page, the button and how far through a video you got. Never your browser’s user agent, and never your IP address: what is stored of that is the same keyed hash described below, which cannot be turned back into an address and exists only to tell a flood of requests from one machine apart from a room full of real people. We keep those rows for up to 13 months and then delete them. Clearing it makes you a new visitor to us and changes nothing about how the site works.

The second is a referral cookie called rd_ref. It is set only if you arrive here through somebody’s Refer & earn link, it holds the six-character code from that link for 60 days, and it is read once — at the moment an account is created — to credit the person who sent you. It is never used for advertising, never sold and never passed to anyone else. Clearing these signs you out and forgets a referral link you followed; nothing else breaks.

Following one of those links also records that it was followed, so the person whose link it is can see how many people opened it. What we store is the link’s code, the hour, and a keyed hash of your IP address — never the address itself, and nothing that can be turned back into it. It exists only so that opening the same link twice in an hour counts once. We keep those rows for up to 13 months and then delete them, and if the person whose link it was closes their account, theirs are deleted straight away.

Two of these are buttons rather than requests, on your account page. Download a copy of what we hold, as one file: your projects, characters, renders, edits, drafts, writing and credit history, with links to every video and image. Those links last about an hour, so save what you want to keep. Or close your account, which blanks your name and email here and deletes your content and the files behind it. That normally finishes within minutes; the 30 days in clause 06 is the outer limit, not the wait. Closing also ends a paid plan, which is not the same as cancelling one: clause 05 of the refunds page is where what that does to your money is written down. Take the copy first: once the account is closed there is nothing left to send.

What we keep when you close, and why, is written out in clause 06: the record of what was charged, because tax and accounting rules require it, and the technical logs until they rotate away.

For anything else, write to [email protected] from the address on your account. We will correct something that is wrong, or tell you exactly what happened with a particular render. We answer within 30 days and we do not charge for it. If you are in a place that gives you formal rights over your data, such as the UK, the EU or California, these are those rights and asking for them will never get your account treated differently.

ReelDouble is for adults. You have to be 18 or older to use it, it is not aimed at anybody under 18, and we do not knowingly collect anything from them. If you believe a child has an account here, write to us and we will remove it.

Everything moves over HTTPS. Files in storage are reached through links that expire rather than through public URLs, payment details never reach our servers, and access to the database is limited to the people who run the service. No system is perfect, and if we ever have a breach that affects you we will tell you.

The application, the database and the files are hosted in the United States. If you use ReelDouble from elsewhere, your data is processed there.

When this policy changes, the date at the top changes with it, and a significant change is called out on the page rather than slipped in. This page is the record of what we do with your data, so it is the place to check.