Skip to main content

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 SFTP for very large transfers. 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, the Client App suits artists who'd rather queue a job and walk away, and SFTP suits scripted or pipeline-driven transfers. The general guideline is to move to SFTP or the Client App once a single upload passes roughly 300 GB, both handle large transfers more reliably than a browser upload, see upload formats and size limits for archive formats and the full breakdown.

Every one of those three paths is 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

Short retention isn't just tidiness, it's a confidentiality feature. Render output, the frames and files you're actually paying for, stays on our storage for 45 days after the job completes. The scene and input files you uploaded to make that render happen are cleared sooner: 14 days after completion. Both windows close automatically. Once a file passes its window, it's deleted for good, and that can't be reversed, not by you, and not by our support team.

The upside for a project that matters: your files don't sit on our storage indefinitely waiting to be forgotten about. An unreleased design or a pitch deck under wraps doesn't linger as a copy on a server past the point you needed it there. It either leaves under your control, downloaded to your own storage, or it's gone automatically. See downloading your renders and how long we keep your files for the full breakdown of both windows and 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.

Cloud import: one direction only

If you connect Google Drive or Dropbox, both integrations are import-only: we pull files in from your cloud account, but nothing renders back out to them automatically. That's a deliberate boundary, not a missing feature. It means a Drive or Dropbox connection you set up for uploading can't quietly become a second copy of your output sitting in a cloud account you didn't plan for, or one that's shared more widely than the render job itself. Delivery only happens through the web portal, SFTP, or Client App auto-download described above; if your workflow needs finished output back in a Drive or Dropbox folder, that's a manual move (or a Client-App-automated one) after download, not a direct sync.

Confidential projects: NDA and BYOC

What's described above, how files move, the short retention windows, 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

FAQ

Q: How long do you keep my files? A: Render output, your finished frames and files, stays on our storage for 45 days after the job completes. Uploaded scenes and input files are cleared sooner: 14 days after completion. Both windows close automatically, and once a file is past its window it's deleted for good, support can't recover it. See downloading your renders and how long we keep your files for the full breakdown.

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. Files also don't stay around indefinitely, output is deleted 45 days after job completion and scene files 14 days after, both automatically and irreversibly. If a project needs a formal confidentiality commitment on top of that, an NDA is available on request (see above).

Last updated: July 10, 2026