Baselines Security & data residency
Baselines has a Forge frontend that runs on Atlassian and a backend that Plugin Developers operates on Amazon Web Services. This page describes exactly where your data goes, how access is scoped, what is stored and what is only processed transiently.
Unlike a Forge-only app, Baselines does send the Confluence content it processes to a backend that Plugin Developers operates on AWS — that is how it builds, stores and serves baselines and PDFs. We set out that flow plainly here rather than claim your content never leaves Atlassian.
Where your data lives
Baselines has two parts:
- A Forge frontend (Forge UI Kit) that runs inside Atlassian's platform and reads your Confluence content on your behalf.
- A backend that Plugin Developers operates on Amazon Web Services (AWS, US West region). The Forge app talks to it over HTTPS through Atlassian's Forge Remote mechanism; the app also serves classic Atlassian Connect pages.
Baseline records, scheduled-baseline configurations, permission assignments and app settings are stored in a PostgreSQL database on AWS. A baseline record holds references to your pages (page ID, title, link, type, path, version and dates), the space, and the creator's account ID and display details — not a permanent copy of your page bodies. Live page content and attachments are read from Confluence on demand when you view, compare, export or import a baseline.
App permissions
Baselines requests the Confluence permissions it needs and no more. A Confluence administrator reviews and approves them on install.
| Permission | Why Baselines needs it |
|---|---|
Read content read / READ | Capture pages and attachments into a baseline and build exports. |
Write content write / WRITE | Publish a baseline back into Confluence when you use Import (creates a new page). |
Act as user act-as-user / ACT_AS_USER | Read and write on your behalf so snapshots and imports respect your own access. |
User-scoped access
Because Baselines acts on your behalf, it can only ever read content you are already permitted to read, and a baseline only captures what the requesting user can access. Import writes to Confluence only when you explicitly choose to, and always creates a new page rather than overwriting existing content.
What data is processed and where
| Data | Used for | Stored? |
|---|---|---|
| Confluence page content & attachments | Building, viewing, comparing, exporting and importing baselines | Read on demand; not persisted as a permanent copy |
| Baseline records (page references, space, versions, dates) | Identifying and re-serving a snapshot | PostgreSQL on AWS |
| Schedules, permissions, settings | Your Baselines configuration | PostgreSQL on AWS |
| User account ID & display details | Showing who created a baseline; readable names | PostgreSQL on AWS (with the baseline record) |
| Assembled HTML + images for a PDF | Producing an export | Transient in S3; auto-deleted within one day |
PDF export and the rendering service
To export a baseline, the backend assembles the pages into one HTML document (with embedded images and any Jira issue macros) and sends it to a rendering service Plugin Developers operates on AWS (AWS Lambda + Amazon S3). The service converts the HTML to a PDF and returns it. Controls on that path:
- Requests to the rendering service are authenticated with an API key and carried over HTTPS.
- The service restricts outbound fetches (an SSRF filter) so it only retrieves the expected content.
- Intermediate files for a render job live in a private S3 bucket and are automatically deleted on a short lifecycle (within one day); they exist only to produce your PDF.
Transport & authentication
The Forge frontend authenticates to the backend through Atlassian's Forge Remote mechanism (a platform-issued token), so backend calls are tied to your Atlassian identity. All traffic between the frontend, the backend and the rendering service is over HTTPS. Access to the backend infrastructure on AWS is restricted to Plugin Developers.
Sub-processors & data residency
Baselines relies on two infrastructure sub-processors:
| Sub-processor | Role |
|---|---|
| Atlassian | Forge platform + Confluence Cloud (frontend runtime and content source). |
| Amazon Web Services | Backend compute, the PostgreSQL database of baseline records, and the PDF rendering service (Lambda + S3), in AWS US West. |
No advertising or analytics vendor is introduced into the handling of your Confluence data.
Privacy & terms
Baselines is published by Plugin Developers. We do not sell, rent or disclose your data except to the sub-processors above as needed to run the service, or as required by law. For the full statements see the Privacy Policy and Terms of Service, or contact support@plugin-developers.com.
Was this page helpful? Yes · No · Contact support