Portal SLA Clocks runs entirely on Atlassian Forge. It has no remote back end and makes no calls outside your Jira site.
On the portal, the app first checks that the person viewing a request can open it. For customers it calls GET /rest/servicedeskapi/request/{key} as that customer. For portal users without a customer account it calls the same endpoint and GET /rest/servicedeskapi/request/{key}/participant as the app, and compares the reporter and participant account IDs with the viewer's. It then reads GET /rest/servicedeskapi/request/{key}/sla as the app and passes on only the SLAs a project admin picked.
On the settings page it calls GET /rest/api/3/mypermissions to check admin rights, GET /rest/servicedeskapi/servicedesk/projectId:{id} to find the service desk, and GET /rest/api/3/field to list SLA names. All three run as the admin.
| Record | Contents | Kept for |
|---|---|---|
| Project settings | SLA names, the names customers see, and three on/off choices, keyed by service desk ID | Until changed or the app is uninstalled |
That's the only record. SLA times, request details, reporter and participant IDs are used during the page load and then dropped. No names, email addresses or account IDs are stored.
It has no scope that writes to Jira. It doesn't send data to the developer or to any third party, and it doesn't use analytics or tracking.
Uninstalling the app removes its Forge storage.