Data Processing Agreement — Quadrilingo
Last updated: 17 November 2026
This Data Processing Agreement (“DPA”) forms part of the agreement under which the customer (“Customer”, “Controller”) uses Quadrilingo (the “App”) provided by Thibaut Keller, Route des Riaux 1, 1782 Lossy, Switzerland (“Processor”, “we”), namely our End User License Agreement or the Atlassian Marketplace standard agreement with our Provider-Specific Terms (the “Agreement”). It applies automatically when the Customer accepts the Agreement. A countersigned copy is available on request at support@quadrilingo.com.
1. Definitions
- “Applicable Data Protection Law” means all data protection laws that apply to the processing of Customer Personal Data under the Agreement, including the EU General Data Protection Regulation 2016/679 (“GDPR”), the Swiss Federal Act on Data Protection of 25 September 2020 (“FADP”), the UK General Data Protection Regulation and Data Protection Act 2018 (“UK GDPR”), and, where applicable, the California Consumer Privacy Act (“CCPA”), each as amended.
- “Customer Personal Data” means personal data processed by the Processor on behalf of the Customer through the App, as described in Annex 1.
- “Sub-processor” means any processor engaged by us to process Customer Personal Data.
- “Personal Data Breach” means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, Customer Personal Data.
- Other terms (for example “controller”, “processor”, “data subject”, “processing”) have the meaning given in Applicable Data Protection Law.
2. Roles and scope
2.1 The Customer is the controller and we are the processor of Customer Personal Data. Where the Customer acts as processor for a third party, we act as its sub-processor, and the Customer is responsible for passing on any relevant instructions.
2.2 This DPA does not apply to personal data that we process as controller (for example licensing data received from Atlassian or support communications), which is governed by our Privacy Policy.
2.3 Annex 1 describes the processing.
3. Instructions
3.1 We process Customer Personal Data only on the Customer's documented instructions, including with regard to transfers to third countries, unless required to do so by law; in that case we inform the Customer of that legal requirement before processing, unless the law prohibits this. The Agreement, this DPA, and the Customer's configuration and use of the App (for example choosing spaces, languages, glossaries and pages to translate) are the Customer's complete instructions.
3.2 We will inform the Customer if, in our opinion, an instruction infringes Applicable Data Protection Law, unless the law prohibits this.
3.3 We will not sell Customer Personal Data, use it for our own purposes, or use it to train AI models.
4. Customer obligations
The Customer is responsible for the lawfulness of the processing, including having a legal basis for submitting content to the App and informing its users. The Customer will not use the App to process special categories of personal data unless it has assessed that this is appropriate.
5. Confidentiality
We ensure that every person authorised to process Customer Personal Data is bound by an obligation of confidentiality and only accesses Customer Personal Data where needed to provide, support or secure the App.
6. Security
6.1 We implement the technical and organisational measures described in Annex 2. We may update them as long as the overall level of protection is not reduced.
6.2 The Customer acknowledges that the App runs on the Atlassian Forge platform and that the security of Confluence Cloud and of the Forge platform is the responsibility of Atlassian.
7. Sub-processors
7.1 The Customer gives a general authorisation for us to engage Sub-processors. The current list is published at quadrilingo.com/subprocessors (Annex 3).
7.2 We will inform the Customer of any intended addition or replacement of a Sub-processor at least 30 days in advance, by updating that page and by e-mail to the Customer's technical contact as provided by Atlassian.
7.3 The Customer may object on reasonable data protection grounds within that period. We will discuss the objection in good faith. If we cannot resolve it, the Customer may terminate the affected subscription by uninstalling the App; we will support a pro-rata refund of prepaid fees for the remaining term to the extent the Atlassian Marketplace allows it.
7.4 We impose on each Sub-processor data protection obligations that offer at least the same level of protection as this DPA, and we remain responsible for their performance. For Atlassian, this is the Atlassian Forge Data Processing Addendum.
8. International transfers
8.1 We are established in Switzerland, which the European Commission recognises as providing an adequate level of protection.
8.2 We will only transfer Customer Personal Data to, or allow access from, a country that does not provide an adequate level of protection under Applicable Data Protection Law if appropriate safeguards are in place, such as the EU Standard Contractual Clauses (with the amendments required for Swiss law) or certification under the EU-U.S. or Swiss-U.S. Data Privacy Framework, and, for the UK GDPR, the UK International Data Transfer Addendum. Countries recognised as adequate by the European Commission, by the Swiss Federal Council (Annex 1 of the Swiss Data Protection Ordinance) or under the UK GDPR need no additional safeguard.
8.3 The processing locations of each Sub-processor are listed in Annex 3.
9. Assistance
9.1 Data subject requests. We will promptly forward to the Customer any request we receive from a data subject concerning Customer Personal Data, and will not respond directly unless instructed. Most Customer Personal Data is stored in the Customer's Confluence site, where the Customer can access, correct or delete it directly. We will provide reasonable assistance for data held in the App's storage.
9.2 Security, breaches, impact assessments and consultations. Taking into account the nature of the processing and the information available to us, we will assist the Customer in ensuring compliance with its obligations regarding security of processing, notification of personal data breaches to authorities and data subjects, data protection impact assessments and prior consultations with authorities (Articles 32 to 36 GDPR and Articles 8, 22, 23 and 24 FADP), in particular by providing reasonable information, for example our security page, data flow description and answers to security questionnaires.
10. Personal Data Breaches
10.1 We will notify the Customer without undue delay, and where possible within 48 hours, after becoming aware of a Personal Data Breach affecting Customer Personal Data.
10.2 The notification will include, as far as available: the nature of the breach, the categories and approximate number of data subjects and records concerned, the likely consequences, and the measures taken or proposed. Information may be provided in stages.
10.3 We will take reasonable steps to contain the breach and mitigate its effects, and will cooperate with the Customer.
10.4 Notification is not an acknowledgement of fault or liability.
11. Deletion and return
11.1 Translated pages and page properties are stored in the Customer's Confluence site and remain under the Customer's control; the Customer can keep or delete them at any time, including after the end of the Agreement.
11.2 Translated pages and page properties are the return of Customer Personal Data: the Customer keeps them, exports them or deletes them in Confluence, at its choice. When the Customer uninstalls the App, the App's data in Forge storage is deleted by Atlassian according to Atlassian's retention schedule. Glossaries stored with our translation provider are deleted at the latest 31 days after their creation. We do not keep copies of Customer Personal Data outside these systems, except support communications sent to us by the Customer, which are handled as described in our Privacy Policy.
11.3 On request, we will confirm in writing that deletion has been initiated for the data under our control.
12. Audits
12.1 We will make available to the Customer the information reasonably necessary to demonstrate compliance with this DPA, including our security page, data flow description and answers to reasonable security questionnaires (at most once per year, unless a Personal Data Breach has occurred).
12.2 If that information is not sufficient, the Customer may carry out an audit, at most once per year, with at least 30 days' notice, during business hours, at its own cost, by itself or by an independent auditor bound by confidentiality. The audit must not give access to other customers' data. Audits of Atlassian and DeepL are performed through the reports and certifications they make available.
13. Liability
Each party's liability under this DPA is subject to the limitations of liability in the Agreement, to the extent permitted by Applicable Data Protection Law. This does not limit either party's liability to data subjects under Applicable Data Protection Law.
14. Term and precedence
14.1 This DPA applies as long as we process Customer Personal Data.
14.2 In case of conflict between this DPA and the Agreement on data protection matters, this DPA prevails.
14.3 This DPA is governed by the law and jurisdiction of the Agreement, unless Applicable Data Protection Law requires otherwise.
15. CCPA
Where the CCPA applies and the Customer is a “business”, we act as the Customer's “service provider”. We will not sell or share Customer Personal Data, retain, use or disclose it for any purpose other than providing the App under the Agreement, or combine it with personal data we receive from other sources, except as permitted by the CCPA. We will comply with the CCPA applicable to service providers and inform the Customer if we can no longer do so.
Annex 1 — Description of the processing
| Item | Description |
|---|---|
| Subject matter | Machine translation of Confluence Cloud pages and management of multilingual page versions |
| Nature of processing | Reading pages, segmenting text, sending text for machine translation, writing translated pages, storing links, settings, glossary, translation memory and usage counters, detecting outdated translations |
| Purpose | Providing the App to the Customer |
| Duration | Term of the Agreement, plus the retention periods in Annex 2 and our data flow description |
| Categories of data subjects | Customer's employees, contractors and other users of the Confluence site; any person mentioned in the content of pages translated by the Customer |
| Categories of personal data | Any personal data contained in page text, page titles and glossary entries (for example names, job titles, business contact details); technical identifiers (site, space and page IDs); the language and time zone of the signed-in user, read only to suggest default space settings and not stored; account and group IDs listed in a source page's edit restrictions, applied to the translated page's restrictions in the Customer's Confluence site only where this does not widen edit access, and not stored by the App; the account ID of the last author of a source or translated page, read only to detect manual edits and not stored. The App does not store user account IDs. |
| Special categories | Not intended. Only if contained in content the Customer chooses to translate (see section 4). |
| Frequency | Continuous, on demand and when automatic updates are enabled |
| Translation engine | DeepL SE, paid API |
Annex 2 — Technical and organisational measures
Architecture and isolation
- The App runs exclusively on Atlassian Forge; no servers or databases operated by the Processor.
- Per-installation storage isolation provided by Forge; no cross-tenant data access.
- Translated content is stored as Confluence pages, protected by Confluence permissions.
Access control
- Minimal Confluence scopes (
read:page:confluence,write:page:confluence,read:confluence-content.summary,read:space:confluence,storage:app). - Before a translation is queued, the App checks, as the requesting user (
asUser()), that the user can read the source page, create pages in the space and edit an existing translation. The translation itself then runs under the App's own identity (asApp()). Automatic updates only refresh existing translations, never translated pages edited by a person. The language menu shown on pages runs as the viewing user and shows the status of, and a link to, only pages that user can see. Translated pages inherit the view restrictions of their source page; the source page's edit restrictions (plus the App's own account) are applied to them only where this does not widen edit access, and never from a restriction list the App could not read in full. The App does not change the restrictions of a translated page that has its own view restrictions. Before each update the App re-reads the translated page and does not write to it if it was trashed, archived, moved or edited by someone (unless a user permitted to edit it asked to overwrite that page). - Space settings and glossaries: viewing a glossary and changing settings or glossaries require a space-administrator check, made as the user on the server at every request. The App's global admin page shows only spaces and pages the signed-in user can already see.
- No collection of Atlassian passwords or API tokens.
- Customer site administrators can disable the Processor's access to App logs.
Data minimisation
- Only text to be translated, page titles, short context and relevant glossary entries are sent to the translation engine; the glossary of a space is stored in full in our DeepL account, separately for each site (with a second copy of its entries into German, using the Swiss terms, for spaces translated into Swiss Standard German), so that DeepL can apply it; code, macro parameters, mentions, links, e-mail addresses, URLs and phone numbers are kept local.
- No page content, names or account IDs in logs; no analytics or tracking.
- Translation jobs contain no user identifiers (page IDs, language and version only).
Encryption and secrets
- All connections over HTTPS.
- Translation engine API key stored as an encrypted Forge environment variable; never in source code or logs.
- Additional-volume (quota) codes are signed offline by the Processor and verified inside the App with a public key; they contain only the site ID, a monthly volume, issue and expiry dates (at most 400 days apart) and technical format and key identifiers, and are valid only for that site.
Secure development and vulnerability management
- Automated tests, linting and review before each release.
- Dependency scanning on every build; high and critical findings block the build.
- Vulnerabilities fixed within the Atlassian Marketplace Security Bug Fix Policy timeframes.
- Test data is synthetic; no Customer Personal Data used in development.
Retention
- Queue messages: at most 24 hours. Technical job records (IDs, dates, counters; no content): 1 to 7 days. Logs: 30 days. Translation memory: deleted 90 days after last use (plus up to 48 hours for platform deletion). Glossaries at DeepL: re-created every 25 days while in use, deleted on replacement, and at the latest 31 days after creation, including after uninstallation.
Incident management
- Documented incident response: containment, assessment, notification of Atlassian within 24 hours, notification of customers as set out in section 10, post-incident review.