CRACI Data Processing Agreement
Last updated: November 19, 2026
This Data Processing Agreement (“DPA”), including Schedules A–C, is concluded between CRACI Corporation Oy, Business ID 3573431-1 (“CRACI” or “Processor”), and the business customer using the CRACI services (“Customer” or “Controller”). The “Agreement” means the CRACI Terms of Service accepted by the Customer, together with any separate agreement concluded between CRACI and the Customer for the provision of the Services. The Customer’s identity, address and business identification details are those provided in the Agreement or in the Customer’s account in the Services. This DPA is incorporated into the Agreement and takes effect when an authorised Customer representative accepts the Agreement identifying this DPA, whether by signature or recorded electronic acceptance. CRACI shall retain the accepted version and evidence of acceptance.
Terms not defined in this DPA have the meanings given in the Agreement or Regulation (EU) 2016/679 (“GDPR”). Mandatory data protection law and applicable executed standard contractual clauses prevail. Subject to those requirements, this DPA prevails over conflicting Agreement terms concerning personal data processing; the Agreement’s liability provisions apply as provided in Section 2.12.
1.
BACKGROUND
1.1.
The Customer determines the purposes and essential means of processing personal data on its behalf through the Services (“Personal Data”), or acts on the documented instructions of its controller. Where the Customer is itself a processor, CRACI is its subprocessor and references to the Customer as Controller mean the Customer acting within its authorisation from the relevant controller. The Customer shall obtain the required upstream authorisation for CRACI, its subprocessors and instructions. CRACI acts as processor when providing the CRACI platform, including managed continuous integration (CI) runners, related software supply chain security and compliance features and AI Features, as described in the Agreement (“Services”). Acceptance of CRACI’s privacy notice does not replace this DPA.
1.2.
The processing described in Schedule A is performed only for the Customer’s documented purposes. CRACI shall protect Personal Data and perform its own processor obligations under applicable Data Protection Regulation. Nothing in this DPA makes CRACI a processor for activities for which it actually determines its own purposes and essential means.
1.3.
CRACI acts as an independent controller only for processing for which it determines its own purposes and essential means, such as its own billing, statutory accounting, customer relationship management, marketing, product usage analytics and security logs, as described in CRACI’s privacy notice. This processing is outside the processor instructions in this DPA and must be separately lawful and transparent. Account and security data are allocated according to the actual purpose of each operation, not automatically excluded. CRACI shall not reclassify Customer Content as its own controller data to bypass this DPA. If a new activity involves independent or joint controllership, the parties shall assess and document the appropriate arrangement before commencing it.
1.4.
The Customer remains responsible for the lawful purpose and basis of its processing, necessary notices to data subjects (such as developers whose information is included in the Customer’s code repositories and build data), data minimisation, accuracy, retention instructions and supervision of its authorised users. These responsibilities do not relieve CRACI of its own obligations. The Customer authorises the processing of data from code repositories and other third-party services that it connects to the Services.
2.
PROCESSING OF PERSONAL DATA
2.1.
The subject matter, duration, nature and purposes of processing, categories of data subjects, and the Customer’s rights and obligations are specified in Schedule A. Only data necessary for the Services ordered and the features used may be processed. Depending on those Services, Personal Data may include:
- user and team information processed on the Customer’s behalf, such as team memberships, roles and permissions configured by the Customer;
- Customer Content: source code and commit metadata, including commit author names and email addresses; job logs and job metrics; artifact metadata; dependency information, software bills of materials (SBOMs) and vulnerability information; inventory data; and inputs to and outputs of AI Features, such as proposed code changes and pull requests;
- connected service information: identifiers, authorisation tokens and metadata relating to connected code repositories, source code hosting platforms and other third-party services;
- credentials and secrets made available by the Customer to jobs executed in the Services, to the extent they contain Personal Data;
- technical information processed on the Customer’s behalf: IP addresses and other technical metadata contained in job execution data and Customer Content; and
- Special-category, criminal-offence and other restricted data are subject to Schedule A and are not generally authorised.
2.2.
Each party shall comply with the GDPR and other applicable Union or Member State data protection and data security laws (“Data Protection Regulation”) in its respective role. CRACI shall maintain the records required of processors, cooperate with competent supervisory authorities, and provide sufficient guarantees of appropriate technical and organisational measures.
2.3.
CRACI shall process Personal Data only on documented instructions from the Customer, including this DPA, the Agreement, the Customer’s configuration and feature selections in the Services, and subsequent written instructions, including instructions regarding transfers. If Union or Member State law requires other processing, CRACI shall inform the Customer of that legal requirement before processing unless that law prohibits notice on important grounds of public interest. CRACI shall not use Personal Data for its own purposes, including advertising, general service development or training, fine-tuning, evaluation or customer-independent improvement of AI models. AI providers and their downstream providers may process Personal Data only under binding contractual restrictions and verified settings preventing such reuse; a prohibition written into a prompt alone does not satisfy this obligation. Customer-specific generation of output to provide the instructed Services is permitted; model training is not.
2.4.
CRACI shall immediately inform the Customer if, in its opinion, an instruction infringes Data Protection Regulation, and promptly notify the Customer if it cannot comply with an instruction. CRACI may suspend only the affected processing while the parties resolve an unlawful or impossible instruction, without preventing legally required protective measures. Material changes to processing purposes, restricted data, or the Customer’s instructions require documented agreement before implementation.
2.5.
CRACI shall ensure that all persons authorised to process Personal Data, including employees and contractors, are bound by confidentiality commitments or appropriate statutory confidentiality obligations, receive appropriate training, and access data only as necessary for their tasks and on instructions. Confidentiality continues after their engagement and this DPA end. Separate entities processing Personal Data are subject to the subprocessor requirements; personnel acting under CRACI’s direct authority remain subject to its access and confidentiality controls. Personal Data shall not be disclosed except on documented instructions, under this DPA, or as required by applicable law.
2.6.
CRACI shall process Personal Data in the European Economic Area (“EEA”) except for transfers specifically identified and authorised in the completed Schedule C or subsequently authorised through its change procedure. A transfer includes making Personal Data available to a separate recipient in a third country through remote access. Before any transfer, CRACI shall ensure a valid GDPR Chapter V mechanism: an applicable adequacy decision covering the recipient and processing, or appropriate Article 46 safeguards. Where standard contractual clauses are used, the relevant parties shall execute the applicable Commission clauses with the correct module, completed annexes, locations and security measures, and carry out and document any required transfer assessment and supplementary safeguards. Article 49 derogations shall not serve as the default mechanism for recurring service-provider transfers. CRACI shall provide transfer documentation on request, monitor changes affecting protection and suspend affected transfers if adequate protection cannot be ensured. It shall notify the Customer of legally binding disclosure requests unless prohibited, assess their legality, challenge unlawful or disproportionate requests where reasonable legal grounds exist, and disclose only what is legally required.
2.7.
CRACI shall implement and maintain appropriate technical and organisational measures under Article 32 GDPR, including the minimum commitments in Schedule B, taking account of the state of the art, implementation costs, processing context and risks to individuals. CRACI shall regularly test and review the measures, remedy identified deficiencies without undue delay and not materially reduce the overall level of protection during the Services. Subprocessor arrangements must maintain appropriate protection throughout the processing chain.
2.8.
CRACI shall notify the Customer without undue delay after becoming aware of a Personal Data Breach affecting Personal Data and shall not wait for a complete investigation or a supervisory-notification assessment. The initial notice shall include available information on the nature of the breach, categories and approximate numbers of affected individuals and records, likely consequences, containment and remedial measures, and a contact point. Missing information shall follow in phases without undue delay. CRACI shall promptly contain and investigate the breach, preserve relevant evidence, mitigate adverse effects and assist with the Customer’s assessment, documentation and notifications under Articles 33 and 34 GDPR. CRACI shall maintain an incident record and report material developments and corrective action. Notices shall be sent to the Customer’s designated security contact in Schedule A and, if unavailable, its Agreement contact; unsuccessful delivery shall be escalated through available contact channels. The Customer decides on notifications to authorities and individuals, without prejudice to CRACI’s own mandatory obligations.
2.9.
Taking account of the nature of processing, CRACI shall assist the Customer through appropriate technical and organisational measures, insofar as possible, in responding to requests to exercise data-subject rights under Chapter III GDPR, in accordance with Article 28(3)(e). Taking account of the nature of processing and the information available to it, CRACI shall also assist the Customer in ensuring compliance with Articles 32–36 GDPR, including security, breach assessment, impact assessments and prior consultation, in accordance with Article 28(3)(f). CRACI shall promptly forward requests concerning Personal Data and not respond substantively except on instructions or where legally required. Assistance includes locating, exporting, correcting, restricting and deleting data; identifying recipients; and providing relevant data flows, security and transfer information in time for applicable deadlines. CRACI shall make available all information necessary to demonstrate compliance with Article 28 and allow and contribute to audits, including inspections, by the Customer or its mandated independent auditor. Reasonable notice, confidentiality, security controls and use of existing reports may be agreed, but shall not replace necessary inspections or impose absolute frequency limits. Notice may be shortened where a breach, suspected non-compliance or authority request warrants it. Audits shall minimise unnecessary disruption and protect unrelated data. CRACI shall procure equivalent assurance and necessary audit cooperation through its subprocessor contracts, and promptly remedy its non-compliance at its own cost. Reasonable fees for exceptional assistance or audits must be agreed in advance, shall not be disproportionate or dissuasive, and shall not delay mandatory cooperation or apply to remedying CRACI’s breach.
2.10.
The Customer grants general written authorisation to use only the subprocessors fully identified in Schedule C for the stated processing, subject to the transfer requirements. CRACI shall actively notify the Customer in writing at least seven (7) days before adding or replacing a subprocessor, including its legal identity, service, data involved, processing and access countries, transfer mechanism and safeguards. The Customer may object during that period on reasonable data protection grounds. The parties shall seek a suitable alternative in good faith; pending resolution the proposed subprocessor shall not process the affected Personal Data. If no satisfactory solution is available, CRACI shall cease the affected processing or the Customer may terminate the affected Services without an early termination penalty and receive a refund of unused purchased Credits allocated to those Services and recurring fees prepaid for the unused terminated period. Each subprocessor must be bound by a written agreement imposing the same data protection obligations as this DPA insofar as applicable, including confidentiality, security, assistance, audit, deletion and onward-subprocessor controls. CRACI remains fully liable to the Customer for performance of those obligations by subprocessors, subject to mandatory law and the liability clause below. CRACI shall maintain an accurate, accessible register of the processing chain and provide updates; posting a revised website list alone is not advance notice.
2.11.
During the Services and the applicable post-termination retrieval period, the Customer may retrieve Personal Data and choose return followed by deletion or deletion without return, and may amend that instruction before completion. CRACI shall provide return in a structured, commonly used, machine-readable electronic format and shall not require a return request before expiry or termination. In the absence of an earlier lawful deletion instruction, CRACI shall preserve the data needed for return and switching until the retrieval period defined in Section 8 (Customer Content) of Terms of Service has ended and any timely return request has been completed.
2.12.
CRACI shall then securely delete Personal Data from active systems, including those of its subprocessors, without undue delay and within thirty (30) days, or by an earlier mandatory deletion deadline, and shall confirm deletion on request.
2.13.
Personal Data remaining in backups shall be deleted through scheduled backup expiry and rotation, no later than twelve (12) months after the relevant backup was created. Individual Customer records cannot be selectively deleted from backups before expiry. Until deletion, backup data shall remain protected under this DPA, isolated from ordinary use and accessed only where necessary for disaster recovery. If a backup is restored, previously deleted Personal Data shall be deleted again before the restored system resumes ordinary processing. CRACI shall ensure that its subprocessors comply with the same requirements. This backup retention arrangement does not override any mandatory full-erasure deadline.
2.14.
Where Union or Member State law requires retention, CRACI shall identify its basis and period, restrict use and access to that obligation and delete the data when it ends.
2.15.
Subject to mandatory law, the Agreement’s liability provisions, including the limitation of liability applicable to breaches of data protection and security obligations, apply also to claims between the parties arising from this DPA. This DPA creates no separate indemnity, additional liability cap or duplicate recovery. Nothing in the Agreement or this DPA limits data subjects’ rights or compensation claims under Article 82 GDPR, any mandatory statutory liability or contribution right to the extent it cannot lawfully be limited, or the powers of supervisory authorities, including orders and administrative fines. Each party remains responsible for its own obligations under Data Protection Regulation; no contractual cap binds an authority or a data subject. The Agreement’s liability regime limits monetary recovery between the parties only insofar as legally permissible and does not excuse performance of this DPA.
2.16.
This DPA remains in force throughout the Services and until Personal Data and copies have been returned or deleted as required, including any lawful retention. Acceptance or updating of CRACI’s privacy notice does not constitute acceptance of this DPA or amend the Agreement or this DPA. Changes to this DPA require documented agreement, except for subprocessor updates made in accordance with its notice and objection procedure.
2.17.
Confidentiality, security, transfer restrictions, assistance, audit and deletion duties continue for as long as relevant Personal Data are retained; liability and accrued rights survive as applicable. The Agreement’s governing-law and dispute-resolution provisions apply, without prejudice to mandatory GDPR remedies and competent supervisory authorities.
Schedule A
DESCRIPTION OF PROCESSING AND CUSTOMER INSTRUCTIONS
Service selection and parties
The Customer and its identification details are those in the Agreement or in the Customer’s account in the Services. The processing covers the Services and features used by the Customer under the Agreement.
Subject matter and purpose
Processing necessary to provide the Services, including execution of the Customer’s CI jobs, generation of SBOMs, vulnerability monitoring and management, maintenance of the Customer’s component inventory, provision of compliance evidence and, where used, AI Features generating proposed fixes and pull requests. Purposes exclude AI model training, general service development and reuse for other customers. Regulatory notifications or submissions towards authorities and/or customers on customer's behalf are not included unless separately agreed with documented instructions and authorisation.
Nature and frequency
Receipt from the Customer, authorised users and connected code repositories; execution, transmission, storage, organisation, retrieval, analysis, generation of proposed code changes, export, restriction and deletion. Processing is ongoing during the Services, when jobs are executed and when the relevant feature or support operation is used. Only necessary data may be sent to each subprocessor.
Data subjects
The Customer’s employees, contractors, representatives and authorised users; developers and other individuals whose information is included in the Customer’s code repositories, commit history and build data; and other individuals whose Personal Data the Customer includes in Customer Content.
Data categories
The categories specified in the processing clause apply only to the extent present in the purchased Services and permitted instructions. CRACI’s independent processing as a controller, such as billing, CRM, product usage analytics and security logging, is outside this schedule.
Restricted data
Special categories under Article 9 GDPR, criminal-conviction or offence data under Article 10, and processing specifically targeting children are not authorised under the standard Services. The Customer shall not deliberately submit such information or instruct its collection or inference without a prior written processing amendment identifying the data, legal conditions, necessity and additional safeguards. If restricted data are incidentally received or inferred, CRACI shall limit access, avoid onward disclosure, notify the Customer and seek lawful deletion, redaction or other handling instructions.
AI processing
Where the Customer uses AI Features, vulnerability information and the necessary code context may be transmitted to the authorised AI providers listed in Schedule C only to generate the requested output, such as proposed fixes and pull requests. Model changes do not permit new recipients, locations, training purposes or retention practices outside this DPA. Inputs and outputs remain subject to confidentiality, purpose limitation, access, transfer and deletion safeguards. CRACI shall verify contractual no-training restrictions and relevant settings before sending Personal Data. A feature shall remain disabled if the required safeguards are unavailable.
Subject matter and purpose
Third-party platforms and services connected or integrated by the Customer are selected by the Customer and operate under their own terms with the Customer; their role depends on the actual processing. Any Customer Content or other data transmitted by CRACI to such platforms or services, including code changes and other outputs, is transmitted in accordance with the Customer’s instructions and configuration. CRACI’s own transfers and processing remain subject to this DPA.
Subject matter and purpose
Processing continues for the Services and the return and deletion periods in Section 2.12. Unless the Customer configures otherwise, job logs, metrics and dependency information are stored for thirty (30) days after execution; data linked to an inventory item is retained while that item remains in the inventory. Vulnerability information follows the associated job or inventory item. Job caches follow Customer-configurable retention settings; only artifact metadata is stored unless separately agreed.
As a rule, Customer source code is not retained on CRACI’s platform after job execution. Where the Customer uses CI/CD or CRACI-provided caching features to store source code or portions of it, that content remains subject to the applicable cache retention settings. Source code or other content written to job logs remains subject to the applicable log retention period.
Fixbox processes Customer source code only while the relevant Fixbox task is active. Commits and pull requests generated by Fixbox are stored in the Customer’s connected code repository. Once the task is completed, Fixbox closes and source code is no longer retained on CRACI’s platform, except to the extent stored in Customer-directed caches or logs as described above. Fixbox logs describing code changes may remain available after the task has ended and are subject to the applicable job log retention period.
For each AI recipient, Schedule C shall specify input and output retention, any human access and deletion controls, including whether prompts, responses or diagnostic logs are retained. No AI processing of Personal Data may start until those periods, recipients, locations and restrictions are agreed. No Customer source code may be included in CRACI’s routine backups. The Customer may give documented shorter-retention or deletion instructions. CRACI’s controller retention periods in its Privacy Notice do not apply here. Anonymous usage statistics fall outside this DPA only where individuals cannot be identified by means reasonably likely to be used; pseudonymisation alone is insufficient.
Customer rights and obligations
The Customer may issue lawful documented instructions, choose return or deletion, receive compliance information, exercise audit rights, object to proposed subprocessors on reasonable data protection grounds, and obtain the assistance set out in this DPA. The Customer shall control its user permissions, connected repositories, job configurations and secrets, review of AI-generated output and end-user devices and give necessary lawful instructions. Customer-side security responsibilities do not exclude CRACI’s responsibility for the platform or its processing chain.
Operational contacts for privacy, processing instructions and security/breach matters
The contact person designated by the Customer and CRACI in the Services, using the contact details maintained there. The Customer shall keep these details up to date.
Schedule B
TECHNICAL AND ORGANISATIONAL MEASURES
Minimum measures
CRACI maintains an information security management system certified under ISO/IEC 27001. The following are minimum commitments applicable throughout the Services. Alternative measures must provide at least equivalent, risk-appropriate protection.
Access and segregation
Maintain named accounts, role-based least-privilege access, timely joiner/mover/leaver procedures and periodic access review. Require multi-factor authentication for privileged and administrative access. Enforce Customer isolation, including isolated execution environments for each job, segregate storage and validate isolation when features change. Limit contractor and support access to authorised tasks.
Encryption and secrets
Use current, supported encryption for data in transit and stored Personal Data, including databases, job data and backups, with controlled key access. Protect access tokens, API keys and other secrets in restricted storage; exclude them from public content and unnecessary logs; rotate or revoke on compromise, offboarding or disconnection. Make Customer secrets available only to the jobs that require them and mask them in job logs.
Application and build environment security
Use authenticated and authorised access to Customer Content. Provide a Customer-configurable firewall for job execution environments, allowing the Customer to define network egress rules and restrict destinations accessible from jobs. Outbound access is unrestricted unless the Customer configures restrictions. Isolate production from development and avoid production Personal Data in testing unless necessary and safeguarded. Maintain secure development and change review, vulnerability assessment, supported components and risk-prioritised patching.
Logging and monitoring
Maintain access, administrative, security and material disclosure records proportionate to risk, protected against unauthorised alteration and access. Minimise Personal Data in logs and prevent logging of source code, secrets, credentials or tokens unless specifically necessary and protected. Set documented retention periods and monitor suspicious access, isolation failures and abnormal transfers.
Availability, resilience and backups
Maintain appropriate backup, recovery and continuity arrangements, restrict backup access and test restoration. Backups containing Personal Data are stored within the EEA and deleted through scheduled expiry and rotation no later than twelve (12) months after creation, in accordance with Section 2.12. Individual Customer records cannot be selectively deleted from backups before expiry. Following deletion from active systems, backup data shall remain isolated from ordinary use and may be accessed only where necessary for disaster recovery. If a backup is restored, deletion instructions shall be reapplied before ordinary processing resumes. Backup retention shall not override any mandatory full-erasure deadline.
AI and integration controls
Maintain an inventory of approved AI providers and prevent routing to unapproved recipients or regions. Apply binding no-training and limited-retention terms, verify provider settings and monitor changes. Send only the minimum data needed for the function; redact or pseudonymise unnecessary identifiers where feasible. Restrict human review by vendors to authorised, necessary and confidential processing. Do not use Customer Content to train AI models, except on the relevant Customer’s documented instructions to train a Customer-specific model exclusively for that Customer. Do not combine different Customers’ data for training or use a model trained on one Customer’s data to provide features or functionality to another Customer.
Organisational and incident measures
Maintain confidentiality undertakings, relevant staff training, vendor due diligence, an accountable security contact and documented incident procedures covering detection, escalation, containment, investigation, evidence preservation and Customer notification. Regularly evaluate control effectiveness and maintain remediation records. Subprocessor reviews shall cover onward access, locations, deletion and incident escalation. Require critical subprocessors to hold an ISO/IEC 27001 or SOC 2 Type II certification or provide equivalent assurance, reviewed annually.
Rights, deletion and assurance
Maintain procedures to locate and export Personal Data, correct and restrict records, honour deletion instructions and communicate them to subprocessors. Securely erase active copies and expire backup copies under the agreed schedule; maintain deletion confirmation and any lawful-retention record. Provide relevant testing, assessment and audit information to the Customer under appropriate confidentiality protections.
Schedule C
SUBPROCESSORS, LOCATIONS AND TRANSFERS
Subprocessor list
| Subprocessor name | Purpose | Description | Location | Transfer clauses (for non-EEA locations) |
|---|---|---|---|---|
| Amazon Web Services, Inc. | Hosting and infrastructure | Execution of CI jobs and storage of Customer Content, job data and backups | EEA | N/A |
| Google LLC | Hosting and infrastructure | Execution of CI jobs and storage of Customer Content, job data and backups | EEA | N/A |
| Hetzner Online GmbH | Hosting and infrastructure | Execution of CI jobs and storage of Customer Content, job data and backups | EEA | N/A |
| Microsoft Corporation | Hosting and infrastructure | Execution of CI jobs and storage of Customer Content, job data and backups | EEA | N/A |
| Lettermint B.V. | Email sending | User invitations and notifications sent on the Customer’s instruction | EEA | N/A |
AI providers
| Subprocessor name | Purpose | Location | Transfer clauses (for non-EEA locations) | Input and Output Retention | Human access | Model training |
|---|---|---|---|---|---|---|
| Amazon Web Services, Inc. | Generation of proposed fixes and pull requests | EEA and USA | Standard Contractual Clauses (SCCs) | 30 days | for abuse cases | no |
| Microsoft Corporation | Generation of proposed fixes and pull requests | EEA and USA | Standard Contractual Clauses (SCCs) | 30 days | for abuse cases | no |
| OpenAI, OpCo, LLC | Generation of proposed fixes and pull requests | EEA and USA | Standard Contractual Clauses (SCCs) | 30 days | for abuse cases | no |
CRACI’s current subprocessors are listed in the tables above. The list forms part of this DPA and identifies each subprocessor’s legal entity, purpose of processing, categories of Personal Data, processing and access countries, applicable transfer mechanism, retention periods and onward providers, where relevant. CRACI shall keep the list up to date. Additions and replacements remain subject to the notification and objection procedure set out in this DPA; updating the table does not replace that procedure.
For AI subprocessors, the second table also specifies input and output retention, human access, deletion controls and restrictions on model training.
Providers outside this processor inventory
Providers used solely for CRACI’s own activities as a controller, such as payment and billing services (e.g. Stripe and Metronome), accounting services, CRM and website analytics and marketing tools, are not subprocessors under this DPA. If any of them also receive Personal Data on the Customer’s behalf, they shall be added above.
Authorised baseline and updates
Completed register version/date: November 17 2026. Conclusion of this DPA approves only the subprocessors listed above at the time of conclusion. Subsequent additions and replacements follow the advance notice and objection procedure in this DPA. CRACI shall retain evidence of the authorised version, acceptance, notices and objections. Approval does not waive transfer safeguards or other mandatory obligations.