QR Hub for Confluence
Product Docs Trust Centre Privacy Policy Security Policy

QR Hub for Confluence
Privacy Policy

Last updated: June 2026

Overview

Agilva Solutions built QR Hub for Confluence with privacy as a design principle, not an afterthought. This policy explains precisely what data the app accesses, how it is used, and what protections are in place. The short version: we access the minimum data needed to render the UI, we store nothing, and we share nothing with any third party.

Data collected

QR Hub for Confluence reads the following data from the Confluence API when you use the content action feature:

  • Page title — displayed in the content action modal.
  • Space name — displayed in the content action modal.
  • Content type and version — displayed in the content action modal.
  • Author display name — displayed in the content action modal.

This data is fetched on demand when you open the content action modal. It is rendered in the UI and immediately discarded. It is never written to any database, log, or storage layer.

QR Hub does not collect:

  • Email addresses or personal identifiers
  • Page content or body text
  • URLs entered into the Global QR Generator
  • Downloaded QR codes or their contents
  • Usage patterns, session data, or event logs
  • IP addresses or device identifiers

How data is used

The metadata fetched from Confluence (page title, space name, content type, author) is used exclusively to populate the content action modal UI shown to the user who triggered the action. It is used for no other purpose.

QR code generation is performed entirely client-side. The URL used to generate a QR code is processed within the Forge frontend runtime only and is never transmitted to Agilva Solutions or any external service.

Data storage

QR Hub for Confluence does not use any persistent storage. This includes:

  • No Forge Storage (storage:app or storage:user)
  • No external databases
  • No browser local storage
  • No server-side logs
  • No cookies

Every interaction with QR Hub is stateless. Nothing persists between sessions.

Third parties

QR Hub for Confluence does not integrate with, transmit data to, or rely on any third-party services. There are no external APIs, no analytics providers, no advertising networks, and no data brokers involved at any layer of the app.

The app runs exclusively within Atlassian’s Forge infrastructure. Atlassian’s own privacy policy governs the infrastructure layer.

Your rights

Because QR Hub does not store any personal data, there is no data held about you that could be accessed, corrected, or deleted. If you have concerns about the data Atlassian holds as part of your Confluence subscription, those should be directed to Atlassian in accordance with their privacy policy.

If you have any privacy-related questions about QR Hub specifically, please contact us directly.

Contact

Privacy questions or concerns can be directed to Agilva Solutions. Get in touch here and we will respond within one business day.