Privacy Policy

Effective date: October 11, 2026

This policy explains what information RenderGod collects, why, who receives it, how long we keep it, and the choices and rights you have. It covers the RenderGod desktop app, the website rendergod.app, the web dashboard at app.rendergod.app, the RenderGod iPhone app (in beta), and the RenderGod add-on for Blender (together, the "Service").

RenderGod is operated by Zoock Studio ("we", "us"). We decide how and why your information is used, which makes us the data controller. You can reach us about anything in this policy at team@rendergod.app.

1. What we collect and why

1.1 Your account (from Google Sign-In)

You sign in with Google. You need an account to use RenderGod, including the Free plan. From Google we receive your name, email address and whether Google has verified it, your profile picture link, and your Google account identifier. We use this to create and secure your account, sign you in to the app and website, link your plan and computers to you, and contact you about your account. See also Google user data below.

1.2 Your computers and sign-in activity

When you use the desktop app, we receive and store:

• The computer's name (as set in your operating system), used as the device label you see in your account, and an identifier derived from it.
• A random installation ID, a device public key (and whether it is protected by the computer's security chip) and registration dates. These let us enforce the number of computers your plan allows and stop someone copying your sign-in to another machine. We do not collect hardware serial numbers or MAC addresses.
• Your operating system, app version, online status and when the app was last seen. While it runs, the app checks your plan with our servers every few minutes and before each job.
• The IP address of your latest sign-in and the country it points to. To work out the country we send the IP address to the lookup service ip-api.com.
• Sign-in security records kept by our sign-in provider, Supabase: the IP address, browser and time of each sign-in and session.

We use this to run plan limits, keep your account secure, show your computers in your account, and help with support.

1.3 Your render queue and settings

Your .blend files and renders stay on your computer. Some details about them are stored with your account:

• When you start your queue, the app saves a copy of it to your account. This includes job names, the full paths of your .blend files and output folders, scene, camera, view-layer, world and compositor names, compositor output paths, frame ranges, render settings, the Blender version and its location, the command used to start Blender, progress, per-frame render times, warnings and error messages, and any Python scripts (hooks) you added to your jobs.
• While Remote Control is on (it is on by default and can be turned off in Settings), the app also keeps an up-to-date summary of your queue, including job names, file paths, settings and progress, so your browser or phone can show it. Your scripts and the Blender command are left out of this summary.

1.4 Remote control from a browser or phone

• Commands and replies travel through our database provider's real-time service, encrypted in transit.
• Preview images stream directly from your computer to your browser or phone over an encrypted (DTLS) connection. We do not receive or store them. If a direct connection is not possible, a relay may be used; the relay passes the encrypted stream on and cannot read it.
• We store a record of each browser or phone session that connects to your computer (its browser identification string, when it started, when it was last active and whether it was revoked) and a log of remote commands (which command, when, and whether it succeeded).
• Live hardware readings (CPU, memory, GPU load and temperature) are sent only while you are viewing them and are not stored.
• To check whether a direct connection is possible, the desktop app contacts public connection-test (STUN) servers operated by Cloudflare, Google, Nextcloud, BlackBerry and several internet-telephony providers each time it starts, even when Remote Control is off. They see your computer's public IP address. When needed, the app also asks your router to open a port for up to two hours.
• If you set your Telegram bot token from a browser, it travels encrypted to your computer and is not stored by us.

1.5 Notifications to your iPhone

If you use the iPhone app, we store its push-notification token. When a render finishes or fails, the notification (computer name, job name and a short status or error) is delivered through Apple's push notification service.

1.6 Error reports

The web dashboard and iPhone app send us error reports (error message and technical details, app build and platform) so we can fix problems. The desktop app does not send error reports. Its logs stay on your computer.

1.7 Payments

Purchases are handled by Lemon Squeezy, our reseller and merchant of record. You enter your payment details with Lemon Squeezy, not with us, and we never see your full card number. We receive and store your customer and subscription identifiers, plan, status and billing dates. On your billing page we show your card brand, last four digits and invoices, which we read live from Lemon Squeezy. When you start a checkout, we pass your account email and an account reference to Lemon Squeezy. If you pay with a different email, we change your Lemon Squeezy customer email to your account email so that receipts reach you.

1.8 Emails and support

• Your email preferences and a record of when you gave or withdrew consent to product news emails.
• The emails we send you and whether they were delivered.
• Messages you send us, and any phone number or Telegram handle you choose to add to them.
• If you join the macOS waiting list: your email and, if you add them, your phone number, Telegram and Discord handles.
• Requests you make to delete your account or exercise your other rights.

1.9 What stays on your computer

The app keeps its settings, queue, logs and sign-in data in its own folders on your computer. This includes your Telegram bot token if you set one up, which on Windows is stored unencrypted so that crash recovery can use it. The app also searches your drives for Blender installations; the results stay on your computer. None of this is uploaded except as described above. Earlier versions of the app also saved your Telegram settings, including the bot token and chat ID, to your account, and that copy is kept with your account. On Windows, uninstalling RenderGod with "delete app data" selected removes these folders for the user who uninstalls. On macOS, delete the app and its folders under ~/Library. The Blender add-on stays in Blender until you remove it in Blender's preferences.

1.10 The Telegram bot

The Telegram feature uses a bot that you create and that runs from your own computer. We do not operate it and do not receive its messages. Whatever you choose to send through it (job names, status, preview images and videos, and file paths in its buttons) goes through Telegram and is handled under Telegram's privacy policy.

1.11 The website

We use only the cookies and browser storage needed to keep you signed in, finish a checkout and keep unsent form drafts. We use no analytics, advertising or tracking cookies, so we do not show a cookie banner. The billing page loads Lemon Squeezy's script, and your profile picture is loaded from Google. The home page plays a video hosted by Vimeo, which receives your IP address to stream it; we ask Vimeo not to track you. Our hosting providers keep short-lived server logs, including IP addresses, for security.

1.12 What you must provide

No law requires you to give us any information. A Google sign-in is needed to create an account, and without an account you cannot use the app. The fields you add to support messages or the waiting list are optional.

2. How we use your information, and our legal grounds

We use your information only for these purposes:

• Providing the Service you signed up for: your account, plan limits, the queue, remote control, notifications and billing. Legal ground: performing our contract with you.
• Security and preventing abuse: protecting accounts, enforcing plan limits, investigating misuse. Legal ground: our legitimate interest in a secure, fairly used Service.
• Support and fixing problems: answering you and using error reports to fix bugs. Legal ground: contract and legitimate interest.
• Understanding and improving RenderGod: we analyse the account, device, queue and settings information described in section 1, such as which features and render settings are used and how long renders take, to decide what to build and fix. We do this ourselves, without third-party analytics services. Legal ground: our legitimate interest in improving the Service.
• Account and billing emails, such as welcome, trial, payment and cancellation messages. Legal ground: contract.
• Product news emails: news, tips and offers about RenderGod. When you create an account you are subscribed, as the sign-in screen says, and you can unsubscribe at any time with the link in any of these emails or on your profile. Some may be triggered by what you do, for example a checkout you did not finish or not using the app for a while. Legal ground: your consent, or our legitimate interest in telling customers about our own product.
• Meeting legal duties, such as tax rules and lawful requests. Legal ground: legal obligation.

We do not sell your information, use it for advertising, build advertising profiles, or use it to train AI or machine-learning models. We make no decisions about you by automated means that have legal or similar effects.

3. Who receives your information

We share information only with the providers that run parts of the Service for us, and only what each one needs:

• Supabase: database, sign-in, real-time messaging and server functions. Our database is hosted in Frankfurt, Germany; some server functions may run elsewhere.
• Netlify: hosting and server functions (sign-in checks, checkout, billing, account requests) for the website, the web dashboard and the iPhone app, which loads the web dashboard. Processed in the United States.
• Google: Sign-In, and delivery of our emails.
• Lemon Squeezy: payments, invoices, tax and refunds. As merchant of record it handles your payment data under its own privacy policy.
• Apple: push notifications and iPhone app distribution.
• Cloudflare and other STUN providers (see 1.4): connection tests and, when needed, an encrypted relay for remote previews.
• ip-api.com: turning your IP address into a country.
• GitHub: hosting app downloads and updates, so it sees your IP address when you download.
• Vimeo: the video on our home page.

Telegram receives data only if you connect your own bot (see 1.10). We may also disclose information when the law requires it, to protect people's rights or safety, or to a buyer if the business is ever sold, in which case this policy continues to protect it.

4. Where your information is processed

Our database is in the EU. Some providers above process data in the United States or elsewhere, and we may access data from outside the EU, only in countries the European Commission recognises as protecting personal data adequately. Where our providers handle data for us outside the EU, our contracts with them include the European Commission's standard contractual clauses or rely on the EU-US Data Privacy Framework. GitHub, Vimeo and ip-api.com handle your IP address under their own privacy policies.

5. How long we keep it

• Account, device, queue and settings data, error reports, remote sessions and the remote command log, sign-in security records, support messages and email records: while your account exists. When you ask us to delete your account, we delete it within 30 days.
• macOS waiting list: until we tell you RenderGod is available for macOS, or until you ask us to remove you.
• Deletion requests: removed when the account is deleted. We then keep only the account's random ID, so that later payment messages about it are ignored.
• Temporary sign-in codes: deleted within a day of expiring.
• Payment and tax records: kept by Lemon Squeezy for as long as tax law requires, and in our own accounting records for 7 years, as tax law requires.
• Do-not-email list: if an email to you bounces permanently, or you ask us never to email you, we keep your address on a do-not-email list so that we respect it.
• Payment event records: subscription identifiers and event types, without your name or email, for our accounting.
• Backups: our providers may keep encrypted backups for a short period. Deleted data disappears from them as they are replaced.
• On your computer: until you delete it or uninstall RenderGod with "delete app data" selected.

6. Your rights

Wherever you live, you can ask us to:

• Give you a copy of the information we hold about you, including in a machine-readable format.
• Correct information that is wrong, incomplete or out of date.
• Delete your account and information.
• Stop or limit a use of your information, or object to a use based on our legitimate interests.
• Stop sending you product news emails. Use the unsubscribe link in any of these emails or untick the box on your profile.

You can object at any time to a use of your information that is based on our legitimate interests. We will stop unless we have compelling grounds to continue.

Email team@rendergod.app from the address on your account. It is free. We reply within one month, and may ask you to confirm that the request comes from you. You can also complain to the data protection authority where you live, for example the authority in your EU country or, in the UK, the Information Commissioner's Office. We would appreciate the chance to fix things first.

7. Deleting your account

Open your profile and choose Request account deletion, or email us. We confirm the request by email and complete it within 30 days. Before deleting we stop any subscription renewal, so you are not charged again. Time already paid for is not refunded automatically. We then delete your account and the information linked to it, except what section 5 says we keep. Messages you sent us by email stay in our mailbox unless you ask us to delete them. You can cancel the request from your profile until it is completed. Files on your computers are not affected; uninstall RenderGod to remove local data.

8. Security

Connections between your devices and our services are encrypted. We restrict database access so each account can reach only its own data, sign app updates, and on Windows encrypt your saved sign-in with the operating system's protection. No system is perfectly secure. If a breach puts your information at risk, we will notify you and the authorities as the law requires.

9. Children

RenderGod is not intended for anyone under 16, and we do not knowingly collect information from children under 16. If you believe a child has given us information, contact us and we will delete it.

10. Google user data

We request only the basic openid, email and profile permissions. We receive your name, email address and its verification status, profile picture link and Google account identifier. We have no access to your Gmail, Drive, Contacts, Calendar or any other Google data. We use this information only as described in section 1.1. It is stored by Supabase, our database provider. We do not sell it, use it for advertising or use it to train AI, and we share it only with the providers listed in section 3 or when the law requires.

RenderGod's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

You can remove RenderGod's access at any time from your Google Account permissions page. To delete the Google data we hold, delete your account (section 7).

11. Do Not Track

We do not track you across other websites and do not let third parties do so through our site, so we do not change our behaviour in response to browser Do Not Track signals.

12. Changes to this policy

When we change this policy we update the effective date above. If a change is significant, we will tell you by email or in the app before it takes effect.

13. Contact

Zoock Studio (RenderGod). Email: team@rendergod.app.