Privacy Policy

Document version: 2026-04 · Last updated: 1 October 2026

This notice is provided under Regulation (EU) 2016/679 (“GDPR”) and explains how personal data is processed when you use Eclipse Render Manager (the website, accounts, licenses, desktop apps, and related services).

1. Data controller

Federico Ventura SRLS
Via Gaetano Donizetti 2, 22063 Cantù (CO), Italy
VAT IT04000010134
Email: [email protected]
PEC: [email protected]

Eclipse Render Manager is a product of Federico Ventura SRLS. Throughout this notice, “we”, “us”, and “our” mean Federico Ventura SRLS.

2. Data we process

Depending on how you use Eclipse, we may process:

• Account data: email address, password hash, verification status, country of residence (ISO country code you select at signup), preferred DCC apps and renderers (up to two each, selected at signup), and account timestamps.
• License and entitlement data: plan or beta status, seat or node limits, device or installation identifiers used for validation, and license status.
• Technical and security data: IP address, approximate location at country level, user agent, logs needed to operate and secure the service.
• Support and community context you send us (for example email or Discord messages).
• When paid plans are enabled: email and transaction status received from the payment provider. We neither receive nor store full card details.
• With your consent only: aggregate website analytics via Google Analytics.
• Account-linked aggregate product usage: Local and Distributed job totals and outcomes, submission modes, supported DCCs and renderers, total frames submitted and completed, and the highest number of Render Nodes simultaneously connected to the account's Coordinator, plus whether ERM and connected Render Nodes have been used on Windows, macOS, or both.

We do not collect your scene files, textures, caches, render frames, or project assets as part of normal product operation. Those stay on your machines and shared storage.

3. Purposes and legal bases

We process data to:

• Create and manage accounts, beta access, and licenses. Country of residence is collected for account administration and, when paid plans apply, for tax and geo rules (contract and legal obligations where applicable). Preferred DCC apps and renderers are collected so we can tailor beta support and understand which tools our users rely on; they are not used for advertising (legitimate interest in operating and improving the service; provided as part of account setup you request).
• Validate licenses, enforce plan limits, and prevent abuse or fraud (contract and legitimate interest in security).
• Provide download access, product updates, and essential service communications (contract / legitimate interest).
• Measure aggregate product use, job outcomes, supported tool and operating-system platform adoption, and Render Node capacity so we can improve and operate Eclipse with data minimisation safeguards (our legitimate interest in product improvement and service planning).
• Comply with legal and tax obligations when payments apply.
• Measure website use in aggregate with Google Analytics only if you consent (consent).
• Enable optional Discord job notifications that you configure in the desktop app (steps requested by you; Discord then processes delivery under its own terms).

We do not use personal data for behavioural advertising.

4. Eligibility

The Service is intended for users aged 18 or older. By creating an account you confirm that you meet this requirement. We do not knowingly collect personal data from children under 18.

5. Beta period

While Eclipse is in beta, access may be offered free of charge under a beta license. Account and license data are still processed so we can authenticate you, issue entitlements, and operate the service. When paid plans open, we will process the additional payment-related data needed for checkout and billing.

6. Desktop apps and local processing

Eclipse Render Manager, Render Node, and related desktop components run primarily on your computers and local network. Job queues, logs, and frames are processed locally or on your farm. License validation and account features may contact our servers. Preferences stored on your device (for example app settings) remain on that device until you clear them.

Eclipse Render Manager sends cumulative aggregate usage counters to the proprietary licensing service and associates them with your account and licence. The counters cover Local and Distributed job totals, completed, failed, partial, and cancelled outcomes, submission modes, supported DCCs and renderers, frames submitted and completed, the maximum number of Render Nodes connected at the same time, and the fixed Windows or macOS category observed for ERM and connected Render Nodes. Render Nodes do not send this telemetry directly to us.

This feature does not send individual job records, project or scene names, file or folder paths, computer names, images, previews, render logs, job identifiers, precise usage times, or render content. It also does not send operating-system versions, application versions, update history, GPU details, AOVs, output formats, notification settings, preview activity, or integration-installation results as product-usage telemetry. Apart from the Windows or macOS category described above, no additional operating-system details are sent. A local one-way job identifier hash is used only to prevent duplicate counting.

6A. Optional issue reports

When Eclipse detects a failed job, failed slice, service problem, application error, farm connection problem, or integration problem, it may offer an optional issue-reporting window. Nothing is sent unless you deliberately select Send report.

A report includes the account and license relationship, a report identifier, product and application version, Windows or macOS platform, Local or Distributed mode, supported DCC and renderer categories where applicable, a technical error category and fingerprint, the related job identifier, occurrence count, your optional note, and submission timestamps.

If you choose to include diagnostic logs, the package may also contain recent Eclipse and render log excerpts, task and slice status, limited job metadata, service-health results, operating-system version and architecture, and technical error messages. Eclipse attempts to remove credentials, email addresses, and your home-directory path before upload. Scenes, project files, textures, caches, rendered images, previews, and render outputs are not included. Diagnostic text may still contain project, path, computer, or network information written by a DCC or renderer, so you can send the issue without logs.

Diagnostic packages are compressed and uploaded directly to private Cloudflare object storage using a short-lived authorisation. They are used only for support, failure reproduction, reliability improvements, and identifying repeated technical problems. Render Nodes do not receive licensing credentials or upload reports directly.

7. Optional Discord job notifications

Eclipse may offer an optional Discord notification feature in desktop Settings. You can enable, configure, and disconnect it at any time. It is not required to use Eclipse.

When you enable it:

• You connect via Discord OAuth and choose a webhook for a channel on a Discord server you control (for example your studio server). This is not an Eclipse community bot and is not used for marketing or licence messages.
• You choose which render-job status events to send (for example completed, failed, partial, started, cancelled, or other job statuses you enable in Settings). Notifications go only to the channel you selected.
• Message content is limited to job metadata you already see in Eclipse (for example scene name, status, frame range, DCC, job id, and submit labels when present). We do not include Discord user ids or your email in these messages.
• Webhook URLs and Discord server or channel identifiers are stored on your computer as local settings. Eclipse cloud services do not receive these notification pings; delivery goes from your machine to Discord.

Discord processes the message as the service that hosts your channel, under Discord's terms and privacy policy. If we later expand notification content (for example screenshots, full file paths, or log excerpts), we will update this notice.

Separately, if you join our public Discord community for support, that use is governed by Discord's terms and privacy policy and is independent of the optional job-notification feature.

8. Payments

When paid plans are enabled, Stripe (and related checkout tools such as Link, where offered) process the data required for payment, fraud prevention, receipts, disputes, refunds, and tax compliance. Stripe or a related entity may act as merchant of record where configured. We receive only what we need to verify payment and deliver entitlements.

9. Google Analytics

Only with your consent, we use Google Analytics 4 on the website to measure visits and interactions in aggregate (for example pages viewed, clicks on key links, outbound links such as Discord, and scroll depth). The tag is not loaded before consent, and we do not enable advertising or remarketing features. You can change your choice under Manage Cookies in the footer or in the Cookie Policy. Legal basis: consent.

10. Providers and recipients

Depending on the feature used, data may be processed by:

• Hosting, delivery, and infrastructure providers for the website and license services.
• Cloudflare for private storage of optional diagnostic packages you choose to send.
• Stripe for payments when paid plans are live.
• Discord, if you enable optional job notifications from the desktop app (messages delivered to your chosen webhook/channel) or if you join our community, in both cases subject to Discord's terms and privacy policy.
• Advisers or authorities where required by law.

Each provider processes data according to its role and applicable law. We do not sell your personal data.

11. International transfers

Some providers may process data outside the European Economic Area. Where that happens, transfers rely on an adequacy decision, standard contractual clauses, or another mechanism recognised by the GDPR, as stated by the relevant provider. Discord may process notification content outside the EEA under its own transfer mechanisms.

12. Retention

We keep personal data only as long as needed for the purposes above:

• Account and license records: while your account is active, then up to 24 months after closure or last login (unless a longer period is required for disputes or security).
• Account-linked aggregate product-usage counters: while the account is active, then generally up to 24 months after closure, after which they are deleted or irreversibly anonymised unless a longer period is required for a documented legal or security reason.
• Security and abuse-prevention logs: typically up to 12 months.
• Optional diagnostic packages: normally 30 days; the associated issue and support history may be retained for up to 24 months.
• Payment and tax records (when paid plans apply): for the periods required by applicable law.
• Analytics: according to Google Analytics settings and your consent (withdrawable at any time).
• Discord webhook and channel settings for optional notifications: on your device until you disconnect the feature or clear local settings.

13. Your rights

Where provided by the GDPR, you may request access, correction, deletion, restriction, portability, or objection, and withdraw consent without affecting processing already carried out. To exercise these rights, email [email protected] (or PEC) from the address linked to your account. We may need to verify your identity before fulfilling a request. You may also lodge a complaint with the Italian Data Protection Authority (Garante) or the competent authority in your country. For optional Discord notifications, you can disconnect the integration in Settings at any time.

You may object, on grounds relating to your particular situation, to account-linked aggregate product-usage processing based on legitimate interests. We will stop that processing unless we demonstrate compelling legitimate grounds that override your interests, rights, and freedoms, or it is needed for legal claims.

14. Contact

For personal data requests and privacy questions: