Privacy & Access Notes

How Content Formatting Macros Handles Data

Principle 1 - Content Stays in Confluence

Content Formatting Macros does not transmit page content, attachment data, or user information to external servers. All macro rendering is performed within the Atlassian Confluence Cloud environment using Atlassian's Forge or Connect app runtime.

The only external communication is:

• License verification with the Atlassian Marketplace
• Optional background image URLs you configure in the Background or Banner macros (the browser fetches these directly)

Principle 2 - Visibility Macros Are UI Controls, Not Security Boundaries

Conditional Show and Conditional Hide macros change what is displayed in the browser. They do not change Confluence's underlying access control.

A user with page-read permission can still access all page content via:

• The Confluence REST API
• The page export (PDF, Word)
• The Confluence mobile app

Do not use Conditional Show/Hide to protect sensitive data. Use Confluence Page Restrictions for true access control.

Conditional macros are appropriate for:

• Audience targeting (showing relevant content to relevant users)
• Reducing visual clutter (hiding admin notes from general readers)
• Progressive disclosure (revealing advanced content to expert users)

Principle 3 - Attachment Deletion Is Permanent

The Attachment Management Center's delete function permanently removes files from Confluence. There is no recycle bin or undo. Always confirm the file list carefully before executing a bulk delete.

User Data in Macros

The User Profile macro reads user data from Confluence's user directory. Only data that users have voluntarily entered in their Confluence profile is displayed. The macro does not access email systems, HR systems, or external directories.

Questions About Data Processing

For questions about how Clovity processes data as the app vendor, contact developers@clovity.com or review the app's privacy policy on the Atlassian Marketplace listing.