Baselines Docs
Baselines Docs
Last updated: 2026-10-20
Baselines for Confluence Cloud is a Confluence Cloud app that captures point-in-time snapshots of pages and their attachments. It runs on Atlassian Forge. To create and serve baselines, the app reads your Confluence content and stores baseline records in Forge's hosted storage: references to the pages you snapshot, the space involved, how you group baselines into documents and releases, your schedules, permissions and settings, and a log of who did what in the App. It does not keep a permanent copy of your page bodies: the actual page content and attachments are read from Confluence on demand when you view, compare, export or republish a baseline. PDF export sends the assembled content and images to a rendering service operated by pluginDevs on Amazon Web Services (AWS), where the intermediate files are deleted as soon as they are used and the finished PDF is removed within one hour. Our sub-processors are Atlassian, AWS for PDF export, and an Atlassian-approved analytics tool for product-usage analytics, which never carry your Confluence content and which your administrator can turn off. We do not sell or rent your data. A deleted baseline stays in Deleted for 30 days, where it can be put back, and is then removed; everything is removed within 90 days of uninstalling the app.
Baselines for Confluence Cloud ("Baselines", the "App") is a content-snapshot and version-tracking app for Confluence Cloud, published by pluginDevs ("we", "us", "our"). This Privacy Policy explains what data the App accesses and processes, why, where it is stored, and the choices you have. It applies to the Baselines app installed from the Atlassian Marketplace.
In data-protection terms, the Atlassian customer who installs Baselines is the controller of the Confluence data involved; pluginDevs, through the App, processes that data on the customer's behalf to provide content snapshots, comparison, export, republishing and scheduling.
Baselines is an Atlassian Forge app. Its interface, its processing and its stored records run inside Atlassian's platform, with one exception for your content: producing a PDF, which is described below. Apart from that, the App sends only product-usage analytics outside Atlassian, also described below.
A baseline is a saved snapshot taken at a moment in time. When you create one, the App reads the pages you selected (and their attachments) and records what it needs to identify and re-serve them later. When you view, compare, export or republish a baseline, the current or captured version of each page is read from Confluence at that time.
Baselines accesses only the data it needs to capture and serve snapshots:
To build, display, compare, export and republish baselines, Baselines reads the Confluence content you select: pages, blog posts and their attachments, with their versions and their place in the page tree. This content is read from Confluence at the time it is needed (for example when a baseline is created, viewed, compared, exported or republished).
Baselines reads basic user profile details, such as a display name, so it can show who created a baseline and who did what with readable names.
Baselines stores the records and settings needed to provide the service: baseline records (for each snapshot: references to the captured items, the space, and who created it and when), scheduled-baseline configurations, permission assignments, app settings, the documents and releases you group baselines into, and a log of who did what in the App. These records are stored in Forge SQL. Baseline records reference your pages; they are not a permanent copy of your page bodies.
We process the data above solely to provide the features you installed Baselines for:
We do not use your Confluence data for advertising, profiling, model training, or any purpose other than operating Baselines for you.
Baseline records, schedules, permissions and settings are stored in Forge SQL, the hosted database Atlassian provides to apps on its Forge platform. Atlassian holds that data alongside your Confluence site's own app data. Records made before September 2026 are also kept in a stopped database pluginDevs operates on Amazon Web Services: nothing is written to it or read from it, and it keeps them until we delete them.
What is persisted is the baseline record, meaning references to your pages and the metadata described above, and not a permanent store of your full page bodies. The live page content and attachments are fetched from Confluence on demand for viewing, comparison, export and republishing, processed to fulfil your request, and not retained as a separate long-term copy beyond the baseline record and the short-lived export files described next.
When you export a baseline, the App assembles the pages into a single document and sends that document and its images to a rendering service that pluginDevs operates on Amazon Web Services (AWS) in the United States, which converts it to a PDF. This is the one path on which Confluence content leaves Atlassian, and the files it produces are deleted within an hour of the export. For customers whose Atlassian data is held outside the United States, this means a PDF export is processed in the United States.
The uploaded document is deleted as soon as the renderer has read it, and the images once the render has used them. The finished PDF is kept in private storage, reachable only through a short-lived link issued to you, and is deleted automatically within one hour. A rendered PDF contains your page content, so it is treated as content rather than as metadata and is not kept beyond that window.
To understand how Baselines is used and improve it, the App sends product-usage analytics to an Atlassian-approved analytics tool, on Atlassian's pre-approved Runs on Atlassian allowlist: which screens and features are used, marked with your site so installs can be told apart, never with a person. We never send page content, page titles, baseline names, names, email addresses, account ids or any other end-user data. Your Atlassian administrator can turn it off in Atlassian Administration, in Baselines' settings under Connected apps, and Baselines keeps working normally. So that a fault cannot send a flood of events, Baselines keeps short-lived counts in its own storage inside Atlassian, which are removed within three days.
Baselines uses three sub-processors:
No other sub-processor or external service handles your Confluence data. Each processes data under its own terms and security commitments, and no advertising vendor is introduced anywhere.
We do not sell, rent or trade your personal information, including email addresses, and we do not disclose it to third parties, except to the infrastructure sub-processors named above as needed to run the service, or as required by applicable law or regulation. Any non-personal, aggregate information we may handle to operate and improve the service is processed only as described in this policy.
Baselines acts on your behalf using Atlassian's authorization, so it can only read content you are permitted to read, and a baseline only ever captures content the requesting user can access. Republish (formerly Import) publishes content back to Confluence only when you explicitly choose to, and it creates a new page rather than overwriting existing content.
Baselines requests the Confluence permissions needed to operate:
A Confluence administrator approves these when the app is installed.
Baseline records, releases, schedules, permissions and settings are retained for as long as they exist in the App, that is, until you delete them or uninstall the App. The log of who did what is kept for as long as the App is installed. Two retention windows then apply, and we state them rather than leaving "removed" open to interpretation:
Rendered PDF exports are removed within one hour of being produced, as described above, and so are the other files an export leaves on the rendering service. While an export is being built, the pages it has collected are kept in Forge hosted storage so that it can be resumed; if it is not finished, they are deleted within two days.
The App keeps some working details of your own unfinished or recent jobs, such as a freeze's page selection and an export's file name, in your browser for up to a day.
If you want your data removed sooner than these windows, contact us and we will action it.
Your underlying Confluence pages, attachments and any pages created by Republish (formerly Import) remain in Confluence and are unaffected by deleting a baseline, since they belong to your Confluence instance, not to Baselines.
The App runs in Atlassian's Forge platform. Traffic to the rendering service is over HTTPS; the service accepts only authenticated requests, restricts what it fetches, and deletes its files within an hour. Access to it is restricted to pluginDevs, and it is monitored for threats, with alerts reaching us as they occur. See our Security & data residency page for more.
This policy and our processing of personal data are governed by the laws of the European Union, including the General Data Protection Regulation (GDPR), together with the applicable local laws of the EU member state in which pluginDevs is established.
Your organisation (the Atlassian customer) is the controller of the Confluence data Baselines processes; pluginDevs, through the App, acts as a processor on your behalf, and Atlassian, AWS and the analytics provider act as sub-processors. Data subjects can exercise their rights, including access, rectification, erasure and restriction, through your organisation's own Confluence, which remains the system of record for your pages; pluginDevs will reasonably assist with any such request that reaches us and concerns the App data we hold. Nothing here limits mandatory rights available to you under the data-protection law of your own place of residence.
We may update this Privacy Policy from time to time to reflect changes in the app or in legal requirements. When we do, we will revise the "Last updated" date shown above. Material changes will be reflected on this page.
If you have questions about this Privacy Policy or how Baselines handles data, contact pluginDevs: