Data policy

Uploads go straight from your browser to private object storage over a signed, one-time link — they never pass through a public bucket or a shared folder. Nobody else on the farm can browse, list, or open your files. There is no public gallery of anyone's scenes.

To actually render a frame, your .blend file is downloaded onto a GPU provisioned for that job, rendered, and the output is uploaded back to your private storage. The copy on that GPU is removed once the box is done with it — it isn't kept around by us or by our infrastructure partner after the job finishes.

We don't open, inspect, or use the contents of your scene for anything beyond running the render you asked for and reading the technical scene data needed to run it correctly (frame range, cameras, render engine, and similar settings).

Members of our team can look up account and job records to help with a support request, billing issue, or to investigate abuse of the service. This isn't routine browsing of user files, and it isn't used for anything beyond resolving the issue at hand.

Deleting a file or a render removes the underlying data from storage, not just the listing. There's no separate step, no grace period, and no way for us to bring it back once you've deleted it — so keep your own copy of anything you can't afford to lose.

One exception: your billing history (what you were charged, for which filename, and when) stays on your account after the file itself is deleted, the same way a receipt outlives the thing you bought. It never includes the actual render data.

Your uploads and renders aren't sold, used for training, or handed to anyone outside of what it takes to run the render itself (our infrastructure partner, for the duration of that job) and to process payment for your account (our payments provider, for billing records only — it never sees your files).