Pulse — Privacy Policy

Last updated: April 2026

1. Overview

Bytera ("we", "us", "our") is committed to protecting your privacy. This Privacy Policy explains how Pulse, 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 Pulse. Atlassian is not responsible for our data practices.

2. Data We Access

Pulse is a Confluence app that analyzes content health and AI-readiness across your instance. To provide this functionality, Pulse accesses the following data through Atlassian APIs:

2.1 Confluence Content (Read-Only Access)

  • Page content: Titles, body content, and structure — accessed during health scans to calculate quality scores.
  • Page metadata: Last modified date, version history, contributors — used for content quality analysis.
  • Space metadata: Space names and structure — used to organize health reports by space.
  • Links: Internal page links and smart links — analyzed for broken link detection.

Important: Pulse has read-only access to your Confluence content. It cannot modify, delete, or create any pages or content.

2.2 User Context

  • Atlassian Account ID: Used to identify admin users for settings management. We do not access profile details beyond what Atlassian provides in the app context.

3. Data Processing

Important: Pulse runs entirely within the Atlassian Forge platform. No data is sent to any external servers or third-party services. All processing happens within Atlassian's secure cloud infrastructure.

3.1 Content Analysis

When Pulse scans your content, it calculates quality scores per page using our proprietary scoring engine. All calculations run entirely within the Forge runtime. No AI, machine learning, or external APIs are used in the scoring process.

3.2 Forge Platform

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

  • Forge SQL (MySQL): Used to store scan results (aggregated scores per space and instance) and admin-configured content policies. No raw page content is stored.
  • Forge App Storage: Used for app configuration settings.

4. Data We Store

Data Type Where Retention
Scan results (aggregated health/AI scores per space) Forge SQL (within Atlassian cloud) Until app is uninstalled
Content policy rules (admin-configured) Forge SQL (within Atlassian cloud) Until deleted by admin or app is uninstalled
App configuration Forge App Storage Until app is uninstalled

We do not store any raw page content. We do not store any user personal data. Scan results contain only aggregated, numerical scores — not the content itself. All data remains within the Atlassian cloud environment.

5. How We Use Data

We use the data we access exclusively for:

  • Calculating content health and AI-readiness scores (core app functionality).
  • Detecting broken internal links.
  • Storing aggregated scan history for trend analysis.
  • Applying admin-configured content quality policies.

We do not sell, rent, share, or use your data for advertising, marketing, analytics, or any purpose other than providing Pulse functionality.

6. External Services

Pulse does not use any external services. No data leaves the Atlassian Forge environment. There are no external API calls, no third-party integrations, and no data transmission outside of Atlassian's cloud infrastructure.

7. Data Security

We implement industry-standard security measures:

  • Forge Sandbox: Pulse runs in Atlassian's secure Forge environment with tenant isolation and sandboxed execution.
  • No External Communication: Unlike many apps, Pulse has no external backend — your data never leaves Atlassian's infrastructure.
  • Least Privilege: We request only read-access scopes — the minimum necessary for app functionality.
  • No Raw Content Storage: Only aggregated scores are persisted, never the content itself.

8. Data Sharing

We do not share your data with any third parties. Since Pulse operates entirely within the Forge platform with no external services, there is no data transmission outside of Atlassian's cloud environment.

The only exception: We may disclose data when required by law, legal process, or to protect our rights or the safety of users.

We do not use any third-party analytics, advertising, or tracking services within Pulse.

9. 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 only store aggregated scores, uninstalling Pulse 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 admin@bytera.tech.

10. Permissions Explained

Pulse requests the following Atlassian API scopes and their justification:

Permission Why It's Needed
Read pages To access page content for health and AI-readiness scoring
Read spaces To list and organize health reports by space
Read content details To access metadata (dates, versions, links) for scoring calculations
App storage To store scan results and content policy configuration

11. 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.

12. Contact

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