Trust & data

runime does not train any model on your prompts, your uploads or anything it generates for you. There is no training pipeline in the product: your screenplay, reference images, voice samples, boards and finished shots exist to make your film and for nothing else.

We do not sell, rent or trade your content or your personal data, and we do not use it to target advertising — not ours and not anyone else's.

Nobody here browses your projects. Access to production data is limited to the people who operate the service, and is used to diagnose a fault or answer a support request you raised — not to look at your film.

Your material is sent to a model provider only at the moment you ask for a generation, and only the part that generation needs. Every provider below is bound by a data processing agreement, and under their enterprise/API terms Google Vertex AI and OpenAI do not use API inputs to train their models.

Two exceptions we would rather you heard from us:

• Runway's terms of use reserve the right to use inputs and outputs for model training. If a production must never touch anyone's training set, choose a different video model for it — the model is a per-project setting.
• sync.so, the lip-sync pass (reached through fal.ai), takes a broad, sublicensable licence over content uploaded to it, including for its own marketing. For unreleased client work, either keep the lip-sync pass off or ask us about enterprise terms first.

The complete list of third parties that can receive your data, what each one is for, where it runs, and its own policy. This is the same list the Privacy Policy renders — there is one source for it in the codebase, so the two pages cannot drift apart. Providers are added here before they are switched on.

Projects, screenplays and generated media live for as long as your account does — a film you are still cutting must not evaporate. Delete a film, or close the account, and every byte of it is erased within 24 hours. Server access logs are kept 90 days. Billing records are kept 7 years because US tax law requires records that support a filed return, and no deletion request can shorten that one.

The full table, category by category with the legal basis for each, is in the Privacy Policy.

Privacy Policy — retention periods

You do it yourself, and nobody has to be in the loop. Delete a film from its own menu, or close the whole account from the account page. Either way the material disappears from the product at once and is erased from our storage within 24 hours by a job that runs every hour — not by someone reading an inbox. Copies held by a model provider fall under that provider's own retention window; we pass the request on where the provider offers a channel for it.

The 24-hour gap is the only undo there is, and it exists for a reason: a film may still be rendering when you delete it, and pulling the bytes out from under a running job leaves fragments nobody can reach. Write to us inside that window and we can stop it. After it, there is nothing left to restore from.

Deletion requests: support@runime.com

runime can clone a voice from a sample, and can recast a recording into a character's voice. Because that is digital-replica technology, consent is not a checkbox in the browser: the server refuses to create a cloned voice unless it can write down who gave consent, whose voice it is and their relationship to that person, the exact sentence they agreed to, when, and for which production. The record is kept apart from the project so it survives the film being archived or deleted.

If you need that record for a delivery pack, a broadcaster's compliance form or a festival submission, ask us and we will export it for the production.

Cloning a voice you do not have permission to use is a breach of the Terms of Service, and our audio provider independently screens and blocks samples it recognises as protected or synthetic.

Traffic is encrypted with TLS. Sign-in runs through Firebase Authentication and we never hold a password. Only the server-side service account reads the database; the browser cannot reach it directly. Your IP address is used to rate-limit abuse-sensitive endpoints — it lives in a counter that expires with its window, and we do not write it to our database; our hosting provider keeps its own access logs. Card details never reach our servers — Stripe takes them directly and is PCI DSS Level 1. If a personal-data breach occurs we notify the affected people and the supervisory authority within 72 hours.

What we are not: runime is not SOC 2 audited and not ISO 27001 certified, and we hold no other security certification. If your procurement process requires one, we would rather you knew now than after a signature. We are happy to complete a security questionnaire and to answer anything on this page in writing.

Every generated take records the model that made it, so a finished film knows exactly which providers touched it. The project info panel turns that into a per-film licence report: which providers were used, what each one's terms require of the person shipping the film (credits, permissions, plan conditions), and what does not transfer to a client. It is a summary of terms we read, not legal advice — but it is specific to your film rather than generic. The report itself is written in Turkish today, in both interfaces.

Beside the picture, an export can carry what a festival, a broadcaster or a post house asks for: subtitles as .srt and .vtt (optionally prefixed with the speaker's name), separate dialogue and M&E stems for dubbing and re-mixing, and a mix conformed to EBU R128 at −23 LUFS with the measured loudness report a channel's QC reads. Each of those is priced and rendered as its own master.

Every downloaded film carries a stereo track and, alongside it, a genuine 5.1 surround track — element-based routing with decorrelated rears, not a gain-scaled copy of the fronts. Stereo stays the default track so ordinary players are unaffected; a surround-capable player will offer the 5.1. If the surround encode fails the film still ships, stereo-only.

One inbox, read by us: privacy and deletion requests, security reports, unauthorised-likeness and copyright notices, security questionnaires, and anything on this page you want confirmed in writing.

• Email: support@runime.com
• Legal entity: IS.TEAM LLC, 8 The Green, Ste A, Dover, DE 19901 (Delaware, United States)
• Terms of Service · Privacy Policy · Explicit Consent