RenderBuddy Privacy Policy
Effective date: [[EFFECTIVE_DATE]]
This policy explains what personal data RenderBuddy collects, why, where it goes, how long we keep it, and what you can do about it. It covers the RenderBuddy website (renderbuddy.app), the RenderBuddy phone app, the RenderBuddy Agent for Windows, and the RenderBuddy plugins for Unreal Engine, Houdini and Blender. Together we call these "RenderBuddy".
1. Who is responsible for your data
The controller of your personal data is:
PentaPixels SARL
[[REGISTERED_ADDRESS]]
Tunisia
Unique identifier (RNE): [[RNE_ID]]
Privacy contact: [[PRIVACY_CONTACT_EMAIL]]
General support: support@renderbuddy.app
Representative in the European Union (GDPR Article 27): [[EU_REPRESENTATIVE]]
Representative in the United Kingdom (UK GDPR Article 27): [[UK_REPRESENTATIVE]]
We process personal data under Tunisian law, in particular Organic Law no. 2004-63 of 27 July 2004 on the protection of personal data. If you are in the European Economic Area or the United Kingdom, the GDPR or the UK GDPR also applies to you, and this policy is written to meet it.
INPDP declaration reference: [[INPDP_DECLARATION_REF]]
2. The short version
- You sign in to the phone app with Google. We get your name, email address and profile photo from Google.
- The Agent on your PC sends the state of your renders to our cloud so your phone can show it: progress, frame numbers, job and scene names, file paths, error messages, your computer's name and Windows user name, and hardware details. These are end-to-end encrypted on your PC: only your PC and your phones can read them.
- Preview images of a frame are sent only when you ask for one, end-to-end encrypted in the same way.
- Some information stays readable to us, Google and Apple so the service can work: your account, whether a machine is online, which app is open and its state, the kind of job, the types and times of events, and the text of push notifications. Section 4 lists all of it. It is stored on Google's servers in the United States.
- Your scene and project files (.uproject, .hip, .blend) and your rendered frames never leave your PC. Only a small preview of a frame does, when you ask.
- The plugins talk only to the Agent on the same computer. They send nothing to the internet.
- The phone app has no analytics, no crash reporting and no ads.
- The website uses analytics only if you accept them.
- You can delete your account and its data from the phone app at any time.
3. What we collect, and from where
3.1 The website
- Server logs. The website is hosted on Netlify. Netlify records each request to the website, including the visitor's IP address and browser, to serve the website and keep it secure, as described in Netlify's privacy statement. Netlify's dashboard shows us recent requests for a short time (24 hours on our current plan). We use it only to fix problems with the website, and we don't copy or keep these logs.
- Your theme choice (light or dark), stored in your browser under the key
rb-theme. - Your cookie choice, stored in your browser under the key
rb-consent. - Analytics, only if you accept them. Then the site loads Google Tag Manager, which loads: Google Analytics 4 (measurement ID G-LG08KFYJVJ). Analytics tools typically collect your IP address, device and browser details, the pages you visit and how you got there. See the Cookie Policy for details.
- Fonts are served from our own site. Your browser does not contact Google Fonts.
3.2 Your RenderBuddy account (phone app)
You sign in with your Google account through Firebase Authentication. We receive and store:
- your name, email address and profile photo address, as held by Google;
- a Google account identifier and a RenderBuddy user ID;
- when your account was created and when you last signed in.
We do not receive your Google password.
3.3 The phone app
- Push notification token. To send you notifications, the app registers with Firebase Cloud Messaging and stores a token, the platform (Android or iOS), the app version and the time it was saved.
- Watch entries. While a screen shows a machine, the app records that you are watching it (a random ID created for this installation of the app, the screen, and a time). The Agent uses this to send live numbers only while you look.
- Machine names. If you rename a machine, we store the new name, end-to-end encrypted.
- Commands you send: stop a render, request a preview, or start a render. A command contains its type, a status, the time, and the app and job it is for (a random job ID). For a start, the names of the preset, sequence, queue, node or take you picked are end-to-end encrypted.
- Requests to add a phone. When you add a phone to a computer, the phone stores a short-lived request that the computer answers with its key, encrypted so that only that phone can open it. A request can be used for 2 minutes.
- App integrity checks. The app uses Firebase App Check with Google Play Integrity (Android) or Apple DeviceCheck (iOS) to prove that requests come from the real app. Google or Apple process device and app integrity signals for this.
- Camera. The camera is used only to scan the pairing QR code, on your phone. Camera images are not stored or sent to us. On Android, scanning uses Google's ML Kit on the device; Google states that ML Kit may send it limited information about the performance and use of the feature.
- Preview images you view (see 3.4).
The phone app has no analytics, no crash reporting, no advertising and no tracking SDKs.
3.4 The desktop Agent
The Agent runs on your Windows PC. It collects information from your PC and from the plugins, and sends it to our cloud so your phone can show it.
When the Agent shows a pairing code (before you pair):
- a random machine ID created by the Agent;
- your computer's name, end-to-end encrypted, so the phone that scans the code can show which PC you are pairing;
- your IP address, used for abuse limits (see 3.7).
After you pair, the Agent encrypts the information below on your PC before it sends it (see section 4), except the items marked "readable".
About the machine:
- the computer's name and your Windows user name;
- operating system version, CPU and GPU model, total memory, total disk space, and the list of drives (drive letter or path, and size);
- the Agent's version, and whether the Agent is online, with timestamps (readable);
- which supported apps (Unreal Engine, Houdini, Blender) are installed or running (readable), and their versions;
- your email address, stored with the pairing so the Agent can show which account it is paired with (readable).
About your renders, caches, simulations and TOP cooks:
- state (for example rendering, finished, failed, stopped) and the kind of job (readable), progress, current and total frames, elapsed and remaining time;
- job and scene names: for example job name, level, map or sequence name, Houdini node paths, take names and TOP node names;
- file and folder paths: for example project folder, the .hip file name, the .blend file path, and output paths;
- render settings: for example renderer, resolution, frame range, frame rate, samples, render device, camera name and anti-aliasing settings;
- the job's author field (Unreal Engine usually fills this with your Windows user name);
- error and warning messages from the app, which may contain file paths or names;
- free disk space on the output drive and an estimate of the space still needed;
- the lists you can start renders from: Unreal presets, sequences and saved queues, and Houdini watched nodes and takes;
- events such as "render started", "render finished", "black frames detected", "not enough disk space" or "app not responding" (readable: the type of event and its time).
Live numbers, only while your phone app is showing that machine:
- CPU, GPU and memory load, video memory use, and free and total space of a drive.
Preview images:
- When you tap Preview, the Agent sends one image of the current frame, at most 1920 pixels on its longer side.
- The image is encrypted on your PC with a key that only your PC and your phones have. We, Firebase and Google store only unreadable data, with the time the image was taken.
- For Houdini and Blender, the Agent reads the frames the renderer wrote on your disk and makes the preview on your PC. Your full-size frames stay on your disk.
- The Agent also checks frames for "black frame" problems on your PC. That check sends only the result, not the image.
What never leaves your PC: your scene and project files (.uproject, .hip, .blend and their assets) and your full-size rendered frames.
3.5 The plugins (Unreal Engine, Houdini, Blender)
The plugins send information only to the Agent on the same computer (address 127.0.0.1). They do not connect to the internet. What they send to the Agent is what section 3.4 describes. The plugins store their own settings locally: in Unreal Engine's per-user settings, in your Houdini preferences folder (renderbuddy_settings.json) and in the Houdini scene file (which nodes you watch), and in Blender's add-on preferences.
3.6 Support and community
- If you email support@renderbuddy.app, we receive your email address, your message and anything you attach (for example Agent logs). Our email is hosted by [[EMAIL_PROVIDER]].
- The RenderBuddy community is on Discord. Discord is a separate service with its own privacy policy. We see what you post there, like any member.
- If you use "Report a bug", the form is run by Tally (Tally BV, Belgium), which stores your answers and the files you attach in the European Union. The button fills in only which part of RenderBuddy you used, its version, the version of your 3D software or phone system, and your operating system. Everything else is what you type or attach. Logs can contain scene names and file paths: you see the file before you attach it. A copy of your report's title, description, steps and those details is posted to a private channel on our Discord server that only the RenderBuddy team can read. The email or Discord name you give, if any, and your files stay in Tally.
3.7 Security and abuse-prevention records
- Audit log. When you pair, unpair, restore or extend a pairing, or when a pairing attempt fails, we record your user ID (or the machine ID), the event, the machine ID, the time, your IP address shortened to its network (the last part of an IPv4 address is set to 0; an IPv6 address is cut to its /48 network) and your device's user agent (browser or app identification string). When an account is deleted, we record only the user ID and the time.
- Rate limits. To stop abuse of pairing and previews, we count recent attempts. For pairing codes, your IP address is reduced (IPv6 to its /56 network) and then hashed, and the counter is stored under that hashed key, together with the machine ID. Other counters are stored under your user ID or the machine ID. A counter holds only the times of recent attempts.
- Server logs. Google Cloud keeps technical logs of requests to our cloud functions. They include IP addresses, user agents, user IDs and machine IDs, and, when a pairing request is refused, the chain of forwarded IP addresses, each shortened the same way as in the audit log.
- Deleted-account marker. When you delete your account, we keep your former user ID and the time of deletion, so that a pairing still in progress cannot recreate the account.
4. What is end-to-end encrypted, and what isn't
When you pair, the QR code carries a key from your PC to your phone. The key never passes through our servers. Your PC and your phones use keys made from it to encrypt (AES-256-GCM) what they send each other. A phone you add with "Add a phone" gets the key from your PC, encrypted for that phone only, after you check that both screens show the same six-digit code.
End-to-end encrypted (only your PC and your phones can read it):
- your computer's name, your Windows user name and its hardware details (operating system, CPU, GPU, memory, drives and their paths), and the name you give the machine in the app;
- job, scene, node, take, preset, queue and sequence names, file and folder paths, and error messages;
- frames, progress, time left, samples, disk space figures, TOP work-item counts and the machine's live load;
- the lists you can start renders from, and the details of the commands you send;
- preview images.
What we, Google and Apple can see (encrypted in transit and at rest by Google, but readable by our cloud services):
- your account: your name, email address and profile photo from Google, and your user ID;
- a random ID for each machine, whether it is online and since when, and the Agent's version;
- which supported apps (Unreal Engine, Houdini, Blender) are installed or open, and their state (for example rendering or idle);
- the kind of job (render, cache, simulation or TOP cook), whether it is a single frame, the types of events (for example "render finished"), whether a job was stopped from the phone or on the PC, and their times;
- the type of each command (for example stop or preview), its status and time, and the app and the random job ID it is for;
- when someone watches a machine in the app;
- when a preview is taken, and when something is written and roughly how much (sizes are rounded);
- when the lists you can start renders from change, and roughly how long they are;
- your push notification tokens, with the platform and the app version;
- the text of push notifications (below).
Push notifications say only which app and what happened, for example "Render Failed: Unreal Engine: Render failed. Open RenderBuddy for details." They never contain the machine's name, job names, file paths, error messages or numbers. They are delivered through Firebase Cloud Messaging (Google) and, on iPhone, Apple Push Notification service (Apple), which can read their text. They go to every phone signed in to your account.
End-to-end encryption protects your data on our servers and on the way. It can't protect a PC or phone that someone else controls. A key can't be taken back from a phone: to shut every phone out, unpair the machine and pair it again.
5. Why we use your data, and our legal basis
Under the GDPR we must tell you the legal basis for each use.
| Purpose | Data | Legal basis (GDPR) |
|---|---|---|
| Create and run your account; sign you in | Google account data (3.2) | Contract (Art. 6(1)(b)) |
| Pair machines with your account; show their status, progress and previews; carry out your commands | Agent, app and plugin data (3.3, 3.4) | Contract (Art. 6(1)(b)) |
| Send push notifications | Push token, events (3.3, 3.4) | Contract (Art. 6(1)(b)); your phone also asks your permission |
| Protect the service: App Check, rate limits, audit log, server logs, deleted-account marker | 3.3, 3.7 | Legitimate interests (Art. 6(1)(f)): keeping accounts and machines secure and preventing abuse |
| Answer support requests | 3.6 | Contract, or legitimate interests when you are not a user |
| Remember your website theme and cookie choice | 3.1 | Legitimate interests; strictly necessary storage |
| Website analytics | 3.1 | Consent (Art. 6(1)(a)); you can withdraw it at any time |
| Comply with the law and answer lawful requests | Any, as required | Legal obligation (Art. 6(1)(c)) |
Under Tunisian law, we process your data with your consent, which you give when you create an account and pair a machine, and on the other grounds that Organic Law 2004-63 allows, such as performing our contract with you.
We do not sell your data. We do not use it for advertising. We do not make decisions about you by automated means that have legal or similarly significant effects.
6. Who receives your data
We use these service providers. They process data on our behalf and under our instructions.
| Provider | What for | Data |
|---|---|---|
| Google LLC and Google Ireland Ltd: Firebase and Google Cloud (Authentication, Realtime Database, Cloud Firestore, Cloud Storage, Cloud Functions, Cloud Messaging, App Check, Cloud Tasks, Cloud Logging) | Hosting the RenderBuddy service, sign-in, push notifications, security | Everything in sections 3.2 to 3.4 and 3.7 |
| Apple Inc. | Push notifications to iPhone (APNs); DeviceCheck | Push token, notification text, device integrity signals |
| Google (Play Integrity, ML Kit) | App integrity checks on Android; on-device QR scanning | Device integrity signals; ML Kit usage information |
| Netlify, Inc. | Website hosting | Visitor IP addresses and request logs |
| Google (Tag Manager and Google Analytics 4) | Website analytics, only with your consent | See the Cookie Policy |
| [[EMAIL_PROVIDER]] | Support email | Your emails |
| Tally BV (Belgium) | Bug-report form | What you submit in the form, and its files |
Other recipients:
- Discord is an independent service with its own privacy policy. When you report a bug, a copy of its title, description, steps and details is posted to our private Discord channel.
- Apple (App Store) and Google (Google Play) are independent services with their own privacy policies when you use them.
- Authorities, when the law requires us to disclose data.
- A buyer or successor, if PentaPixels SARL or RenderBuddy is sold or merged. We will tell you before your data falls under a different privacy policy.
7. Where your data is stored, and international transfers
Our cloud data is stored and processed by Google in the United States:
- Cloud Firestore: multi-region nam5 (United States);
- Realtime Database: United States (us-central1);
- Cloud Functions, Cloud Tasks: us-central1 (United States);
- Cloud Storage (previews): [[STORAGE_BUCKET_LOCATION]];
- Firebase Authentication and Cloud Messaging: Google's global infrastructure.
This means your data is transferred from Tunisia, the EU, the UK or your country to the United States.
- For users in the EU and UK: Google LLC is certified under the EU-U.S. Data Privacy Framework and its UK Extension, and Google's data processing terms for Firebase and Google Cloud include the European Commission's Standard Contractual Clauses. You can ask us for a copy of the safeguards at [[PRIVACY_CONTACT_EMAIL]].
- For transfers from Tunisia: Organic Law 2004-63 requires authorisation from the Instance Nationale de Protection des Données Personnelles (INPDP) for transfers abroad. Authorisation reference: [[INPDP_TRANSFER_AUTH_REF]].
Bug reports you send with the form are stored by Tally in the European Union. The copy posted to our Discord channel is stored by Discord in the United States. Discord relies on the EU-U.S. Data Privacy Framework and its UK Extension, and on the European Commission's Standard Contractual Clauses.
8. How long we keep your data
These are the retention periods as RenderBuddy works today.
| Data | How long |
|---|---|
| Account data (Google name, email, photo, IDs) | Until you delete your account |
| Machine record (name, hardware details, installed apps) | Until you unpair the machine or delete your account |
| Pairing (session) record, including your email | Until you unpair, someone else pairs the machine, or you delete your account. A pairing that lapses (the Agent was closed for more than 24 hours) stays stored but unusable until one of those happens |
| Machine credential (a hash of a secret only the Agent knows) | Until you unpair or pair again, or the Agent finds its pairing has lapsed, or you delete your account |
| Machine status, online state and live numbers | Replaced as they change; deleted when you unpair, the machine changes owner, or you delete your account |
| Events (for push notifications) | Deleted as soon as the notification is sent, normally within seconds. A small "already sent" marker is kept for about one hour. An event that can't be sent within 30 minutes is deleted without a notification |
| Commands you sent from the phone | Deleted by the app once it has the result. Otherwise deleted by the Agent once the command is more than 10 minutes old, the next time the Agent is connected, and at the latest when you unpair, the machine changes owner, or you delete your account |
| Watch entries | Removed when you leave the screen, the app goes to the background or your phone disconnects; ignored after 30 minutes |
| Job records (names, paths, settings, errors) | Until you unpair or remove that machine, or delete your account |
| Preview images | Replaced by the next preview. Deleted when a render finishes, when you unpair, when the machine changes owner, and when you delete your account. After a render fails or is stopped, the last preview stays until one of those happens |
| Push notification tokens | Until you sign out of the app on that phone, delete your account, or Firebase reports the token as no longer valid |
| Pairing codes | Expire after 10 minutes; deleted at the next daily clean-up |
| Rate-limit counters | Only attempts from the last hour count; counters are deleted at the next daily clean-up after that, so at most about 25 hours |
| Audit log (user or machine ID, event, time, shortened IP address, user agent) | 12 months, then deleted at the next daily clean-up |
| Deleted-account marker (former user ID, time) | Kept with no time limit, to prevent a deleted account from being recreated |
| Google Cloud server logs | About 30 days (Google Cloud's default) [[LOG_RETENTION]] |
| Database backups | [[BACKUP_RETENTION]] |
| Machine sign-in identities (see 9) | Each holds only a machine-based ID and sign-in times. It is replaced the next time the machine is paired, and deleted at the daily clean-up once the machine is unpaired or its pairing has lapsed for more than 24 hours |
| Support emails | As long as needed to handle your request, then [[SUPPORT_EMAIL_RETENTION]] |
| Bug reports (in Tally and our Discord channel) | Until the bug is closed, then deleted within 12 months. Tally removes deleted reports from its backups within 90 days |
| Website analytics (with consent) | 2 months for data about individual visits in Google Analytics. Aggregated reports, which don't identify visitors, are kept longer. |
Our commitment: we intend to delete lapsed pairings automatically. We will update this table when we do.
On your own devices:
- The Agent keeps, in
%APPDATA%\RenderBuddy, a pairing file encrypted by Windows for your user account (owner ID, machine ID, a restore secret and the encryption key), and a copy of the plugins' local access token for older plugins. In%LOCALAPPDATA%\RenderBuddyit keeps a machine secret, encrypted by Windows for your user account, from which the machine ID is derived, and the plugins' local access token and key (agent.lockandagent.key), made anew each time it starts. Uninstalling the Agent does not delete these files and does not unpair the machine: unpair first, or remove the machine in the phone app, then delete the folders. - The Agent's log is kept in memory only and is gone when the Agent closes, unless you save it with Save diagnostics… in the Agent's Help menu, which writes a text file where you choose and sends it nowhere.
- The phone app keeps one key for each paired computer in the iPhone Keychain or the Android Keystore-backed secure storage (excluded from backups), a random installation ID, your theme choice, a cache of your profile photo, and local caches kept by the Firebase SDKs, which hold the encrypted data and the readable information listed in section 4. Decrypted previews are kept in memory only. Signing out deletes the computers' keys, decrypted previews and the photo cache, and stops push notifications to that phone. The app does the same when your account is deleted or disabled from another device. The Firebase SDKs' caches and the installation ID stay until you uninstall the app.
9. How we protect your data
- Pairing uses single-use codes that expire after 10 minutes. We store only hashes of the codes.
- Each paired machine signs in with its own identity, limited to that one machine and that one pairing. Unpairing or pairing again cuts off the old identity at once. A machine can never act as your account.
- Security rules on our databases let only you, and the machines you paired, read your machines' data.
- What your PC reports about your work and your machine, and your preview images, are end-to-end encrypted with AES-256-GCM (see section 4). The key travels from your PC to your phone only inside the QR code or, for a phone you add, encrypted for that phone after you check the same six-digit code on both screens. Your phone refuses previews that are unencrypted, out of date (more than 15 minutes old) or encrypted with a different key, and doesn't show updates that fail their check.
- Preview images can only be downloaded through short-lived links (5 minutes) given to the machine's owner.
- The phone app uses Firebase App Check, so our servers accept requests only from the genuine app.
- On Windows, the Agent's pairing file is encrypted with Windows Data Protection (DPAPI) for your user account.
- The plugins can reach the Agent only on the same computer, and must present a random key that the Agent creates each time it starts.
- The Agent and the phone app connect to our cloud only over encrypted connections (TLS). The plugins' connection to the Agent never leaves your computer.
- Deleting your account requires a fresh Google sign-in, and machines cannot do it.
No system is perfectly secure. If a breach affects your data, we will notify you and the authorities as the law requires.
10. Your rights
You have the right to:
- access your data and get a copy of it;
- correct inaccurate data;
- delete your data;
- object to processing based on our legitimate interests;
- restrict processing in some cases;
- receive the data you gave us in a portable format (GDPR);
- withdraw your consent at any time, where we rely on consent, without affecting what was done before;
- lodge a complaint with a supervisory authority (see section 14).
Tunisian law (Organic Law 2004-63) also gives you the right to access, correct and oppose the processing of your data.
How to use your rights:
- Delete everything: in the phone app, open Settings, then Delete account. See section 11.
- Remove one machine: unpair it in the Agent, or remove it in the phone app.
- Rename a machine: on the machine's page in the app.
- Anything else: email [[PRIVACY_CONTACT_EMAIL]]. We may ask you to confirm your identity, for example by writing from the email address of your account. We answer within one month.
11. Deleting your account
In the phone app: Settings, Delete account. You confirm by typing DELETE and signing in with Google again. This deletes, straight away:
- your account and sign-in;
- all your machines, their pairing, status, online state, live numbers, events, commands, watch entries and preview images;
- your machine credentials, job records, installed-app records and push notification tokens;
- pairings that were still in progress.
Your Agents lose their pairing and show the pairing screen again.
What is kept after deletion:
- the audit log entries about your account, for up to 12 months, and an entry recording the deletion (user ID and time);
- rate-limit counters, which expire within about a day;
- the deleted-account marker (section 3.7);
- Google Cloud server logs, until they expire;
- the machine sign-in identities (section 9), until the next daily clean-up.
Data on your own devices (section 8) is not deleted by this. Delete the Agent's folders and uninstall the app to remove it.
12. Children
RenderBuddy is not directed at children under 16. We do not knowingly collect data from children under 16. If you believe a child has given us data, contact us and we will delete it.
13. Changes to this policy
We will post any change on this page and update the effective date. If a change matters to you, for example a new use of your data, we will tell you in the app or by email before it applies. Where the law requires your consent, we will ask for it.
14. Contact and complaints
Privacy questions: [[PRIVACY_CONTACT_EMAIL]]
Post: PentaPixels SARL, [[REGISTERED_ADDRESS]], Tunisia
You can complain to a supervisory authority:
- In Tunisia: the Instance Nationale de Protection des Données Personnelles (INPDP), www.inpdp.nat.tn.
- In the EU or EEA: the data protection authority of the country where you live or work. The list is at edpb.europa.eu.
- In the UK: the Information Commissioner's Office (ICO), ico.org.uk.
We would like the chance to answer your concern first, so please contact us.