Data Processing Agreement
Last updated 10 October 2026
This agreement sets out how AKRIBOS processes personal data on behalf of its customers when they use the AKRIBOS product, as required by Article 28 of the GDPR.
§01 Parties and scope
1.1 This Data Processing Agreement ("DPA") is entered into by AKRIBOS AI B.V., based in Amsterdam, The Netherlands, registered with the Netherlands Chamber of Commerce (KvK) under number 83548335 ("Processor", "we"), and the organisation that agrees to it as a customer of AKRIBOS ("Controller", "you").
1.2 This DPA forms part of the agreement under which we provide the AKRIBOS product to you (the "Principal Agreement"). It applies whenever we process personal data on your behalf in performing the Principal Agreement ("Controller Data"). Terms such as "personal data", "processing" and "data subject" have the meaning given in the General Data Protection Regulation (EU) 2016/679 ("GDPR").
1.3 Personal data we collect through our website, for example when you book a call, is not covered by this DPA. That is described in our Privacy Policy.
§02 Subject matter and duration
2.1 We process Controller Data only to provide the AKRIBOS product: reading your cloud configuration with the read-only access you grant, analysing it, and showing you findings, attack paths and recommended fixes. The categories of data, data subjects and processing operations are set out in Annex 1.
2.2 AKRIBOS is designed to read configuration, not the contents of your workloads. We do not make changes to your cloud environment.
2.3 This DPA lasts as long as we process Controller Data under the Principal Agreement.
§03 Instructions from the Controller
3.1 We process Controller Data only on your documented instructions. The Principal Agreement, this DPA and your configuration and use of the product are your complete instructions at the time of signing. Further instructions must be given in writing, which includes email.
3.2 If EU or Member State law requires us to process Controller Data in another way, we will tell you before we do so, unless that law prohibits it.
3.3 If we believe an instruction infringes the GDPR or other data protection law, we will tell you without delay and may suspend that instruction until you confirm or change it.
§04 Confidentiality and security
4.1 Everyone we authorise to process Controller Data is bound by a duty of confidentiality, either by contract or by law, and has access only to the extent their role requires.
4.2 We maintain the technical and organisational measures in Annex 3, which are designed to give a level of security appropriate to the risk, as required by Article 32 GDPR.
4.3 We may update these measures as technology develops, provided the overall level of protection does not decrease. On request, we will give you a current description of the measures.
§05 Personal data breaches
5.1 We will notify you without undue delay, and in any case within 48 hours, after becoming aware of a personal data breach affecting Controller Data.
5.2 The notification will include, as far as known at the time, the information listed in Article 33(3) GDPR. Where not everything is known yet, we will provide it in phases as our investigation progresses.
5.3 We will take reasonable steps to contain the breach and limit its consequences, and will help you meet any obligation to notify the supervisory authority or data subjects. A notification by us is not an admission of fault or liability.
§06 Assistance to the Controller
6.1 Taking into account the nature of the processing and the information available to us, we will help you comply with your obligations under Articles 32 to 36 GDPR, including data protection impact assessments and prior consultations with a supervisory authority.
6.2 We keep a record of processing activities carried out on your behalf, as required by Article 30(2) GDPR.
6.3 If Controller Data is at risk through seizure, insolvency or other actions by third parties, we will inform you without delay, unless we are legally prohibited from doing so, and will make clear to those third parties that you are the controller of the data.
§07 Subprocessors
7.1 You give us general authorisation to engage subprocessors. The subprocessors we use when this DPA is concluded are listed in Annex 4.
7.2 We will tell you at least 30 days before we add or replace a subprocessor. You may object on reasonable data protection grounds within that period. If we cannot reasonably accommodate the objection, you may terminate the affected part of the Principal Agreement without penalty.
7.3 We impose data protection obligations on each subprocessor that are no less protective than those in this DPA, and we remain responsible to you for their performance.
§08 International transfers
8.1 We host and process Controller Data in the European Economic Area.
8.2 We will only transfer Controller Data outside the EEA, or allow a subprocessor to access it from outside the EEA, if the transfer meets the requirements of Chapter V GDPR. That means an adequacy decision under Article 45, or appropriate safeguards such as the European Commission's Standard Contractual Clauses under Article 46.
§09 Audits
9.1 On request, we will make available the information you need to demonstrate that we meet our obligations under Article 28 GDPR, such as documentation of our measures, certifications and third-party audit reports where available.
9.2 If that information is not enough, you may audit us, or have an independent auditor who is not our competitor and is bound by confidentiality do so. Audits take place during normal business hours, at most once a year unless a supervisory authority requires otherwise or after a personal data breach, with at least 30 days' notice and in a way that limits disruption to our operations.
9.3 Each party bears its own costs of an audit, unless the audit shows that we materially breached this DPA.
§10 Data subject requests
10.1 Taking into account the nature of the processing, we will help you, by appropriate technical and organisational measures, to respond to requests from data subjects exercising their rights under Chapter III GDPR.
10.2 If a data subject contacts us directly about Controller Data, we will forward the request to you without delay and will not respond ourselves unless you instruct us to.
§11 Term, deletion and return
11.1 This DPA ends automatically when the Principal Agreement ends and we no longer process Controller Data.
11.2 Within 30 days after the Principal Agreement ends, we will delete Controller Data, or return it to you first if you ask before that date, unless EU or Member State law requires us to keep it. Copies in backups are deleted on the normal backup rotation and remain protected under this DPA until then.
11.3 On request, we will confirm the deletion in writing.
§12 Liability
12.1 Each party's liability under this DPA is subject to the limitations of liability in the Principal Agreement, to the extent permitted by law. Nothing in this DPA limits either party's liability to data subjects under Article 82 GDPR.
§13 Final provisions
13.1 If this DPA conflicts with the Principal Agreement, this DPA prevails in relation to the processing of Controller Data. If the European Commission's Standard Contractual Clauses apply, they prevail over both.
13.2 If any provision of this DPA is invalid or unenforceable, the rest remains in force, and the provision is replaced by a valid one that comes as close as possible to its purpose.
13.3 This DPA is governed by the laws of the Netherlands. Disputes arising from it are submitted to the competent court in Amsterdam.
13.4 We may update this DPA to reflect changes in law or in our services. We will notify you of material changes in advance, and any change will not reduce the protection of Controller Data.
§14 Annex 1: Processing details
| Processing | Categories of data | Data subjects |
|---|---|---|
| Reading and analysing your AWS, Google Cloud and Azure configuration | Cloud configuration and metadata that may contain personal data, such as IAM user names, email addresses, resource names and tags, access policies and access log metadata | Your employees, contractors and other people who have identities or are named in your cloud environments |
| Findings, attack paths and recommended fixes | Results derived from the configuration above, including the identities and resources they refer to | As above |
| User accounts and access management | Name, work email address, role, authentication and authorisation data | Your users of the AKRIBOS terminal and dashboard |
| Audit trail, security and operations | Activity logs, such as who ran which review and when, IP addresses, timestamps and error data | Your users of the AKRIBOS terminal and dashboard |
| Support | Contact details and the contents of support requests | Your users and contacts |
We do not intend to process special categories of personal data under Article 9 GDPR. You should not place such data in cloud configuration that AKRIBOS reads.
§15 Annex 2: Contacts
For you, instructions may be given by the person who accepts this DPA on your behalf and by the administrators of your AKRIBOS account. For us, instructions and questions about this DPA go to privacy@akribos.ai. Report security incidents to security@akribos.ai.
§16 Annex 3: Technical and organisational measures
- read-only access to your cloud: AKRIBOS uses the read-only roles you grant and cannot change your environment
- hosting and processing of Controller Data in the EU
- encryption of data in transit and at rest
- logical separation of each customer's data
- role-based access for our staff, granted on a need-to-know basis and reviewed regularly
- strong authentication for access to production systems
- an audit trail of access to and actions on Controller Data
- regular backups and tested restore procedures
- vulnerability management, patching and secure software development practices
- incident detection and response procedures, and a public responsible disclosure policy
- confidentiality obligations for all staff and subprocessors
- deletion procedures for when data is no longer needed or the agreement ends
§17 Annex 4: Subprocessors
The current list of subprocessors, including their location and the service they provide, is available on request at privacy@akribos.ai.