Privacy
Last updated: 16 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. When a request page opens, it reads some personal data through Atlassian's APIs, such as the viewer's account ID and the assignee's name, to decide what to show. It shows only what the administrator switched on, and keeps none of that data afterwards. It stores only the administrator's settings and writes short technical logs at Atlassian. If you email us for support, we receive what you send. Nothing goes to any other service, and nothing is sold.
Who we are and who is responsible
Portal Request View Plus ("the App") is a Forge app for Jira Service Management Cloud. It is made by Rishabh Chulet, an independent developer (sole proprietor) in Madhya Pradesh, India, trading as Creet ("the Developer", "we", "us"). We are responsible for the App and for this policy.
The organisation that installs the App on its Atlassian site is "the Customer". The people who use the Customer's help centre are "portal users". The Customer decides what goes into its Jira site and which items the App shows. Atlassian hosts the site and the App.
- For data inside the Customer's Jira site, we act only on the Customer's instructions, given through the App's settings.
- We decide how support emails sent to us are used.
What the App does
It adds a panel to request pages in the Customer's help centre. For each request type, a Jira administrator chooses what the panel shows: the assignee's display name, the request's service targets (SLAs), linked requests, and read-only fields the administrator selects. Nothing is shown for a request type until an administrator switches it on.
Personal data the App handles, and why
The App reads data through Atlassian's APIs only when a request page or the settings page is opened. It uses that data to build that one panel or page, and keeps none of it afterwards (see "Processed, not kept" below).
- The viewer's account ID and account type (for example "customer" or "agent"). Atlassian provides these with each panel load. Why: to ask Jira, as the viewer, whether they may open the request, and to refuse logged-out visitors. They are not sent to the browser.
- The request as the viewer sees it, from Jira Service Management: its key, request type and reporter, including the reporter's account ID. Why: to confirm the viewer may see the request before anything else is read. The reporter is not shown in the panel.
- The assignee's display name, if the administrator switched it on. Why: to show who is working on the request. Account IDs, email addresses and avatars are dropped on the server and never sent to the browser.
- Values of the fields the administrator selected. These can include people's display names (for user-picker fields) or anything that people typed into those fields. Why: to show those fields. Only the selected fields are read.
- Linked requests (key, summary, status and link type) and service targets (name, state and remaining time), if switched on. Why: to show them. A linked request's key and summary are shown only to a viewer who can open that request, which the App checks with Jira Service Management as that viewer. For other linked requests the viewer sees nothing, or only the link type and status if the administrator chose that.
- The viewer's customer organizations. These are read only when the administrator limited the panel, or part of it, to certain organizations. Why: to decide which parts this viewer may see.
- On the settings page (Jira administrators only): whether the current user is a Jira administrator, plus the site's service projects, request types, fields, link types and customer organization names. Why: to let an administrator choose what to show.
The App never reads comments, worklogs, attachments, time tracking, watchers, votes or security levels, and an administrator cannot switch them on. Portal users see only what the administrator switched on, and only on requests they can already open.
Processed, not kept
All of the data above is handled in memory while one panel or the settings page is built. Then it is discarded. The App does not copy, cache or store requests, names, account IDs, organization memberships or field values. Forge may briefly cache a panel's response for up to about five minutes to avoid repeat calls. That cache is held by Atlassian, inside the Customer's site.
What the App stores
Only the administrator's settings. For each request type, these are:
- which items are switched on
- which fields and link types are selected
- the labels and headings the administrator typed
- the ID numbers of any customer organizations chosen as an audience
The settings are not about any person, and they include no request content. Do not type personal data into labels or headings.
Logs
To find and fix errors, the App writes one short technical entry each time it runs. Entries go to Atlassian's Forge logging service. Each entry holds:
- the event name
- the request key (for example "HELP-42") and request type ID
- the viewer's account type and whether the viewer check passed
- whether organization rules applied
- which data source answered, with its HTTP status
- counts of items shown, and timings
- on an error, the error message, cut to 300 characters
A request key does not name anyone. It can be linked to a person by someone who can open that request in the Customer's Jira site, so we treat logs as personal data. Logs never contain field values, summaries, names, email addresses, account IDs or organization names.
Atlassian keeps Forge logs for a limited period set by Atlassian, and we keep no copy of our own. We can read logs from the Customer's site only if the Customer's administrator allows log sharing with app developers in Atlassian administration. We use them only to give support and fix errors.
Support emails
If you write to support@creet.in, we receive your name, email address and whatever you include, such as your site URL and screenshots. We use it only to answer you and to fix the problem you report.
Mail to creet.in is forwarded by our domain provider, Spaceship, to a Google Gmail mailbox. It is therefore processed by those two companies, possibly outside India, under their own privacy policies. Please do not send your customers' request contents or personal data unless we ask for them to fix a problem.
Where data is kept
- Settings and logs: on Atlassian's Forge platform, for the Customer's site, in locations chosen by Atlassian.
- Data the App reads: handled only inside Forge while one page is built, as above.
- Support emails: in our mailbox, as described above.
We run no servers or databases of our own.
Sharing
We do not sell, rent or share personal data. We do not use it for advertising, analytics, profiling or AI training. The App declares no external network access, so it cannot send data to any server other than Atlassian's own APIs. The only other parties involved are:
- Atlassian: hosts and runs the App, its storage and its logs. Atlassian also processes installation, billing and Marketplace accounts under its own terms and privacy policy.
- Spaceship and Google: carry and store support email, as described above.
We may disclose information if the law requires it, and we will tell the Customer about it where the law allows.
Retention and deletion
- Data the App reads: not kept. It is gone once the page is built, or when Forge's short cache expires.
- Settings: kept in the App's storage while the App is installed. An administrator can change or clear them at any time. When the Customer uninstalls the App, Atlassian deletes the App's stored data under its rules for Forge apps.
- Logs: deleted automatically by Atlassian at the end of its Forge log retention period.
- Support emails: kept for up to 24 months after the last message in a conversation, then deleted. We delete them sooner if you ask.
Your rights
Depending on where you live, data protection law may give you rights, such as the GDPR in Europe and the UK or India's Digital Personal Data Protection Act. These can include the right to access, correct or delete personal data, to object to or restrict its use, to receive a copy, and to complain to a data protection authority.
- Data in a Jira site, such as requests, names and field values: the App keeps none of it. Contact the organisation that runs the help centre, which controls that data in Jira.
- Logs or support emails: write to support@creet.in. We reply within 30 days, and may first ask you to confirm who you are.
Security
How we protect the App and how to report a problem are described in our security policy.
Children
The App is a business tool for Jira Service Management and is not directed at children.
This website
This policy covers the App. The creet.in website, including this page, uses Google Analytics to count visits and see where visitors come from. Analytics cookies are off by default for visitors in the EEA, the UK and Switzerland, and nothing from the website is used for advertising. See the website privacy notice.
Changes
We update this page, with a new date, before releasing any version of the App that handles personal data differently.
Privacy contact
Rishabh Chulet (Creet)
Madhya Pradesh, India
Email: support@creet.in (put "Privacy" in the subject)