How we handle your files: security, retention, and confidentiality
How we handle your files: security, retention, and confidentiality
This page covers how your files move onto and off Super Renders Farm, how long we keep them, who can get into your account, and what to do if a project needs a signed confidentiality agreement on top of the defaults below. Studios usually ask because the stakes are concrete, not abstract: an archviz team rendering a residential tower before the developer's press release, or a VFX house delivering a competitive pitch, needs to know exactly what happens to a scene between upload and delivery, not a generic promise that files are "safe."
How your files move
Every file you send us travels one of three ways: the web portal over HTTPS, the desktop Client App, or S3 access with the access key from your account. Which one makes sense depends mostly on size and workflow: the web portal suits a quick upload of a single scene or a small project, and the Client App suits artists who'd rather queue a job and walk away, and large transfers. The general guideline is to move to the Client App once a single upload passes roughly 300 GB, since it handles large transfers more reliably than a browser upload; see upload formats and size limits for the full breakdown.
All three paths are digital-only. Super Renders Farm doesn't receive or ship physical media of any kind, no drives couriered in, no drives shipped back out, so there's no physical hand-off step anywhere between your machine and ours: everything that reaches the farm arrives as an upload, and everything that leaves does so as a download.
How long your files stay on the farm
Files stay available for as long as needed to run your jobs and let you download your results; there is no fixed automatic deletion period. When you want a project gone, ask us and we delete its scenes and output. Deletion on request can't be reversed, not by you, and not by our support team.
The upside for a project that matters: you decide when a copy stops existing on our side. An unreleased design or a pitch deck under wraps doesn't have to stay on a server past the point you needed it there: download it to your own storage, then ask us to delete the project. See downloading your renders and how long we keep your files for your download options.
Who can access your account
Your account has a single login, and there's no separate multi-user or team-seat feature today. If a studio needs several people working under one shared billing account, contact support to talk through options, sharing a single login across a team isn't something we recommend, since it makes it hard to know who did what if something ever needs to be traced back. Two-factor authentication isn't currently supported, so the strongest thing you can do on your side is a strong, unique password, ideally kept in a password manager, and never sharing your credentials, even internally, even with a trusted teammate covering for you for a day.
Confidential projects: NDA and BYOC
What's described above, how files move, deletion on request, single-login accounts, is what every studio gets without asking. Some projects need more: an unreleased development that can't be shown publicly yet, a competitive pitch that can't reach a client's other bidders, or a contract that requires a signed confidentiality agreement with every vendor who touches the files. For those, we can put a Non-Disclosure Agreement in place on request, see working under NDA: rendering confidential projects for how that works, or start directly from the render farm NDA page.
Because the farm is fully managed, you're also not remoting into shared machines, installing software, or managing render-engine licenses yourself to get a job done, your scene goes in, and your output comes back to your account. For studios where even that arrangement isn't enough, where the requirement is holding your own cloud storage credentials for the entire engagement instead of using the upload paths above, our guide to customer-owned credentials in cloud rendering (BYOC) covers that dedicated model. For broader policy questions, privacy, refunds, terms, see legal and policies.
Related
- Downloading your renders and how long we keep your files — how long files stay available, and download options.
- Upload formats and size limits — why uploads go in unpacked, the 300 GB guideline, and transfer methods.
- Working under NDA: rendering confidential projects — the NDA process in detail.
- Legal and policies — privacy, refunds, and terms.
- Still have questions? Reach out via 24/7 live chat at knowledge.superrendersfarm.com, or email supportcenter@superrendersfarm.com.
FAQ
Q: How long do you keep my files? A: Render output and the scenes you upload stay available as long as needed to run your jobs and let you download your results; there is no fixed automatic deletion period. Ask us and we delete a project's files; that deletion can't be reversed. See downloading your renders and how long we keep your files for download options.
Q: Can you sign an NDA before I upload? A: Yes. A Non-Disclosure Agreement can be put in place on request, before you send us anything. See working under NDA: rendering confidential projects or the render farm NDA page for how to start that process.
Q: Does anyone else see my project files? A: Rendering on the farm is a fully managed, automated pipeline: you upload your scene, it renders, and the output comes back to your account, with no step where you need to remote into shared machines yourself. When you want a project's files removed, ask us and we delete them. If a project needs a formal confidentiality commitment on top of that, an NDA is available on request (see above).