Legal
Legal
Our commitments as your processor under Article 28 GDPR, with the security measures and transfer clauses.
Effective Version 1.0
This Data Processing Agreement ("DPA") sets out how Colchix processes personal data for its customers, as Article 28 of the GDPR requires. It forms part of our Terms of Service and every Order Form, with no separate signature needed. If you'd like a countersigned copy for your records, tick "Signed DPA" in the security pack on our Security & deployment page, or write to privacy@colchix.com.
This DPA applies whenever Colchix B.V. ("Colchix", "we") processes personal data contained in Customer Data on behalf of the customer ("Customer", "you") while providing the Service. For that data, you are the controller and we are your processor. Where you are yourself a processor for another controller, we are your sub-processor, and you confirm that controller has authorized our appointment.
Terms such as personal data, processing, controller, processor, data subject and personal data breach have their meaning in the GDPR. "Data Protection Law" means the GDPR and the laws implementing or supplementing it, and, where they apply, the UK GDPR and the Swiss Federal Act on Data Protection (FADP). Other capitalized terms have their meaning in the Terms.
What we process, about whom, for what and for how long is described in Annex I.
We process personal data only on your documented instructions. The agreement, your configuration of the Service (which agents you enable, which devices you enroll, your retention plan, your policies) and your use of its features are your instructions. Further instructions must be in writing and consistent with the agreement.
We don't process personal data for any other purpose, unless EU or member state law requires it; in that case we tell you first, unless that law forbids it. We tell you immediately if we believe an instruction infringes Data Protection Law.
We don't use personal data in Customer Data to train AI models, ours or anyone else's, and we don't sell it or use it for advertising.
Everyone at Colchix authorized to process personal data is bound by confidentiality, by contract or by law, and receives access only where needed to run, support or secure the Service.
We implement and maintain the technical and organizational measures in Annex II, to ensure a level of security appropriate to the risk, as Article 32 GDPR requires. We may update them as technology and threats evolve, provided the overall level of protection is not reduced.
General authorization. You authorize us to engage sub-processors. Our current sub-processors are listed on our Sub-processors page, which is Annex III to this DPA.
Changes. We tell you at least 30 days before we add or replace a sub-processor, by email to your account's owners and on that page. You may object on reasonable data protection grounds within 15 days of our notice. We'll then work with you in good faith on an alternative; if we can't find one within 30 days, you may end the affected part of the Service, and we refund the prepaid fees for the remaining term.
Their obligations. Each sub-processor is bound by a written agreement with data protection obligations no less protective than this DPA. We remain responsible to you for their performance.
Taking into account the nature of the processing, we help you:
We notify you without undue delay, and at the latest within 48 hours after becoming aware of a personal data breach affecting your personal data. As far as we know it at the time, our notice describes the nature of the breach, the categories and approximate number of data subjects and records concerned, the likely consequences, and the measures taken or proposed; we complete it as we learn more.
We take reasonable steps to contain the breach, investigate it and limit its effects, and we cooperate with you in notifying authorities and data subjects where you must. Our notice is not an admission of fault.
Location. For Service deployments run by Colchix, personal data is hosted on Google Cloud in the Netherlands (region europe-west4), unless your Order Form names another region. Where the Service runs in your own cloud account or data center, the data stays in your environment, and we access it only as you allow, for support.
Transfers. We transfer personal data outside the European Economic Area only with appropriate safeguards under Chapter V GDPR. Where a sub-processor or Colchix staff access personal data from a country without an adequacy decision, the European Commission's standard contractual clauses (Implementing Decision (EU) 2021/914) apply, Module 3 (processor to processor), or the sub-processor's certification under the EU–US Data Privacy Framework.
Customers outside the EEA. If you are established outside the EEA in a country without an adequacy decision, Module 4 (processor to controller) of the standard contractual clauses applies between us for personal data we send back to you, and is incorporated into this DPA by reference.
Choices in the clauses. In the clauses: Clause 7 (docking) does not apply; under Clause 9, option 2 (general written authorization) applies, with the notice period in section 5; the optional language in Clause 11 does not apply; the supervisory authority under Clause 13 is the Dutch Autoriteit Persoonsgegevens; under Clauses 17 and 18, the clauses are governed by Dutch law and disputes go to the courts of Amsterdam. Annexes I to III of this DPA complete the clauses' annexes.
UK and Switzerland. For data protected by the UK GDPR, the UK International Data Transfer Addendum to the clauses applies, with the information in this DPA completing its tables. For data protected by the Swiss FADP, the clauses apply with the Swiss Federal Data Protection and Information Commissioner as the competent authority, and references to member states read as including Switzerland.
We make available the information needed to demonstrate compliance with this DPA. First, we answer your reasonable security questionnaires and give you our security documentation, under confidentiality. If that isn't enough to demonstrate compliance, or an authority requires it, you may audit us, once a year unless a breach or an authority calls for more: with at least 30 days' notice, during business hours, through an independent auditor bound to confidentiality, in a way that doesn't disrupt our operations or expose other customers' data. Each party bears its own costs of an audit.
When the agreement ends, you can export your Customer Data for 30 days, as the Terms describe. After that, we delete the personal data from the Service, and from our backups as they expire, within a further 14 days, unless EU or member state law requires us to keep it. On request, we confirm the deletion in writing.
Each party's liability under this DPA is subject to the limits in the Terms, except where Data Protection Law doesn't allow them. This DPA lasts as long as we process personal data for you.
If this DPA conflicts with the Terms or an Order Form on anything about personal data, this DPA prevails. If it conflicts with the standard contractual clauses, the clauses prevail.
Parties. The controller is the Customer, as named in the Order Form, with the contact given there. The processor is Colchix B.V., John M. Keynesplein 10, 1066 EP Amsterdam, the Netherlands, reachable at privacy@colchix.com.
Data subjects.
Categories of personal data. Depending on the agents and features you enable:
| Agent or feature | Personal data |
|---|---|
| ARGUS (discovery), from the agent and extension | A device identifier made on the device with a key that never leaves it; the device's operating system, agent version, department and enrollment details; which AI tools, sites and extensions are detected, when, how often and for how long; which browsers are used and whether the extension runs in them. No content, no names, no email addresses of the people using the device. |
| Connected sources (ARGUS, ATHENA) | Where you connect enterprise AI platforms (such as ChatGPT Enterprise or Claude Enterprise) or other sources: the activity records they provide, such as the tool, time, account type, activity category and the user or team context they carry, which can include a user name. Not conversation histories. |
| License and cost data | The licenses, seats and prices you give us, or that your connected sources provide, to compare what you pay for with what is used. |
| TALOS (protection) | Text and files entered into supported AI tools, processed in transit only to find and mask sensitive values before they reach the AI service, and not stored; records of what was masked, by category and count, never the values themselves. |
| ATHENA (governance) | Policies, decisions, approvals, exceptions and audit evidence about AI use, including the identity of the Users who make them, and the user context of records from connected sources. |
| Derived insights | What Colchix works out from the data above: usage and adoption by team, department, role and tool; estimated spend, unused licenses and potential savings; value measures; risk and exposure scores for tools; how well use fits your policy; evidence readiness. Shown by group, with groups below a minimum size (5 devices, unless you set more) pooled with others. |
| Your settings | Teams, departments and roles; policies per team, tool and kind of data (mask, explain or leave), approvals and exceptions; categories you define yourself, such as a client list; retention and region. |
| The console | Users' email addresses, password hashes, second-factor secrets (encrypted) and recovery codes (hashed), roles, sign-in sessions, failed sign-in attempts, and the actions they take; requests sent to us through the console. |
| Security logs | IP addresses and connection details in request logs, not linked to the data above. |
Special categories. The Service is not designed to process special categories of data. Where TALOS is enabled, such data may appear in content typed into AI tools; TALOS processes it only in transit, to detect and mask it, and doesn't store it.
Nature of the processing. Collection, pseudonymization on the device, transmission, storage, organization, analysis and classification (including by THEMIS, our own AI model, as our AI Transparency page describes), masking, consultation, export, and erasure.
Purpose. Providing the Service under the agreement: discovering AI tools and showing their use, cost, value and risks (ARGUS); protecting sensitive data at runtime, under the policies you set per team, tool and kind of data (TALOS); turning AI activity into governance records and evidence (ATHENA); informing your decisions about AI tools, licenses, budgets and team policies; and supporting and securing the Service. Not evaluating individual people, as our Acceptable Use Policy sets out.
Frequency. Continuous, for as long as the Service is in use.
Retention. As set by your plan, and by the agreement for the rest:
| Data | Kept for |
|---|---|
| Observed AI usage events | 30, 90, 180 or 365 days, as your plan sets; 90 days by default |
| Session metadata | 12 months |
| Failed sign-in attempts | 1 day |
| AI literacy (Article 4 AI Act) evidence | 5 years |
| Administrative actions in the audit trail | 7 years |
| Exports you create | Until you delete them |
| Security logs | 30 days |
| Backups | 14 days |
Everything is deleted when the Service ends, as section 10 describes.
Location. As section 8 describes: Google Cloud in the Netherlands (europe-west4) for deployments run by Colchix, unless the Order Form names another region; your own environment for private cloud and on-premises deployments.
Our security program is structured on ISO/IEC 27001. We are not certified yet; certification is on our roadmap. The measures below apply to deployments run by Colchix; where the Service runs in your environment, the measures for that environment are yours, and those for our software and support remain ours. Our Security page describes them in more detail.
Organizational.
People.
Physical.
Technological.
The sub-processors you authorize are those listed on our Sub-processors page, which forms this annex, as updated under section 5.