How your data is handled
Your HTML stays in your Confluence site. HTML Macro is built on Atlassian Forge: it saves your HTML, CSS and JavaScript inside the Confluence page and runs it in the reader’s browser, inside an isolated frame. RVS Softek has no servers of its own and does not receive or store your content.
- Runs entirely on Atlassian Forge
- No RVS Softek servers
- Runs in an isolated frame
- Admins control outside websites
At a glance
The short answers to the questions buyers ask first.
Where is macro code stored?
Inside the Confluence page, in the macro’s settings, on Atlassian’s infrastructure
Where is it rendered?
In the reader’s browser, inside an isolated frame that can’t read the Confluence page, the reader’s session or cookies
Does content reach RVS Softek servers?
No. The app runs entirely on Atlassian Forge
Does the app use AI services outside Atlassian?
No. The optional HTML Macro Builder runs in Atlassian Rovo
Does the app contact outside services?
Only websites a macro’s author chooses to embed or call. Admins can restrict these to a trusted-domains list
Can admins control it?
Yes. Turn JavaScript off, restrict outside websites, and choose which groups may add or edit macros
Is data used for advertising or sold?
No. The app contains no analytics, tracking or advertising code
Platform
Atlassian Forge, Confluence Cloud
What the app can access
The app asks Confluence only for the permissions its features use. Most of them support the admin settings and the change history.
read:confluence-user
- Why the app needs it
- Check that a user is a Confluence admin before showing the admin settings
read:confluence-groups
- Why the app needs it
- Let admins pick which groups may add or edit HTML macros, and check a user’s group membership
read:page:confluence
- Why the app needs it
- Read the change history kept on each macro’s page
write:page:confluence
- Why the app needs it
- Add an entry to that change history when a macro is saved
search:confluence
- Why the app needs it
- Find the pages that contain HTML macros, to build the admin audit log
read:app-data:confluence / write:app-data:confluence
- Why the app needs it
- Keep the history of admin settings changes in a record only the app can reach
read:space:confluence, read:content-details:confluence, write:content.restriction:confluence
Older versions- Why the app needs it
- Kept for an audit page that older app versions could create. The current version only reads its old entries
storage:app
- Why the app needs it
- Keep admin settings, data saved by macro scripts, and code from Rovo
Good to know
- 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.
Reaching outside websites
The app never chooses websites on its own. These two doors open only where a macro’s author points it.
Server-side web requests
- Why
- Embed a web page by URL, and let a macro’s own script call an outside API
Images, styles, fonts, media and frames in the browser
- Why
- Let a macro’s HTML show content from websites its author chose
Where your content lives and how it renders
Macro code is saved inside the Confluence page that holds it. It gets the same permissions, version history, backups and data residency as the rest of the page.
- 01
Write HTML, CSS and JavaScript
Write them in the editor, start from a snippet, or enter a web address to embed.
- 02
Click Save
The macro stores the code (or the address) in the page, and the save is added to that macro’s change history. Nothing is copied to RVS Softek.
- 03
Someone views the page
The app loads in their browser and runs the code there.
Rendering stays inside the browser
- Code runs in an isolated frame with no access to the Confluence page, the reader’s session, cookies or the app’s own storage.
- Admins can switch JavaScript off for the whole site. Pages then show the HTML and CSS only.
- When a macro’s script makes a web request, the app’s backend sends it. Confluence cookies and sign-in details are never forwarded.
What is stored where
HTML, CSS, JavaScript, or the embedded web address
- Where
- In the page’s macro
- How long
- As long as the page or macro exists — normal Confluence version history applies
Change history per macro (who saved, when, editor or Rovo)
- Where
- A content property on the macro’s own page
- How long
- The last 50 saves per macro
Admin settings (JavaScript on/off, trusted domains, allowed groups)
- Where
- Forge storage on Atlassian’s infrastructure, encrypted at rest, following your site’s data residency
- How long
- Until changed, or until the app is uninstalled
History of admin settings changes (who changed what, when)
- Where
- An app-only record in Confluence that users can’t open
- How long
- The last 1,000 changes
Data a macro’s own script saves
- Where
- Forge storage, kept separately for each macro (up to 64 KB)
- How long
- Until the script removes it, or until the app is uninstalled
Code generated by Rovo
- Where
- Forge storage, kept separately for each macro
- How long
- Until replaced, or until the app is uninstalled
Browser storage used by a macro’s script, and the editor theme
- Where
- The reader’s own browser
- How long
- Until the reader clears browser data
Good to know
- The change history stores Atlassian account IDs, not names or email addresses. Anyone who can view a page can read that page’s change history.
- Data that one macro saves can’t be read by any other macro.
Rovo AI (HTML Macro Builder)
The Builder is optional and runs inside Atlassian Rovo. If no one opens it, nothing is sent to Rovo.
- 01
Click Ask Rovo on the macro
An editor starts the Builder from the macro itself.
- 02
Rovo opens beside the page
The app passes only a reference to the macro — not the page content or the macro’s existing code.
- 03
Describe what you want
The editor describes what they want, and Rovo writes HTML, CSS and JavaScript.
- 04
Review, then Apply
The code waits in Forge storage. It changes nothing until an editor clicks Apply.
What this means for your data
- Only users who are allowed to edit HTML macros can apply or discard Rovo code.
- Rovo runs inside your Atlassian site, under your organization’s Rovo settings and Atlassian’s data policies.
- The editor also offers a prompt to copy into another AI tool. Copying it sends nothing: the user pastes it wherever they choose.
- Review AI-generated code before applying it.
Outside websites
The app contacts an outside website only when a macro’s author points it there. It never chooses websites on its own, and admins decide how open this is.
Embeds a web page by URL
- What is sent
- A request for that page
- Where it goes
- The website at that URL
Writes a script that calls an outside API
- What is sent
- The request the script builds (it can include data the script collects)
- Where it goes
- The API the script calls
Uses outside images, fonts, styles or media in the HTML
- What is sent
- The reader’s browser loads them, as on any web page
- Where it goes
- The websites that host them
Clicks Ask Rovo
- What is sent
- A reference to the macro, then the editor’s chat
- Where it goes
- Atlassian Rovo, inside your site
Admin controls (Confluence settings → HTML Macro)
- Trusted domains: allow only websites on your list for embedded pages and script requests. Strict mode also blocks outside images, styles and frames that aren’t on the list.
- JavaScript: turn scripts off across the site.
- User permissions: let everyone, or only selected groups, add and edit HTML macros.
- Audit log: see who saved each macro and who changed each setting.
- Script requests are limited to secure (https) addresses. The app blocks requests to private and internal network addresses.
- Treat a macro’s script like any code your team publishes. Whatever it collects is sent where its author decided.
- RVS Softek is never one of these destinations, and help links in the app carry no page or user data.
Uninstall, exports and logs
- Uninstalling
- Atlassian keeps the app’s Forge storage (admin settings, script data, Rovo code) for 28 days, then deletes it. Macro code and the per-page change history stay with the pages.
- Page export
- In a Confluence PDF or Word export, the HTML is converted to standard Confluence text. An embedded web page appears as a link.
- Account data
- The app stores Atlassian account IDs only in change history and the settings history. It stores no email addresses, passwords or tokens.
- Logs
- The app’s Forge logs record technical errors and, when group restrictions are on, each edit-permission decision (account ID and group names). They aren’t used to record macro code or page content, and RVS Softek reads them only through Atlassian’s developer console.
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.
