Data processing agreement
Data processingagreement
How the operator of KibaCloud processes personal data on behalf of its customers. This agreement is part of the terms every customer accepts when creating a workspace, and is the same for every customer.
Last updated: November 21, 2026
01
Purpose and scope
Art. 28(3) GDPR
(a) The purpose of this data processing agreement (this DPA) is to ensure compliance with Article 28(3) and (4) of Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data (the GDPR).
- (b) The controller and the processor listed in Annex I have agreed to this DPA in order to ensure compliance with Article 28(3) and (4) GDPR.
- (c) This DPA applies to the processing of personal data as specified in Annex II.
- (d) Annexes I to V are an integral part of this DPA.
- (e) This DPA is without prejudice to obligations to which the controller is subject by virtue of the GDPR.
- (f) This DPA does not by itself ensure compliance with obligations related to international transfers in accordance with Chapter V GDPR.
02
Interpretation and precedence
(a) Where this DPA uses the terms defined in the GDPR, those terms shall have the same meaning as in the GDPR.
- (b) This DPA shall be read and interpreted in the light of the provisions of the GDPR.
- (c) This DPA shall not be interpreted in a way that runs counter to the rights and obligations provided for in the GDPR or in a way that prejudices the fundamental rights or freedoms of the data subjects.
- (d) In the event of a contradiction between this DPA and the provisions of related agreements between the Parties existing at the time when this DPA is agreed or entered into thereafter, this DPA shall prevail.
03
Description of the processing
Art. 28(3) GDPR
The details of the processing operations, in particular the categories of personal data and the purposes of processing for which the personal data is processed on behalf of the controller, are specified in Annex II.
04
Instructions, purpose and duration
Art. 28(3)(a) GDPR
(a) The processor shall process personal data only on documented instructions from the controller, unless required to do so by Union or Member State law to which the processor is subject. In this case, the processor shall inform the controller of that legal requirement before processing, unless the law prohibits this on important grounds of public interest. Subsequent instructions may also be given by the controller throughout the duration of the processing of personal data. These instructions shall always be documented.
- (b) The processor shall immediately inform the controller if, in the processor's opinion, instructions given by the controller infringe the GDPR or the applicable Union or Member State data protection provisions.
- (c) The processor shall process the personal data only for the specific purpose(s) of the processing, as set out in Annex II, unless it receives further instructions from the controller.
- (d) Processing by the processor shall only take place for the duration specified in Annex II.
05
Security of processing
Art. 28(3)(c) and Art. 32 GDPR
(a) The processor shall at least implement the technical and organisational measures specified in Annex III to ensure the security of the personal data. This includes protecting the data against a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access to the data (personal data breach). In assessing the appropriate level of security, the Parties shall take due account of the state of the art, the costs of implementation, the nature, scope, context and purposes of processing and the risks involved for the data subjects.
- (b) If the processing involves personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic data or biometric data for the purpose of uniquely identifying a natural person, data concerning health or a person's sex life or sexual orientation, or data relating to criminal convictions and offences ("sensitive data"), the processor shall apply specific restrictions and/or additional safeguards.
06
Confidentiality
Art. 28(3)(b) GDPR
The processor shall grant access to the personal data undergoing processing to members of its personnel only to the extent strictly necessary for implementing, managing and monitoring of the contract. The processor shall ensure that persons authorised to process the personal data received have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.
07
Documentation and audits
Art. 28(3)(h) GDPR
(a) The Parties shall be able to demonstrate compliance with this DPA.
- (b) The processor shall deal promptly and adequately with inquiries from the controller about the processing of data in accordance with this DPA.
- (c) The processor shall make available to the controller all information necessary to demonstrate compliance with the obligations that are set out in this DPA and stem directly from the GDPR. At the controller's request, the processor shall also permit and contribute to audits of the processing activities covered by this DPA, at reasonable intervals or if there are indications of non-compliance. In deciding on a review or an audit, the controller may take into account relevant certifications held by the processor.
- (d) The controller may choose to conduct the audit by itself or mandate an independent auditor. Audits may also include inspections at the premises or physical facilities of the processor and shall, where appropriate, be carried out with reasonable notice.
- (e) The Parties shall make the information referred to in this Clause, including the results of any audits, available to the competent supervisory authority/ies on request.
08
Sub-processors
Art. 28(2), (3)(d) and (4) GDPR
(a) The processor has the controller's general authorisation for the engagement of sub-processors from an agreed list, set out in Annex IV. The processor shall specifically inform in writing the controller of any intended changes of that list through the addition or replacement of sub-processors at least 14 days in advance, thereby giving the controller sufficient time to be able to object to such changes prior to the engagement of the concerned sub-processor(s). The processor shall provide the controller with the information necessary to enable the controller to exercise the right to object.
- (b) Where the processor engages a sub-processor for carrying out specific processing activities (on behalf of the controller), it shall do so by way of a contract which imposes on the sub-processor, in substance, the same data protection obligations as the ones imposed on the data processor in accordance with this DPA. The processor shall ensure that the sub-processor complies with the obligations to which the processor is subject pursuant to this DPA and to the GDPR.
- (c) At the controller's request, the processor shall provide a copy of such a sub-processor agreement and any subsequent amendments to the controller. To the extent necessary to protect business secret or other confidential information, including personal data, the processor may redact the text of the agreement prior to sharing the copy.
- (d) The processor shall remain fully responsible to the controller for the performance of the sub-processor's obligations in accordance with its contract with the processor. The processor shall notify the controller of any failure by the sub-processor to fulfil its contractual obligations.
The written notice under point (a) is sent by email to the owners of the controller's workspace, and the planned change is shown on /subprocessors with its start date. The controller may object by email to privacy@kibacloud.io within that notice period, on reasonable grounds relating to data protection; a change the controller does not object to is approved. If an objection cannot be resolved, the controller may terminate the agreement with effect before the new sub-processor begins processing its personal data, which is then deleted in accordance with Clause 12(d).
09
International transfers
Chapter V GDPR
(a) Any transfer of data to a third country or an international organisation by the processor shall be done only on the basis of documented instructions from the controller or in order to fulfil a specific requirement under Union or Member State law to which the processor is subject and shall take place in compliance with Chapter V GDPR.
- (b) The controller agrees that where the processor engages a sub-processor in accordance with Clause 8 for carrying out specific processing activities (on behalf of the controller) and those processing activities involve a transfer of personal data within the meaning of Chapter V GDPR, the processor and the sub-processor can ensure compliance with Chapter V GDPR by using standard contractual clauses adopted by the Commission in accordance with Article 46(2) GDPR, provided the conditions for the use of those standard contractual clauses are met.
10
Assistance to the controller
Art. 28(3)(e) and (f) GDPR
(a) The processor shall promptly notify the controller of any request it has received from the data subject. It shall not respond to the request itself, unless authorised to do so by the controller.
- (b) The processor shall assist the controller in fulfilling its obligations to respond to data subjects' requests to exercise their rights, taking into account the nature of the processing. In fulfilling its obligations in accordance with (a) and (b), the processor shall comply with the controller's instructions.
- (c) In addition to the processor's obligation to assist the controller pursuant to point (b), the processor shall furthermore assist the controller in ensuring compliance with the following obligations, taking into account the nature of the data processing and the information available to the processor: (1) the obligation to carry out an assessment of the impact of the envisaged processing operations on the protection of personal data (a 'data protection impact assessment') where a type of processing is likely to result in a high risk to the rights and freedoms of natural persons; (2) the obligation to consult the competent supervisory authority/ies prior to processing where a data protection impact assessment indicates that the processing would result in a high risk in the absence of measures taken by the controller to mitigate the risk; (3) the obligation to ensure that personal data is accurate and up to date, by informing the controller without delay if the processor becomes aware that the personal data it is processing is inaccurate or has become outdated; (4) the obligations in Article 32 GDPR.
- (d) The Parties shall set out in Annex III the appropriate technical and organisational measures by which the processor is required to assist the controller in the application of this Clause as well as the scope and the extent of the assistance required.
11
Personal data breaches
Art. 33 and 34 GDPR
In the event of a personal data breach, the processor shall cooperate with and assist the controller for the controller to comply with its obligations under Articles 33 and 34 GDPR, where applicable, taking into account the nature of processing and the information available to the processor.
- (a) Data breach concerning data processed by the controller. In the event of a personal data breach concerning data processed by the controller, the processor shall assist the controller: (i) in notifying the personal data breach to the competent supervisory authority/ies, without undue delay after the controller has become aware of it, where relevant (unless the personal data breach is unlikely to result in a risk to the rights and freedoms of natural persons); (ii) in obtaining the following information which, pursuant to Article 33(3) GDPR, shall be stated in the controller's notification, and must at least include: (1) the nature of the personal data including where possible, the categories and approximate number of data subjects concerned and the categories and approximate number of personal data records concerned; (2) the likely consequences of the personal data breach; (3) the measures taken or proposed to be taken by the controller to address the personal data breach, including, where appropriate, measures to mitigate its possible adverse effects. Where, and insofar as, it is not possible to provide all this information at the same time, the initial notification shall contain the information then available and further information shall, as it becomes available, subsequently be provided without undue delay; (iii) in complying, pursuant to Article 34 GDPR, with the obligation to communicate without undue delay the personal data breach to the data subject, when the personal data breach is likely to result in a high risk to the rights and freedoms of natural persons.
- (b) Data breach concerning data processed by the processor. In the event of a personal data breach concerning data processed by the processor, the processor shall notify the controller without undue delay after the processor having become aware of the breach. Such notification shall contain, at least: (1) a description of the nature of the breach (including, where possible, the categories and approximate number of data subjects and data records concerned); (2) the details of a contact point where more information concerning the personal data breach can be obtained; (3) its likely consequences and the measures taken or proposed to be taken to address the breach, including to mitigate its possible adverse effects. Where, and insofar as, it is not possible to provide all this information at the same time, the initial notification shall contain the information then available and further information shall, as it becomes available, subsequently be provided without undue delay.
- (c) The Parties shall set out in Annex III all other elements to be provided by the processor when assisting the controller in the compliance with the controller's obligations under Articles 33 and 34 GDPR.
12
Non-compliance and termination
Art. 28(3)(g) GDPR
(a) Without prejudice to any provisions of the GDPR, in the event that the processor is in breach of its obligations under this DPA, the controller may instruct the processor to suspend the processing of personal data until the latter complies with this DPA or the contract is terminated. The processor shall promptly inform the controller in case it is unable to comply with this DPA, for whatever reason.
- (b) The controller shall be entitled to terminate the contract insofar as it concerns processing of personal data in accordance with this DPA if: (1) the processing of personal data by the processor has been suspended by the controller pursuant to point (a) and if compliance with this DPA is not restored within a reasonable time and in any event within one month following suspension; (2) the processor is in substantial or persistent breach of this DPA or its obligations under the GDPR; (3) the processor fails to comply with a binding decision of a competent court or the competent supervisory authority/ies regarding its obligations pursuant to this DPA or to the GDPR.
- (c) The processor shall be entitled to terminate the contract insofar as it concerns processing of personal data under this DPA where, after having informed the controller that its instructions infringe applicable legal requirements in accordance with Clause 4(b), the controller insists on compliance with the instructions.
- (d) Following termination of the contract, the processor shall, at the choice of the controller, delete all personal data processed on behalf of the controller and certify to the controller that it has done so, or, return all the personal data to the controller and delete existing copies unless Union or Member State law requires storage of the personal data. Until the data is deleted or returned, the processor shall continue to ensure compliance with this DPA.
Deleting the workspace, or disconnecting an AWS account from it, instructs the processor to delete the personal data concerned. Where the controller chooses return under point (d), the processor sends a CSV file of the workspace's inventory by email before deleting it.
13
Annex I: Parties
This DPA is concluded between the customer, as controller, and the operator of KibaCloud, as processor.
- Controller: the customer that created the workspace, as defined in the terms at /terms. Address: as provided by the customer. Contact: the email addresses of the workspace's owners, and the customer's data protection officer, if it notifies one to the processor. Signature and accession date: accepted electronically, together with the terms, when the workspace is created, on the date recorded with that acceptance.
- Processor: Georg Schwarz, c/o POSTFLEX PFX-038-404, Emsdettener Strasse 10, 48268 Greven, Deutschland. Contact: Georg Schwarz, owner, privacy@kibacloud.io. The processor has not appointed a data protection officer, as none is required. Signature and accession date: accepted electronically, together with the terms, when the workspace is created, on the date recorded with that acceptance.
14
Annex II: Description of the processing
Art. 28(3) GDPR
The personal data this DPA covers is the inventory KibaCloud collects from the AWS accounts the customer connects.
| Item | Description |
|---|---|
| Categories of data subjects | People named in the names and tags of the customer's AWS resources, or of the AWS accounts it connects, typically the customer's own staff and contractors, for example as the owner of a resource. |
| Categories of personal data | Resource names and tag keys and values exactly as they appear in AWS, and the names and tags the customer gives connected accounts, which can include people's names and email addresses; the findings and anomalies derived from them. The technical metadata stored alongside, such as resource identifiers, region, state and type, identifies no one by itself. |
| Sensitive data | None. Resource names and tags are not intended to hold special categories of data, consistent with AWS's guidance against storing sensitive information in tags. |
| Nature of the processing | Reading resource names, tags and technical metadata from the customer's AWS accounts through a read-only role the customer creates, on a regular schedule and immediately after an account is connected; storing them; showing them in the customer's workspace; deriving findings and anomalies from them; and including connected account names in anomaly emails to the workspace's owners and admins. |
| Purpose | To provide the Global Resource View service to the customer: a searchable inventory of its AWS resources across accounts and regions, findings about unused resources, and alerts about unusual changes. |
| Duration | For the term of the agreement and, after it ends, until the personal data is deleted or returned as Clause 12 sets out. |
| Processing by sub-processors | Each sub-processor in Annex IV processes the personal data only for the purpose /subprocessors states for it, for as long as the processing above lasts. |
This DPA does not cover account and usage data: the names, email addresses and roles of workspace members and invitees, the workspace audit log, sign-ins and sessions, abuse protection, product analytics and error monitoring. For that data the processor is an independent controller, as the privacy notice at /privacy describes.
15
Annex III: Technical and organisational measures
Art. 32 GDPR
The processor implements the following measures for the processing described in Annex II, including the measures by which it assists the controller.
- Access to the customer's AWS accounts: through a role the customer creates in its own account, whose policy lists individual read actions and contains no action that creates, changes or deletes anything. Each scan uses short-lived credentials that AWS issues for it, and no long-lived credential of the customer's is stored. Assuming the role requires an external identifier unique to each connected account. The customer can revoke access at any time by deleting the role, without involving the processor.
- Data minimisation: only resource metadata is stored. The processor never reads the contents of storage objects, database rows, or application or audit logs. Where an AWS read call returns more than metadata, such as a function's environment variables, the processor discards it without storing it. The role grants no access at all to identity and access management, CloudTrail, Secrets Manager, Parameter Store, key management, CloudWatch Logs or billing.
- Separation between customers: every workspace's data in the database is scoped to that workspace by row-level security, and an access layer checks the user's membership and role before any query runs. Code that bypasses that layer fails the build.
- Encryption: connections from browsers and between the application and the database use TLS. The database is encrypted at rest.
- Protection at the edge: the application is reachable only through a content delivery network with a web application firewall, and the origin refuses requests that did not pass through it.
- User identification and authorisation: users sign in with a verified email address and a password subject to a minimum length. Sign-in attempts are rate-limited, account creation is protected against automated sign-ups, and resetting a password ends the account's other sessions. Within a workspace, roles limit who can manage members, connected accounts and billing.
- Storage: the inventory is stored in the processor's database in Frankfurt, Germany. No copy is kept on work devices or in development or test environments.
- Backup and restore: the database is backed up continuously and can be restored to any point in a recent period, which recovers data lost or altered through an incident. Deleted data drops out of the backup once that period has passed.
- Physical security: the processor runs no premises where personal data is processed. Hosting, including the database, runs on AWS infrastructure, whose physical security AWS provides under its ISO 27001 certification and SOC 2 reports.
- Logging: changes to the workspace, its members, invitations and subscription are recorded in an audit log the workspace's owners and admins can read. Application errors and logs are monitored.
- System configuration: infrastructure is defined in code and deployed by an automated pipeline that authenticates to AWS with short-lived credentials and stores no AWS keys. Third-party build steps are pinned to exact versions. Production runs in its own AWS account, separate from development and testing.
- Testing: an automated test suite, including tests of the separation between workspaces at the database level, must pass before every deployment. Dependencies are kept current through automated update requests.
- Governance: KibaCloud is operated by one person, who alone has access to production systems and to the personal data. Administrative access to every service provider and to the source code requires two-factor authentication. The AWS accounts for production, testing and development have no root user credentials, and the root user of the management account is protected by two-factor authentication and not used for day-to-day work. Passwords are unique per service and kept in a password manager. Work devices with access to production systems or to the personal data use full-disk encryption and lock when idle, and the development environment has no access to production. The processor holds no security certification of its own.
- Data quality: each scan refreshes the inventory from AWS, so changes the customer makes in AWS, corrections and deletions included, reach KibaCloud with the next scan.
- Limited retention: automated jobs delete resources that no longer exist in AWS, collected resources after a subscription has ended without being renewed, and all of a workspace's data after the workspace is deleted.
- Erasure and portability: disconnecting an AWS account deletes the personal data concerned. Deleting the workspace stops scanning at once and deletes the personal data once the period in which a mistaken deletion can be reversed has passed. On request, the inventory is returned as a CSV file by email.
- Assistance with data subject requests: a request the processor receives is forwarded to the workspace's owners and not answered by the processor. The customer can see all stored personal data in its workspace, and corrects or deletes it at its source in AWS, where the next scan picks the change up.
- Assistance with personal data breaches: in addition to what Clause 11 lists, a notification names the affected workspaces and AWS accounts and when the breach happened.
- Other assistance: questions about the processing, including for a data protection impact assessment, are answered in writing at privacy@kibacloud.io.
These measures are subject to technical progress and development, and the processor may update them, provided that an update does not materially lower the overall security of the personal data.
16
Annex IV: Sub-processors
Art. 28(2) and (4) GDPR
The controller authorises the sub-processors listed on /subprocessors, where each one's purpose, contracting entity, location and transfer safeguard are set out. That list changes only as Clause 8 sets out.
17
Annex V: US state privacy laws
CCPA, Cal. Civ. Code §1798.100 et seq.
For the California Consumer Privacy Act (CCPA) and similar US state privacy laws, the processor is the customer's service provider, or processor as those laws may name it, for the personal data described in Annex II. The processor does not sell or share personal information. It does not retain, use or disclose that personal information for any purpose other than providing the service, or outside its direct business relationship with the customer, and does not combine it with personal information from other sources. The rest of this DPA applies to it as well.