Security Policy
Last updated: 21 October 2026. Publisher: Webelisys.
Introduction
This page describes how Quick Table Export protects your data: where it runs, what it can access, what it keeps, and how security problems are handled. What the app does with your data is described in more detail in the privacy policy.
The app runs entirely on Atlassian's platform. It has no server of its own, calls no address outside Atlassian, never stores your page content or any personal data, and sends no data to Webelisys or to any third party.
Where the app runs and where your data goes
Quick Table Export 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 page and building the spreadsheet are done by the app's functions, which run on Atlassian's Forge platform. Webelisys runs no server for the app.
When you export a table, the app reads the page, and the earlier versions of it you choose, and returns the table to your browser during that single request. The Excel file is built in memory by the app's function, the CSV file is built in your browser. Your page content is never written to any database, any log or any file. The app declares no external domain and no remote back end, so it has no way to send data outside Atlassian.
On sites where Rovo, Atlassian's AI assistant, is turned on, the app's agent reads a table of the page you have open, with your permissions, and returns it to Rovo as text. What Rovo does with that text is handled by Atlassian under its own terms.
Encryption
All traffic between your browser, Confluence and the app's functions 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 request counter described below. Your pages stay in Confluence and are protected by Atlassian like the rest of your Confluence data. See the Atlassian Trust Center.
Access and permissions
The app requests only the two permissions it needs: reading Confluence pages, and access to its own app storage, which it uses only for the request counter.
Every page is read in your name, with your own Confluence permissions, both from the panel and from the Rovo agent. A page you are not allowed to see cannot be read by the app. 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.
What the app keeps, and for how long
To limit automated use, the app sets a limit of 60 requests per minute on each Confluence site. To count them, it keeps a single record per site in the storage that Atlassian provides to apps. This record holds only the current minute and a number. It contains no name, no account, no page and no content.
The record stays within Atlassian, in the location of your Confluence site, and is overwritten by the first request of each new minute. The limit is not strict: if this storage is unavailable or answers in more than 2 seconds, the request goes through anyway, and several requests made at the same moment can let a few more than 60 through in a minute. Atlassian deletes the record 28 days after the app is uninstalled, as described in the Forge storage documentation.
Logs and tracking
The app's code writes no logs. It sets no cookies, uses no analytics and contains no tracking. Webelisys receives no information about which pages you export or how often you use the app. Atlassian, as the platform operator, keeps its own operational records under its own policies.
How the app handles what it reads
The content of your pages is treated as data, never as code. The screen is built with Atlassian's UI Kit components, which encode what they display. In CSV files, any value that a spreadsheet could run as a formula is neutralised. Each request has fixed limits: a page with more than 15 MB of content is not exported, and a table stops at 10,000 rows and 200 columns.
The app holds no password, API token or other secret, and never asks for your Atlassian password or API token.
Vulnerability management
Before each release, we run the app's automated checks: its tests, a validation of its manifest, and an audit of its dependencies against known vulnerabilities. The exact versions of its dependencies are fixed in its lock file, and we update them when a security fix is published.
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, as the Marketplace rules require, and we inform the affected customers.
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.