DPA · YARIPO

Data Processing Agreement

This Data Processing Agreement governs the processing of personal data that Yaripo SpA carries out on behalf of its clients in the context of consulting, academy, SaaS products, AI, support, PoC, automation, hosting and integration services, under standards compatible with GDPR and the EU data protection framework.

Executive summary

Enterprise-ready DPA

This DPA is designed for Yaripo to operate, as a general rule, as Data Processor on behalf of the Client, covering scenarios including consulting, compliance review, data protection, AI, academy, support and digital products.

Contractual approach. This document organises the data protection layer applicable to the relationship between Yaripo and its clients when Yaripo processes personal data on their behalf.
Legal design basis

GDPR + EU data protection framework

The contractual logic follows the minimum structure typically required for processing on behalf of a controller: subject matter, duration, purpose, data types, categories of data subjects, confidentiality, security, sub-processors, assistance, audit and end of service.

Important. Where a client requires specific international transfer annexes, additional standard contractual clauses or closed lists of sub-processors, these can be documented separately.
01

Subject matter and relationship with the main contract

Data protection annex

The DPA governs the processing of personal data that Yaripo carries out on behalf of the Client in the provision of services. It shall operate as an annex to or integral part of the main contract, taking precedence in matters of personal data processing where a specific conflict arises.

02

Roles of the parties

Client as Controller, Yaripo as Processor

The baseline structure designates the Client as Data Controller and Yaripo as Data Processor, as a general rule, with respect to data processed on behalf of the Client.

Yaripo's own processing. This does not prevent Yaripo from acting as an independent controller for its own data relating to billing, corporate security, legal compliance, commercial activity or the defence of rights.
03

Scope of processing

Purpose, duration and categories

The DPA shall describe, at a minimum, the subject matter of the processing, its duration, the nature and purpose, the types of personal data and the categories of data subjects. In Yaripo, this covers consulting, academy, SaaS, AI, support, PoC, automation, hosting and integration.

Categories may include professional contact data, end users, enterprise datasets, technical logs, prompts, inputs, outputs and, exceptionally, sensitive or financial data if the Client validly incorporates or instructs Yaripo to process them.

04

Processing under Client instructions

Limits and lawfulness of processing

Yaripo shall process personal data only in accordance with documented instructions from the Client, unless required to do so by applicable law.

The Client must ensure that it has a sufficient legal basis, legitimate purposes and the authority to provide Yaripo with the data that is the subject of the service.

05

Security and confidentiality

Technical and organisational measures

The Processor shall provide sufficient guarantees to implement appropriate technical and organisational measures.

In practice, Yaripo may apply access controls, encryption, MFA, secrets management, monitoring, environment segregation, backups, vulnerability management and reasonable incident response measures.

06

Sub-processors

General enterprise authorisation

For enterprise environments, the most practical model is generally a general authorisation for sub-processors, with an obligation to impose equivalent obligations on them and to notify the Client of relevant changes.

Recommended design. Yaripo may use general authorisation with the Client retaining the right to raise a reasoned objection to a material sub-processor.
07

International transfers

Adequate mechanisms by jurisdiction

Where processing involves international transfers, the DPA may allow for the use of adequate mechanisms according to the applicable jurisdiction, including adequacy decisions, standard contractual clauses and equivalent contractual, technical or organisational safeguards.

Yaripo structures these safeguards in accordance with the GDPR and applicable EU data protection framework for both domestic and international contracts.

08

Security incidents

Reasonably prompt notification

The prudent wording that best serves this purpose is: notification to the Client as soon as reasonably practicable after an incident with a material impact on personal data processed under the DPA has been confirmed.

Notification. Specific regulatory timeframes or particular contractual requirements may continue to apply where relevant to the specific case.
09

Audit and compliance evidence

Reasonable minimum, controlled scope

Yaripo may make available to the Client reasonably necessary information to demonstrate compliance through documentation, policies, questionnaire responses, control summaries or other appropriate evidence.

On-site audits or intrusive testing should only proceed on an exceptional basis, with a limited scope, prior notice and under strict confidentiality obligations.

10

End of service: return or deletion

Closure of processing

Upon termination of services, Yaripo may return or delete the personal data at the Client's election, unless a legal retention obligation or residual need for backup, defence or compliance purposes applies.

11

Sensitive data and financial data

Enhanced cases and restrictions

As Yaripo may provide data protection assessment and review services in organisations, the DPA shall contemplate that the Client may instruct the processing of sensitive or financial data.

In such cases, the Client must ensure a valid legal basis, necessity and sufficient authority, and Yaripo must limit processing to the strictly necessary scope.

12

Minimum operational annex

Processing quick reference

Every DPA shall be closed with an operational annex summarising: