PRIVACY POLICY
Effective date: 15.07.2026
Last updated: 25.07.2026
This Privacy Policy explains what personal data we collect when you use the Rhino.Ecologic® plug-in (currently a free beta) and related services, why we collect it, how long we keep it, who we share it with, and what rights you have. It is a companion to the Rhino.Ecologic End-User License Agreement (EULA); where the two touch on data protection, this Policy governs.
We are committed to complying with the General Data Protection Regulation (GDPR) (EU) 2016/679 and applicable national data-protection laws.
1. Who We Are (Data Controller)
The data controller responsible for your personal data is McNeel Europe S.L.
- Postal address: McNeel Europe S.L.Roger de Flor, 32-34, local, 08018 Barcelona, Spain
If you have questions or wish to exercise your rights, contact us using the details above.
2. Scope
This Policy applies to personal data processed through the Rhino.Ecologic plug-in, its authentication and licensing services, and its related online infrastructure. Because the current version is a free beta, it collects detailed technical and usage data to support testing, compatibility, security, and product improvement, as described below.
3. What Data We Collect and Why
3.1 Account & identity information
When you create an account we collect your email address (to identify your account and communicate with you) and your first and last name (to personalise your account). Legal basis: performance of a contract (Art. 6(1)(b) GDPR).
3.2 Professional & demographic information
We collect your organisation, profession, discipline, industry, and country to understand how the software is used professionally, tailor support, and provide region-appropriate features. Legal basis: your consent (Art. 6(1)(a) GDPR), which you may withdraw at any time.
3.3 Account metadata
We record your account status (e.g. active, pending, suspended, revoked), your access role (e.g. admin, user, viewer), and how you first signed up (signup source, such as an invitation link or registration campaign). Legal basis: performance of a contract (Art. 6(1)(b) GDPR) for status and role; legitimate interests (Art. 6(1)(f) GDPR) for understanding how users discover the product.
3.4 Authentication & security logs
Each time you log in or attempt to, we record whether it succeeded or failed (and the reason for failure), together with the timestamp. We use this to protect your account and detect security incidents. Legal basis: legitimate interests (Art. 6(1)(f) GDPR); and, where applicable, legal obligation (Art. 6(1)(c) GDPR).
3.5 Session data
During an active session we collect your IP address, approximate location (city and country) derived from your IP, timezone, client/browser user-agent, session start and end times, and your software environment, the versions of .NET, Rhino, Grasshopper, the Rhino.Ecologic plug-in, and the ecological model data in use. We use this to maintain your session, provide support, and ensure compatibility. Legal basis: performance of a contract (Art. 6(1)(b) GDPR); legitimate interests (Art. 6(1)(f) GDPR) for security and compatibility.
3.6 Device information
To verify that you are using an authorised device and to prevent licence misuse, we collect a technical profile of your device:
- a device fingerprint, stored in hashed (pseudonymous) form;
- machine ID and hardware UUID: operating-system-level identifiers;
- MAC address, stored in hashed (pseudonymous) form;
- hardware specifications: CPU model and core count, total RAM, GPU model and VRAM;
- operating system: type, version, build, and architecture.
We use this only for device verification and a consistent licence experience across your machines. Hashing reduces exposure but does not remove GDPR applicability: these identifiers, and the device profile as a whole, remain personal data because they can be linked to you through your account. Legal basis: legitimate interests (Art. 6(1)(f) GDPR) — licence integrity and fraud prevention.
3.7 Usage data
Each time you run an ecological analysis, we collect usage metrics linked to your session: project names and file-path/location identifiers, voxel counts, analysis and simulation durations, whether runs failed, and whether a custom plant library was used. We use this to improve the software, understand professional use, and diagnose performance issues. Legal basis: performance of a contract (Art. 6(1)(b) GDPR); legitimate interests (Art. 6(1)(f) GDPR) for product improvement.
Please note: project names and locations are supplied by you and may contain personal or sensitive information. We recommend using neutral project names that do not include names of individuals or sensitive location details.
3.8 API keys
If you create API keys, we store the name you give each key and its last-used and expiry dates. We store only a cryptographic hash of the key itself; the raw key is never retained after creation. Legal basis: performance of a contract (Art. 6(1)(b) GDPR).
3.9 Administrative audit logs
When our authorised personnel perform administrative actions, we log those actions together with the IP address of the person performing them, for security and accountability. Legal basis: legitimate interests (Art. 6(1)(f) GDPR); legal obligation (Art. 6(1)(c) GDPR) where applicable.
4. How Long We Keep Your Data
| Data category | Retention period |
| Account & identity information | While your account is active, plus 30 days after deletion |
| Account metadata (status, role, signup source) | While your account is active, plus 30 days after deletion |
| Authentication & security logs | 12 months |
| Session data | 12 months |
| Device records | While the device is associated with your account |
| Usage logs | 24 months, then aggregated and anonymised |
| API-key records | Until the key expires or you revoke it |
| Administrative audit logs | 24 months |
We review retention periods periodically and delete or anonymise data that is no longer needed.
5. Who We Share Your Data With
We do not sell your personal data. We may share it with:
- Infrastructure providers : cloud hosting and database services used to operate the platform, acting as data processors under GDPR and bound by data-processing agreements;
- Security and fraud-prevention services to protect the integrity of the service;
- Legal authorities where required by law or to protect the rights, property, or safety of McNeel, our users, or others.
6. International Transfers
Where personal data is transferred outside the European Economic Area (EEA), for example, to an infrastructure provider, we put appropriate safeguards in place, such as the European Commission’s Standard Contractual Clauses.
7. Your Rights Under GDPR
| Right | What it means |
| Access (Art. 15) | Request a copy of the personal data we hold about you. |
| Rectification (Art. 16) | Ask us to correct inaccurate data (name, email, organisation, country, professional details). |
| Erasure (Art. 17) | Ask us to delete your personal data, unless we must retain it by law (e.g. certain security or audit logs). |
| Restriction (Art. 18) | Ask us to pause processing in certain circumstances. |
| Portability (Art. 20) | Receive the data you provided in a machine-readable format. |
| Object (Art. 21) | Object to processing based on legitimate interests, including device tracking and usage analytics. |
| Withdraw consent (Art. 7(3)) | Withdraw consent for professional/demographic data at any time, without affecting prior lawful processing. |
To exercise any right, contact us at [privacy contact email]. We will respond within one month (Art. 12(3) GDPR). You also have the right to lodge a complaint with your local supervisory authority.
8. Security
We protect your personal data using industry-standard measures, including:
- passwords and API keys stored only as cryptographic hashes — raw values are never stored;
- device identifiers (MAC address, fingerprint) stored in pseudonymous hashed form;
- access to personal data restricted to authorised personnel and audit-logged;
- all administrative actions recorded in an audit log.
No method of transmission or storage is completely secure, and as beta software the service may carry additional risk; we work to protect your data but cannot guarantee absolute security.
9. Children
Rhino.Ecologic is a professional design tool intended for use by adults and is not directed at children. We do not knowingly collect personal data from children under the age of 16 years.
10. Changes to This Policy
We may update this Policy from time to time. When we do, we will update the “last updated” date above and, where changes are significant, notify you by email or through the application.
11. Contact
Address: McNeel Europe S.L.Roger de Flor, 32-34, local, 08018 Barcelona, Spain
You may also contact your local data-protection authority to lodge a complaint.

© 2026 McNeel Europe S.L. All rights reserved.
