Terms of Service

1. Who we are, and what these terms cover

RenderDay is a cloud rendering service for Blender files. It is operated by Sascha Schwabbauer, a sole proprietorship based in Bochum, Germany, with the postal address c/o POSTFLEX PFX-318-277, Emsdettener Straße 10, 48268 Greven. "We" and "us" in this document mean that business. The VAT number and the rest of the statutory details are in the imprint.

These terms govern every render job you place. They become a contract between you and us when you pay for a job, and the version in force at that moment is the version that governs it.

Read the privacy policy too. It is not part of this contract, but it explains what we do with your personal data and, importantly, where in the world it is processed.

2. Who can use RenderDay

You need to be 18 or older, or the age of majority where you live.

You need a working email address. Everything about a job goes there: the price, the confirmation, the notice that your frames are ready. Give us an address you actually read. Depending on what the job costs us, we may ask you to click a link in a confirmation email before we start.

You can use RenderDay as a consumer or for your business. A few clauses below apply only to business customers, and they say so where they do.

3. How a render job works

1. You upload a .blend file, or a .zip containing the .blend and its assets. The zip is usually the better choice, because everything the scene references travels with it.
2. We open the file and read its settings: frame range, cameras, output format, samples, resolution. We also check for the things that most often ruin a render, such as missing textures, broken linked libraries and unbaked caches, and we show you what we found. This step is free.
3. You choose what to render: camera, frame range, resolution, sample count, Blender version, output format. You give us your email address here.
4. We render test frames of your actual scene on our GPUs and measure how long they take. From those measurements we calculate a price for the whole job and show it to you next to a frame from your own scene. This step is also free. It usually takes a few minutes and is normally finished within twenty.
5. You pay. The price we showed you is the price you pay. Stripe handles the transaction, and the contract for that job is concluded when your payment succeeds.
6. We render the job, email you when it is done, and you download the results from the website as a ZIP archive.

A price is a quote for one specific job with specific settings. Change the settings and we re-price. Each quote carries a validity period shown on screen; once it lapses you may need a fresh one.

4. Your files stay yours

We claim no ownership of anything you upload or anything that comes out the other end. The .blend file, its assets and the rendered frames are yours.

To run the job you give us permission to store your files, copy them onto rendering machines, render them and hand you the results. That permission covers nothing else, and it lasts as long as we hold the files (section 9).

We do not show your files or your renders to anyone. We do not publish them, we do not put them in marketing, and we do not use them to train machine-learning models. If we ever want to show something you rendered, we will ask you first. In practice the only person who might open your file is the operator named in section 1, and only to work out why a job failed.

We do measure how your jobs run. Frame times, GPU seconds, scene complexity, the settings you picked, whether the render succeeded: we keep that and use it to price jobs more accurately and schedule them better, including by fitting statistical models to it. It describes the work, not the artwork. No image data, no geometry, no textures, no scene contents.

5. What you may not upload

You promise that you own what you upload or have permission to use everything in it: models, textures, HDRIs, fonts, audio, all of it. We do not vet your files, so we rely on that promise.

Do not upload:

• anything that infringes someone's copyright, trademark or other rights
• illegal content of any kind, and in particular child sexual abuse material, which we report to the authorities
• content that is defamatory, or that invades somebody's privacy
• files carrying malware, or scripts written to attack our systems rather than to render a scene

Do not attack the service either: no working around the rate limits, budget limits or abuse controls in section 10, no scripted traffic beyond what a person could plausibly generate, no probing our infrastructure.

If you break these rules we can stop your jobs, delete your files and refuse you further service. Where we cancel a job you have already paid for, we refund the part we have not performed. We may also claim compensation for damage the breach causes us.

6. Prices, VAT and payment

Every price we show you includes VAT. The number on the quote screen, in the quote email, on the pay button and on your receipt is the same number, and it is what leaves your account. Nothing gets added at the end.

We are registered for VAT under the EU One-Stop-Shop scheme, so the VAT inside the price is the rate of the country you are in. If you are a business in another EU country and give us a valid VAT ID, the reverse charge applies and the tax line goes to zero. Outside the EU no EU VAT applies. In all three cases the total stays exactly what we quoted; only the tax line inside it moves.

Prices are in euros. If your card settles in a different currency, your bank sets the rate and may add a fee. That part is between you and your bank.

Stripe processes the payment. We never see or store your card number. Stripe's own terms and privacy policy apply to the payment itself. We pay Stripe's processing fee out of the quoted price, so you never pay it separately.

After you pay you get an order confirmation by email, repeating the terms of the job on a durable medium as §312f BGB requires. If you need an invoice with your company details on it, ask and we will issue one.

If a payment is reversed or charged back after we have rendered, we may bill you for the work and decline further jobs until it is settled. Email us before you go to your bank. We answer, and a problem we know about is one we can usually fix.

7. Your right of withdrawal

If you are a consumer you have a statutory right to withdraw from a distance contract within 14 days, without giving any reason. The period starts on the day the contract is concluded, which for us is the day your payment succeeds.

To withdraw, tell us clearly that you are withdrawing. The withdrawal page does it in two steps and sends you written confirmation immediately; an email to support@renderday.com is equally enough, and so is a letter to the address in section 1. No particular form of words is required and you do not have to explain yourself. Sending the declaration before the 14 days are up is enough; it does not have to reach us within the period.

If you withdraw, we refund everything you paid, through the same payment method, within 14 days of receiving your declaration. You will not incur any fees for that refund.

If you asked us to start rendering during the withdrawal period and then withdraw part way through, you pay a proportionate amount for what we had already rendered by the time your declaration reached us, measured against the whole job. You do not pay for the rest.

There is a catch, and it is a statutory one. Rendering is a digital service, and under §356 Abs. 5 BGB the withdrawal right ends once we have fully performed, but only if you expressly asked us to start before the 14 days were up and confirmed you understood that doing so would cost you the right. That is what the two checkboxes at the pay button are for. Tick them and let us finish your render, and the right is gone: you asked for the frames now rather than in a fortnight, and you have them. Leave them unticked and we cannot start until the 14 days have passed, because starting would mean burning GPU time on a job you can still cancel.

Withdrawal is a separate thing from the refunds in section 8, and neither takes anything away from your statutory rights.

The full statutory instruction on withdrawal, in its official wording, is on the withdrawal page. Where this summary and that text differ, that text is the one that counts.

8. Refunds

Withdrawal aside, here is when money comes back.

We failed to deliver. The render never completes, our systems break, or we cancel the job: you get all of it back. You should not have to ask. We refund and tell you.

We got it wrong. Corrupt frames, the wrong camera, settings you did not choose: we re-render for free, or refund you if you would rather have the money than the frames.

You got what you asked for and did not like it. That is not a refund. Too few samples, weak lighting, a texture you forgot to pack: we rendered your scene with your settings. Look at the test frame before you pay, and read the preflight report. It exists for precisely this.

Ask within 14 days of delivery, at support@renderday.com, with the job ID and what went wrong. Approved refunds go back through Stripe to the card you paid with. Your bank decides how long that takes to appear.

None of this touches your statutory rights for digital products under §§327 ff. BGB, which run for two years and which we cannot sign away.

9. How long we keep your files

Your uploaded files and your rendered frames stay on our systems for 30 days after you last do anything with the project. Then we delete them.

Download what you need inside that window and keep your own copy. We are a render farm, not a backup service, and once the files are gone we cannot get them back for you.

You can ask us to delete a project sooner and we will. We keep the record of the job after the files go: settings, timings, cost, your email address. Section 4 says what we use it for, and the privacy policy says how long we keep it and what you can do about that.

10. Free analysis, free quotes, and the limits on them

Analysis and pricing cost you nothing, but pricing burns real GPU time on our account. Every quote is a small bill we pay so you can see a real frame and a real number before deciding. That is why there are limits.

We use Cloudflare Turnstile to check that an upload comes from a person. We cap how much free GPU time one visitor can use before their first purchase, and we cap what the free tier spends across everyone in a day. When a cap is reached, free work queues behind paid work rather than failing, and the screen will tell you it is queued rather than pretending it is broken.

We also cap render settings, such as resolution, sample count and frame count, at levels well above any ordinary job. If yours hits one, get in touch and we will look at it.

None of this applies to work you have paid for.

11. What we promise, and what we do not

We promise to render the file you gave us, with the settings you chose, and to deliver the result.

We do not promise the service is always available, that a render finishes by a particular time, or that Blender behaves. Time figures are estimates. We show you what we have actually measured rather than a flattering number, but queues get long and machines die. If you have a deadline, leave yourself room.

We do not promise that every Blender feature, add-on or third-party plugin works on our machines. We support standard Blender. If your scene leans on something unusual, ask before you pay rather than after.

We do not fix your scene. A render is only ever as good as what goes into it.

If part of the service is labelled beta, treat it that way: it can change or disappear.

If you are a consumer, your statutory rights to conformity of digital services under §§327 ff. BGB apply whatever this section says.

12. Our liability

We are liable without limit for damage caused by intent or gross negligence, for injury to life, body or health, under the Produkthaftungsgesetz, and wherever we have given a guarantee.

For slight negligence we are liable only where we breach a duty that the contract exists to perform and that you are entitled to rely on, a so-called Kardinalpflicht, and then only for damage of a kind that was foreseeable and typical when the contract was made.

Beyond that we are not liable.

In particular we are not liable for what your own file does. A scene that renders badly because of how it was built is not our doing. Nor are we liable for your internet connection, for Stripe, or for a bug in Blender.

Business customers only: you indemnify us against third-party claims arising from your content or your breach of these terms, including reasonable legal costs. We will tell you promptly about any such claim and let you run the defence. This paragraph does not apply to consumers, who are liable under the ordinary rules of law and nothing more.

Nothing in these terms limits liability that German law does not permit us to limit.

13. Suspension and termination

You are not subscribed to anything. Each job is its own contract and ends when it is delivered. To stop using RenderDay, stop uploading.

To cancel a job that is already running, email us. If the render has already happened we cannot un-render it, and section 8 governs what comes back.

We can suspend or end your access if you break section 5, if your use threatens the service, or if the law requires it. We will tell you why by email unless we are not permitted to.

If we shut RenderDay down altogether, we finish the jobs that are paid for or refund them.

The clauses that should outlive the contract do: ownership of content (section 4), liability (section 12), and governing law (section 15).

14. Changes to the service and to these terms

We change the service as we go: new hardware, new Blender versions, different prices, features added and taken away. Price changes apply to future jobs and never to one you have already paid for.

When we change these terms we post the new version here with a new date at the top. The terms that govern your job are the ones in force when you paid for it, so a change never reaches backwards into an order you have already placed. If a change materially affects you and we have your email address, we will write to you.

We do not treat your continued use of the site as agreement to new terms. You agree to them by placing your next order under them, and not before.

If one clause here turns out to be invalid, the rest stays in force and the statutory rule takes the place of the invalid clause.

15. Governing law and courts

German law applies. The UN Convention on Contracts for the International Sale of Goods does not.

If you are a consumer living in the EU, that choice does not take away the protection of the mandatory consumer law of the country you live in, and you can bring a claim in the courts where you live.

If you are a business, the courts of Bochum, Germany have exclusive jurisdiction.

We are neither obliged nor willing to take part in dispute resolution before a consumer arbitration board (§36 VSBG). If something has gone wrong, write to us. We would much rather sort it out directly.

16. How to reach us

support@renderday.com

Email is the whole support system. There is no ticket portal, no chatbot and no phone tree, and the person who answers is the person who built the thing.