Quick Table Import Quick Table Import

Security Policy

Last updated: 21 October 2026. Publisher: Webelisys.

Introduction

This page describes how Quick Table Import 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, stores no data, and sends no data to Webelisys or to any third party.

Where the app runs and where your data goes

Quick Table Import is built on Forge, Atlassian's platform for cloud apps. Its panel is hosted by Atlassian and runs in your browser, inside Confluence. The Excel or CSV file you choose in the panel is read in your browser, in memory, and is never uploaded. When you insert the table, the panel sends it to Confluence, and to Confluence only. Webelisys runs no server for the app.

On sites where Rovo, Atlassian's AI assistant, is turned on, the app's agent runs as functions on Atlassian's Forge platform. It downloads the attachment you name from Confluence, or receives the table data from Rovo as text, reads it in memory, and adds the table at the bottom of the page. What you type in Rovo is handled by Atlassian under its own terms.

The app declares no external domain and no remote back end, so it has no way to send data outside Atlassian. The tables it adds are stored by Confluence in your pages, and follow the data residency of your Confluence site.

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. The app stores nothing of its own, so there is no app data to encrypt at rest. Your pages and attachments 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 four permissions it needs: reading and writing Confluence pages, and listing and downloading the files attached to a page.

Every request is made in your name, with your own Confluence permissions, both from the panel and from the Rovo agent. A page you are not allowed to edit cannot be changed by the app: Confluence refuses. The agent looks for attachments only on the page where you ask for the import, and only the ones your own account can see. The app 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

Nothing. The app uses no app storage at Atlassian and no storage in your browser. It keeps no copy of your files or of the data you give it. The only thing it writes is the table you asked for, in the page you chose. Nothing remains after the app is uninstalled, apart from the tables already added to your pages.

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 files you import, which pages you change 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 file is treated as data, never as code. Each cell is written to the page as text in Confluence's own document format, keeping at most bold, italic, underline or strikethrough, so nothing in the file can add links, markup or scripts to the page. The panel is built with Atlassian's UI Kit components, which encode what they display. File sizes and row counts are limited, as described in the documentation.

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.