bytera
Book a demo
← Pulse

Pulse — Privacy Policy

Last updated: June 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, to enforce per-user rate limits, and as a pseudonymous identifier in usage telemetry (Section 6). We do not access profile details (names, email addresses) beyond what Atlassian provides in the app context.

3. Data Processing

Important: Pulse runs entirely within the Atlassian Forge platform. Your Confluence content is never sent to servers outside Atlassian's cloud infrastructure. The only outbound connection is product usage metrics, described in Section 6.

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 AI Processing — Atlassian Forge AI (Advanced edition)

The AI semantic duplicate detection feature (available in the Advanced edition) uses Atlassian Forge AI — the LLM service operated by Atlassian inside the Forge platform. When it runs, Pulse submits limited, size-capped content excerpts and page metadata to Forge AI — never full page bodies — to identify pages with likely similar content.

  • Processing happens within Atlassian's platform — your content is not sent to any third-party AI provider.
  • Inputs are strictly size-capped and are not stored by this feature.
  • On the Standard edition, this AI feature is never invoked.

3.3 Forge Platform

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

  • Forge SQL (MySQL): Used to store scan results (per-page and per-space health/AI scores and page titles) and admin-configured content policies. No page bodies are stored.
  • Forge App Storage: Used for app configuration settings.
  • Forge AI (LLM): Used only for the Advanced edition's semantic duplicate detection, as described in Section 3.2.

4. Data We Store

Data Type Where Retention
Scan results (per-page and per-space health/AI scores, page titles) 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 page bodies. We do not store any user personal data. Scan results contain scores and page titles — never the content itself. All stored 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.
  • Detecting likely duplicate pages (including, on the Advanced edition, via Atlassian Forge AI as described in Section 3.2).
  • 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, or any purpose other than providing Pulse functionality.

6. External Services

Your Confluence content never leaves the Atlassian environment. Pulse has no external backend: content analysis runs in the Forge runtime, and AI processing uses Atlassian's own Forge AI service inside the platform — not a third-party AI provider.

The single outbound connection Pulse makes is product usage metrics sent to PostHog — an analytics tool on Atlassian's approved analytics tools list, declared in the app's Forge manifest under the analytics category with end-user data out of scope. These metrics are feature-usage events (e.g. "dashboard opened") keyed to pseudonymous identifiers (Atlassian account ID and site identifier) and contain no names, no email addresses, no page content, and no page titles. They exist solely so we can understand which features are used and improve the product, and site admins can manage this egress through Atlassian's admin controls.

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.
  • Content Stays in Atlassian: Pulse has no external backend — your Confluence content never leaves Atlassian's infrastructure.
  • Least Privilege: We request only read-access scopes — the minimum necessary for app functionality.
  • Permission-Aware: Pulse honors Confluence permissions — users only see results for spaces and pages they can access.
  • No Page-Body Storage: Only scores and titles are persisted, never page bodies.
  • Rate Limiting & Usage Caps: All backend operations, including AI features, are rate-limited and budget-capped per user and per site.

8. Data Sharing

We do not share your Confluence content with any third parties. Content analysis and AI processing stay within Atlassian's cloud environment.

The only third-party service Pulse communicates with is PostHog — an Atlassian-approved analytics tool that receives the usage metrics described in Section 6. It never receives your content.

The only other 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 advertising or cross-site 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 scores and page titles, 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 support@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
Read content summaries To check pages for similar content (duplicate detection)
Read content analytics To combine page view counts with health scores (high-traffic alerts)
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: