How your data is handled
Your content stays in your Confluence site. Canvas Blocks for Confluence is built on Atlassian Forge: every macro saves its settings and content inside the Confluence page, and files you add are stored as attachments on that page. 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
- No AI, analytics or tracking
- Files stay on your page
At a glance
The short answers to the questions buyers ask first.
Where is macro content stored?
Inside the Confluence page, in the macro’s settings, on Atlassian’s infrastructure
Where are uploaded files stored?
As attachments on the same Confluence page — images, 3D models, page-builder layouts and templates
Where are macros rendered?
In the reader’s browser, inside Atlassian’s sandboxed Forge frame, using libraries bundled with the app
Does content reach RVS Softek servers?
No. The app runs entirely on Atlassian Forge
Does the app contact outside services?
No. The app declares no outside hosts, so Forge blocks it from sending data off Atlassian
Does the app use AI services?
No.
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 macros use. Almost every Confluence request runs as the signed-in user, so the app can’t see or change a page that user can’t.
read:page:confluence
- Why the app needs it
- Read a page’s headings (Numbered Headings) and its citations (BibTeX reference list)
write:page:confluence
- Why the app needs it
- Apply heading numbers to a page when an editor saves Numbered Headings settings
read:confluence-content.all
- Why the app needs it
- Read page content needed to build exports and reference lists
write:confluence-content
- Why the app needs it
- Save page updates made by macros at the editor’s request
read:content-details:confluence
- Why the app needs it
- Read page details such as attachment lists
read:attachment:confluence
- Why the app needs it
- Show images, 3D models and saved layouts that macros keep as page attachments
write:attachment:confluence / write:confluence-file
- Why the app needs it
- Upload images, 3D models, button snapshots and page-builder layouts to the page
delete:attachment:confluence
- Why the app needs it
- Remove an attachment the editor replaces or deletes inside a macro
read:confluence-user
- Why the app needs it
- Show display names and a user picker for survey managers, and check whether a user is a site admin
storage:app
- Why the app needs it
- Keep survey questions and responses, and Numbered Headings defaults, in Forge storage
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.
- It requests no permission to reach any website or service outside Atlassian.
Where your content lives and how it renders
Macro content 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
Insert a macro
Insert a Canvas Blocks macro (Tabs, Cards, Button, Alert, Survey and so on) and configure it in its dialog.
- 02
Click Save
The macro stores its text, styling and options in the page. Files you add are uploaded as attachments to that page. Nothing is copied to RVS Softek.
- 03
Someone views the page
The macro loads in their browser, reads its settings from the page and draws the content there.
Rendering stays inside the browser
- Libraries for maths (KaTeX), LaTeX, 3D models, panoramas and rich text are bundled with the app. No outside rendering server is used.
- HTML entered in the HTML Editor and other rich-text fields is cleaned before it is shown.
- Images and 3D files are read from the page’s own attachments, using the viewer’s Confluence access.
What is stored where
Macro content and settings (text, colours, links, icons, tabs, cards, dates, formulas)
- Where
- In the page’s macro
- How long
- As long as the page or macro exists — normal Confluence version history applies
Images, 3D models, panoramas, button snapshots
- Where
- Attachments on the same page
- How long
- Until deleted from the page
PageBuilder layouts, version history and saved templates
- Where
- JSON attachments on the same page
- How long
- Until deleted from the page
Survey questions, settings and managers
- Where
- Forge storage on Atlassian’s infrastructure, encrypted at rest, following your site’s data residency
- How long
- Until the app is uninstalled
Survey responses
- Where
- Forge storage, one record per respondent
- How long
- Until the app is uninstalled
Numbered Headings default format
- Where
- Forge storage (formatting choices only, no page text)
- How long
- Until changed, or until the app is uninstalled
Small viewer preferences (last open tab, a dismissed pop-up)
- Where
- The reader’s own browser storage
- How long
- Until the reader clears browser data
Surveys
The Survey macro is the one place where the app keeps who answered, so it is worth reading in full.
- Each respondent can answer once
- The app uses the respondent’s Atlassian account ID to enforce this.
- Anonymous surveys
- The account ID is not kept with the answers, and it never appears in results or CSV exports.
- Named surveys
- Results show the respondent’s Confluence display name. Email addresses are never stored.
- Who can edit it, and who sees results
- Only the survey’s creator, its managers and site admins can edit it. Who sees results is set by the creator.
Outside services
Canvas Blocks talks only to your Confluence site. It has no Git, AI, analytics or other third-party integrations.
Confluence (your site)
- Used?
- Yes
- Where data goes
- Stays in your site: pages, attachments and Forge storage
RVS Softek servers
- Used?
- No
- Where data goes
- Nothing is sent to RVS Softek
AI providers
- Used?
- No
- Where data goes
- None
Analytics or tracking
- Used?
- No
- Where data goes
- None
Other outside websites
- Used?
- No
- Where data goes
- Forge blocks the app from reaching hosts it hasn’t declared, and it declares none
Links carry no data
- Links you add to buttons, cards or banners open only when a reader clicks them. The app doesn’t call them.
- Help links in the app open RVS Softek’s public documentation. They carry no page or user data.
Uninstall, exports and logs
- Uninstalling
- Atlassian keeps the app’s Forge storage (surveys and Numbered Headings defaults) for 28 days, then deletes it. Macro content and attachments stay with the pages.
- Page export
- In a Confluence PDF or Word export, each macro is converted to standard Confluence content (text, tables, panels) so it reads without the app.
- Downloads
- Survey CSV files and HTML downloads are created in your browser. Only the survey creator or a site admin can export a CSV.
- Account data
- The app keeps Atlassian account IDs only for survey creators, managers and respondents. It stores no email addresses, passwords or tokens.
- Logs
- The app’s Forge logs hold technical details for troubleshooting (status codes, error messages, page IDs). They aren’t used to record macro content or survey answers, 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.
