Data Processing Addendum
Version 2026-06-22 · Last updated June 22, 2026
This Data Processing Addendum (“DPA”) forms part of the agreement between the customer (“Controller”) and Crossary(operated as a sole trader, “Processor”, “we”) for use of Crossary, and governs our processing of personal data on your behalf. Enterprise customers may require a counter-signed copy or their own paper — contact support@crossary.com.
1. Roles
The Controller determines the purposes and means of processing. We act as Processor, processing personal data only on the Controller’s documented instructions (including via the product’s features) and as described in these terms and the Privacy Policy.
2. Subject matter, duration, nature and purpose
We process personal data to provide Crossary: ingesting uploaded specification artifacts, extracting field inventories, generating and storing mapping suggestions, and producing exports. Processing lasts for the duration of the Controller’s account, unless otherwise required by law.
3. Categories of data and data subjects
Personal data is whatever the Controller includes in account details and uploaded content. Data subjects may include the Controller’s users, team members, and any individuals referenced within uploaded artifacts. The Controller is responsible for ensuring it has a lawful basis to upload such content.
4. Our obligations
- process personal data only on documented instructions;
- ensure personnel with access are bound by confidentiality;
- implement appropriate technical and organizational security measures (see section 7);
- assist the Controller, taking into account the nature of processing, with data-subject requests and with security, breach-notification, and impact-assessment obligations.
5. Subprocessors
The Controller authorizes our use of the subprocessors listed on the Subprocessors page. We impose data-protection obligations on each subprocessor and remain responsible for their performance. We will inform the Controller of intended changes and allow a reasonable opportunity to object on data-protection grounds.
6. Data-subject requests
Where a data subject contacts us directly, we will refer them to the Controller. We will provide reasonable assistance to help the Controller respond to access, rectification, erasure, portability, and objection requests.
7. Security measures
We maintain measures including: passwords hashed with bcrypt; encryption in transit (TLS); EU-hosted storage and database; tenant isolation; authentication rate-limiting; and error monitoring. A fuller description is available on request.
8. Personal data breach
We will notify the Controller without undue delay after becoming aware of a personal data breach affecting the Controller’s data, and provide information reasonably available to assist the Controller’s own notification obligations.
9. Return and deletion
On termination, or on the Controller’s request, we delete the Controller’s personal data. Account deletion cancels any active subscription and removes workspaces, projects, integrations, uploaded artifacts, and exports, including the underlying stored files, subject to limited retention required by law and routine backup cycling. The Controller can also delete individual integrations or projects in-product at any time, which erases their data and stored files.
10. Audits
We will make available information reasonably necessary to demonstrate compliance with this DPA and contribute to audits as required by applicable law, subject to reasonable confidentiality and security safeguards.
11. International transfers
Where processing involves transfers outside the European Economic Area, we rely on appropriate safeguards such as the EU Standard Contractual Clauses and/or the EU–US Data Privacy Framework where the recipient is certified.
12. Precedence and governing law
In the event of a conflict between this DPA and the Terms of Service on data-protection matters, this DPA prevails. This DPA is governed by the law of Portugal.