How your data is handled
Your diagrams stay in your Confluence site. PlantUML Diagrams for Confluence (Pro) is built on Atlassian Forge: it stores diagram code inside the Confluence page and draws diagrams in the reader’s browser. RVS Softek does not receive or store your diagram content, and the app never writes it to its logs.
- Runs entirely on Atlassian Forge
- No RVS Softek servers
- Renders in a network-locked frame
- Diagram code never leaves your site
At a glance
The short answers to the questions buyers ask first.
Where is diagram code stored?
Inside the Confluence page, in the macro’s settings, on Atlassian’s infrastructure
Where are diagrams rendered?
In the reader’s browser, inside an isolated, network-locked frame, using the PlantUML library bundled with the app
Does diagram content reach RVS Softek servers?
No. The app has no servers of its own — it runs entirely on Atlassian Forge
Does the app use AI services outside Atlassian?
No. The optional ✨ Generate with Rovo button opens Atlassian Rovo
Does the app contact external services?
No.
Is data used for advertising or sold?
No. The app contains no analytics or tracking
Platform
Atlassian Forge on Confluence Cloud
What the app can access
The app asks Confluence only for the permissions its features use. Every Confluence request runs with the signed-in user’s own access, so the app can never see or change a page that user can’t.
read:page:confluence
- Why the app needs it
- Read a page’s diagram macro, and check that the user may view or edit the page
write:page:confluence
- Why the app needs it
- Rewrite old macros during a Data Center migration
read:confluence-user
- Why the app needs it
- Check that a user is a Confluence admin before showing the app’s admin settings
storage:app
- Why the app needs it
- Keep app settings and migration progress in Forge storage
report:personal-data
- Why the app needs it
- Report stored Atlassian account IDs to Atlassian once a week, and erase data for closed accounts
read:attachment:confluence
Migration only- Why the app needs it
- Read diagram files that older Data Center apps attached to pages
read:content.metadata:confluence
Migration only- Why the app needs it
- Convert diagrams nested inside other macros
read:space:confluence
Migration only- Why the app needs it
- Rebuild “Spacegraph” page-tree diagrams
read:hierarchical-content:confluence
Migration only- Why the app needs it
- Read the page tree for Spacegraph diagrams
Good to know
- Migration-only permissions are used only when a Confluence admin runs Migrate from Data Center in the app’s admin settings.
- The app does not request access to Jira, and it can’t manage spaces or site settings. It doesn’t read or store users’ email addresses.
Rovo integration
One optional integration — and it never leaves Atlassian.
✨ Rovo
- What it does
- Opens the Atlassian Rovo chat so you can ask for PlantUML code
- Where data goes
- Stays inside Atlassian, under your organization’s Rovo settings
Good to know
- Rovo runs inside your Atlassian site, under your organization’s Rovo settings and Atlassian’s data policies.
Where your diagrams live and how they render
Diagram code is saved inside the Confluence page that holds it, so it gets the same permissions, version history, backups and data residency as the rest of the page.
- 01
Write or paste PlantUML
Write or paste PlantUML code in the editor, or start from a template.
- 02
Click Save
The macro stores the code and the diagram name inside the page. Nothing is copied to RVS Softek.
- 03
Someone views the page
The app loads in their browser, reads the code from the page and draws the diagram there.
Rendering stays inside the browser
- The real PlantUML engine, Graphviz (for DOT and diagram layout) and KaTeX (for math) are bundled with the app. No outside rendering server is used.
- Diagrams render in an isolated frame with no network access. It can’t reach the Confluence page, the user’s session or the internet.
- Remote !include / !includeurl lines are not fetched. The popular C4, Azure and Kubernetes libraries are bundled, so those work offline. Other remote includes are skipped, and images in a diagram can’t load from outside websites.
- Admins can set restricted keywords that block matching diagrams from being saved or shown.
What is stored where
Diagram code, name
- Where
- In the page’s macro
- How long
- As long as the page or macro exists — normal Confluence version history applies
Admin settings (restricted keywords, title display)
- Where
- Forge storage on Atlassian’s infrastructure, encrypted on disk, following your site’s data residency
- How long
- Until changed, or until the app is uninstalled
Migration progress (page IDs and titles), per admin
- Where
- Forge storage
- How long
- Until the scan finishes or is cleared, or until the admin’s account is closed
Diagrams saved by older app versions
- Where
- A copy in Forge storage
- How long
- Moved into the page when opened in the editor; the old copy remains until uninstall
Good to know
- Uninstalling: Atlassian keeps the app’s Forge data for 28 days, then deletes it. Diagram code inside pages stays with the pages.
- Downloads: SVG and PDF downloads are created in your browser.
- Page export: in a Confluence PDF or Word export, a diagram appears as its PlantUML code, not as a picture.
- Logs: the app’s Forge logs contain technical details only (page IDs, status codes, counts, error messages). They never contain diagram code, page content, tokens or email addresses.
Rovo AI, step by step
Rovo is Atlassian’s AI, and it runs inside your Atlassian site. The app never talks to an AI provider itself.
- 01
Click ✨ Generate with Rovo
It sits in the diagram toolbar.
- 02
Answer once
The first time, the app asks “Is Rovo Agent enabled on your Confluence instance?”. The answer is saved once for the whole site.
- 03
Rovo opens beside the page
If the answer is Yes, the Atlassian Rovo chat opens beside the page.
- 04
Ask Rovo, then copy
Ask Rovo for PlantUML code, then copy it into the macro’s editor (click the macro, then the pencil icon).
What this means for your data
- The app only opens the Rovo chat. It doesn’t send your diagrams or page content to any AI provider, and it doesn’t receive or store your Rovo conversation.
- If Rovo is turned off, or the site answered No, the button stays inactive. The rest of the app works normally.
- AI-generated code is treated like any other diagram: review it before saving.
Questions about your data?
For security questionnaires, data-handling questions or deletion requests, email our support team — or ask us anything about hosting, permissions and security.
