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

Permissions (scopes)

The App requests only these Confluence permissions:

ScopeWhy
read:page:confluenceRead the page to be translated and its page properties
write:page:confluenceCreate 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.summaryReceive “page updated” events to detect outdated translations
read:space:confluenceCheck, 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:appStore settings, glossary, links index, translation memory and quota counters in Forge storage
External connection to api.deepl.comMachine 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

Data protection

Encryption

Secure development

Vulnerability disclosure

If you believe you have found a security vulnerability in Quadrilingo, please e-mail security@quadrilingo.com with:

What you can expect from us:

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:

  1. Contain the issue (for example disable the affected feature, rotate keys, deploy a fix).
  2. Assess which customers and which data are affected.
  3. Notify Atlassian through its partner support channel within 24 hours of discovering the incident, as required by Atlassian.
  4. 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.
  5. 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.
  6. 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