Data & permissions

What this app stores

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 it requests, 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

For this app's general data-handling commitments - sub-processors, data residency, what happens on uninstall - see the trust center.