Data Processing Agreement
Last updated: October 15, 2026
Version in force: 2026-10-15
This agreement is the appendix to the Terms of Sale required by Article 28 of Regulation (EU) 2016/679 (“GDPR”). It is accepted together with the Terms of Sale, by an administrator of the customer organisation. “Customer” means the organisation identified in the RhinoQR account, acting as controller; “Provider” means the Publisher as identified in the Legal notice, acting as processor.
1. Purpose
This agreement governs the processing of personal data carried out by the Provider on behalf of the Customer under the Terms of Sale in force (the “Main Agreement”).
In the event of a conflict, this agreement prevails over the Main Agreement in all matters concerning the protection of personal data.
2. Description of the processing
Nature and purpose
Hosting and operation of an industrial item-tracking application: user account management, traceability of production operations, storage and consultation of documents and 3D models, collaborative annotations, notifications.
Data subjects
The users designated by the Customer: its employees, its temporary staff and, where applicable, external contributors to whom it grants access.
Categories of data processed
- Identification: sign-in identifier, display name, role, organisation membership.
- Authentication: password hash and salt (scrypt), encrypted TOTP secret (AES-256-GCM), backup codes, session token hashes — never the tokens themselves.
- Technical logs: IP address, user agent, timestamp, action performed, identifier and name of the person who performed it.
- Production activity: QR code scans, status changes, production events carrying the operator's name.
- Uploaded content: documents, photographs, 3D models and annotations — which may incidentally contain personal data, depending on what the Customer uploads.
- Plain-language search, if the organization enables it: the text of the questions asked, sent to be turned into filters and not stored by the Service.
- Billing: data transmitted to the payment provider; the Service stores no card number.
No special category data within the meaning of Article 9 GDPR is processed, and the Service is not designed to receive any. No profiling, no automated decision-making within the meaning of Article 22, no audience measurement, no advertising tracker.
The processing lasts as long as the Main Agreement, subject to the retention periods in Article 6.
3. Provider obligations
The Provider undertakes to:
- process the data only on the Customer's documented instructions, and solely to perform the Main Agreement;
- inform the Customer if it considers an instruction to infringe the GDPR;
- ensure the confidentiality of the data and that every person authorised to access it is bound by a confidentiality obligation;
- implement the technical and organisational measures described in Article 11;
- assist the Customer in responding to data subject requests (Article 5);
- notify any data breach in accordance with Article 7;
- assist the Customer in maintaining its record of processing and, where applicable, in carrying out an impact assessment;
- delete or return the data at the end of the Main Agreement (Article 8);
- make available to the Customer the information needed to demonstrate compliance with this agreement.
4. Sub-processors
The Customer authorises the use of the following sub-processors. This list is exhaustive as at the version date of this agreement and was established by reading the source code, not inferred from declared dependencies.
- Vercel Inc. — application hosting, route execution and scheduled jobs (United States). Data transmitted : all application traffic.
- Neon, LLC — PostgreSQL database (a Databricks group company) (United States). Data transmitted : all metadata, accounts and logs.
- Cloudflare, Inc. — storage of uploaded files (Cloudflare R2) and bot protection on the sign-in form (Turnstile) (United States). Data transmitted : uploaded files; interaction with the sign-in form.
- Stripe Payments Europe, Limited — payment and invoicing (Ireland, with transfers covered by a dedicated addendum). Data transmitted : billing details and subscription status. Card numbers never pass through the Service.
- Functional Software, Inc. (Sentry) — technical error logging and performance measurement (data hosted in the European Union (EU region); provider established in the United States). Data transmitted : error traces and load timings, with no personal data and no session recording (`sendDefaultPii: false`).
- Resend (Plus Five Five, Inc.) — service email delivery: signup link, password reset (United States, with processing in the European region (Ireland) for this account). Data transmitted : the recipient's email address and the message body. No workshop content, no documents.
- Mistral AI — part recognition and plain-language search — optional features, disabled by default (France). Data transmitted : for recognition, only a part's geometric summary (detected shape, dimensions, material, standard designation); for search, the text of the question as typed and the list of offered filters. No file, no raw geometry, no project, piece or layer name, no search result.
What does not leave
Fonts are downloaded at build time and served from the Service's own domain: no browser call to a third party. No audience-measurement or advertising-tracking tool is used.
Transfers outside the European Union
Vercel Inc.; Neon, LLC; Cloudflare, Inc.; Functional Software, Inc. (Sentry); and Resend (Plus Five Five, Inc.) are United States companies. These transfers are covered by the European Commission's standard contractual clauses and, where applicable, by the recipient's participation in the EU–US Data Privacy Framework. The corresponding agreements are archived by the Provider and shared with the Customer on request, as is the hosting region selected with each of them.
Change of sub-processor
The Provider informs the Customer of any planned addition or replacement of a sub-processor with thirty (30) days' notice, allowing the Customer to object. Where the change is imposed by an infrastructure provider that itself grants only a shorter notice period, the information is given without delay once known, if necessary after the change takes effect; the Customer's right to object remains intact. In the event of a legitimate objection, either Party may terminate the Main Agreement without compensation.
5. Data subject rights
The Provider assists the Customer in handling requests. The actual state of the available means, without embellishment:
- Access and portability: an administrator of the Customer may at any time export all of their organisation's data, in JSON, from the application. A complete archive including the files themselves is provided by the Provider on request.
- Rectification: directly by an administrator of the Customer, within the application.
- Erasure: account deletion by an administrator of the Customer.
- Restriction: account deactivation by an administrator of the Customer.
- Objection: not applicable, as the processing is based on performance of the contract and not on legitimate interest.
A caveat to be aware of regarding erasure: the name of the person who performed an action survives as a copy in the audit log and in production events, until their retention period expires. This retention is justified by the security of the Service and by the integrity of the manufacturing history, and it is capped at 12 months for the audit log.
The Provider never responds directly to a data subject: it forwards the request to the Customer, the sole controller.
6. Retention periods
Periods actually enforced, by a daily scheduled job:
- Audit log (IP address, user agent, author name): 12 months.
- Sign-in attempts (IP address, identifier), successful and failed alike: 12 months.
- Expired sessions: purged daily.
- Deleted items (trash): 30 days, then permanent purge including stored files.
- Active accounts and content: for the duration of the Main Agreement, then Article 8.
7. Data breach
The Provider notifies the Customer of any data breach within twenty-four (24) hours of becoming actually aware of it, so as to allow the Customer to meet its own 72-hour deadline towards the supervisory authority.
The notification states, as far as available: the nature of the breach, the categories and approximate number of data subjects and records concerned, the likely consequences, the measures taken or proposed, and the contact point's details.
The Provider documents every breach, including those it does not consider notifiable, and keeps that documentation available to the Customer.
Detection means actually in place: an audit log covering more than 70 action types; anomaly detection (sign-in from a new country or new IP address, bursts of scans outside working hours, mass export, serial account creation, sign-out of an administration account); sign-in attempt rate limiting; monitoring of application errors, and of both the failure and the silence of backups.
8. Fate of the data at the end of the contract
At the end of the Main Agreement, the Customer chooses, within thirty (30) days, either the return of its data in a structured, commonly used format followed by its deletion, or its immediate deletion. Failing a choice within that period, the Provider proceeds with deletion.
Deletion covers the database and the stored files. Existing backups are erased by rotation within a maximum of three (3) months (twelve weekly backups retained). The Provider issues a deletion certificate on request.
9. Audit
The Customer may, once a year and at its own expense, after thirty days' notice, have compliance with this agreement verified. The Provider may satisfy this obligation by sharing its technical documentation and the results of its automated checks.
10. Acceptance, version and governing law
This agreement is concluded electronically, as Article 28(9) GDPR expressly permits. It is accepted by an administrator of the customer organisation, the only person entitled to bind the controller; the date, the accepted version and the IP address of the acceptance are retained.
Every version carries a dated identifier and remains available at its own address after being superseded: an acceptance therefore never points to a text that can no longer be found. Any new version requires a fresh acceptance.
This agreement is governed by French law. Any dispute falls to the courts designated in the Legal notice.
11. Technical and organisational measures
The measures below are verified in the source code. None of them is merely declarative.
Separation of customer data
PostgreSQL row-level security, in forced mode, on 30 tables carrying customer data. Isolation is enforced by the database itself rather than by application code: a query with no scope set returns no rows, instead of returning another customer's. Bypassing it is restricted to explicitly named, identifiable code paths, used only for cross-cutting operations.
Authentication
- Passwords: scrypt, a distinct salt per user, constant-time comparison so that verification time reveals nothing.
- TOTP two-factor authentication available, secret encrypted with AES-256-GCM at rest, single-use backup codes.
- Attempt rate limiting: 5 per IP address over 15 minutes, 10 per account over 30 minutes.
- Bot protection on the sign-in form.
- Sessions via HttpOnly, Secure, SameSite cookies, with expiry; only the token hash is stored.
Encryption
- In transit: HTTPS enforced, with two-year HSTS, subdomains included and preload.
- At rest: encryption provided by the database and file storage hosts.
- Browser offline cache: encrypted with AES-256-GCM, the key being derived server-side from the session token — a lost device does not surrender the data cached for shop-floor work.
File access
No file is served publicly. Every access goes through a short-lived signed URL: 5 minutes for reads, 10 minutes for writes. An upload's size is signed into the URL and then re-checked against the object actually stored.
Application security
- Nonce-based Content Security Policy, with no “unsafe-inline” directive and a distinct nonce per request.
- X-Frame-Options: DENY, Referrer-Policy and Permissions-Policy headers.
- A four-level role hierarchy, checked at the entry of every route.
- Schema validation of incoming data for exchange formats.
- Automated dependency monitoring and a security audit on every integration.
Traceability
- An audit log covering more than 70 action types, with author, IP address, user agent and timestamp.
- Document views and downloads are logged, not just modifications.
- Support access to Customer data is traceable: identity impersonation is governed by a signed token valid for 15 minutes, impossible towards another administration account, and logged at both its start and its end.
- Anomaly detection: new country or new IP address at sign-in, bursts of scans outside working hours, mass export, serial account creation.
Backup and continuity
- Weekly database backup to separate object storage, 12 archives retained (about three months).
- Password hashes are excluded from backups: a stolen archive yields no authentication material.
- Monitoring of failure and of silence: a failure is reported and logged, and the absence of a backup is detected by a daily freshness check — the only way to see a job that no longer runs, since it raises no error.
- Tooled and proven restoration: an automated procedure restores a backup into a disposable database and compares the data row by row against the source.
- An inventory of stored files is embedded in every backup and checked against the actual storage contents: a reference pointing to a vanished file is detected and reported.
Acknowledged limitations
Stated deliberately: a serious customer would find them out, and it is better that they read them here.
- Database backups do not contain the bytes of the files (3D models, PDFs, photographs), but their complete inventory. A copy of the files themselves is tooled and being put into service.
- No guarantee of point-in-time consistency between the database and the stored files.
- No contractual service level (availability, restoration time) is committed to at this stage. The Service relies on its hosts' infrastructure, with no additional redundancy.