Privacy Policy

The company behind the runime service (the “Service”) is IS.TEAM LLC, a limited liability company formed in Delaware, United States. It is the “business” under U.S. state privacy law and the “controller” under the GDPR: the party that decides what is collected and why, and the party you can hold to this document.

• Legal name: IS.TEAM LLC
• Address: 8 The Green, Ste A, Dover, DE 19901
• Jurisdiction: Delaware, United States
• Registration no. (Delaware File Number): 10536716
• Tax ID (EIN): 32-0850176
• Contact: support@runime.com

We are a United States company and the Service runs on infrastructure in the United States and, for some providers, elsewhere. Wherever you are, your information is processed in the United States — if you are outside it, that is an international transfer, and the “Data transfers and processors” section below names every company involved, what each one does and where it holds the data, so you can check the claim rather than take it.

The law that applies to you follows you, not us. A resident of California, Colorado, Texas or any other U.S. state with a comprehensive privacy statute has the rights that statute grants. Someone in the EEA, the UK or Switzerland has the rights the GDPR grants. Both sets are set out below, and we honour whichever applies to you.

Your paid subscription and token purchases are carried out by Stripe, Inc. (Merchant of Record — Stripe Managed Payments), acting as Merchant of Record. Your card details are collected directly by Stripe and are never stored on IS.TEAM LLC servers; with respect to that payment data Stripe is an independent data controller under its own privacy policy. These purchases are also governed by our Terms of Service.

We process the following categories of personal data while you use the Service:

Account and identity data

• Your name, email address, profile picture (avatar) and unique account identifier as provided by Google when you sign in with Google
• Your account status and your language and interface preferences

Service and content data

• The scripts, stories, ideas and instructions you write for production
• The reference images you upload (character, location or object images)
• The video, image and audio assets you create with the Service and their associated project data
• Your own voice recorded in the voice-changer (STS) feature. This recording is processed in order to be recast into the character voice you select. It is sensitive personal information — biometric data under the GDPR, and “sensitive personal information” under the U.S. state statutes that use that category — so it is processed only with your explicit consent, only for that purpose, and never to identify you. It is kept with the film’s audio so you can re-run or revert the take, and it is erased with the film: deleting the film, or closing your account, removes it within 24 hours. Ask us and we will remove it sooner.
• Voice-consent records. When you have a character voice cloned, we record the consent itself: your account identifier, whether the voice is your own or someone else’s, the name of that person where you tell us it is someone else’s voice, the exact wording you agreed to, the date, and the project it was given for. Without this record the clone is refused. Where the record contains a third party’s name, you are confirming to us that you have that person’s permission; the record exists so that permission can be evidenced later, and it is kept separately from the project so that deleting a film does not delete the proof behind the voice in it.

Technical data (device and network)

• IP address — used to count requests against the rate limits on abuse-sensitive endpoints (sign-in, share-link unlock). The counter expires with its rate-limit window and the address is not written to our database; our hosting provider records it in its own access logs
• Browser type, operating system, device and screen information, language preference
• Server access logs (URL, status code, timestamp)

Billing data

• Subscription type and status, token wallet balance and spending records
• Payment identifiers held on Stripe’s side (customer, subscription and payment IDs); the card number and CVV never reach our systems

Communication data

• The messages you send us for support, privacy requests or notifications, and their attachments

We also store a small number of cookies and similar browser storage; these are described in detail in our Cookie Policy.

We process your personal data for the following purposes:

• Providing the Service: creating your account, maintaining your session and keeping your projects available.
• Film production: running your script, story or idea through the AI production pipeline to generate scene images, video clips, dialogue voice-over, music and sound effects, and preparing the full-film MP4 output.
• Personalization: keeping the content you create consistent with your character, location and style preferences.
• Voice changer (STS): only with your explicit consent, recasting the voice you record into the character voice you select.
• Voice-consent records: keeping a durable record of the permission behind a cloned voice, so that it can be evidenced to a client, a broadcaster or a festival, and so that a complaint about an unauthorised voice can be investigated.
• Billing: managing subscription and token purchases, metering spend and issuing your invoices.
• Security and abuse prevention: enforcing quotas and blocking misuse and account-takeover attempts.
• Service improvement: debugging and aggregate (non-personalized) performance analysis.
• Legal obligations: records that must be kept under tax, commercial and other legislation.
• Communication: responding to support requests and sending mandatory service notices (renewal, security, contract changes).
• Marketing (only with explicit consent): product updates and campaign announcements; you may opt out at any time.

U.S. state privacy law does not require a legal basis for each purpose the way the GDPR does — it asks instead that a purpose be disclosed and not exceeded, which the table below does for every reader. The bracketed articles are the GDPR bases, for users in the EEA and the UK.

To provide the Service your information is shared with a limited number of contractually bound processors, named in full below. A data processing agreement is in place with each of them, and none of them may use what we send for their own purposes. For transfers out of the EEA, the UK or Switzerland into the United States we rely on the European Commission’s Standard Contractual Clauses and, where the provider is certified, on the EU–U.S. Data Privacy Framework and its UK and Swiss extensions.

We never sell, rent or trade your personal data for advertising purposes. Sharing takes place only with the processors listed above and only to the extent needed to provide the Service. Where the competent authorities make a duly issued written request, sharing may be carried out limited strictly to the scope of that request.

runime does not use your prompts, uploads or generated output to train AI models. The model providers above are a separate matter and we do not generalise about them: most of them contractually exclude API inputs from training under their enterprise terms, and at least one reserves the right to train on inputs and outputs. Which provider does what is named individually on our Trust page.

We retain your personal data only for as long as necessary for the purpose of processing. Once the statutory retention periods (e.g. invoice records) expire, the data is deleted or anonymized.

How that is honoured, concretely. Deleting a film hides it immediately and erases every byte of it within 24 hours — the stills, the video takes, the dialogue, the music, the 3D models, the exported master and its subtitles. Closing your account does the same to every film you own, cancels your subscription and removes the account itself. Neither needs a request and neither is done by hand: an automated pass runs every hour and takes whatever has come due. A record that the erasure happened is kept — what, whose, asked when, finished when — with no content in it, because being able to show that we deleted something is part of having deleted it.

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

Two things deliberately survive a deletion, and you should know why. Billing records are kept for 7 years because tax law requires records that support a filed return — note that the authoritative transaction records are held by Stripe as Merchant of Record, not by us; ours is an internal token ledger, and that goes when your account does. Voice-consent records are kept because they are the evidence that a real person permitted a voice to be cloned: deleting the film must not delete the proof that making it was allowed. Neither of these contains your screenplay or your footage.

We take technical and organisational measures appropriate to the risk. Concretely, and checkably:

• All connections are end-to-end encrypted with TLS 1.2+.
• Authentication is managed by Firebase Authentication; we do not store passwords, and sign-in happens through Google.
• Only the server-side service account accesses the database; the client cannot access data directly.
• Abuse-sensitive endpoints are rate-limited per IP address, and that address is not stored in our database.
• Payment card data never reaches our systems; Stripe is PCI-DSS Level 1 compliant.
• Regular vulnerability scanning is carried out on third-party dependencies.
• If we discover a breach of personal data we notify the people affected without undue delay, and any regulator entitled to notice — under the GDPR that is a supervisory authority within 72 hours, and in the United States it is whatever each applicable state breach-notification statute requires.

Which of these you can enforce depends on where you live, but we extend all of them to everyone — running two standards of care would mean deciding which customers deserve the lesser one, and there is no version of that we would want to explain.

1. Know and access. What we hold about you, where it came from, why we have it, and who we have shared it with.
2. Correct. Fix anything inaccurate or incomplete.
3. Delete. Erase your films and your account. You do not have to ask — both are self-serve, and both complete within 24 hours (see “Retention”). We keep only what the law obliges us to, and the retention table says exactly what that is.
4. Take it with you. A copy of what you gave us, in a portable format. Your films can also be exported from the product itself at any time.
5. Opt out of sale, sharing and targeted advertising. There is nothing to opt out of: we do not sell your personal information, and we do not share it for cross-context behavioural advertising — not in the plain sense of those words and not in the broader sense the California statute gives them. We run no advertising and we have no advertising partners.
6. Limit the use of sensitive information. The only sensitive category we handle is a voice recording you deliberately upload, used only to produce the take you asked for and never to identify you.
7. Not be discriminated against for exercising any of this. The Service works the same, and costs the same, either way.
8. Object, restrict, and withdraw consent (GDPR arts. 18, 21, 7(3)). Withdrawal stops future processing; it does not unmake what was lawfully done before.
9. Not be subject to a decision made solely by a machine that has a legal or similarly significant effect on you (GDPR art. 22). We make no such decisions: the models here generate film, they do not judge people.
10. Appeal a refusal. If we decline a request you may ask us to reconsider, and we will answer in writing with our reasons.

An authorised agent may make a request for you where state law allows it; we will ask for proof of their authority and, separately, for confirmation from you.

Requests are free and we answer within 30 days. Where a statute allows an extension for a complex request we will tell you before taking it, not afterwards.

• Email (fastest): support@runime.com
• Post: IS.TEAM LLC, 8 The Green, Ste A, Dover, DE 19901

Write from the address your account uses, and say plainly what you want. We may ask one further question to confirm it is you — handing someone else’s films to the wrong person is the failure this step exists to prevent.

If we get it wrong: in the EEA, the UK or Switzerland you may complain to your local supervisory authority. In the United States you may complain to your state Attorney General — in California, also to the California Privacy Protection Agency. You do not need our permission and you do not have to come to us first, though we would rather you did, because we can actually fix it.

runime does not provide the Service to users under the age of 13. Users under 18 may use the Service only with the knowledge and supervision of a parent or legal guardian; this supervision is also required for paid subscription and token purchases.

If we detect data belonging to a user under the age of 13, the relevant account is closed immediately and the data is deleted. If you wish to delete an account belonging to your child, you can reach us at support@runime.com.

California, and by now many other states, give residents a statutory set of privacy rights. They are listed under “Your rights” above and we honour them for everyone, wherever they live. This section adds the disclosures those statutes ask for specifically.

• Categories collected, and why. Identifiers (your name, email and account id), commercial information (what you bought and what it cost you), internet activity (how the product is used, for reliability and abuse prevention), audio and visual information (the films you make and any voice recording you upload), and sensitive personal information limited to that voice recording. Every category, its purpose and its source is set out in the sections above.
• We do not sell your personal information and we do not share it for cross-context behavioural advertising, as those terms are defined in the California statute. We have not done so in the preceding twelve months. There is no “Do Not Sell or Share” link on this site because there is nothing behind it — we run no advertising.
• We do not knowingly sell or share the information of anyone under 16, and the Service is not offered to under-13s at all.
• Sensitive information is not used to infer characteristics about you. A voice recording is used to produce the take you asked for, and for nothing else.
• Automated decisions and profiling. The Service generates film automatically, but it makes no decision that produces a legal or similarly significant effect on any person, so it is not profiling in the sense these statutes regulate.
• Global Privacy Control. We respect an opt-out preference signal your browser sends. Since we neither sell nor share, there is nothing for it to switch off; it is honoured regardless.

California residents may also ask for the specific pieces of information we hold, and the categories of third party we disclosed them to, for the preceding twelve months. Use the request channel above.

The GDPR, the UK GDPR and the Swiss FADP apply to you because of where you are, not where we are. They apply to us in full.

• Your data goes to the United States. We are a U.S. company and the Service runs there. For those transfers we rely on the European Commission’s Standard Contractual Clauses with each processor, and on the EU–U.S. Data Privacy Framework (and its UK and Swiss extensions) where a provider is certified under it. The processor list above names every recipient and the region it holds data in, so you can verify this rather than take our word for it.
• Rights under articles 15–22 — access, rectification, erasure, restriction, portability, objection, and withdrawal of consent — are listed above and exercised through the same channel.
• Article 22. Producing a film is a fully automated process, but it does not produce a decision with legal or similarly significant effects on you, so it is not a decision based solely on automated processing in the article’s sense.
• Article 9. A voice recording you upload is biometric data. It is processed on your explicit consent alone, for the single purpose you gave it for, and withdrawing that consent stops it.
• Complaints. You may complain to the supervisory authority where you live or work, without going through us first.

We have not appointed an Article 27 representative in the Union or the UK. If your volume of use makes one necessary for you, tell us and we will address it rather than leave the question open.

We may update this policy from time to time due to changes in legislation or updates within the scope of the Service. We announce material changes by email or inside the Service before they take effect; for minor text and formatting corrections you can rely on the “Last updated” date at the top of this page.

If you do not wish to accept the policy, you retain the right to stop using the Service and to ask us to close your account. For questions, requests or feedback, and to read the consent text you agreed to, see the consent notice or email support@runime.com.