BlitzRenderSign in

BlitzRender Acceptable Use Policy

Version 2026-10-28. Part of the BlitzRender Service Terms. Supersedes 2026-10-27: we report content that suggests a threat to somebody's life or safety to the police (section 4), and you may take a decision of ours to the courts (section 5).

Your scene runs on a machine we rent by the hour from an independent host, and we are responsible to that host, to our other customers and to the law for what runs there. This policy says what you may not upload or render, what we do about it, and how to reach us if we got it wrong.

Whose policy this is. This policy is issued by BlitzRender, the trade name of Noelia Caba Martín, sole trader, of Plaza del Sol 4, 18620 Alhendín, Granada, Spain. You can reach us at support@blitzrender.com.

1. Content you may not render

You may not upload or render:

  • content that is unlawful where you are or where we are, including any sexual depiction of a minor, content that incites violence, or content whose possession is itself an offence;
  • content you do not have the right to use — somebody else's models, textures or footage included without permission, or a client's work you are not authorised to render;
  • anything designed to harm the machine that renders it, the people who operate it, or anybody who opens the output;
  • content that is racist, hateful, abusive or discriminatory, that defames somebody, or that is obscene.

Why the last item is there. The machines are rented from a marketplace whose own terms do not allow that content on them, and those terms bind every job we run, wherever you are and whatever your local law permits. It is their rule passed on, not a judgement we are making about your work.

We do not inspect your scenes for any of this. We rely on you, and we act when it is reported to us or when the automated scan described below finds it.

To report content, write to support@blitzrender.com, in English or Spanish — it is our single point of contact for anybody, and for the authorities of any EU member state. Say why you believe the content is illegal or breaks this policy, give the job reference or the link that identifies it, your name and email address, and that you believe in good faith that your report is accurate and complete. We confirm that we received it, decide without undue delay, and tell you what we decided and how to contest it.

2. Things you may not do with the service

  • Embed a script meant to execute. Blender can carry Python in a file. On our machines it never runs, and a file that tries — a script set to run automatically when the file opens, or a driver expression carrying code (our scan reports these as auto_run_script and driver_namespace_payload) — is refused before it renders. Ordinary driver expressions used for rigging are fine and are reported at a lower severity.
  • Reach out from a render. The process that opens your scene has no network access, and the machine holds only a credential for your one job, which expires with it. Attempting to reach anything, read anything on the machine that is not your scene, or use the credential for anything but your job's own storage is a breach.
  • Use the card for anything but rendering. Mining, general-purpose computation dressed as a scene, or a scene whose purpose is to occupy hardware rather than produce frames.
  • Render for a restricted end use. Work for the design, development, production or use of nuclear, chemical or biological weapons or missiles, or for a military end use or end user that export-control law restricts — military end uses in China or Russia among them.
  • Use the service from or for a sanctioned place or person. The Service Terms (section 2) say who that is: somebody in a country or region under comprehensive sanctions, named on a sanctions list, or owned or controlled by somebody who is. Letting such a person use your account, or rendering on their behalf, is the same breach.
  • Get around the limits. A scene may be up to 2 GiB and a job up to 20,000 frames; accounts have bounds on jobs in flight and uploads per day. Splitting one workload across several accounts to get past a bound, or asking for accounts under other people's names, is a breach.
  • Probe us. Testing our systems for weaknesses is welcome only when we have agreed to it in writing beforehand. Otherwise it is a breach, whatever you find.
  • Abuse the payment rails. Paying with an instrument that is not yours, disputing a payment for work that was delivered, or using top-ups and refunds to move money rather than to render.
  • Game the referral programme. Attributing your own accounts to your own referral code, directly or through a ring of accounts, or referring accounts that exist only to be referred.

3. What we do

  • Every scene is scanned before it runs. The scan looks for embedded scripts, drivers that carry code, and references outside the file. Only findings rated low or medium pass. Anything else refuses the job, releases your reservation, and tells you what kind of finding it was.
  • Scripts never execute, whatever the scan finds — the scan is a second line, not the first.
  • Renders run isolated. The process that opens your scene cannot reach the network, there is one job per machine, the machine holds a credential for that job only, and it is destroyed when the job ends.
  • A person may look at a refusal. If a refused scene looks like a false positive — a rig with ordinary drivers is the usual case — a person can review the scan's findings and let the job through. We look at the findings, not at your scene.

4. What happens if this policy is breached

Depending on what happened, we may refuse the job, park it for a person to look at, suspend your account, or close it. Where the law requires us to report something, we report it — and where content suggests a criminal offence that threatens somebody's life or safety, we tell the police or the judicial authorities at once, with what we know. The marketplace we rent from can also act on its own rules, and may stop providing machines for work that breaks them. Unused credit on a closed account is handled under the Service Terms.

We will tell you what we did, the facts and grounds it rests on, whether it was decided automatically, and how to ask us to look again, unless the law prevents it. We will not describe our anti-abuse checks in detail, because describing them would help somebody route around them.

5. If we got it wrong

Write to us at support@blitzrender.com with the job reference. A refusal at intake is the scan's judgement and can be reviewed; a suspension is ours and can be appealed the same way. Asking us is not the only way: you may also take any decision of ours to the courts.

6. Changes

If this policy changes we will publish a new version with a new date, and you will be asked to accept it with the Service Terms before your next job or top-up.

BlitzRender · acceptable use policy · version 2026-10-28

Version 2026-10-28 · SHA-256 b1cfed8a7a990974… · All legal documents