Privacy Policy — Quadrilingo
Last updated: 17 November 2026
1. Who we are
Quadrilingo (the “App”) is provided by Thibaut Keller, Route des Riaux 1, 1782 Lossy, Switzerland (“we”, “us”, “our”).
- Privacy questions and requests: privacy@quadrilingo.com
- Security issues: security@quadrilingo.com
We, and not Atlassian, are responsible for the processing of personal data described in this policy. Atlassian's own privacy policy governs Atlassian's products, including Confluence Cloud and the Atlassian Marketplace.
2. Scope
This policy explains:
- how the App handles data from your Confluence Cloud site when we process it on behalf of our customers (sections 3 to 6); and
- how we handle personal data for our own purposes, for example licensing, support and security communications (section 7).
It applies to Switzerland (Federal Act on Data Protection, “FADP”), the European Union and the European Economic Area (General Data Protection Regulation, “GDPR”), and any other country where the App is used, to the extent the local law applies.
3. Our role
- Content processed by the App (page text, page titles, glossary entries, settings): your organisation (the customer that installed the App) is the controller. We act as a processor and only process this data to provide the App, following your organisation's instructions and our Data Processing Agreement. If you are a user of a Confluence site, your organisation's privacy notice applies to you; please contact your organisation first.
- Our own business data (section 7): we are the controller.
4. What the App processes on behalf of customers
4.1 Data the App reads, creates or stores
| Data | Why | Where it is kept |
|---|---|---|
| Text and title of the pages you ask the App to translate, or that are set to update automatically; text and title of the page on which a user opens the “Translate this page” dialog (read in memory only, to estimate the volume and suggest the page's language, and not stored); text and title of a page that already has translations, each time someone edits it (read in memory only, to detect outdated translations; only a fingerprint is kept) | To produce the translated pages and keep them up to date | Your Confluence site (source and translated pages). Text sent to the translation engine is described in 4.3. |
| Links between a source page and its translations (page IDs, language and language variant, version numbers, translation status) | To show the language switcher and detect outdated translations | Your Confluence site (page content properties) and the App's storage on Atlassian's Forge platform |
| Space settings (source language, target languages, automatic updates on or off, formal or neutral tone, German for Germany or for Switzerland, French for France or for Switzerland) | To apply your choices | The App's storage on Forge |
| Language and time zone of the signed-in user, as provided by Confluence | To suggest default space settings (for example Swiss German for a user in Switzerland) | Not stored: only read while one of the App's screens loads or saves |
| Glossary entries entered by your space administrators (only space administrators can view or change them) | To translate your terms consistently | The App's storage on Forge and the translation engine (see 4.3) |
| Previously translated text segments (translation memory) | To avoid re-translating unchanged paragraphs | The App's storage on Forge |
| Edit restrictions of a source page (account and group IDs allowed to edit it) | To apply the same edit restrictions to the translated page, only where this does not allow more people to edit it | Written to the translated page's restrictions in your Confluence site, only where this does not widen edit access (otherwise left unchanged). Not stored by the App and never logged. |
| Status, creation date and last author (account ID) of the source and translated pages | To avoid writing to pages that are in the trash, archived, moved or edited by someone, and to recognise a translated page edited by a person (it is then never updated automatically) | Read in memory only; not stored and never logged |
| Number of characters translated per site and per month | Quota and licence management | The App's storage on Forge |
| Quota code, if we issued one for your site (site ID, monthly volume, issue and expiry dates; no names or e-mail addresses) | To apply the additional translation volume agreed with your organisation | The App's storage on Forge |
| Technical identifiers in logs (site, space and page IDs, error codes, counts) | Operation, troubleshooting and security | Atlassian's Forge logs (see 6). Logs never contain page content, names or e-mail addresses. |
Pages can contain personal data written by your authors (for example names, roles or contact details). The App processes such data only as part of the page text. The App is not designed to process special categories of personal data (Art. 9 GDPR) or sensitive personal data (Art. 5(c) FADP), for example health data; please do not use it to translate such content unless your organisation has assessed that this is appropriate.
4.2 What the App does not do
- It does not read comments, attachments, user profiles or e-mail addresses of your users. (It only receives from Confluence the language and time zone of the signed-in user, see 4.1, and does not store them.)
- It does not put user account IDs in its translation jobs or its storage. The App checks the permissions of the user who starts a translation, then performs the translation under its own app identity.
- Before text leaves your page for translation, the App removes code blocks, macro parameters, user mentions, links, e-mail addresses, URLs and phone numbers, and replaces them with neutral placeholders. They are put back locally afterwards.
- It does not use analytics, tracking or advertising tools.
- It does not sell personal data and does not use your content to train any AI model. We do not run our own servers.
4.3 Translation engine
Translations are produced by DeepL SE (Cologne, Germany) through its paid API, under our own DeepL contract and data processing agreement. You do not need a DeepL account. The App sends DeepL only the text segments to be translated, the page title, short context (for example the heading above a paragraph) and, if the space has a glossary, that glossary: the whole glossary of the space is stored in our DeepL account as a DeepL glossary so that DeepL can apply it (with a second copy of its entries into German, using the Swiss terms, if the space translates into Swiss Standard German). According to DeepL, texts sent through its paid API are not stored permanently, are deleted after translation and are not used to train its models; DeepL may keep them for a short time (according to its terms, at most 72 hours) if needed to handle an error. Glossaries are stored in our DeepL account under a random name, re-created every 25 days while they are in use, deleted as soon as they are replaced, and in any case deleted at the latest 31 days after they were created (see 6). DeepL may process data in the European Union, in the United States and in other regions where it uses Amazon Web Services infrastructure, including the Asia-Pacific region (see 9 and our sub-processor list).
5. Where data is hosted
- Your Confluence site: translated pages and their links are ordinary Confluence pages and properties. They stay under your administrators' control and follow your site's Atlassian data residency settings.
- Atlassian Forge: the App runs on Atlassian's Forge platform. Its storage and queues are hosted by Atlassian. Atlassian aims to run the App in the same location as your site, but may sometimes run it elsewhere for reliability, performance or security reasons.
- Translation engine: see 4.3.
6. How long data is kept
| Data | Retention |
|---|---|
| Source and translated pages, page properties | Until your users or administrators delete them. They remain in your Confluence site if the App is uninstalled. |
| Settings, glossary, links index, translation memory, quota counters, quota code (Forge storage) | While the App is installed. Translation memory entries are deleted 90 days after they were last used (Atlassian's platform may take up to 48 more hours). Quota counters are deleted after about 13 months. Technical job records (IDs, dates, counters; no content) are deleted within 1 to 7 days. After uninstallation, Atlassian deletes the App's storage according to its own retention schedule; Atlassian can restore it if you reinstall within 21 days. |
| Processing queue (page IDs, language and version only; no user identifier) | Up to 24 hours (technical maximum 96 hours). |
| Forge logs (no content) | 30 days. Your site administrators can turn off our access to the App's logs. |
| Text sent to DeepL | Deleted by DeepL after translation, except short-term storage (at most 72 hours according to DeepL's terms) if needed to handle an error. |
| Glossaries stored at DeepL | Deleted as soon as they are replaced, and in any case at the latest 31 days after they were created, including after the App is uninstalled. |
7. Personal data we process as controller
| Data | Purpose | Legal basis (GDPR) | Retention |
|---|---|---|---|
| Licence and contact data that Atlassian shares with us when your organisation installs, evaluates or buys the App (organisation name, name and e-mail address of technical and billing contacts, licence tier, dates), and our record of any quota code we issue for your site (organisation, site ID, volume, expiry date) | Manage licences, provide support, inform you about important changes to the App (for example security notices), meet legal obligations | Legitimate interest in managing our customer relationships and running our business (Art. 6(1)(f)); contract (Art. 6(1)(b)) where you are yourself our customer; legal obligation (Art. 6(1)(c)) for accounting | Duration of the licence plus 24 months. Where these data appear in accounting records (for example Atlassian payment reports): 10 years (Art. 958f Swiss Code of Obligations). |
| Support and security messages (name, e-mail address, content of the message, any attachments you send) | Answer your request, investigate and fix problems | Legitimate interest (Art. 6(1)(f)); contract (Art. 6(1)(b)) where you are yourself our customer | 24 months after the request is closed. |
| Vulnerability reports | Fix security issues, notify Atlassian and customers where required | Legitimate interest; legal obligation | 24 months after the issue is closed, longer if required by law |
| Website server logs (IP address, date, page requested) | Security and operation of the website | Legitimate interest | Our website is hosted by GitHub, Inc. (GitHub Pages, USA), which logs visitors' IP addresses for security purposes and keeps them according to its own privacy statement. We do not receive these logs. |
We do not send marketing e-mails without your consent. We do not use cookies or analytics on our website.
Please do not send us page content or other personal data in support requests unless it is needed to solve your problem. If you do, we use it only for that request.
We do not use automated decision-making or profiling that has legal or similarly significant effects.
8. Who receives personal data
We do not sell or rent personal data. We share it only with:
- Atlassian (hosting of the App on Forge; Marketplace licensing and billing);
- our translation engine provider (see 4.3) for the content to be translated;
- Infomaniak Network SA (Switzerland) for our e-mail (support and security messages);
- GitHub, Inc. (GitHub Pages, USA) for our website;
- our accountant or fiduciary, for accounting records;
- authorities, if we are legally required to do so.
The current list of sub-processors for App data is published at quadrilingo.com/subprocessors.
9. International transfers
We are based in Switzerland. The European Commission recognises that Switzerland provides an adequate level of data protection. Personal data may be processed in the following countries:
- Switzerland (us);
- the countries where Atlassian hosts your site and the Forge platform according to your site's data residency settings, and the countries named in Atlassian's sub-processor list, which include the United States. Atlassian relies on the EU-U.S. and Swiss-U.S. Data Privacy Framework and on Standard Contractual Clauses;
- Germany and other EU countries (DeepL SE is established in Germany), the United States and other countries in which DeepL uses Amazon Web Services infrastructure, including in the Asia-Pacific region. According to DeepL, its transfers outside Europe rely on the EU-U.S. Data Privacy Framework and Standard Contractual Clauses;
- Switzerland for our e-mail provider, Infomaniak Network SA;
- the United States for our website host, GitHub, Inc. (website server logs only).
The EU/EEA countries are recognised by Switzerland as providing an adequate level of protection, and the United States are recognised for companies certified under the Swiss-U.S. Data Privacy Framework. When personal data is transferred to another country without an adequate level of protection under Swiss or EU law, the transfer relies on the European Commission's Standard Contractual Clauses (with the amendments required for Swiss law), concluded by us or by our sub-processor with its own sub-processors.
10. Security
We protect data with the measures described on our security page: the App runs entirely on Atlassian's Forge platform, uses only the Confluence permissions it needs, encrypts data in transit, keeps secrets in encrypted Forge variables, and never writes page content to logs. No system is completely secure. If a security incident affects your data, we will inform your organisation without undue delay.
11. Your rights
Depending on the applicable law, you may have the right to access your personal data, have it corrected or deleted, restrict or object to its processing, receive it in a portable format, and withdraw consent at any time.
- For data processed by the App on behalf of your organisation (sections 3 to 6), please contact your organisation. We will help it respond.
- For data we process as controller (section 7), write to privacy@quadrilingo.com. We may ask you to prove your identity.
You can also complain to a data protection authority: in Switzerland, the Federal Data Protection and Information Commissioner (FDPIC, www.edoeb.admin.ch); in the EU/EEA, the authority of your country of residence or work.
12. Children
The App is a business tool. It is not intended for children.
13. Changes to this policy
We may update this policy. The date at the top shows the latest version. We will announce material changes on this page and, where the change affects App data, give our customers advance notice as described in our Data Processing Agreement.
14. Contact
Thibaut Keller, Route des Riaux 1, 1782 Lossy, Switzerland — support@quadrilingo.com