Privacy Policy
Page Tree Sorter for Confluence Cloud
As of: 2026-10-06
1. Controller and contact
The app “Page Tree Sorter” (“the app”) is provided by Medi@Business Frank Löffler, Am Anger 6, 91550 Dinkelsbühl, Germany, represented by Frank Löffler (owner).
Privacy requests and support: via the support form
2. Roles
- The customer (your organization) is the controller of the data in its Confluence Cloud site.
- Atlassian operates Confluence Cloud and the Forge platform on which the app runs entirely (compute, storage, logs). Atlassian’s processing is governed by your agreements with Atlassian.
- Medi@Business provides the app’s code. The app sends no data to servers of Medi@Business or any third party. Medi@Business cannot access the app’s storage in your site. Medi@Business can only see the technical logs (section 5), unless your site admin has turned off log access.
3. Data the app processes
| Data | Purpose | Location |
|---|---|---|
Sort mode of a page (A–Z, Z–A, Manual), account ID of the space admin who set it, timestamp | apply and display the sort rule and who set it | content property page-tree-sorter.mode on the page in your Confluence |
| Sort mode of a folder with the same fields | as above (folders have no content property the app can use) | app’s Forge storage (key-value store), key foldermode:<id> |
| Overview index: page/folder ID, title, space ID, type, mode, setter’s account ID, timestamp | “Sorting” space overview, personal data reporting to Atlassian | Forge storage, keys space:<spaceId>:node:<id> and node:<id> |
Job data: timestamps and locks (job:node:<id>, run:<id>, dirty:<id>, conflicts:<id>, selfmove:<id>), IDs of pages that could not be moved (lastrun:<id>) | control sort jobs, prevent parallel runs and loops, permission hint in the dialog | Forge storage. Locks are short-lived; lastrun:<id> is kept until that level is sorted again; selfmove:<id> until the app’s own move event arrives (at most about 2 minutes) |
| IDs, titles, order and parents of pages, folders, whiteboards, databases and smart links | compute the target order and move items | in memory during processing only, not stored (except titles in the index) |
Not processed: page content (text, attachments, comments), names, email addresses or other profile data. The UI shows the name for a stored account ID by fetching it from Atlassian at display time; it is not stored. Page titles may in rare cases be personal data themselves; they are stored only for the overview.
4. Location, no transfer to third parties
- The app runs on Atlassian Forge only. It declares no external hosts (no egress permission) and transfers no data outside Atlassian.
- According to Atlassian, Forge storage is located with the Confluence site and follows its data residency setting. Content properties are part of your Confluence data.
- Medi@Business does not transfer any data to third countries. Atlassian’s infrastructure locations are governed by Atlassian.
5. Logs
The app writes technical logs to Atlassian’s Forge logging: event names, page, folder and space IDs, counts and HTTP status codes. Logs contain no titles, content or account IDs. Atlassian makes them available to Medi@Business for troubleshooting unless your site admin disables log access in Atlassian Administration. Atlassian’s retention applies.
How the app is secured and how to report a vulnerability: security policy.
6. Legal basis
- Processing on behalf of and as instructed by the customer: Art. 6(1)(b) GDPR (performance of the contract for the use of the app) or Art. 6(1)(f) GDPR (customer’s legitimate interest in a traceable configuration: who set a sorting rule).
- Logs for troubleshooting: Art. 6(1)(f) GDPR (legitimate interest in secure operation).
7. Retention and deletion
- Reset to inherited deletes the content property or folder entry and the index row immediately.
- Trashed pages: the content property stays on the page until Confluence purges it. The app therefore keeps the index row (hidden in the overview), so the weekly privacy run keeps reporting the account ID and sets it to empty for closed accounts. If the page is restored, it shows up in the overview again. Purged pages are removed from the index immediately. Confluence sends no event for deleted folders: a space admin removes their index row in the overview (“Reset to inherited”), which also works after the folder was deleted. The weekly privacy run does not remove rows; for closed accounts it only sets the account ID to empty.
- Closed Atlassian accounts: every week the app reports all stored account IDs through Atlassian’s Personal Data Reporting API and replaces the account ID of closed accounts with an empty value in the content property, folder entry and index.
- Uninstall: Atlassian deletes the app’s Forge storage (index, folder modes with account ID and timestamp, job data); Atlassian states that it is retained for up to 28 days after uninstallation and is not restored automatically on reinstall. Content properties on pages remain part of your Confluence data (mode, account ID, timestamp) and are reused on reinstall. Remove them before uninstalling with “Reset to inherited” if required.
8. Your rights
Data subjects have the rights of access, rectification, erasure, restriction, data portability and objection (Art. 15–21 GDPR) and the right to lodge a complaint with a supervisory authority (Art. 77 GDPR). As the data lives in your organization’s site, please contact its administrators first. Medi@Business handles requests via the support form.
9. Changes
This policy is updated when the app or the law changes. The version published at https://codemonkey.cloud/apps/page-tree-sorter/ applies.
← Back to the documentation