A concise beta-facing summary of what Collabrador processes, what stays local, and where the limits of Free, Playground, Webviewer, and paid workflows are.
Choose what you share. Control who can join.
Operator and media owner: Alexander Grasser-Parger, Staudgasse 76, 1180 Vienna, Austria. contact@collabrador.live.
This website explains Collabrador and provides a space for public collaborative design contributions and discussion. Report content, request review or find the authority contact point. Reports do not require an account or a purchase.
Collabrador is a realtime collaboration tool for Rhino and Grasshopper. When users join a Design Session, they decide which workspace to enter and which model data to share. The service is designed to use pseudonymous identifiers where possible and to avoid collecting personal data that is not needed to operate the collaboration service.
Data published from Rhino travels through Cloudflare to participants in the selected workspace and to viewers granted access. Cloudflare hosts the website and operates the collaboration backend, including Workers, Durable Objects, KV and R2. Shared geometry and its metadata may contain personal information if users include it in their models. Playground and Pinboard content is public; workspace passwords, invitations and access links determine access to protected sessions.
Service and account data is processed to provide the requested collaboration functions and access, and to enforce usage limits, prevent abuse and maintain service security. Contractual processing relies on Article 6(1)(b) GDPR where necessary for a contract or requested pre-contractual steps; necessary security and abuse prevention rely on legitimate interests under Article 6(1)(f). Customers must have an appropriate basis for any personal data they choose to share in project content.
The collaboration and diagnostics R2 buckets currently report Eastern Europe; website media reports Western Europe. Their jurisdiction is set to default, rather than an enforced EU jurisdiction. This is not a promise that the entire service processes data only in the EU. Cloudflare's global network, collaboration participants and other providers may process data outside the EEA. Cloudflare describes its processing terms and international-transfer safeguards in its Data Processing Addendum.
Rhino Hide / Show / Isolate state, display modes, viewport choices, and ordinary local files remain local. Local saved-session archives, if explicitly created by a user, remain on that user's machine and are not deleted by server-side room retention.
Collabrador uses TLS for transport. Current beta builds also use payload encryption modes for collaboration payloads, but the protection level depends on the workspace type.
Free normal workspaces use basic encrypted payloads. If a workspace password is set, that password is used for payload encryption. If no password is set, the workspace name is used as a fallback secret. This reduces casual plaintext exposure, but it is not confidential or NDA-grade protection.
Beta, workshop, and paid workspaces require workspace-password-based encrypted collaboration payloads and use license/seat-token boundaries. Free users, revoked seats, expired seats, or seats from another license cannot enter a license-bound workspace.
The Webviewer can make a design session visible outside Rhino, but it is not DRM. Playground and Pinboard are public or public-facing spaces and should not be used for confidential, client, competition, NDA, personal, or secret project material.
Current beta defaults: Free rooms are retained for 24 hours. Beta Pair, Beta Studio, Pro Team, and Pro Studio rooms are retained for 336 hours. Workshop rooms are retained for 96 hours. Admin/support rooms are retained for 720 hours. Playground live room state is currently ephemeral in this deployment. Pinboard posts and comments are retained for 24 hours.
Diagnostics reports may be retained for up to 7 days. Pseudonymous activity/quota and admin-history exports may be retained for up to 6 months. Sparse paid security audit rows are retained through the current license or validity period. At that boundary they are excluded from protected audit reads and are physically removed by bounded daily maintenance; migration or a due backlog can require subsequent daily cycles, and failures remain visible to operators.
Cached snapshots, hydrate packs, viewer meshes, and similar helper artifacts are not intended as long-term archives. They are cleared through room reset, share-layer removal, rebuild replacement, explicit purge flows, or normal room retention cleanup.
This direct-url page is not a full Terms of Service. For beta use, the basic rules are:
For general enquiries, technical support, privacy questions, data export/deletion requests, or admin reset requests, email contact@collabrador.live.
Support email is handled through Google Workspace. Google processes sender/recipient addresses, message contents, attachments and associated email metadata to deliver and store correspondence. We use this information to answer your request and retain it for as long as needed to resolve the enquiry and meet any related legal obligations. Google Workspace has separate processing and regional settings; the Cloudflare bucket locations do not determine where email is processed. See Google's Cloud Data Processing Addendum.
Describe the request briefly. For technical issues, include your Collabrador and Rhino versions and the steps that led to the problem. A license ID or purchase reference can help locate records. Do not email passwords, access tokens, credential files, or confidential models.
Before disclosing records or making account or workspace changes, we verify your authority for the specific request. We will explain the available action and any limits, including local copies and separately retained billing records.
For paid workflows, customer identity and billing records are expected to remain mainly in Stripe, while Collabrador stores operational license and seat metadata.