Skip to content
Creet / Portal Request View Plus
Overview Help Terms Privacy Security

Security

Last updated: 6 November 2026. Applies to Portal Request View Plus for Jira Service Management Cloud.

In short: Portal Request View Plus runs only on Atlassian's Forge platform. It has no servers, database or network access of its own. Before it reads anything, it checks with Jira, as the viewer, that the viewer may open the request. It shows only what a Jira administrator switched on. Report a security problem to support@creet.in.

Scope

This policy covers Portal Request View Plus ("the App"), a Forge app made by Rishabh Chulet, an independent developer in India trading as Creet ("we", "us"). How the App handles personal data is described in the privacy policy.

Hosting

  • The App is hosted on Atlassian's Forge platform. Its code runs on Atlassian's infrastructure, and its settings are kept in Forge storage for each Jira site where it is installed. Atlassian runs, patches and secures that infrastructure under its own security program. See Atlassian's Trust Center.
  • We run no servers, databases, file stores or third-party services for the App.
  • The App declares no external network access, remote backends or web triggers. Forge therefore lets it call only Atlassian's own APIs, so it cannot send data anywhere else.
  • Each installation's storage is separate, and one customer's site cannot read another's.

Access controls

Inside the App.

  • The viewer is checked first. Before the App reads anything with its own permissions, it makes two calls as the viewer. Jira confirms the viewer may browse the request, and Jira Service Management returns the request as the viewer would see it. If either check fails, the App reads nothing else and shows nothing.
  • Trusted identity only. The request and the viewer's identity come from Atlassian's signed context, never from the browser. The portal panel sends no parameters the server would trust.
  • Off by default. Nothing is shown for a request type until a Jira administrator switches items on. Each item has its own switch.
  • Blocked fields. Comments, worklogs, attachments, time tracking, watchers, votes, security levels and a few other fields are on a fixed deny list. An administrator cannot switch them on.
  • Admin functions are separate. The settings page runs in a separate function that the portal panel cannot call. Every change checks with Jira that the person making it is a Jira administrator.
  • Least privilege. The App asks only for the read scopes it uses (read:jira-work, read:servicedesk-request, read:organization:jira-service-management) plus storage:app for its settings. It never asks for write access to Jira data.

Our own access.

  • Only the developer can deploy the App, change its source code or read its logs. No one else has these rights.
  • We have no access to customers' Jira sites or data. We can read the App's logs from a customer's site only if that site's administrator allows log sharing in Atlassian administration.
  • The accounts that can deploy or change the App use unique passwords kept in a password manager. Development machines run endpoint protection and automatic security updates.

Data protection

  • Little is stored. The App stores only the administrator's settings and keeps no copy of requests, names or field values. The privacy policy lists exactly what it reads and stores.
  • Encryption. All traffic between the App, Atlassian's APIs and the browser goes over Atlassian's HTTPS connections. Forge storage is encrypted at rest and backed up by Atlassian.
  • Least data shown. People appear by display name only. Email addresses, account IDs and avatars never reach the browser. Service targets are reduced to their state and remaining time.
  • Caps. List lengths and text lengths are limited, so the panel cannot be used to export data in bulk.
  • Checked input. Settings are checked when they are saved and again when they are loaded. Unknown keys are dropped, field IDs must match Jira's format, and labels are stored as plain text.
  • No secrets. The App holds no API keys, tokens or passwords. Atlassian's platform handles authentication.
  • Safe logs. Logs record technical events only and never contain field values, names, email addresses or account IDs.

Security testing

  • Every release runs about 100 automated tests. They cover the viewer check and the order of calls, the allow-list and deny-list, organization rules that fail closed, and checks that no account ID or email address can reach the output.
  • Every deployment first passes forge lint, which checks the manifest and permissions.
  • Dependencies are checked for known vulnerabilities with npm audit before each release. Vulnerable packages are updated or overridden before the release goes out.
  • Every version submitted to the Atlassian Marketplace is also scanned by Atlassian's automated security tooling.

Reporting a vulnerability

If you think you have found a security problem in the App, email support@creet.in with "Security" in the subject. Include the steps to reproduce it and what an attacker could gain. Please do not include your customers' request contents, and give us a reasonable time to fix the problem before you disclose it publicly.

  • We reply within 2 working days (Monday to Friday, India Standard Time).
  • We rate each confirmed issue by its CVSS score and keep the reporter informed until it is fixed.
  • We will not take action against anyone who reports in good faith, stays within their own Jira site and does not access other people's data.
  • You can also report through Atlassian, which records Marketplace app vulnerabilities in its Atlassian Marketplace Security (AMS) project.

How fast we fix vulnerabilities

We follow Atlassian's Marketplace security bug fix policy for cloud apps. Each period starts when the issue is reported or confirmed:

  • Critical (CVSS 9.0 or more): within 10 days
  • High (7.0 to 8.9): within 4 weeks
  • Medium (4.0 to 6.9): within 12 weeks
  • Low (below 4.0): within 25 weeks

Fixes are deployed through Forge to every installation. Customers do not need to do anything unless a fix needs new permissions, in which case Jira asks an administrator to accept them.

Incident response

A security incident is any actual or suspected unauthorised access to, or use, disclosure, change or loss of, customer data through the App, or any compromise of the App or of the accounts that can deploy it. If one happens, we:

  1. Investigate straight away. We work out what happened, which sites and data are affected, and whether it is still going on.
  2. Contain it. We deploy a fix, switch off the affected feature or ask Atlassian to delist the App, and change the passwords of any exposed accounts.
  3. Notify Atlassian within 24 hours through Atlassian's developer support portal, and keep Atlassian updated until the incident is resolved.
  4. Notify affected customers within 72 hours where possible. We tell them what happened, what data was involved, what we have done and what they should do. We also meet any notification duty the law places on us.
  5. Fix the cause and review. We find the root cause, fix it, add tests so it cannot happen again, and write down what we learned.

Security contact

Rishabh Chulet (Creet)
Madhya Pradesh, India
Email: support@creet.in (put "Security" in the subject)

Changes

We will update this page, with a new date, whenever the way the App is hosted, protected or supported changes.

© 2026 Portal Request View Plus, made by Creet

Help Terms Privacy Security Atlassian Marketplace support@creet.in