Trust center

This page sets out what our apps do with your data, what they are allowed to do, and what we commit to. It is written to be checked, not believed: wherever a claim can be verified from the app's own manifest or from Atlassian's platform, we say how.

The short version

Nothing leaves Atlassian. Our apps run entirely on Atlassian Forge, inside Atlassian's infrastructure. They declare no external egress, which means the platform itself blocks any outbound call to a server of ours or anyone else's. There is no Execolab server in the path — not for content, not for analytics.

We store almost nothing. No page content is ever copied out of Confluence. What little we do store is listed below, item by item.

No analytics, no tracking. We collect no usage data, and no telemetry is implemented in any published app.

What each app stores

Multilingual Pages for Confluence

Data Where it lives Why
The list of languages configured on a page A content property on that page, inside your Confluence Avoids re-reading and re-parsing the whole page on every view. Rebuildable at any time from the page itself.
A reader's language choice for a given page Forge storage, Atlassian-hosted, keyed by account ID and page ID So a reader who picks a language finds it again on their next visit. Capped in number, with the oldest entries evicted.

Page content is never stored, copied or logged. Translations stay in the Confluence macros where their author typed them.

Diagnostic logs record technical identifiers — a page ID, an error code, a correlation reference — never the content of a page.

Permissions we request, and why

Atlassian shows you these at install time. Each one is here because a specific call needs it; the list below was established by removing them all and letting the platform state what it required.

Permission What it is for
read:page:confluence Read a page's content to find the language macros in it, and read our own stored summary
write:page:confluence Write that summary back to the page
read:confluence-user Read the reader's account language, to pick the right translation
read:confluence-content.summary Be notified when a page changes, so the summary stays current
storage:app Store the reader's language preference

We removed a permission from this list during an audit: an earlier version requested a broader write access it never actually used. Asking for a permission "just in case" is not acceptable to us.

Sub-processors

None. No third party processes your data on our behalf, because no data reaches us in the first place.

Where your data is

Content stays in your Confluence instance and follows the data residency you have configured with Atlassian.

App storage — the language preferences described above — is hosted by Atlassian as part of the Forge platform, and is governed by Atlassian's own terms. We do not choose or control its location independently.

What happens if you uninstall

No content is lost. Your translations remain in your Confluence pages; they belong to you and are stored nowhere else.

In view mode, each macro shows a Confluence error message in place of its content, and the language switcher stops working. Open the page in edit mode and all the text is there, ready to copy wherever you need it.

We recommend exporting or copying your content before a permanent uninstall, while the app is still running.

Reporting a vulnerability

Write to security@execolab.com. Please do not open a public issue.

We commit to acknowledging your report within two working days, keeping you informed of our assessment, and crediting you if you wish once the matter is resolved.

What we do not claim

We would rather state a limit than let you discover it:

Each app also publishes its own list of limits — for Multilingual Pages, it is here.


Questions about anything on this page: contact@execolab.com.