Legal and policies at Super Renders Farm

This page consolidates the legal and policy information that applies to using Super Renders Farm: how we handle your data, what our refund commitment covers, how we treat the project content you upload, and how to reach us about any legal or privacy question. It is written in plain English so you can read it once, understand what applies to you, and find the right contact path quickly.

A note on scope before we start. This is the consolidated docs-side reference for our policies. It applies per applicable regional law — including but not limited to the General Data Protection Regulation (GDPR) in the European Economic Area, the California Consumer Privacy Act (CCPA) in California, and general data-protection principles in other jurisdictions. The formal is a separate document that covers account use, billing rules, and platform conduct in contractual form; where this docs page and the formal Terms differ, the formal Terms control.

Super Renders Farm operates from 2314 Bonnie Brae, Santa Ana, CA 92706, USA. The current legal entity is a sole proprietorship; an LLC formation is in progress for mid-2026. The transition will be transparent to users — no service interruption and no substantive change to the policies described on this page.

Privacy and data handling

What we collect

We collect information necessary to provide the rendering service:

Account information — email address, name, password (stored as a salted hash, never in plain text), and billing details. Full payment card numbers are handled by our payment processor; we do not store them on our infrastructure.
Project files — the 3D scenes, textures, plugins, and assets you upload for rendering. These are stored on our render infrastructure for the time needed to run your job, plus the retention windows described below.
Job metadata — render configuration (frame range, output format, renderer choice, plugin settings), job timing, error logs, and credit consumption. Retained per the standard schedule.
Usage analytics — aggregate, non-identifying data about how the service is used (number of jobs, average render duration, error patterns) used to operate and improve the platform.
Communication records — support chat messages, email correspondence, and other written communication with our team. Retained for support context and as required by applicable law.

How we use it

We use this information to:

Provide the rendering service — run your jobs, deliver output frames, bill correctly against your credit balance.
Communicate with you about service status, billing events, security notices, and support requests you've opened.
Improve the service — aggregate analytics, identify recurring failure patterns, refine pricing and infrastructure decisions.
Comply with legal obligations — respond to lawful requests from authorities, maintain financial records, enforce the Terms of Service.

We do not sell your personal information. We do not share your account data or project files with third parties except: (a) payment processors that handle billing on our behalf, under their own privacy commitments; (b) infrastructure providers that host portions of our service, under contract; (c) legal authorities where required by valid legal process; (d) parties you explicitly authorize us to share with (e.g., a studio IT team you ask us to coordinate with).

We may collect, store, and process this data per applicable regional law including but not limited to GDPR (EU/EEA/UK/Switzerland) and CCPA (California). The substantive practices described above apply uniformly to all users; specific local-law rights are described in the "Your rights regarding personal information" section below.

Your project content is treated as confidential

The 3D scenes, textures, and assets you upload for rendering are treated as confidential. Our operations team does not browse, open, or access the contents of your project files except as needed to support the rendering process — for example, diagnosing a failed job that you've reported, responding to a support ticket you've opened, or addressing a security incident.

We do not repurpose your project content for any other use. We do not train models on your scenes, share them with other customers, publish frames as samples without your permission, or otherwise treat them as anything other than confidential work product owned by you.

For projects that need formal contractual confidentiality coverage — feature film VFX, unreleased commercial work, regulated-industry projects — we provide a Non-Disclosure Agreement on request. See the NDA section below.

Data retention

Retention windows applied to each category of data:

Account information — retained for the duration of your account, plus a reasonable window after account closure for billing reconciliation and any legal-compliance retention obligations (typically multi-year for tax records).
Project input files — retained on render storage during job processing plus a short post-completion window so re-renders can pull from the same upload. After that window, input project files are removed from the active render storage.
Output frames — retained for 45 days after job completion, then automatically deleted. This retention applies uniformly across all users; it does not vary by plan. We recommend downloading promptly, or configuring the Client App to auto-download finished frames to your local storage.
Job metadata and logs — operational logs are retained per the standard schedule (typically shorter for runtime logs and longer for billing-relevant metadata).
Communication records — retained as needed for ongoing support context and as required by applicable law.

Customer data confidentiality applies per industry-standard render-pipeline practices and applicable local regulation. If a specific retention question matters for your engagement (e.g., a contractual requirement that data be deleted within a defined window after delivery), contact the legal address below so we can confirm in writing.

Cookies and tracking

The website uses cookies — small text files stored on your device — for two purposes:

Strictly necessary cookies keep you logged in, remember your dashboard preferences, and support core flows (top-up, job submit, output download). These cannot be disabled without breaking the service.
Analytics cookies measure aggregate usage so we can improve the service. We use Google Analytics for this purpose, configured to anonymize IP addresses where supported and to avoid sharing identifiable data across services.

You can restrict or block cookies from your browser settings. With analytics cookies disabled, the service continues to work normally. With strictly necessary cookies blocked, you will not be able to sign in.

We do not use cookies for advertising, retargeting, or sale of personal information. Where applicable regional law requires a cookie consent banner (for example, GDPR in the EU/EEA and similar regimes elsewhere), the banner is presented on first visit and your choice is remembered.

Your rights regarding personal information

Depending on your jurisdiction, you have rights regarding the personal information we hold about you. These may include:

Access — request a copy of the information we hold about you.
Correction — ask us to correct inaccurate information.
Deletion — request that we delete your information, subject to legal exceptions (we must retain billing records for tax compliance, and we cannot delete data that is the subject of an active legal hold).
Portability — request your information in a portable, machine-readable format.
Objection or restriction — object to certain processing or ask us to restrict it to defined purposes.
Withdrawal of consent — where we process information based on your consent, you can withdraw consent at any time.

These rights apply per applicable regional law. Users covered by GDPR (the European Economic Area, the United Kingdom, and Switzerland) have explicit rights under GDPR Articles 15–22 and we honor them within 30 days of a verified request. California residents covered by CCPA / CPRA have parallel rights under California Civil Code Section 1798.100 et seq., and we honor them within 45 days of a verified request (extendable to 90 days for complex requests, as the law permits). For users in other jurisdictions, we extend the same substantive rights as a matter of policy, subject to applicable local law — including specific frameworks such as Brazil's LGPD, Canada's PIPEDA, Japan's APPI, and equivalent regimes.

To exercise any of these rights, use the contact paths in the "How to reach us" section at the end of this page. We do not charge a fee for standard requests.

Refund policy

Our refund policy balances customer protection against the operational reality of compute-billed services: once a render machine starts working on your frames, the compute time is consumed whether the result is useful to you or not. The eligibility rules below reflect that.

Eligible for refund

We refund render credits in these circumstances:

Failure attributed to our rendering system. If a job fails because of an issue on our side — a worker crash, a license server outage, a network failure mid-render, or a similar infrastructure event — we refund the credits used by the failed portion of the job once the cause is verified in our logs. Completed frames are not refunded.
Billing-system error. If you were charged for compute that you did not actually use because of a bug in our billing pipeline, we correct the charge and refund the difference.
Unused credit balance, on account closure. If you have an unused credit balance and want to close your account, we can return the unused balance, subject to processing fees from the payment processor and any compliance-driven minimums.

Refunds are processed per applicable consumer-protection law in your jurisdiction. Where local law mandates a specific refund procedure or timeframe for digital services (for example, EU Directive 2011/83/EU on consumer rights for distance contracts, or analogous state-level rules in the United States), we follow that procedure in addition to the practices described here.

Not eligible for refund

User-caused render failures. A scene that fails because of a configuration error, missing assets, an unsupported plugin combination, or an incompatibility in your project file is the user's responsibility. We provide support to help you diagnose and re-submit, but the compute used by the failed render is not refunded.
Quality complaints on completed renders. If a render finishes successfully but the visual result does not match what you expected (wrong color profile, missing detail, noise level higher than anticipated), this is a scene-configuration matter, not a service failure. See for diagnostic guidance; a re-render with corrected settings is billed normally.
Mid-render cancellation of a working job. Once a frame starts rendering, the compute time used is billed. Canceling mid-job saves credits on frames that have not yet started; it does not refund frames that are already in progress.
"Buyer's remorse" on completed work. Standard remorse-based refund requests for renders that completed successfully are outside the policy.

How to request a refund

For any of the eligible circumstances above:

Open a support request with the job ID and a short description of what went wrong.
Attach or reference the relevant logs and error messages from your account dashboard.
Wait for review. Our team checks farm-side logs to confirm the failure cause and the affected frame range.
Refund processed if eligible — typically within 5 business days, returned to the original payment method, subject to payment-processor timing.

For disputes about eligibility (we determined a failure was user-caused but you believe it was farm-side, or vice versa), escalate to the legal contact address below with the full context. Eligibility decisions are made on the evidence; we are not interested in arguing past it.

Non-Disclosure Agreement (NDA)

For projects that require formal contractual confidentiality coverage, we provide a Non-Disclosure Agreement on request.

Default confidentiality without a signed NDA

For everyday studio work, the confidentiality treatment described in the Privacy section above is sufficient: our team does not access your project content except as needed to support rendering, files are encrypted in transit and at rest, and access is restricted to operations personnel on a need-to-have basis. No signed NDA is required for this default behavior to apply.

When a formal NDA is appropriate

A signed NDA is the right path when:

Your contract with your end client requires you to have NDAs in place with all sub-contractors and service providers handling project assets.
The project involves unreleased intellectual property where disclosure would have measurable competitive or commercial impact (a feature film before its trailer release; an unreleased product visualization; a brand campaign before its launch date).
The project is in a regulated industry (defense, healthcare, financial services) where data handling is contractually scoped.
The project is high-profile commercial or entertainment work where confidentiality is the industry-standard expectation.

How to request

Email the legal contact address below (or ask through the account-dashboard support flow for ongoing relationships) with:

Your account email and a reference to your account.
A brief description of the project — one or two sentences is enough; we do not need confidential project specifics to issue an NDA.
Whether you need a one-way NDA (we agree to keep your information confidential), a mutual NDA (both parties agree), or your studio's own NDA template signed by us.

We turn around standard NDA requests within 2–3 business days. Custom NDAs or modifications to a studio's bespoke template take longer depending on the changes required.

A dedicated explains the NDA process in more detail for prospective customers evaluating Super Renders Farm before opening an account.

Compliance frameworks

We operate in compliance with applicable data-protection and consumer-protection law in the jurisdictions where our users are located. The substantive practices described on this page (collection, use, retention, rights, security) apply uniformly to all users; the specific legal framework that backs them depends on where you live.

The most commonly referenced frameworks:

GDPR (Regulation EU 2016/679) for users in the European Economic Area, the United Kingdom (UK GDPR), and Switzerland (Swiss Federal Act on Data Protection, aligned with GDPR principles). We process personal data on lawful bases — typically contract performance, since you have asked us to provide the rendering service. Data subject requests are honored within 30 days under Article 12. Breach notification follows Articles 33 and 34 where applicable.
CCPA / CPRA (California Civil Code Section 1798.100 et seq.) for California residents. Rights to know, access, delete, and opt out of sale apply; we do not sell personal information. Requests are honored within 45 days, extendable to 90 days for complex requests, as the law permits.
Other jurisdictional frameworks — including but not limited to LGPD (Brazil), PIPEDA (Canada), APPI (Japan), the Personal Data Protection Act (Singapore), the Privacy Act (Australia), and analogous regimes elsewhere — are honored where they apply to our processing of your information.

We do not maintain separate per-jurisdiction policy pages. The universal disclosure above is intended to cover the substantive rights and obligations that apply across the regions where we serve users. If a specific local-law question matters for your engagement, contact the legal address below and we will address it in writing.

For users in jurisdictions covered by GDPR, you also have the right to lodge a complaint with your local data protection authority if you believe we have not handled your personal data correctly. We encourage you to contact us first so we can resolve the issue directly.

Security

A short summary of the security practices that back the privacy commitments above:

Data in transit is encrypted using TLS for web traffic, secure protocols (SFTP) for direct file transfers, and encrypted channels for internal worker-to-storage communication.
Data at rest is stored on encrypted volumes on our render infrastructure.
Account passwords are stored as salted hashes, never in plain text; password reset flows do not transmit the original password.
Payment information is handled by our payment processor; we do not store full card numbers, CVV codes, or expiration dates on our infrastructure.
Access controls restrict which team members can access which systems, applied on a need-to-have basis with periodic review.
Incident response procedures define how we respond to security events, including notification of affected users where required by applicable law.

A note on two-factor authentication. 2FA is not currently supported on Super Renders Farm accounts. The recommended account-security practice is a strong, unique password (at least 16 characters, generated by a password manager) that is not reused on any other service. 2FA support is on the roadmap; until it ships, password hygiene and avoiding credential sharing are the controls in your hands.

A note on shared accounts. Multi-user / team accounts are not currently an official feature. Studios that need shared billing with separate user identities should contact support to discuss workarounds. Single-login credential sharing is not recommended — it complicates auditing and creates a security blast radius if any one user's device is compromised.

Acceptable use

The full Acceptable Use rules are in the . The short version, in plain English:

The service is for legitimate rendering work — 3D scenes, animation, VFX, archviz, motion design, and adjacent creative use.
Do not upload content that is illegal in your jurisdiction or under United States federal law.
Do not use the service to attempt to attack, probe, or extract data from our infrastructure, other customers, or third parties.
Do not attempt to circumvent billing, share account credentials in violation of the Terms, or resell render capacity without a separate written agreement.
Do not use the service in a way that creates legal exposure for us under sanctions, export-control, or anti-money-laundering law.

Violations of Acceptable Use may result in suspension or termination of the account; the Terms of Service describes the procedure and any applicable refund handling for terminated accounts.

How we update these policies

We may update this page as our practices evolve, our legal entity changes (sole proprietorship → LLC mid-2026), or applicable law changes. Material updates are announced in two ways:

A dated entry is added to the change log at the bottom of this page.
Account holders are notified by email when an update materially changes how we collect, use, retain, or share personal information, or how we process refunds.

Continued use of the service after a material update constitutes acceptance of the updated policies. If you do not accept a material change, the right path is to close your account; any unused credit balance is refundable on closure as described in the Refund Policy section.

How to reach us about legal, privacy, refund, or NDA matters

For any legal, privacy, refund, or NDA-related inquiry:

Email: . This is the same address as general support; please mark the subject line "Privacy request", "Legal inquiry", "Refund", or "NDA" so the message is routed for proper tracking and retention.
Postal address: Super Renders Farm, 2314 Bonnie Brae, Santa Ana, CA 92706, USA.
Support chat: available through the dashboard and through knowledge.superrendersfarm.com for general questions; formal requests should go to the email address above so there is a written record.

For account-related questions that are not legal in nature — billing detail changes, credit balance, technical support on a job — the standard support channels are the right path. The legal email is for formal privacy requests, refund disputes, NDA requests, and compliance questions where a written record matters.

— service overview.
— credit model, payment methods, invoice handling.
— NDA process for prospective customers.
— formal contractual terms covering account use, billing, service-level expectations, and platform conduct. This separate document is the binding legal Terms; the page you are reading is the plain-English docs reference.

FAQ

Q: How is my project content protected when I upload it to the farm? A: Project files are treated as confidential. Our team does not access them except as needed to support rendering — for example, diagnosing a failed job you've reported. Files are encrypted in transit and at rest, and access is restricted to operations personnel on a need-to-have basis. For projects requiring formal contractual confidentiality, we provide a Non-Disclosure Agreement on request.

Q: How long are my rendered frames kept on the farm? A: Output frames are retained for 45 days after job completion, after which they are automatically deleted. Retention does not vary by plan. Download promptly, or configure the Client App to auto-download finished frames to local storage.

Q: I'm in the EU — what privacy rights apply to me? A: You are covered by GDPR (or UK GDPR if you are in the United Kingdom, or the Swiss Federal Act on Data Protection if you are in Switzerland). You have rights to access, correct, delete, and port your personal information, plus other GDPR-defined rights including objection and restriction. We respond to verified requests within 30 days.

Q: I'm in California — what privacy rights apply to me? A: You are covered by CCPA / CPRA. You have rights to know, access, delete, and opt out of sale (we do not sell personal information). We respond to verified requests within 45 days, extendable to 90 days for complex requests, as the law permits.

Q: I'm in a country not specifically named on this page — what protections apply to me? A: The substantive rights described in the Privacy section (access, correction, deletion, portability) are extended to all users as a matter of policy, subject to applicable local law. Specific local frameworks — LGPD in Brazil, PIPEDA in Canada, APPI in Japan, and analogous regimes elsewhere — are honored where they apply to our processing of your information.

Q: How do I get an NDA in place for a confidential project? A: Email the legal contact above with your account details and a one-or-two sentence project description (no confidential specifics needed to issue an NDA). State whether you need a one-way, mutual, or your-template NDA. Standard NDA requests turn around in 2–3 business days; custom templates may take longer.

Q: My render failed but I was still charged. Can I get a refund? A: It depends on the cause. Failures attributed to our rendering system (worker crash, license server outage, network failure mid-render) are eligible for refund of the failed portion, verified in farm-side logs. Failures caused by scene configuration on the user side (missing assets, unsupported plugin combination, misconfigured renderer) are not eligible. Open a support request with the job ID and we'll review the logs.

Q: Can I delete my account and remove all my data? A: Yes. Email the legal contact above to request account closure. We remove your account information, project files, and any retained output frames, subject to retention requirements for billing records (multi-year for tax compliance) and any active legal hold. Unused credit balances can be refunded on closure, subject to payment-processor processing fees.

Q: Does Super Renders Farm sell my data to third parties? A: No. We do not sell personal information, and we do not share project content with anyone outside of (a) payment processors that handle billing under contract, (b) infrastructure providers under contract, (c) legal authorities where required by valid legal process, and (d) parties you have explicitly authorized us to share with.

Q: Is 2FA supported on Super Renders Farm accounts? A: Not currently. The recommended security practice is a strong, unique password (at least 16 characters, generated by a password manager) and not reusing it across other services. 2FA support is on our roadmap.

Legal and policies