DPA Addendly v2.5 — Personal data processing agreement (Article 28 GDPR)
Version 2.5 — 3 November 2026. Annex to the Addendly Terms v3.6. Replaces version 2.4 of 2 November 2026 for new sign-ups from publication. For existing Customers, this version applies following express acceptance and no earlier than 30 days after notice by email and in the app, under Article 10 of the Terms; until then, the previously accepted version remains applicable, subject to mandatory law. Courtesy translation.
1. Parties, roles and subject matter
1.1 Controller: the customer subscribing to the Addendly General Terms (the “Customer”), a business or professional managing changes to private engagements or works contracts.
1.2 Processor: X20 Digital Trust Services S.r.l., Via Luigi Varanini 24, 20127 Milan, tax code and VAT number 12300800963, certified email (PEC) x20digitaltrust@pec.x20digitaltrust.com, email info@x20digitaltrust.com (“X20”).
1.3 This agreement governs X20's processing of personal data on behalf of the Customer in providing Addendly. Only for accounts, billing and pilot requests does X20 act as independent controller: the Service Privacy Notice applies, rather than this agreement.
1.4 Definitions are those in Article 4 GDPR. The Service is Addendly; the Data is described in Annex A.
2. Documented instructions
2.1 X20 processes Data only on the Customer's documented instructions. Documented instructions comprise this agreement and its annexes, the General Terms, the settings chosen by the Customer in the Service (changes, reminders, users and permissions), and subsequent requests sent in writing to the contacts in Article 1.2.
2.2 X20 does not use Data for its own purposes, transfer it or disclose it to third parties except as provided in Article 5, and does not use it to train artificial intelligence models; the Service includes no generative artificial intelligence features.
2.3 If X20 considers that an instruction infringes the GDPR or other data protection provisions, it immediately informs the Customer and suspends or refuses the instruction for as long as it remains unlawful. The Customer's written confirmation does not remedy the unlawful instruction or authorise its execution.
2.4 Where Union or Member State law requires X20 to carry out further processing, X20 informs the Customer before proceeding, unless the law prohibits such information on important grounds of public interest.
3. Confidentiality and authorised persons
3.1 X20 authorises only persons necessary for providing and supporting the Service to process Data, identifying and instructing them in writing under Article 29 GDPR and Article 2-quaterdecies of the Italian Privacy Code, and binding them to confidentiality after the relationship ends as well.
3.2 X20 staff access Data only when essential for maintenance, security or Customer-requested support, with minimum privileges and logged operations.
4. Security measures
4.1 Annex B v2.5 is contractual and describes the measures of the Service. Its scope is the account application and its server functions. The measures and subprocessors are those listed in Annexes B and C in force.
4.2 X20 may update measures to reflect technical or regulatory developments, provided that the security level is not reduced; material changes are communicated to the Customer.
4.3 The Customer is responsible for configuring its users, assigning permissions, using personal credentials and activating two-factor authentication where the Service makes it available.
5. Subprocessors
5.1 The Customer gives X20 general authorisation to use the subprocessors listed in Annex C, with whom X20 enters into agreements imposing data protection obligations no less onerous than those in this agreement.
5.2 X20 informs the Customer of any addition or replacement of subprocessors with at least 15 days' notice (Article 28(2) GDPR), including in case of security emergencies or provider-imposed changes; if the notice period cannot be observed, X20 suspends the affected processing before entrusting it to the new subprocessor. The Customer may object to both additions and replacements on reasonable grounds and, if no solution is found, terminate without penalties. On such termination, X20 refunds the paid but unused period.
5.3 X20 is responsible for its subprocessors' conduct as for its own.
6. Transfers outside the European Economic Area
6.1 Annex C identifies, for each entity, its address, processing and remote-access countries, onward chains, transfer safeguard and verification date. No transfer starts before Chapter V GDPR safeguards have been verified for the specific processing and entity.
6.2 Where the standard contractual clauses under Decision (EU) 2021/914 are used, X20 enters into them in its own capacity as exporting processor, module 3, completing the annexes, transfer assessment and necessary supplementary measures. Any reliance on the DPF requires valid participation by the specific entity and coverage of the processing. The Customer may obtain copies of safeguards from info@x20digitaltrust.com, with only confidential information unnecessary for verification redacted.
7. Assistance to the Customer
7.1 X20 assists the Customer in handling the exercise of rights through appropriate technical and organisational measures. Contractual corrections are documented through linked changes; legally required rectification and deletion take place through authorised, logged and selective interventions, retaining a record of the intervention and limiting residual data to what is necessary. X20 forwards requests received from individuals to the Customer without undue delay, without deciding on their merits.
7.2 Breaches. X20 notifies the Customer of any personal data breach of which it becomes aware without undue delay and in any event within 48 hours of becoming aware, providing the information under Article 33(3) GDPR to the extent available, and cooperates with the Customer's assessments and notifications. Notification does not constitute an admission of liability.
7.3 Under Article 28(3)(f) GDPR, X20 assists the Customer with obligations under Articles 32–36, taking account of the nature of processing and the information available: security, breaches, notifications and communications, impact assessments and prior consultation. Annex B and the Security information sheet support but do not exhaust the assistance owed.
7.4 X20 makes available to the Customer the information necessary to demonstrate compliance with Article 28 GDPR.
8. Audits
8.1 X20 makes available to the Customer all information necessary to demonstrate compliance with Article 28 GDPR, including relevant security and subprocessor documentation. It responds without undue delay and within 30 days, or within a shorter period necessary to comply with legal obligations or an authority’s request. No annual limit applies to requests or audits.
8.2 X20 allows for and contributes to all audits, including inspections, conducted by the Customer or another auditor mandated by the Customer under Article 28(3)(h) GDPR, without charging the Customer. Documentary, on-site and system audits are not conditional on demonstrating an incident or other justified grounds.
8.3 The parties promptly coordinate audit notice and arrangements according to the circumstances, without making audits subject to X20’s discretionary consent. In cases of urgency, incidents, suspected non-compliance or an authority’s request, audits take place within the necessary timeframe, including without notice where required. Arrangements protect security, confidentiality, trade secrets and other customers’ data without preventing or rendering audits ineffective. Auditors are not automatically excluded because they compete with X20; confidentiality obligations do not prevent legally required disclosures.
8.4 Nothing in this article limits supervisory authorities' powers or X20's obligations towards them.
9. Deletion and return
9.1 The Customer may request export and switching to another provider under Articles 11.4–11.5 of the Terms. On termination, the Customer chooses between return and deletion under Article 28(3)(g) GDPR. For return, the Customer has 90 days, with assistance even if ordinary access is suspended and delivery in a structured, commonly used format; deletion of Data and copies follows. Unless otherwise instructed, data remains available for return for 90 days after termination and is then deleted.
9.2 If the Customer chooses deletion, X20 carries it out within 30 days of the request, including before termination, without waiting for the return window. It also deletes existing copies. Only X20's legal obligations or instructions for different retention agreed in writing as to duration and conditions are excepted. Any residual data is limited to necessary data, purposes and periods; in the event of a restore, deletions already carried out are reapplied.
9.3 The Customer determines retention instructions: normally 10 years after completion of the works; longer only if the limitation period is interrupted, a dispute or enforcement of a decision is ongoing, or another statutory obligation requires it. The Customer ensures necessary copies; export alone does not guarantee compliant retention. Holds are documented and selective, reviewed every 12 months and lifted when their grounds cease.
9.4 The deletion procedure identifies the operational person responsible, records requests and interventions and checks storage, attachments, events and residual copies before written confirmation to the Customer.
10. Liability and relationship with the General Terms
10.1 Liability and compensation are governed by applicable law, including Article 82 GDPR, without contractual limitations. Individuals’ rights, authorities’ powers and statutory rules on liability and recourse between parties involved in processing remain unaffected.
10.2 Each party is responsible for its own breaches of the obligations specifically imposed on it by the GDPR. The Customer warrants that it has a legal basis for the processing entrusted to X20, has provided individuals with the required notice and does not upload to the Service data unnecessary for managing changes.
10.3 This agreement prevails over the General Terms for processing personal data on the Customer's behalf. In a conflict with other agreements between the parties concerning the same processing, this agreement prevails unless the other agreement provides greater safeguards for individuals.
11. Duration, assignment, law and jurisdiction
11.1 This agreement lasts for the duration of the Service contract and, where necessary, survives until deletion under Article 9 is complete.
11.2 Assignments and succession are governed by applicable law and Article 11.3 of the Terms, without advance assignment consent being given through this DPA. The DPA follows the Service relationship; transfer of the contractual position is governed by applicable law. Processing instructions, measures and safeguards, and verification of safeguards under Article 28(1) GDPR, remain applicable. Article 11.3 of the Terms governs succession notices, Customer termination and refunds for the unused prepaid period. Additions and replacements of subprocessors remain subject to Article 5. Mandatory effects of statutory succession remain unaffected.
11.3 Italian law applies; jurisdiction is determined under ordinary statutory rules.
Annex A — Description of processing
| Item | Content |
|---|---|
| Subject matter | the Addendly service for documenting changes to private engagements and works contracts, sending proposals and collecting decisions with an email code |
| Duration | duration of the service and return/deletion under Article 9; Customer instructions for necessary retention |
| Nature and purpose | collection, recording, organisation, storage, consultation, extraction, sending invitations and receipts, return and deletion, to manage and document the Customer's relationship with the client |
| Individuals | consumer and professional clients, representatives and contacts; Customer users for project operations; third parties mentioned or depicted in necessary attachments |
| Data | name, email, project role, descriptions, amounts, timing, necessary photos and PDFs, versions, fingerprints, events, truncated IP, browser, system date and time, outcome of code verification, notes, optional early-start request and optional full-performance consent |
| Special categories | not requested; the Customer avoids excessive data and reports any incidental inclusion for appropriate removal and protection instructions |
| Automation | sending codes, integrity checks and amount calculations; no profiling or solely automated decisions under Article 22; no AI training |
Annex B — Technical and organisational measures
Version 2.5 — 3 November 2026. Scope: account application, database, attachment storage and server functions of the Service.
| Area | Measures |
|---|---|
| Access and segregation | Supabase authentication with email sign-in links; owner, collaborator and reviewer roles; row-level policies separating organisations. Administrative functions require an authorised administrator and a two-factor session (aal2). |
| Email codes | Approval-link tokens are generated with HMAC-SHA256 and a secret server key and stored as SHA-256 fingerprints; verification codes are stored as HMAC-SHA256 with the same key. Links last 14 days; decision codes last 10 minutes and are blocked after 5 incorrect attempts. The outgoing email queue contains the code needed for delivery. |
| Transport and attachments | Resend delivery uses an HTTPS endpoint. The production header configuration specifies Strict-Transport-Security. The attachment bucket is private, with organisation-based access policies; client downloads require a valid change link and a signed URL lasting 5 minutes. |
| Traceability | Server-generated event hash chain and integrity checks; sent versions and approvals protected against ordinary updates and deletion. Data requests and administrative operations have dedicated records. |
| Export and deletion | Authenticated account export; account deletion requires email confirmation and checks for sole ownership and disputed projects. The procedure removes eligible organisations’ files, structured data and the authentication user, and records the outcome of the data-deletion stage. Blocked requests are recorded. Requests for selective intervention follow Article 9. |
| Application retention | A server cleanup function removes sent email text after 30 days, sent email outside studios after 30 days, and pilot requests, data requests and authentication logs after 12 months. |
| Backup and recovery | Supabase runs daily physical backups of the database, with 8 copies retained; PITR is not enabled. Attachments have a nightly replica on Cloudflare R2, encrypted with AES-256-GCM, retained for up to eight days. Each copy is retrieved and verified using SHA-256. Database and attachment restoration has been verified in an isolated local environment by comparing counts and file hashes. Subsequent deletions are reapplied before data is reused; recovery of non-empty files and repeated application of deletions without further effects have also been verified. Restoration from the Supabase production managed backup has not been verified. |
Annex C — Subprocessors
Verified on 29 and 31 October 2026, as stated for each provider, against the providers’ data processing agreements, their subprocessor lists and the official Data Privacy Framework list (dataprivacyframework.gov).
| Provider and entity | Service and data | Entity address | Processing and access countries | Transfer safeguard | Verification |
|---|---|---|---|---|---|
| Supabase, Supabase Pte. Ltd. | Database, authentication, attachment storage and server functions; account and project data, attachments and events | 65 Chulia Street #38-02/03, OCBC Centre, Singapore 049513 | Data stored in the EU region eu-west-1 (Ireland). Remote access from Singapore (Supabase Pte. Ltd.) and the United States (Supabase, Inc., support; infrastructure providers in the Supabase list of 12 October 2026) | Standard contractual clauses (EU) 2021/914, module 3, incorporated in the Supabase DPA (version 1, 1 August 2026); Singapore and Supabase, Inc. have neither DPF participation nor an adequacy decision | 29 October 2026: project region from the management panel, DPA and subprocessor list |
| Resend, Plus Five Five, Inc. | Transactional email; addresses, names, message content, links, codes and receipts | 2261 Market Street #5039, San Francisco, CA 94114, United States | United States (sending and storage on Amazon Web Services, Inc., and other US providers in the Resend list of 27 August 2026) | EU-US Data Privacy Framework participation active on the official list (status “Active - Re-certification under Review”); alternatively standard contractual clauses (EU) 2021/914, module 3, incorporated in the Resend DPA | 29 October 2026: DPF list, DPA and subprocessor list |
| Cloudflare, Cloudflare, Inc. | Hosting of the web application and website (Cloudflare Pages) and proxy for requests to server functions (Cloudflare Workers); encrypted attachment backups (Cloudflare R2); IP address, technical connection data and data transmitted in requests, including account and project data in transit | 101 Townsend Street, San Francisco, CA 94107, United States | R2 copies stored with EU jurisdiction; request routing over the Cloudflare global network (348 cities, network page read on 31 October 2026), without a guarantee of localisation in the EEA; the actual destinations cannot be determined in advance. Server function responses are not cached (no-store). Support access by the 18 subsidiaries of the Cloudflare group, in 17 countries, with the limitations stated in the list (United States, United Kingdom, Singapore, Australia, Germany, Portugal, France, Japan, Canada, Netherlands, United Arab Emirates, South Korea, Mexico, Malaysia, India, Sweden, Switzerland) and by the developer platform providers in the Cloudflare list of 1 October 2025 (Google LLC: EEA, United States, Australia, India; Oracle America, Inc.: United States, EEA, United Kingdom, Japan, Australia, Canada, Singapore) | Exporter X20, processor; importer Cloudflare, Inc.: EU-US Data Privacy Framework participation active on the official list; alternatively standard contractual clauses (EU) 2021/914, module 3, with Annexes I and II completed by the Cloudflare DPA (version 6.4, 3 April 2026, Article 6.2). The DPF covers only the certified entity and the covered processing; onward transfers are subject to the applicable obligations (Article 6.3 of the Cloudflare DPA), without automatic extension of adequacy | 29 October 2026: DPF list and DPA; 31 October 2026: subprocessor list, DPA and network page |
| Lovable | Former hosting of the app, deactivated on 31 October 2026, and of the website, deactivated on 1 November 2026; technical data of visitors to those pages until deactivation (IP address, user agent, requests) | — | No longer used since 1 November 2026 | No longer used since 1 November 2026 | 31 October 2026: app hosting deactivated; 1 November 2026: website hosting deactivated |
Onward chains: the subprocessor lists referenced in the providers’ DPAs (Supabase, Resend, Cloudflare), as at the verification date. Provider DPAs: Supabase, Resend, Cloudflare. For each transfer, the exporter, importer, applicable safeguard and, where used, standard contractual clauses with the relevant module and annexes are identified. In onward transfers these obligations lie with the parties in the chain that make them, subject to X20’s verification. X20 documents the assessment of each transfer (law and practice of the destination country, supplementary measures) and makes it available to the Customer under Article 6.2. Article 6 remains applicable. Additions and replacements follow Article 5.2, including 15 days’ notice and the right to object. A supplier’s further engagement requires the authorisation procedure in Article 5. For Cloudflare, group entities and third-party providers are listed in the list of 1 October 2025; the applicability and safeguards of individual chains are still under verification.
The Italian version prevails.