Terms

• Your scenes, assets and renders are yours. We render them and hand them back, and we never train on them.
• Every render is quoted before it starts and never charged above the maximum you accepted. Failed renders and cache hits cost nothing.
• Payments are final and are not refunded. In return, deposited credit never expires. Plan credit resets each month.
• You can cancel a plan or delete the account, with everything in it, at any time from the dashboard. There is no process to go through.
• The service is provided as it is, with no uptime guarantee outside an Enterprise agreement, and our liability is capped at the lesser of what you paid us in the last six months and USD 100.

Bakery3 is a sub-brand of Oeave, the trade name under which Bjørn Fjellstad Indahl sells software, and is owned and operated by that same business. Bakery3 is offered as its own product with its own plans, prices and terms: these terms, not the ones at oeave.com, govern it, nothing bought for another Oeave product applies to Bakery3, and Bakery3 credit cannot be spent anywhere else. Payments are taken through Paddle, which acts as Merchant of Record and reseller on the Oeave Paddle account, so the checkout, your receipts and your card statement may name Paddle or Oeave rather than Bakery3. Paddle’s own terms apply to the payment itself; these terms apply to the service.

• Bakery3 is for businesses and professional use. You must be at least 18 and able to enter into a contract on behalf of the account holder.
• You are responsible for what is done with your API keys and browser tokens, and for keeping keys out of client-side code. A key can be revoked at any time from the dashboard; a lost key can only be replaced. See Auth for how tokens are scoped.
• A team lets other people act as your account. The owner’s account is the one that holds the balance, the plan and the ledger, and the owner is responsible for what members do with it.
• Give us accurate billing details. Paddle uses them to work out and remit VAT.

Bakery3 takes a scene described with three.js, traces it on our GPU workers and returns an image, a clip or a set of lightmaps. What we promise is fidelity to the scene you sent, and where a material or a feature cannot be reproduced faithfully the SDK says so before the render is charged, with the object, the reason and the fix. The compatibility report, the estimate and the result are the deliverable; we do not promise that a render will match any other renderer, or that a scene that passes check() today will pass unchanged after a translator update. We may change the renderer, its settings and the worker hardware as long as the documented quality presets keep their meaning.

• You own it. Scenes, assets, manifests and the renders made from them belong to you or to whoever licensed them to you. You grant us only what is needed to store them, render them and return the result to you and your users, for as long as they are in your account.
• We do not train on it. Nothing you upload or render is used to train any model or shown to anyone else. We improve the translator and the cost estimator from compatibility reports, failure records and measured render times, never from your assets.
• You have the rights to it. You are responsible for having the right to upload every model, texture and HDRI you send, and for what your own users send under a browser token you minted.
• It is private and it leaves when you say so. Results are deleted when the project’s retention window ends; any render, and the whole account, can be deleted at once. The Privacy page lists what is kept, where and for how long.

Rendering is paid for from a balance you deposit, or from the credit a plan includes. The current prices are on the Pricing page and are stated before VAT; Paddle adds VAT where it applies, so a deposit is always credited in full.

• Estimate, maximum, actual. Every render is estimated before it starts. The actual charge is measured GPU time at the published rate and is capped at the maximum shown in the estimate. A scene that turns out slower than predicted is our cost, not yours.
• Failed renders are not billed. Neither are cache hits: an unchanged scene rendered again costs nothing.
• Deposited credit never expires and is spent only on rendering. It is forfeited only if you delete the account, so spend it first.
• Plan credit is an allowance included in a plan. It resets on each renewal, does not roll over, is spent before the deposited balance and ends when the plan ends.
• The signup credit is a one-time grant of a small amount to a new account so the first render is free. It is one per person or business; accounts created to collect it more than once may be closed and the grant reclaimed.
• Budgets are yours to set. A project’s monthly budget and an account’s spend limit stop renders from being admitted past them; they are a ceiling on what you are charged, not a promise that a render below them will be accepted.

Refund policy

Deposits and plan fees are final and are not refunded. A deposit is not refunded in whole or in part, and a plan fee is not refunded for a part of a month; cancelling stops the next charge. In return, deposited credit never expires. The only exceptions are the ones Paddle’s buyer terms and mandatory law give you: a consumer in the EU, EEA or UK may withdraw within 14 days of a purchase unless they have started using it, and a render started against a deposit is that use. Because Paddle is the Merchant of Record, a refund request goes through Paddle; a refund Paddle grants under its own policy is Paddle’s decision, and any credit it covered is removed from the account. To ask, write to hello@bakery3.com.

A plan is a monthly commitment that buys throughput on top of the same service: how many renders may run at once, priority in the queue and an included credit allowance. Every plan and pay-as-you-go get the same renderer, the same quality and the same API. A render past the concurrency limit waits in the queue rather than being refused. Plans renew monthly through Paddle until cancelled; you can change or cancel from the billing page and the change applies from the next renewal, or at once when you delete the account. We will tell account holders by email at least 30 days before a plan’s price or included credit changes.

• Upload or render content you have no right to, or content that is unlawful where you or we are.
• Probe, overload or interfere with the service, the workers or another customer’s account, or try to recover the bytes of anyone else’s assets.
• Create accounts to collect the signup credit repeatedly, or share one key across unrelated businesses to avoid a plan.
• Use the service to build a competing rendering service by systematically extracting its outputs or behavior.

Reselling renders as part of your own product or client work is expected and welcome; that is what browser tokens, per-project budgets and usage exports are for.

We run the service with care but without an uptime guarantee. Workers are shared, cold starts happen, and a render may wait in the queue or fail for reasons on our side; when it fails you are not charged, and the failure record tells you why. An Enterprise agreement can add a service level and reserved capacity in writing. Support is by email at hello@bakery3.com, from the people who build the product, and incidents that affect your renders are reported honestly.

The service is provided “as is” and “as available”, and to the fullest extent the law allows we make no warranty of any kind, express or implied, including of merchantability, fitness for a particular purpose, uninterrupted operation or that a render will be free of errors. Renders are computed from the scene you sent, and you are responsible for reviewing them before you publish them. If a render fails or is not delivered, your sole remedy is that it is not charged.

To the fullest extent the law allows, we are not liable to you for any loss arising out of or in connection with the service, however caused. Where liability cannot be excluded, our total liability to you for all claims together is limited to the lesser of the amount you paid us in the six months before the first claim arose and USD 100, and we are never liable for indirect or consequential loss, lost profit, lost business, lost data or the cost of substitute services. These limits do not apply to liability for intent or gross negligence, for death or personal injury caused by our negligence, or for anything mandatory law does not allow to be limited. If any part of these terms is found unenforceable, the rest stands and that part applies to the widest extent the law permits.

• By you: cancel a plan from the billing page or delete the account from Settings, at any time. Keys, tokens and sessions stop working at once and every asset, render and record is purged in the background. Any remaining balance is forfeited when the account is deleted; it does not expire, so spend it first.
• By us: we may suspend or close an account that breaks section 7 or fails to pay, and will say why. If we close an account for any other reason, or stop offering the service, we will give at least 30 days’ notice by email to spend what is left, and return whatever deposited balance remains unspent at the end of it. That is the one case in which a deposit is returned.

We may update these terms as the service changes. The effective date at the top says when it last happened. A change that reduces what you get, raises a price or narrows a promise on this page will be announced to account holders by email at least 30 days before it takes effect; continuing to use the service after that date is acceptance of the new terms.

These terms are governed by Norwegian law. Disputes are heard by the courts of Norway, with Oslo District Court (Oslo tingrett) as the agreed venue, unless mandatory law in your country gives you the right to another. Write to us first; almost everything is settled by email.

For anything about these terms, write to hello@bakery3.com. The Privacy page covers what we collect and keep.