Security Policy — Table Audit & Export for Confluence

Vendor: Le Hoang Quang Trung (sole proprietor), Da Nang, Vietnam.
Security contact: support@trunkle.win
Version 1.0 — 13 October 2026. Reviewed annually, and after any security incident.

This page describes the security practices for this app. It is separate from the privacy policy, which describes what we do with personal data.

A written security review of this app, including the findings against this policy and what was done about them, is published alongside it.

1. Security model

The app has no backend, no database and no network egress. It is a Forge Custom UI app whose static files are served by Atlassian's own infrastructure. Page content is requested from Atlassian's API, checked inside the user's browser, and the spreadsheet is built there too.

The consequence is deliberate and is the most important control in this system: there is no server of ours to breach, no database to leak, and no customer data at rest anywhere. Any security incident involving this app is therefore a question of code integrity or account access, not of a data breach.

2. Data handling

DataWhere it livesRetention
Customer page and table contentThe user's browser, for the few seconds the app runsNone. Never transmitted to us, never stored.
The exported .xlsx fileBuilt in the browser, saved by the browser Held by the customer only. Never uploaded.
Source codePrivate repositoryContains no customer data.
Publishing credentialsThe developer's workstationRotated when no longer needed.

We collect no analytics, no telemetry, no error reports and no usage statistics. We set no cookies. There are no user accounts. There is no AI model in this app, and no data is sent to any third party, because we hold none to send.

Support requests arrive by email. We ask customers not to send table contents with a report, and we do not need them in order to help.

3. Encryption

4. Access control

5. Secure development

6. Vulnerability management

npm audit is run before every release and the results are recorded. A finding that cannot be fixed without a breaking change is documented together with an assessment of whether the vulnerable code is reachable in the shipped bundle.

Atlassian's Security Bug Fix Policy sets our remediation deadlines, and we treat them as hard commitments:

SeverityCVSSFixed within
Critical≥ 9.010 days
High≥ 7.04 weeks
Medium≥ 4.012 weeks
Low< 4.025 weeks

A vulnerability report takes priority over all feature work, without exception.

Reporting a vulnerability

Email support@trunkle.win, or raise a ticket in the Atlassian Marketplace Security (AMS) project. We acknowledge a report within one working day. Please include the steps to reproduce; please do not include customer data.

7. Incident response

A written incident response plan is maintained. Its commitments:

8. What this policy does not claim

Stated plainly, because an overclaiming security policy is worse than none:

These are consequences of the size of the business, not oversights, and they are reviewed as it grows.


Table Audit & Export for Confluence | Documentation | Security review | Support | Privacy policy | support@trunkle.win