bytera
Book a demo
← SyncUp

SyncUp — Privacy Policy

Last updated: May 2026

1. Overview

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

2. Data We Access

SyncUp is a Jira app that provides role-based daily briefs, sprint autopsy reports, and velocity tracking. To provide this functionality, SyncUp accesses the following data through Atlassian APIs:

2.1 Jira Project Data (Read-Only Access)

  • Issues: Issue summaries, statuses, assignees, story points, and sprint assignments — used to generate daily briefs and sprint analysis.
  • Sprints: Sprint names, start/end dates, and states — used for sprint autopsy and velocity tracking.
  • Boards: Board configuration and type — used to identify active sprints per project.
  • Projects: Project names and keys — used to organize reports by project.

Important: SyncUp has read-only access to your Jira data. It cannot modify, delete, or create any issues, sprints, or project configurations.

2.2 User Context

  • Atlassian Account ID: Used to identify the current user for role-based brief generation and permission checks. We do not access profile details beyond what Atlassian provides in the app context.

3. Data Processing

Important: SyncUp 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 Sprint Analysis

When SyncUp generates briefs or autopsy reports, it fetches sprint and issue data through Jira APIs, calculates metrics in-memory, and displays results. No AI, machine learning, or external APIs are used in the analysis process.

3.2 Forge Platform

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

  • Forge SQL (MySQL): Used to store sprint snapshots (aggregated metrics per sprint) and historical velocity data. No raw issue content is stored.
  • Forge App Storage: Used for app configuration settings.

4. Data We Store

Data Type Where Retention
Sprint snapshots (aggregated metrics per sprint) Forge SQL (within Atlassian cloud) Until app is uninstalled
Velocity history (points completed per sprint) Forge SQL (within Atlassian cloud) Until app is uninstalled
App configuration Forge App Storage Until app is uninstalled

We do not store any raw issue content or descriptions. We do not store any user personal data. Sprint snapshots contain only aggregated, numerical metrics — not the issues themselves. All data remains within the Atlassian cloud environment.

5. How We Use Data

We use the data we access exclusively for:

  • Generating role-based daily briefs (core app functionality).
  • Producing sprint autopsy reports on sprint closure.
  • Tracking velocity trends across sprints.
  • Detecting stale issues and blockers.

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

6. External Services

SyncUp 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: SyncUp runs in Atlassian's secure Forge environment with tenant isolation and sandboxed execution.
  • No External Communication: Unlike many apps, SyncUp 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 metrics are persisted, never the issue content itself.

8. Data Sharing

We do not share your data with any third parties. Since SyncUp 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.

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 metrics, uninstalling SyncUp 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

SyncUp requests the following Atlassian API scopes and their justification:

Permission Why It's Needed
read:jira-work Read issues, statuses, and assignments for brief generation
read:sprint:jira-software Access sprint data for autopsy and velocity tracking
read:board-scope:jira-software Identify active boards and their sprints
read:issue-details:jira Access issue metadata for analysis
read:project:jira List projects for report organization
read:user:jira Identify current user for role-based briefs

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: