Security Policy
Last updated: 9 November 2026. Publisher: Webelisys.
Introduction
This page describes how Quick Page Compare (Diff) for Confluence protects your data: where it runs, what it can access, what it keeps, and how security problems are handled. The privacy policy describes in more detail what the app does with your data.
The app runs entirely on Atlassian's platform (Runs on Atlassian). It has no server of its own, calls no address outside Atlassian, never saves the content of your pages, and sends no data to Webelisys or to any third party.
Where the app runs and where your data goes
The app is built on Forge, Atlassian's platform for cloud apps. Its screen is hosted by Atlassian and runs in your browser, inside Confluence. Reading the pages and working out the differences is done by one function that runs on Atlassian's Forge platform. Webelisys runs no server for the app.
The app declares no external domain, no remote back end and no web trigger, so it has no way to send data outside Atlassian, and nothing outside Atlassian can call it. The content of the pages is held in memory for the time of one request. It is never written to any database, any log or any file on a server.
Encryption
All traffic between your browser, Confluence and the app's function goes through Atlassian. Under Forge's shared responsibility model, Atlassian encrypts it with TLS and HSTS, and encrypts at rest the data kept in Forge app storage, which here is only the counter described below. Your pages stay in Confluence and are protected by Atlassian like the rest of your Confluence data. The app stores nothing outside Atlassian. See the Atlassian Trust Center.
Access and permissions
The app requests 4 permissions. It asks for no permission to write or delete anything. What each one is used for:
read:page:confluence: reads the two pages to compare, their versions and their titles.search:confluence: searches pages by title when you type a title to choose a page.read:space:confluence: reads the name of the space of a page, to show it next to the title.storage:app: keeps the counter that limits the comparisons to 60 per minute and per site.
Every page is read in your name (asUser), with your own Confluence permissions. The app never reads a page with the rights of the app itself. If Confluence refuses access to a page, the app does not show it. The app cannot change any page, and has no access to your account details, your email address or your other Atlassian products.
Personal data
The app stores no personal data: no name, no account identifier, no email address. There is therefore nothing for it to report to Atlassian's personal data reporting API, and it does not request that permission.
What the app keeps, and for how long
To limit automated use, the app accepts up to 60 comparisons per minute on each Confluence site. To count them, it keeps small entries in the storage that Atlassian provides to apps: at most 60 per minute, each removed by the storage after two minutes. They hold only a minute and a number. They contain no name, no account, no page and no content.
Atlassian's documentation says that Forge hosted storage retains data for 28 days after uninstallation, as described in the Forge storage documentation. These entries are the only thing there. If the app is installed again, it is a new installation, as described in the Forge data lifecycle documentation.
Because the counter is shared by the whole site, one person can use up the comparisons of a minute for the other people of the same site. They can try again the next minute.
Logs and tracking
For each request, the app writes one short technical line in the logs of Atlassian's Forge platform: a code and a few numbers, such as a status or a duration. The line holds no page title, no account, no link and no content. How long Forge keeps these logs is decided by Atlassian and is not stated here.
The app sets no cookies, uses no analytics and contains no tracking. Webelisys receives no information about which pages you compare or how often you use the app.
How the app handles what it reads
The text of your pages, their titles and the names of their elements are treated as data, never as code: the screen shows them as text. Page and version identifiers, the parameters of a shared link and the addresses you paste are checked against a strict list of allowed forms before any call is made. A pasted address must be on the same Confluence site, and only the page number is taken from it. The app does not call it.
The app holds no password, API token or other secret, and never asks for your Atlassian password or API token.
What the security review checked
Review of the final code on 9 November 2026:
- No secret (password, key, token) in the code or in its history: checked with Gitleaks on the folder and on 220 successive versions.
- Pages are read only with the rights of the person using the app. No read is made with the rights of the app.
- The app changes nothing in Confluence. It asks only for read permissions (pages, spaces, search) and for its own storage.
- No call to an outside server: no external address declared in the manifest, no web trigger.
- Logs contain no page title, account, link or content.
- Static analysis of the application code (Semgrep, JavaScript, Node.js, OWASP and security audit rules): 0 findings.
- The page search field was tried on a live Confluence test site with hostile text (quotes, search operators, script tags, control characters, very long text): no injection and no script ran (November 9, 2026).
- Dependencies (npm audit and Trivy): 0 known advisories at the time of the last check (November 10, 2026). We re-run both tools before each release and update the dependencies when Atlassian or the package authors publish fixes.
Not covered by this review: a penetration test and an audit of Atlassian's infrastructure.
Vulnerability management
Before each release, we run the app's automated tests and an audit of its dependencies against known vulnerabilities. The exact versions of its dependencies are fixed in its lock file.
We fix confirmed vulnerabilities within the deadlines of Atlassian's Security Bug Fix Policy for cloud apps, counted from the report or triage:
- Critical: within 10 days.
- High: within 4 weeks.
- Medium: within 12 weeks.
- Low: within 25 weeks.
Security problems in the Forge platform itself are fixed by Atlassian.
Security incidents
If we learn of a security incident that affects the app, we report it to Atlassian through ECOHELP within 24 hours of becoming aware of it, as the Marketplace rules require, and we inform the affected customers. You can reach us about an incident at contact@webelisys.fr.
Reporting a vulnerability
To report a security problem, write to contact@webelisys.fr with "Security" in the subject. Please describe the problem and how to reproduce it, and do not include personal data or the content of your pages. We acknowledge every report within 2 working days.
Certifications
Webelisys holds no security certification for this app: no SOC 2, no ISO 27001, and no completed CAIQ Lite questionnaire. For Atlassian's own certifications, see the Atlassian Trust Center.