# Privacy notice — Addendly

Version 3.6 — 3 November 2026. Courtesy translation.

## 1. Controller and contact
X20 Digital Trust Services S.r.l., Via Luigi Varanini 24, 20127 Milan, VAT number 12300800963, is controller for accounts, subscriptions and payments, billing and pilot requests. For any privacy request, write to info@x20digitaltrust.com.

## 2. X20 purposes, data and legal bases
| Data and individuals | Purpose | Legal basis and interest | Provision |
|---|---|---|---|
| Name, email, organisation, credentials and support for the individual party to the contract | managing the relationship | Article 6(1)(b), contract and requested precontractual steps | necessary for the service |
| Name, email, role, credentials and support for business representatives and employees | managing accounts and access | Article 6(1)(f), X20's and the business's interest in managing accounts and authorised access | necessary for access |
| Account access and operations | security and abuse prevention | Article 6(1)(f), interest in protecting accounts and service, limited to what is necessary | necessary for security |
| Subscription and transaction data: Paddle order, transaction, subscription and customer identifiers, product, price, paid period, status, renewals, cancellations, refunds and chargebacks, date and time of payment events | purchase and activation of plan and extras, allowances, cancellation and refunds | Article 6(1)(b), contract | necessary for purchase |
| Tax and billing data | accounting and tax compliance | Article 6(1)(c), legal obligations | mandatory for compliance |
| User identifier, email, business domain, trial start, end, status and usage | trial management: duration and limits | Art. 6.1.b, performance of the contract for the individual who is a party; Art. 6.1.f, X20’s and the business’s interest in managing access for representatives and employees | necessary for the trial |
| Hashes of user identifier, normalised email and business domain, grant date | trial uniqueness and prevention of repeated activations | Art. 6.1.f, X20’s legitimate interest in preventing abuse of the free trial and protecting service resources, within necessary limits | necessary to verify trial eligibility |
We use user identifier, email, business domain and trial status to manage its duration, limits and uniqueness. For the uniqueness check, the verified email is normalised to lowercase without the + suffix; for Gmail, dots are also ignored and googlemail.com is equivalent to gmail.com. We do not group users by domain for the following shared email domains: gmail.com, googlemail.com, yahoo.com, yahoo.it, outlook.com, hotmail.com, hotmail.it, live.com, live.it, icloud.com, me.com, mac.com, aol.com, libero.it, virgilio.it, tiscali.it, alice.it, proton.me, protonmail.com, privaterelay.appleid.com. Other domains are also checked at business level. The hashes and grant date remain in the separate anti-abuse register even after account deletion to prevent trial reactivation; they do not contain projects and are not anonymous data. They are retained for as long as necessary to enforce the uniqueness of the offered trial, with review of necessity and deletion when that purpose ceases. The rights in §6 remain available, including objection to processing based on legitimate interests.
The Pilot and extras are purchased online through Paddle.com, authorised reseller (merchant of record). At checkout Paddle collects payment, billing and tax data (for example name, email, country, address, VAT number and payment method) as independent controller under its own privacy notice (https://www.paddle.com/legal/privacy). X20 does not receive or store card data; it receives from Paddle only the subscription and transaction data listed above.
Pilot requests already sent before online purchase contain name, studio, email, telephone and message; they are processed to respond to the request (Article 6(1)(b), requested precontractual steps) and retained as set out in §5. The pilot request form is no longer available in the app.
With “Continue with Google” or “Continue with Apple”, the chosen provider verifies identity as independent controller under its own privacy notice and sends X20 the email, name where available and account identifier, used only for sign-in (Article 6(1)(b)).
Failure to provide necessary data prevents the relevant service. No privacy consent is required to approve a change.
Data is supplied by the individual or, for invited users, by the business: name, email and role. For indirect collection, X20 provides this notice under Article 14 within one month and no later than the first communication with the individual or, if earlier, the first disclosure to another recipient. It provides information before use for further purposes.

## 3. Clients and projects: Customer as controller, X20 as processor
The business or professional sending the change is the Customer and controller for project data; X20 processes it on their behalf under Article 28 and the Addendly DPA v2.5 (for existing relationships, the applicable accepted version). Article 28 defines the role, not a legal basis.
For individual clients who are parties to the contract, the business relies on Article 6(1)(b) to manage and perform the relationship and changes. For representatives and employees, Article 6(1)(f) applies: the business's interest in managing accounts, access and contacts for the relationship. For third parties mentioned in documents, the business relies on Article 6(1)(f): documenting the work and protecting rights arising from the relationship, using only strictly necessary data and assessing competing interests.
Data includes name, email, role, project, descriptions, amounts, timing, necessary attachments, versions and fingerprints, decisions and notes, date and time, truncated IP, browser, code verification, early-start request and full-performance consent where given. Truncated IP addresses and fingerprints remain personal data. Identity documents and special categories are not requested; avoid excessive data. No profiling, solely automated decisions under Article 22, data sales or AI training.

## 4. Recipients, countries and transfers
Access is limited to authorised staff and necessary infrastructure, storage, transactional email and support providers, and authorities where required by law. Entities selling and invoicing in their own name act as independent controllers for those activities. Data is not publicly disseminated.
Supabase provides authentication, database, attachment storage and server functions, including subscription and transaction data. Paddle, as reseller, sells the plan and extras, collects payment, invoices and handles taxes, refunds and chargebacks as independent controller. Resend sends transactional email, including links, codes and receipts. Cloudflare provides hosting for the web application and the website and operates the proxy for requests to server functions, including IP address, technical connection data and data transmitted in requests. Lovable was previously the hosting provider of the app and the website, deactivated on 31 October 2026 for the app and on 1 November 2026 for the website; until then it processed technical data of visitors to those pages (IP address, browser type, requests). The database and primary attachments are stored in the EU region eu-west-1 (Ireland). Encrypted attachment backups are stored on Cloudflare R2 with EU jurisdiction, for up to eight days. The following are transfers outside the EEA: Supabase remote access from Singapore and the United States, under standard contractual clauses (EU) 2021/914; Resend and Cloudflare in the United States, with EU-US Data Privacy Framework participation verified on 29 October 2026 and standard contractual clauses; routing over the Cloudflare global network, without a guarantee of localisation in the EEA, and support access by Cloudflare group companies, with the same safeguards. The DPF covers only the certified entity and the covered processing. Entities, addresses, countries and safeguards are in DPA Annex C; provider agreements: [Supabase DPA](https://supabase.com/legal/dpa), [Resend DPA](https://resend.com/legal/dpa), [Cloudflare DPA](https://www.cloudflare.com/cloudflare-customer-dpa/).
For processing entrusted by the business, DPA Annex C is the contractual list of subprocessors, including entities, addresses, activities, processing and access countries, onward chains and safeguards. Transfers outside the EEA require an applicable Chapter V GDPR safeguard verified for the specific entity: an adequacy decision, including valid and relevant DPF participation, or standard contractual clauses with the necessary assessment and supplementary measures. Copies of safeguards can be requested from info@x20digitaltrust.com.

## 5. Retention
- Accounts: contract duration plus 12 months; account security logs: 12 months, except for incidents and only for necessary data.
- Pilot requests: 12 months after the last update or collection; data requests: 12 months. Sent email bodies and sent messages outside studios: 30 days in the application database. Provider retention follows the agreements linked in §4.
- Subscriptions and payments: for the contract duration; records of transactions, refunds, chargebacks and payment events needed for accounting and the protection of rights: 10 years.
- Billing: 10 years for X20's obligations.
- Projects, versions, attachments and events, on Customer 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. Holds cover only necessary data, are reviewed every 12 months and end when their grounds cease.
- On termination, the Customer chooses return or deletion under the DPA. X20 carries out deletion within 30 days of the request, without waiting for the 90-day return period. Copies are also deleted, subject to legal obligations or retention agreed in writing. The Customer ensures retention of their own necessary copies.
- Links and codes are valid for 14 days and 10 minutes respectively. Verification elements needed to document the decision follow project retention; other data is retained only as necessary for security and management of the relevant access.

## 6. Rights and complaints
Where Articles 15–22 GDPR apply, you may request access, rectification, erasure, restriction and portability, and object to processing based on legitimate interests on grounds relating to your situation. For X20 processing, write to info@x20digitaltrust.com; for business processing, contact the controller identified in the change. X20 promptly forwards relevant requests to the Customer and assists them.
You may complain to the Italian data protection authority (www.garanteprivacy.it) or another competent authority. For any consent-based processing, withdrawal does not affect the lawfulness of earlier processing. The processing described here does not require general privacy consent.
Contractual corrections are documented through linked changes. Legally required rectification and deletion are carried out through authorised, logged and selective interventions, retaining a record of the intervention and limiting residual data to what is necessary. Retention to defend a right is assessed case by case under Article 17(3)(e).

## 7. Security and local storage
Business account access is reserved to persons aged at least 18; consumer clients approve through a link without an account. The app with an account stores the authentication session, selected studio, language and preferences in the browser. Text and attachments in forms that have not yet been submitted remain only in memory while navigating within the open page and are not saved in localStorage or IndexedDB. A reload or closing the page causes these drafts to be lost; signing out clears their content from memory. Persistent preferences may remain after the browser closes and can be cleared through site-data settings. These technical memories are not advertising trackers. On shared devices use a personal profile and clear local data after use. “Try without an account” uses fictitious data and simulated email and separately stores demonstration data in the browser; it does not send real changes. Contractual Annex B identifies measures actually implemented and verified, with their date and scope. No on-demand backup or restore services and no contractual recovery times are guaranteed. Applicable security obligations and those under the DPA remain unaffected.

## 8. The business's client notice, Articles 13 and 14
Before real use the business supplies a notice for its relationship, identifying itself, its address and privacy contacts. It specifies purposes, bases by individual and interests as in §3, necessary data and consequences of non-provision, actual recipients and transfer safeguards as in §4, and rights and complaints as in §6. Alternative arrangements for handling changes are agreed with the business. The notice accompanies the approval-email link.
For indirectly collected data, categories include identifiers, contact details, roles and necessary information on the work and third parties mentioned in attachments; sources include the contract, business contacts and project documents, identifying any publicly accessible sources. Decision data comes from the person using the link. The business informs within one month of collection and no later than the first communication with the individual or, if earlier, first disclosure to another recipient, subject to a documented Article 14(5) exception; information is provided before further purposes are pursued.
Retention: 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. Necessity, reviews and choices under §5 apply. No solely automated decisions are envisaged. The Customer makes contact details available for exercising rights and obtaining copies of safeguards.

## 9. Updates
Updates include a version and date; material changes are communicated to individuals.

The Italian version prevails.
