Acceptable use policy
Last updated 13 September 2026
People
Do not use Cralio to put words in a real person’s mouth without their agreement, to impersonate anyone, or to produce material that is illegal where you are. We will freeze an account being used that way: it can no longer submit work.
Named, so there is no argument about what was meant: no political content presented as the words of someone who did not say them, no endorsement a person did not give, no material depicting a real person in a sexual or degrading way, no voice or face of a child, and nothing designed to make an authority, a bank or a family member believe a message came from someone it did not. Whether you thought it was satire is not the test.
No face or voice of anyone under 18, in any mode, for any reason. This is not a judgement call and there is no exception for your own child.
Material You Do Not Own
Do not upload content you are not entitled to have processed: copyrighted footage, music, fonts or artwork you have no licence for, or the likeness of a person without the consent Terms §3 and the biometric notice require. Before the first thing you send from the upload, statics, music or generation page you confirm you hold those rights — on the sign-up form, on the invitation screen, or on that page itself — and that confirmation names fonts along with everything else and covers every job after it. Until it is recorded, all four of those doors refuse, with nothing charged. A job you already submitted is not caught by that: re-rendering it, refining it, running a deep-QA pass over it or drawing a visualiser from it runs on the confirmation you gave when you sent it, and is charged as usual. A font also carries its own confirmation at the moment you upload it, recorded against that file, because “you agreed once” is not an answer about a specific font licence.
Labelling What You Publish
You must not present the output as unedited footage of a real person where that would mislead. The EU AI Act and the platforms you publish on require, in various circumstances, that synthetic or altered media be labelled as such. What labelling your content needs, in the places you publish it, is your obligation and yours alone — ours ends at the machine-readable marks we put in the file.
The Service Itself
Also prohibited:
- reverse engineering, decompiling or attempting to derive the source of any part of Cralio, or probing its infrastructure or a provider’s;
- scraping, crawling or automated access other than through an interface we publish — the app, and the few requests these documents tell you to make, such as the account-deletion request in the privacy policy and the second opinion on a creative sold through a request rather than a screen in the service terms; there is no public API or webhook product today — and any automation designed to disguise or multiply how much of the service one account is using;
- circumventing a limit, a plan gate, a provider’s refusal or a rate limit;
- uploading malware or anything designed to harm our systems or a provider’s;
- using the service to build, benchmark or train a competing product, or to extract data about a provider’s model;
- reselling Cralio as your own localization service;
- sharing an account between businesses, or opening more than one account to claim a free allowance twice.
Child Sexual Abuse Material
Uploading material that sexually exploits a child is prohibited absolutely, and it is the one thing on this page where we do not weigh anything up.
What happens when we learn of it. The account stops immediately — it cannot submit work, and that takes effect before any credit is spent and before any provider is touched. The material is preserved rather than deleted, which runs against every retention promise on this site and is deliberate: it is copied somewhere no deletion sweep and no storage rule reaches, so it survives the retention window, the account being closed, and the customer deleting the job themselves. We report it to the National Center for Missing and Exploited Children, as United States law requires of us, and we keep the material for at least the ninety days that law then requires.
The stop is not only at submission. Every action that spends money — a new job, a retry, an admin retry, a caption edit, a re-render, a second opinion on a creative — asks the same question before anything is bought, so re-running something already started buys nothing. The one gap in that is ours rather than yours: if the incident table cannot be read at all we let the work through rather than stop every account submitting, and that failure is raised at once as a critical alert so a person catches what slipped. What still works is reading: you can see your own history and your own account, because an account that goes blank teaches its owner to open another one. A frozen account also cannot be erased, and that is true of every freeze rather than only this one — the rule is in What we do about it below. The preserved copy sits outside it in any case: no erasure reaches that copy, and lifting the stop does not release it.
We do not scan what you upload for it. Automatic detection means matching against a database of known material, held by organisations that grant access to it; we do not have that access, so we do not have that detection, and we would rather write that down than let the paragraph above imply otherwise. What we act on is what we are told, what a provider refuses, and what any of us sees. That we did not find something does not mean it was permitted, and nothing here is an invitation to try.
What Our Providers Refuse
Our providers’ rules reach you through us. The companies on the subprocessors page that receive your material — the ones that store it, that read and repaint a creative, that make a track or a clip out of your prompt and the stills you attach, that dub and lip-sync a video, that recut one to another shape, that transcribe its audio — publish their own terms and prohibited-use policies, and we are bound by them for every call we make on your behalf. So they bind what you may submit: material a provider refuses is material we cannot process, and a job refused upstream is a job that fails. Where a provider’s rule is stricter than this policy, the stricter one is the one that decides.
The same is true of our payment processor, whose restricted-business list reaches you the same way. An account whose work we cannot bank is an account we cannot serve.
Enforcement
We may refuse any job and suspend any account immediately, and we may end an account, where we reasonably believe this policy has been breached, where a provider has refused or complained, where a third party has complained credibly, or where the law requires it. We may do so without notice where notice would be impractical or where the breach is serious. Taking a file down is the uploader’s own button rather than ours: what we can do without them is freeze the account, so no further work is bought, and require them to press it.
A frozen account cannot be deleted. While a case against an account is open — for this policy, for a court order, for a rights holder’s preservation demand, for anything at all — a request to erase it is refused. That is the one place where deleting somebody’s data is the wrong answer. Nothing here distinguishes one kind of case from another: the same open case that stops the account buying work stops it being deleted, and closing the case makes it deletable again. We do not explain the refusal at the time; what you are told is that the account is under review and to write to us.
We do not review what you upload looking for problems, and nothing here obliges us to. That we did not catch something does not mean it was permitted.
How to tell us. Write to info@cralio.app. Say enough for us to find the file: where you saw it, what is in it, and anything on it that identifies the account or the job. It is the same address that takes copyright notices and counter-notices under Terms §14, it is a mailbox that receives rather than a no-reply, and it is where a report about material involving a child goes. If what you are reporting is your own face or voice in something somebody else made, say so — the biometric notice explains what we can do directly and what only the person who uploaded it can answer.
Changes to This Policy
We may update this policy without the thirty days’ notice that Terms §16 gives for other changes, where the change narrows what is allowed for safety or legal reasons. A change that widens what is allowed, or that adds an obligation on you beyond safety, takes effect no sooner than 30 days after the date at the top of this page changes.
That date changes when the page does. This policy is not in the version archive that holds the terms of service and the privacy policy — the two documents Terms §3 asks you to accept — so if you need the wording as it stood on a particular day, ask us and we will produce it from our own source history.