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.
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:
Important: SyncUp does not modify your team's issues, comments, or workflows. It reads your boards, sprints and issues. The one thing it writes is a single internal issue of its own, which Jira uses to deliver the email briefings - nothing else is created, changed or deleted.
Important: Your Jira data never leaves Atlassian. SyncUp runs on the Atlassian Forge platform, and your issues, sprint names, comments and team members' names are processed there and sent nowhere else. The only thing SyncUp sends outside Atlassian is product-usage analytics, described under Product analytics.
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 or machine learning is used in the analysis, and your sprint and issue data is not sent to any service outside Atlassian.
SyncUp runs on Atlassian's Forge platform. The following Forge services are used:
| 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.
We use the data we access exclusively for:
We do not sell, rent or share your Jira data, and we do not use it for advertising, marketing or profiling. The product-usage analytics described below carries no Jira data and nothing that identifies a person.
To understand how SyncUp is used and improve it, the app sends product-usage analytics to an analytics tool on Atlassian's pre-approved Runs on Atlassian allowlist, named in Sub-processors below: which screens and features are used, marked with your site so installs can be told apart, never with a person. We never send issue data, sprint names, team members' names, email addresses or account ids.
Your Atlassian administrator can turn it off in Atlassian Administration (Connected apps, then SyncUp), and SyncUp keeps working normally.
SyncUp uses two sub-processors:
No other sub-processor or external service handles your Jira data.
We implement industry-standard security measures:
We do not share your Jira data with any third party. The only data SyncUp sends outside Atlassian is the product-usage analytics described under Product analytics, which carries no Jira data and nothing that identifies a person.
The only exception: We may disclose data when required by law, legal process, or to protect our rights or the safety of users.
In accordance with applicable data protection laws (including GDPR), you have the right to:
To exercise any of these rights, please contact us at support@bytera.tech.
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 |
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.
For any privacy-related questions, data requests, or security concerns: