Tsutsei Software

Atlassian apps/Customer Profiles/Security

Security policy

Last updated: 9 November 2026

This policy applies to the Atlassian Marketplace app Customer Profiles for Jira Service Management (the "App"), provided by Tsutsei Software, a brand of the sole trader identified on the Legal information page ("we").

Reporting a vulnerability

Send security issues to security@tsutsei-support.atlassian.net. Every message creates a tracked request in our support system. Please include the app, your site URL, steps to reproduce and the impact you expect. Do not include passwords, API tokens or customer data.

We confirm receipt within 2 business days, keep you informed about the fix and credit you in the release notes if you wish. Please give us reasonable time to release a fix before disclosing the issue publicly.

Architecture

  • The App runs entirely on Atlassian Forge ("Runs on Atlassian"): Forge functions, the Forge key-value store and Custom UI. No Forge Remote, no egress to external servers, no vendor-side servers or copies of customer data.
  • The App stores only its settings in each customer's Forge storage, encrypted at rest and in transit by Atlassian. It stores no customer or organization data.
  • Jira Service Management data is read with the signed-in user's permissions in the browser; exports and imports are processed there. The only writes are made by the import after the user confirms a preview: detail field values (which can be undone) and, when chosen, new organizations and customers added to organizations and service projects. Nothing is ever deleted.
  • The App requests only the scopes its features need and never asks for passwords or API tokens.
  • The App does not use AI or machine-learning models, and no customer data is processed by such models.

Secure development

  • All data is read and written as the signed-in user, so the App shows and changes only what the user may.
  • Settings are validated (field name formats, limits, threshold ranges) and only Jira administrators can save them; all text reaches the page as plain text; imported files are size-limited and parsed as data only; exports guard against spreadsheet formula injection.
  • Logs contain IDs and error messages only, never field values. Access to logs is limited to the developer (Forge developer console).
  • Every change passes automated unit and end-to-end tests (including permission checks) before it is deployed to production.
  • Dependencies are checked with npm audit before every release; known vulnerabilities are fixed before deploying.

Access control

  • Source code is in private GitHub repositories; GitHub and Atlassian accounts are protected with two-factor authentication.
  • The developer workstation uses full-disk encryption, automatic operating system and security updates, a firewall and malware protection. Unsupported operating system versions are not used.
  • Access to source code, the Forge developer console, the Marketplace partner account and the support site is reviewed every quarter.

Fixing vulnerabilities

Vulnerabilities are scored with CVSS and fixed within the deadlines of the Atlassian Marketplace security bug fix policy:

Severity CVSS Fix released within
Critical 9.0 – 10.0 10 days
High 7.0 – 8.9 4 weeks
Medium 4.0 – 6.9 12 weeks
Low 0.1 – 3.9 25 weeks

Forge deployments reach all installations within minutes, so customers do not need to update the App.

Security incidents

If a security incident may affect customer data, we report it to Atlassian within 24 hours and notify the admins of affected sites within 72 hours where possible. As a data processor under the GDPR, we inform controllers without undue delay. See also the privacy policy and the Data Processing Addendum.