The app runs entirely on Atlassian Forge. It has no servers of its own, makes no outbound network
calls, and keeps all data inside Atlassian's cloud.
Architecture
- Built on Atlassian Forge and eligible for the Runs on Atlassian program.
- No remote backend, no web triggers, and no external network requests.
- Requested scopes are limited to
storage:app, read:jira-work and
write:jira-work — the minimum needed to store templates and create issues.
Data handling
- The only data the app stores is the templates users create (name, project, issue type, summary,
description, labels, sub-task titles and any preset field values).
- Templates never store Atlassian account IDs or any other identifier of a person. A preset
assignee is resolved to the user creating the issue at that moment and is not saved.
- Templates are kept in Forge app storage, scoped to the customer's site installation. Kelvido does
not copy, export or back up customer data anywhere else.
- The app collects no credentials and holds no API keys or secrets.
- The app writes no application logs, so no customer content or personal data is logged.
Encryption
- Data at rest is stored in Atlassian Forge storage, which Atlassian encrypts at rest.
- All traffic between the app, Jira and the user's browser runs over Atlassian's TLS-encrypted
platform connections.
Access control
- Everything a person does in the app is done as that person (
asUser()), so Jira's own
permission checks always apply. The app cannot create or read anything the user could not.
- The one exception is scheduled creation: when a template is set to create issues automatically,
nobody is clicking, so the app creates them with its own identity (
asApp()), limited
to what Jira's project permissions allow apps to do. The reporter of those issues is the app.
- Kelvido's developer and Marketplace accounts are protected with multi-factor authentication.
Secure development
- User input is validated before it is stored: required fields are enforced, labels are sanitised,
and imported JSON is parsed safely and checked before use.
- Jira REST paths are built with Forge's encoding route helper, so user input cannot alter a request
path. Descriptions are sent as Atlassian Document Format text, never as HTML.
- Before every release, dependencies are scanned with
npm audit and the app is checked
with forge lint. A release does not ship while either reports a problem.
- Changes are tested in a separate development environment before they reach production.
Vulnerability management
Reported vulnerabilities are fixed within the Atlassian Marketplace security bug fix policy for cloud apps:
| Severity (CVSS) | Fixed within |
|---|
| Critical (9.0 and above) | 10 days |
| High (7.0 – 8.9) | 4 weeks |
| Medium (4.0 – 6.9) | 12 weeks |
| Low (below 4.0) | 25 weeks |
Customers are notified once a fix for a critical issue is available.
Incident response
- Contain the issue — disable the affected function or roll back the release.
- Notify Atlassian within 24 hours, following Atlassian's app security incident management guidelines.
- Provide updates until the incident is resolved.
- Inform affected customers.
- Record the root cause and the change that prevents it from recurring.
Certifications
Kelvido is a one-person company and does not currently hold third-party security certifications
such as SOC 2 or ISO 27001.
Reporting a security issue
Please email support@kelvido.com with "Security" in the
subject line. We aim to acknowledge reports within one business day.
Documentation · Privacy policy · Terms of service