Security at Quadrilingo
Last updated: 17 November 2026
Quadrilingo is built and operated by Thibaut Keller, a small independent software vendor based in Switzerland. This page explains how the App is built, how we protect your data, and how to report a security issue.
Certifications
We do not hold SOC 2, ISO 27001 or any other security certification, and the App has not undergone an independent penetration test. Instead, we rely on a deliberately small architecture: the App runs entirely on Atlassian's Forge platform, requests only the permissions it needs, and keeps your content in your own Confluence site. Atlassian's security and compliance information for the Forge platform is available in the Atlassian Trust Center.
Architecture
- Forge only. The App is an Atlassian Forge app. Its code runs on Atlassian's serverless platform; its storage, queues and logs are hosted by Atlassian. We do not operate any server, database or remote backend of our own.
- Native user interface. All screens use Atlassian UI Kit, rendered by Confluence itself.
- Translations are Confluence pages. Translated pages are ordinary child pages of the source page. Confluence enforces its own permissions on them; the App does not reimplement access control.
- Tenant isolation. Each installation has its own Forge storage, isolated by the Forge platform. The App never mixes data from different sites. Glossaries stored in our DeepL account are kept separately for each site and never shared between sites.
- Translation engine. Text to be translated is sent to DeepL SE's paid API (
api.deepl.com) under our own contract and data processing agreement. This is the App's only connection outside Atlassian.
Permissions (scopes)
The App requests only these Confluence permissions:
| Scope | Why |
|---|---|
read:page:confluence | Read the page to be translated and its page properties |
write:page:confluence | Create and update translated pages, their page properties and their edit restrictions (based on the source page's edit restrictions, never widening edit access); create a sample page, as the signed-in user, when they click “Translate a sample page” |
read:confluence-content.summary | Receive “page updated” events to detect outdated translations |
read:space:confluence | Check, as the signed-in user, whether they administer a space or may create pages in it, and list the spaces they can see in the App's set-up and admin pages (read-only; nothing is stored) |
storage:app | Store settings, glossary, links index, translation memory and quota counters in Forge storage |
External connection to api.deepl.com | Machine translation |
The App does not request permission to delete pages, read comments or attachments, search your site, or read user profiles.
Authentication and access control
- Authentication between the App and Confluence is handled entirely by the Forge platform. The App never asks for or stores Atlassian passwords or API tokens.
- Before a translation is queued, the App checks as the signed-in user (Forge
asUser()) that the user can read the page, create pages in the space and, if a translation already exists, edit it. A user can therefore only translate pages they can read, into spaces where they may create pages. - The translation job then runs as the App (Forge
asApp()): translated pages are created and updated by the App's own account, which is shown as their author. Jobs carry no user identifier; they carry the ID of the existing translated page that was checked for the user, and a request to overwrite manual edits applies only to that page. Translated pages are child pages of their source page and inherit its view restrictions. Just before each update, the App reads the translated page again: if it was moved elsewhere, archived, put in the trash or edited by someone, the App does not write to it. When editing of the source page is restricted, its list of editors, together with the App's own account, is applied to the translated page only if this does not allow anyone to edit it who cannot edit it today (if that list is empty, only the App can edit the translation); otherwise, or if the current restrictions cannot be read in full, the App leaves them unchanged and shows a warning. The App never removes edit restrictions from a page, and never changes the restrictions of a translated page that has its own view restrictions, and it never overwrites a translated page that someone edited unless a user who may edit that page asks for it. - Automatic updates also run as the App. They only update translations that already exist; they never create new pages, and never update a translated page that someone edited by hand. When a page edit is reported by Confluence, the App ignores pages that are not part of a translation, and does not read who made the edit from the notification; it recognises its own edits by comparing the page's last author with its own account.
- The language menu under a page title runs as the person viewing the page: it shows the status of, and a link to, only the pages that person can see. Other pages appear as “Not available”, with no status and no link. The menu does not read page text. Note: the short label under the title of every page of a translation family lists the language codes of all its translations and their status words (for example “FR · DE · IT”, “DE (up to date)”), with no titles, names or links, and anyone who can view that page can see it, including for translations they cannot open.
- Space settings and glossaries can only be changed by a space administrator, and a glossary can only be viewed by a space administrator; this is checked on the server, as that user, at every request, not only by hiding the screen. The App's admin dashboard (in Confluence administration) lists only the spaces and pages that the signed-in user can already see, checked as that user; it also shows site-level figures (subscription state, monthly translation volume, quota code in force, site ID) and per-space numbers of translations by status, which may include translations of pages that user cannot open (numbers only, no titles or links). The App cannot itself verify that the viewer is a site administrator (Atlassian provides no API for this to apps with the App's permissions); the dashboard's only action, applying a quota code, accepts only codes we signed for your site.
Data protection
- Minimisation. Only the text to be translated is sent for translation. Code blocks, macro parameters, user mentions, links, e-mail addresses, URLs and phone numbers stay in your page and are replaced by neutral placeholders.
- No content in logs. Logs contain only technical identifiers (site, space and page IDs), error codes and counts. They never contain page text, titles, glossary terms, names, e-mail addresses or secrets. Forge logs are kept for 30 days, and your administrators can switch off our access to them.
- No analytics or tracking. The App sends no usage analytics to us or to any third party.
- No AI training. We do not use your content to train any model. DeepL does not use texts sent through its paid API for training, according to its terms.
- Data flows and retention are described in detail in our data flow description.
Encryption
- In transit: all connections use HTTPS.
- At rest: App data is stored in Confluence and in Forge storage, which are protected by Atlassian's platform controls. We do not store your data anywhere else. Glossaries kept in our DeepL account are protected by DeepL's controls. They are stored under random names and deleted at the latest 31 days after creation.
- Secrets: the translation engine API key is stored as an encrypted Forge environment variable. It is never stored in source code, in a repository or in logs.
- Quota codes: codes for additional translation volume are signed offline by us and verified inside the App with a public key, without any call to our systems. A code contains only your site ID, a monthly volume, its issue and expiry dates (at most 400 days apart) and technical format and key identifiers, and does not work on any other site. The signing key is kept offline; it is never stored in the App, in Forge or in our code repository.
Secure development
- Every change is reviewed and tested before release (automated tests, Forge linting, code review).
- Production dependencies are scanned with
npm auditon every build; the build fails on high or critical findings. Vulnerable transitive dependencies of Atlassian SDKs are patched with npm overrides and tracked until upstream releases a fix. Atlassian also scans Marketplace apps for vulnerable dependencies. - The App runs on a supported Node.js runtime.
- Input from users (settings, glossary) is validated on the server side. Glossary exports (CSV) are protected against spreadsheet formula injection. Content returned by the translation engine is validated before it is written to your pages: unexpected markup is rejected.
- Development and testing use synthetic test pages only. No customer data is used for testing.
Vulnerability disclosure
If you believe you have found a security vulnerability in Quadrilingo, please e-mail security@quadrilingo.com with:
- a description of the issue and its impact;
- the steps to reproduce it;
- your contact details (optional).
What you can expect from us:
- acknowledgement within 3 business days;
- a first assessment and severity rating (CVSS) as soon as possible;
- fixes within the timeframes of the Atlassian Marketplace Security Bug Fix Policy: critical 10 days, high 4 weeks, medium 12 weeks, low 25 weeks;
- credit in our release notes if you wish.
Please give us reasonable time to fix the issue before disclosing it publicly, do not access or modify data that does not belong to you, and do not run tests that could degrade the service for other customers. We will not take legal action against researchers who act in good faith and follow these guidelines. This commitment binds only us; it does not cover systems or data of Atlassian, DeepL or our customers.
Atlassian may also report vulnerabilities to us through its Marketplace security program; we handle those reports with the same timeframes.
Incident response
If we become aware of a security incident affecting the App or customer data, we will:
- Contain the issue (for example disable the affected feature, rotate keys, deploy a fix).
- Assess which customers and which data are affected.
- Notify Atlassian through its partner support channel within 24 hours of discovering the incident, as required by Atlassian.
- Notify affected customers without undue delay, and where possible within 48 hours of becoming aware of an incident affecting their personal data, with the information they need to meet their own legal obligations.
- Notify the authorities where we are legally required to do so as controller of our own data (for example the Swiss FDPIC). For customer content, we notify our customers, who decide on any notification to authorities.
- Review the incident and document the measures taken to prevent it from happening again.
Business continuity
Because translated pages are ordinary Confluence pages, they remain readable and editable even if the App or the translation engine is unavailable, and after the App is uninstalled. The App's availability depends on the Atlassian Forge platform and on the translation engine.
Contact
Security: security@quadrilingo.com — Support: support@quadrilingo.com
Thibaut Keller, Route des Riaux 1, 1782 Lossy, Switzerland