Security
This covers every frajdata app. Each app's own section below says where its data lives and which permissions it asks for, and why.
How the apps are built
- Apps act as the person using them, so the permissions you already set in your tool still apply.
- Every request from an app's screens is checked and size-limited in the back end, and the subscription is checked there too.
- The apps hold no passwords, tokens or keys of their own.
- Every commit is scanned for secrets. Dependencies are pinned, reviewed before they are added, and audited for known vulnerabilities before code is pushed.
Report a vulnerability
Email security@frajdata.com with what you found, the steps to reproduce it, and the app and version. Please don't test against sites you don't own, and don't access or change other people's data.
We confirm receipt within two business days, keep you informed while we fix it, and credit you when the fix ships if you'd like. For Atlassian apps, Atlassian's Marketplace security bug fix policy sets the deadlines we work to.
Epic Templates for Jira
Where your data lives
The app runs on Atlassian Forge. What it stores, your templates and short reports of each creation, sits in your Jira site's own Forge app storage, inside Atlassian's cloud. It makes no calls outside Atlassian and sends your data nowhere else. frajdata has no servers for this app and no copy of your data.
Who can do what
Work items are read and created as the person using the app, so Jira's own permissions and security levels apply. A template is visible only to people who can see the project it was saved in, and only that project's administrators or Jira administrators can rename or delete it.
Permissions it asks for
- Read Jira work (
read:jira-work). Read an epic and its children when you save a template, and check which projects you can see and administer. - Write Jira work (
write:jira-work). Create the epic and its children when you use a template. - Rank work items (
write:issue:jira-software). Put the new children in the template's order. Jira refuses ordering without it. - App storage (
storage:app). Keep templates, and short reports of each creation for one day.
Creating a large epic can take a few minutes, so it runs in the background, and the three Jira permissions are marked to act as the person who asked. The app never acts as anyone else.