Skip to content
Artifact Repository Manager
Download

Legal

Data Processing Agreement

Last updated: 14 November 2026 · Version 2026-11-14

Contract terms for customer personal data processed by Aurora on the customer's behalf in an Aurora-hosted Artifact Repository Manager deployment. The standard schedule below applies with the relevant order.

1. Parties, scope and instructions

The customer identified in the order is controller, or a processor authorised by its controller; ACL Aurora Core Labs LTD (Aurora) is processor or subprocessor respectively. Processing lasts for the agreed service or support engagement and consists of receiving, storing, retrieving, transmitting, securing and deleting personal data within the customer's documented instructions. Scope includes hosted catalogue membership and access records, repository metadata, customer-supplied packages and related logs or support material to the extent they contain personal data. Data subjects may include customer staff, administrators, contractors and individuals identified in permitted service or support material. Health, biometric, criminal-offence and minors' personal data, and other special-category data, are prohibited. The customer establishes the lawful basis and required information, and authority from its controller where acting as processor. Aurora processes only on documented instructions unless legally required, notifying the customer where permitted, and informs the customer if an instruction appears unlawful. Support access requires the customer's communicated authorisation code and agreed scope.

2. Confidentiality and security

Aurora applies encryption in transit and at rest, MFA for administrative access, access restricted to authorised personnel bound by confidentiality, and separation between customer environments and data. The customer controls its own users, permissions and on-premise systems. Support access to customer data in Aurora-hosted cloud services requires the customer to communicate an authorisation code for the agreed scope; a general support request is not unrestricted authorisation. The code mechanism does not apply to on-premise installations and grants no access to customer-operated systems. No customer-data backup or restoration service, recovery time, availability SLA or certification is included unless expressly agreed in writing. Customers must keep independent copies. These service limitations do not exclude Aurora’s risk-appropriate security, availability and resilience obligations under Article 32 GDPR or other mandatory duties.

3. Subprocessors

Aurora currently processes customer personal data itself and appoints no external customer-data subprocessors. Aurora is the processor, not an external subprocessor on its own list. Before appointing a future subprocessor, Aurora must identify its legal entity, function, processing locations and transfer safeguards, obtain the customer’s written authorisation and impose equivalent obligations. Aurora remains responsible for its subprocessor’s performance. Under an agreed general authorisation, Aurora gives at least 30 days’ advance notice and an opportunity to object on reasonable data-protection grounds; unresolved affected processing must not proceed without a lawful agreement. Paddle is an independent controller for sales. Optional public-website analytics and customer-contracted integrations are distinct from Aurora’s customer-data subprocessor list; their actual role must be reassessed if their use changes.

4. Assistance and incidents

Taking account of the processing and information available, Aurora assists with data-subject requests, security duties, impact assessments and consultation with authorities under Articles 32–36 GDPR. Aurora notifies the customer without undue delay after becoming aware of a personal data breach affecting customer data, providing available information about nature, affected data, likely consequences and mitigation, with further information as it becomes available. Aurora does not respond to customer data-subject requests except on instructions or legal obligation.

5. International transfers

Aurora-hosted customer-service storage and administration take place within the European Union. Customer-operated deployments and integrations independently selected and contracted by the customer may use other locations; the customer determines and authorises those destinations. Any personal-data transfer outside the EEA for which Aurora is responsible requires documented instructions and a valid GDPR Chapter V mechanism, including appropriate Standard Contractual Clauses, assessments and supplementary measures where required, before transfer. Customer-controlled integrations do not themselves authorise Aurora to appoint an external processor.

6. Return and deletion

Customer personal data is processed for the duration of the relevant service agreement, including an eligible free-plan continuation. When that processing ends, Aurora returns or deletes personal data at the customer’s choice and deletes existing copies unless law requires retention. Active-system deletion is immediate upon effective termination of processing or a valid deletion instruction, following any return requested before deletion. Any residual technical copies are removed within 30 days, protected and excluded from ordinary use until removal. This deadline does not promise backup availability; no customer-data backup or restoration service is included. Plan limits govern ordinary export features but do not restrict mandatory return or deletion rights; request return arrangements at dpo@auroratech.ai before effective termination or deletion. Genuinely anonymous permitted technical aggregates may be retained without a fixed expiry; customer content and merely pseudonymised data do not qualify. Any legally required retention is limited to the applicable obligation.

7. Accountability and audits

Aurora makes available information needed to demonstrate compliance and allows and contributes to audits, including inspections, by the customer or its mandated auditor. The parties coordinate reasonable confidentiality, security and scheduling arrangements without preventing statutory audit rights or regulatory access. Each party maintains records required by law. This DPA prevails over conflicting product terms for processing of customer personal data; mandatory data-subject rights and liability under the GDPR remain unaffected.

8. Standard deployment schedule

The order identifies the customer, its controller/processor role, service, deployment and duration. Aurora is ACL Aurora Core Labs LTD, Strovolou, 77, 2018 Strovolos, Nicosia, Cyprus. Privacy and incident contact: dpo@auroratech.ai. For Aurora-hosted service processing, data is hosted within the European Union and administered from Cyprus. No external customer-data subprocessors are appointed. Security measures are those in section 2; no customer-data backup service or SLA is included. Customer-specific data lasts for the service agreement, with immediate active-system deletion when processing ends or valid deletion is instructed and removal of residual technical copies within 30 days, subject to section 6. An eligible free-plan continuation remains an active service relationship. Customer-operated storage and locations remain under customer control. The authorisation-code mechanism is limited to Aurora-hosted cloud services; it does not apply to on-premise installations or grant access to customer-operated systems. Customer-contracted AI and other integrations follow the customer’s configuration and instructions; record any relevant external destinations and transfer arrangements before enabling them. An individual written agreement may specify additional lawful instructions and commitments without reducing mandatory rights.

9. Technical statistics and excluded content

Where the agreement includes the anonymous-statistics permission, the customer instructs Aurora to derive anonymous aggregates only from lawfully processed technical and usage measurements, within the customer’s authority and applicable documented instructions. This does not authorise anonymising customer content for AI reuse. SpecDox documents, documentation, specifications, source code, prompts, conversations and outputs; repository/package content; terminal/SSH input, output and commands; credentials, infrastructure configurations, targets, scan findings and reports are excluded from AI development datasets even if anonymised. Customer content remains processed only to provide the instructed service, including customer-configured AI workflows, and is subject to return and deletion. Account-linked telemetry remains personal data; hashing alone does not establish anonymity. Before technical aggregates are reused, Aurora must document identification, linkage and extraction risks and ensure confidentiality and content-rights safeguards. Only genuinely anonymous aggregates satisfying those conditions may be retained indefinitely and used for the specified AI purposes, including commercial models. Any own-purpose processing of personal source data requires a separately established lawful basis and transparency before it begins. No external training provider is appointed.

Contact · Privacy · Terms