XPress - Privacy Policy

1. Overview

Bytera ("we", "us", "our") is committed to protecting your privacy. This Privacy Policy explains how XPress, our Confluence app listed on the Atlassian Marketplace, accesses, processes, and protects your data.

Bytera is the data controller and is fully responsible for the privacy, security, and integrity of any data processed by XPress. Atlassian is not responsible for our data practices.

2. Data We Access

XPress is a Confluence app that exports pages and blog posts to PDF, HTML and Markdown. To provide this functionality, XPress accesses the following data through Atlassian APIs:

2.1 Confluence Content (Read Access)

• Page and blog post content: Titles, body content, and formatting - accessed when you initiate an export. When a template asks for them, also the details of the exported pages: who created and last changed each one and when, and its version, and for the first page its labels, address and Page Properties values. When a template keeps or leaves out pages by their labels, the labels of every selected page, only to decide which pages the file holds. When a template takes Page Properties values from the space home page, also that page's Page Properties values, read with your permissions; a home page you cannot open gives none. When a page holds a Page Tree macro, the titles and addresses of the pages it lists, read with your permissions, and, for a tree sorted by date, who created or last changed each page and when, only to put the list in order. When a template prints them, the space's description and the first page's status.
• Attachments: Images and files embedded in pages - accessed to include them in the exported document.
• Space metadata: Space names and structure - used to display content selection options.
• Hierarchical content: Page tree structure - used for bulk and nested page exports.

2.2 Your Content Is Never Changed

• No writes: XPress does not create, change, or delete anything in Confluence. Exported files are kept in XPress's own storage within Forge and are never attached to your pages.

2.3 User Context

• Atlassian Account ID: Used to identify who initiated an export request and to enforce permissions. Inside Forge, it is also used to count how many different people exported in the last 7 days and to check that a download report comes from the person who made the export, and in a scrambled form to limit how many usage events one person's screens can send in an hour. The account ID itself is not sent to analytics.
• Display names: Read only to show or print them where you asked: the names beside a space's recent exports and, when a template prints them, your own name and the names of whoever created or last changed the exported pages. Names are read with your permissions, appear only on your screen or in your own exported file, and are never sent to analytics.
• Time zone: Read from your Atlassian profile, with your permissions, only when a template dates its documents in the time zone of whoever exports. It decides which day the dates in your exported file fall on, and nothing else: it is not printed, not stored, and never sent to analytics. Where your profile does not share it, the dates fall in UTC.

3. Data Processing & External Services

3.1 PDF Rendering Service

When you export content to PDF, formatted content is sent to our secure, cloud-hosted rendering service solely to be converted into a PDF file. HTML exports are produced entirely within Forge and never reach this service. The render service:

• Acts purely as a rendering engine - it does not read, interpret, analyze, or store the content in any way.
• Does not persist any data. Content is processed in-memory and discarded immediately after the PDF is generated.
• Does not log, record, or retain any content or metadata. There is zero data retention on the external service.
• All data is transmitted over encrypted HTTPS connections.

All content reading and file storage happen within the Atlassian Forge environment. The external render service only receives pre-formatted HTML for conversion, returns the resulting PDF and keeps nothing.

3.2 Forge Platform

XPress runs on Atlassian's Forge platform. The following Forge services are used:

• Forge Object Store: Used to store the files you export, in PDF, HTML or Markdown, within the Atlassian cloud environment. Each file is deleted automatically after 30 days. Your site's uploaded logo, fonts and cover image are kept here too, until they are replaced or removed.
• Forge SQL (MySQL): Used to keep your export history, which is deleted automatically after 30 days, and short-lived counts of the usage events your site and each person's screens have sent, which are deleted automatically within 4 days.
• Forge App Storage: Used for app configuration settings and templates.
• Forge Queues: Export and render tasks are processed through Forge async queues for reliable execution.

3.3 Product Analytics

To understand how XPress is used and improve it, XPress sends product-usage analytics to an analytics product on Atlassian's pre-approved allowlist for Runs on Atlassian apps: which screens and features are used and how exports go, marked with your site (its cloud ID and address) so installs can be told apart, never with a person. We never send page content, page or space names, template or file names, names, email addresses, account IDs, or any other end-user data. Your Atlassian administrator can turn it off in Atlassian Administration, in XPress's settings under Connected apps, and XPress keeps working normally.

The events are sent from XPress's server side within Forge, and XPress loads no third-party analytics or tracking code in your browser. So that a fault cannot send a flood of events, XPress keeps short-lived counts in its own storage inside Atlassian, which are deleted within 4 days.

4. Data We Store

We do not store Confluence page content outside of the Atlassian cloud environment. Exported files remain within Forge, managed by Atlassian's infrastructure.

5. How We Use Data

We use the data we access exclusively for:

• Converting Confluence content to PDF, HTML or Markdown (core app functionality).
• Storing exported files within Forge so you can download them.

We do not sell, rent, or share your data, and we do not use it for advertising or marketing. Apart from providing XPress, the only other use is the product analytics described in section 3.3, marked with your site and never with a person.

6. Data Security

We implement industry-standard security measures:

• Forge Sandbox: XPress runs in Atlassian's secure Forge environment with tenant isolation and sandboxed execution.
• Encrypted Transit: All communication between Forge and our render service uses HTTPS/TLS encryption.
• Least Privilege: We request only the minimum API scopes necessary for app functionality.
• No Persistent Storage of Content: Page content is never written to disk on our render service - it is processed in-memory only.
• Infrastructure Security: Our render service runs on secure cloud infrastructure with automatic scaling, patching, and enterprise-grade security controls.

7. Sub-processors and Data Sharing

XPress uses three sub-processors:

• Atlassian: provides the Forge platform (compute, storage and the SQL database). Your Confluence content is read here, and everything XPress keeps is stored here.
• Our rendering service's cloud provider: hosts the rendering service, which receives the formatted content of a PDF export, turns it into a PDF and keeps nothing. HTML and Markdown exports never reach it.
• PostHog (PostHog Inc., United States), an analytics product on Atlassian's pre-approved allowlist: receives only the product analytics described in section 3.3. It never receives page content or personal data.

No other sub-processor or external service handles your Confluence data. We do not share your data with anyone else, except when required by law or legal process, or to protect our rights or the safety of users. XPress uses no advertising or tracking services.

8. Your Rights

In accordance with applicable data protection laws (including GDPR), you have the right to:

• Access: Request information about what data we process.
• Rectification: Request correction of inaccurate data.
• Erasure: Request deletion of your data. Since we do not permanently store content, uninstalling XPress removes all app-related data from Forge.
• Data Portability: Request your data in a portable format.
• Objection: Object to the processing of your data.

To exercise any of these rights, please contact us at support@bytera.tech.

9. Permissions Explained

XPress requests the following Atlassian API scopes and their justification:

10. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify users of material changes by updating the "Last updated" date and, where appropriate, through our Atlassian Marketplace listing.

11. Contact

For any privacy-related questions, data requests, or security concerns:

• Email: support@bytera.tech
• Website: bytera.tech/contact
• Marketplace: Bytera on Atlassian Marketplace