DRAFT – not legal advice. This document is a working draft template for founder and lawyer review. It is not in force, may be incomplete or wrong, and must not be relied on until reviewed by a qualified lawyer. Text in [SQUARE BRACKETS] is a placeholder.

Data Processing Agreement

Last updated: 11 November 2026 (draft)

This Data Processing Agreement ("DPA") forms part of the Terms of Service (the "Agreement") between [OPERATING ENTITY], [ADDRESS], [REGISTRY NUMBER] (the "Processor") and the customer identified in the account or order (the "Controller"). It applies to the extent the Processor processes personal data on behalf of the Controller when providing cadshot (the "Service"), and is intended to meet Article 28(3) of Regulation (EU) 2016/679 ("GDPR"). [DECISION: whether this DPA is accepted automatically with the Terms or signed separately on request.]

1. Definitions and roles

Terms such as "personal data", "processing", "controller", "processor", "data subject" and "personal data breach" have the meanings given in the GDPR. "Customer Data" means the files submitted to the Service for rendering and the images produced from them. "Customer Personal Data" means any personal data contained in Customer Data.

For Customer Personal Data the customer is the Controller (or a processor acting for its own controller, in which case the Processor acts as sub-processor and the customer passes on that controller's instructions) and [OPERATING ENTITY] is the Processor. This DPA does not cover account, billing and log data, for which [OPERATING ENTITY] is an independent controller as described in the Privacy Policy.

2. Details of the processing

ItemDescription
Subject matterRendering of 3D/CAD files into images through the Service
DurationThe term of the Agreement. Each input file is processed only for the duration of its render; each output is cached for at most 30 days.
Nature and purposeReceiving or fetching a file, parsing it, rendering it to a PNG image, returning the image, and caching the image so identical requests can be served again. No other purpose.
Types of personal dataThe Service is not designed to process personal data. Customer Data may incidentally contain it, for example author, organisation or device names in file metadata, names or text modelled or embossed in geometry, or models depicting an identifiable person (such as 3D scans).
Special categoriesNone intended. The Controller will not submit special categories of data (Art. 9 GDPR) or data relating to criminal convictions (Art. 10 GDPR) unless agreed in writing.
Categories of data subjectsDetermined by the Controller; typically the Controller's employees, contractors, customers or other persons referred to or depicted in the files.

3. Controller's instructions

The Processor processes Customer Personal Data only on the Controller's documented instructions, including with regard to transfers to a third country, unless EU or member state law requires otherwise; in that case the Processor informs the Controller before processing unless that law prohibits it. The Agreement, this DPA and the Controller's API requests and dashboard settings are the Controller's complete instructions. The Processor will inform the Controller if, in its opinion, an instruction infringes the GDPR or other EU or member state data protection law.

The Processor does not use Customer Data to train machine-learning models, for analytics, for profiling or for any purpose of its own.

The Controller is responsible for the lawfulness of the processing it instructs, including having a legal basis and giving any required information to data subjects.

4. Confidentiality

The Processor ensures that persons authorised to process Customer Personal Data are bound by confidentiality obligations and access the data only as needed to operate the Service. In normal operation rendering is fully automated and no person views Customer Data.

5. Security

The Processor implements the technical and organisational measures described in Annex 1, taking into account the state of the art, the costs of implementation, the nature, scope, context and purposes of processing and the risks to data subjects (Art. 32 GDPR). The Processor may update the measures provided the overall level of protection is not reduced.

6. Sub-processors

The Controller gives general authorisation for the Processor to engage the sub-processors listed on the Subprocessors page. The Processor will announce any intended addition or replacement on that page and by email to the account address at least [30] days in advance. The Controller may object on reasonable data protection grounds within [14] days; if the parties cannot resolve the objection, the Controller may terminate the affected Service and receive a refund of prepaid fees for the unused period.

The Processor imposes on each sub-processor data protection obligations no less protective than those in this DPA and remains liable to the Controller for the sub-processor's performance.

7. International transfers

Customer Data is processed and stored in the European Union. The Processor will not transfer Customer Personal Data outside the European Economic Area unless the conditions of Chapter V GDPR are met, for example through an adequacy decision or the European Commission's standard contractual clauses. [TO CONFIRM against the final sub-processor list, in particular for any CDN that carries API traffic.]

8. Assistance to the Controller

Taking into account the nature of the processing and the information available to it, the Processor will:

[DECISION: whether assistance beyond the standard features of the Service is chargeable at reasonable rates.]

9. Personal data breach

The Processor will notify the Controller without undue delay, and in any event within 72 hours, after becoming aware of a personal data breach affecting Customer Personal Data. The notification is sent to the account email address and will describe, as far as known, the nature of the breach, the categories and approximate volume of data concerned, the likely consequences and the measures taken or proposed. Information may be provided in stages. The Processor will take reasonable steps to contain and remedy the breach and will cooperate with the Controller's own notification duties. A notification is not an admission of fault or liability.

10. Deletion and return

Input files are deleted automatically when the render ends. Cached outputs expire automatically no later than 30 days after creation. Because of these short periods, return of data is achieved by the Service delivering each output in the API response; the Controller should keep its own copies. On termination of the Agreement no further action by the Controller is required: any remaining cached outputs expire within 30 days, and the Processor keeps no copies unless EU or member state law requires storage. [DECISION: whether to offer a cache purge on request before expiry.]

11. Information and audits

The Processor makes available to the Controller the information necessary to demonstrate compliance with Article 28 GDPR, including this DPA, Annex 1 and, where available, relevant third-party reports or certifications of its hosting providers.

Where that information is not reasonably sufficient, the Controller, or an independent auditor it mandates who is bound by confidentiality and is not a competitor of the Processor, may carry out an audit, including an inspection, no more than once in any 12 months (or more often where a supervisory authority requires it or after a personal data breach), on at least [30] days' written notice, during business hours, and without unreasonably disrupting operations or compromising the security of other customers' data. Each party bears its own costs unless the audit reveals a material breach of this DPA. [LAWYER TO CONFIRM cost allocation.]

12. Liability, term and precedence

Liability under this DPA is subject to the limitations in the Agreement, without limiting either party's liability to data subjects or authorities under the GDPR. This DPA applies for as long as the Processor processes Customer Personal Data. If this DPA and the Agreement conflict on the processing of personal data, this DPA prevails. Governing law and jurisdiction follow the Agreement: [GOVERNING LAW — e.g. Polish law, courts of Warsaw].

Annex 1 – Technical and organisational measures

AreaMeasure
Process isolationEach render runs in its own isolated worker process with limits on memory, CPU time (10 seconds per render), input size and triangle count. A failure or compromise in one render does not expose another customer's data.
No network for workersRender workers have no network access. Files requested by URL are fetched by a separate component that accepts only http(s) and refuses private, loopback and link-local addresses.
Encryption in transitAll traffic to the API, dashboard and website uses TLS. [TO CONFIRM: minimum TLS version; encryption between internal components and to object storage.]
Encryption at rest[TO CONFIRM: whether the output cache and database are encrypted at rest.]
CredentialsAPI keys are stored only as hashes and shown once on creation. Sign-in uses single-use emailed links; no passwords are stored. Keys can be revoked at any time.
Data minimisation and deletionInput files are held in memory or temporary storage only for the duration of the render and then deleted. Outputs are cached for at most 30 days under a hash of file and parameters and expire automatically. Logs are kept at most 30 days and never contain file contents or file names.
Hosting locationCompute and storage are located in data centres in the European Union.
Access controlAdministrative access to production systems is limited to authorised personnel, uses individual credentials and [multi-factor authentication / SSH keys – TO CONFIRM].
Payment dataCard data is collected and processed by the payment provider and never reaches the Processor's servers.
Software integrityThe rendering core uses its own parsers and encoders with no third-party code; third-party components are limited and tracked in the third-party notices. Security updates are applied [within a defined period – TO CONFIRM].
Incident handling[TO CONFIRM: documented incident response and breach notification procedure; backup and restore procedure for account data.]

Annex 2 – Sub-processors

See the Subprocessors page, which is incorporated into this DPA.