Security and data handling: Kayabyte apps for Jira and Confluence
This page states, per app, where data lives, what is stored, which Atlassian permissions the app asks for and why. It matches each app’s manifest and privacy policy. If the two ever differ, tell us at support@kayabyte.dev and we will fix the page.
The short version
- Built on Atlassian Forge. Code runs on Atlassian’s infrastructure and data sits in Forge hosted storage on your own Atlassian site. Data residency follows your site’s Atlassian data residency.
- No data sent to Kayabyte or anyone else. Group Participants, Group Watchers and Personal WIP Limits make no calls to servers outside Atlassian. Burnrate makes none either, unless an admin turns on the optional Tempo import (see below).
- No outside subprocessors. Atlassian is the only one: it hosts the apps, the storage and the logs.
- Deleted on uninstall. When an app is uninstalled, Atlassian deletes its Forge storage under its Forge data retention rules. We can confirm deletion on request.
- Account closures respected. Apps that store Atlassian account IDs report them to Atlassian’s personal data reporting service every week and drop accounts that Atlassian reports as closed.
- Logs. Apps write operational logs on the Forge platform only (error types, status codes, counts and IDs, not names or content). Atlassian keeps them under its Forge log retention rules.
- GDPR. We are based in Norway and treat the GDPR as the baseline. For the data our apps process on your site we act as a processor. Each app’s privacy policy is linked below.
Group Participants
- Stored (Forge storage): project settings (project ID, request type IDs, group IDs and names, on/off switches), the result of the last sync (time and counts) and a snapshot of each rule’s group members as Atlassian account IDs. Not stored: names, email addresses, request content.
- Outside Atlassian: nothing.
- Permissions:
read:jira-work,read:jira-user,read:group:jira,read:user:jira,read:avatar:jira(read groups, members and the people picker);read:servicedesk-requestandwrite:servicedesk-request(read request participants and add or remove participants);storage:app(Forge storage);report:personal-data(weekly personal data reporting).
Group Watchers
- Stored (Forge storage): rules (group IDs and names, space key and name or page ID and title), for each space or page the account IDs of group members with a short state (added by the app, already watching, unwatched, cannot see the page) and counts from the last sync. Not stored: names, email addresses, page content.
- Outside Atlassian: nothing.
- Permissions:
read:confluence-user,read:confluence-groups(read groups and members);read:space:confluence,read:page:confluence,search:confluence(find spaces and pages and check who can see them);read:watcher:confluence,write:watcher:confluence(read, add and remove the watches the app made);storage:app;report:personal-data.
Personal WIP Limits
- Stored (Forge storage): settings only: whether checks are on, the limit, how work is counted, project limits (project ID, key, name) and exempt groups (ID, name). Not stored: work items, account IDs, names, email addresses.
- Outside Atlassian: nothing. The optional Rovo agent runs on Atlassian too.
- Permissions:
read:jira-work(count work in progress per assignee),read:jira-user(assignee names and groups),storage:app.
Burnrate
- Stored (Forge storage): worklog copies (ID, work item ID, author account ID, date, time, calculated cost; comments are not stored), basic fields of work items with logged time, the rate card, budgets and settings. Names, email addresses and avatars are not stored. Costs are only shown to people with the app’s view or manage permission, and the rate card and cost per person only with the manage permission.
- Outside Atlassian: only if an admin connects Tempo
Timesheets. Then the app reads worklogs from
api.tempo.io,api.eu.tempo.ioorapi.us.tempo.iowith the admin’s Tempo API token, kept in Forge secret storage. The app only reads from Tempo; it sends nothing to Tempo, to Kayabyte or to anyone else. Because of this optional connection, Burnrate does not carry Atlassian’s Runs on Atlassian badge; the other three apps do. - Permissions:
read:jira-work(work items and worklogs),read:jira-user(account details for display),storage:app,report:personal-data; external fetch only to the three Tempo addresses above.
Report a security issue
Email support@kayabyte.dev with the app name, what you found and how to reproduce it. A person from our team reads it and replies within one business day (Monday to Friday, Central European Time). Please do not include customer data or credentials, and give us reasonable time to fix an issue before you publish it. We do not run a paid bug bounty programme.
What we do not claim
We hold no compliance certifications such as SOC 2 or ISO 27001, and we have not completed a CAIQ Lite questionnaire. Our security rests on Atlassian’s platform, on asking for the fewest permissions that each app needs, and on storing as little as possible.
See also: support, all products, Jira and Confluence guides.
Jira, Confluence, Forge and Atlassian are trademarks of Atlassian. Kayabyte is an independent developer and is not affiliated with or endorsed by Atlassian.