UtilityStack Labs / Approval Reports DPA Details
Bonterms DPA Details for Approval Reports
Adopted for Marketplace version 4.3.0. These Details and the Additional Term below are expressly incorporated into this app's Provider-Specific Terms alongside the Bonterms Standard End User Agreement v1.0. The DPA applies to Customer Personal Data processed by Provider as a processor under an applicable Customer Order; publication of this page alone does not create an Order or make the DPA effective for a prospective Customer.
These Details accompany the Bonterms Data Protection Addendum v2.0 (Attachment Version) incorporated into this app's customer-provider Main Agreement.
Main Agreement, parties and dates
Main Agreement: the Bonterms Standard End User Agreement v1.0 between the Customer placing an Atlassian Marketplace Order for Approval Reports and the Provider. The Main Agreement date and DPA Effective Date for an applicable Customer are the date of that Customer's first Order for this app under Section 1.2, with the DPA and these Details incorporated in Provider-Specific Terms applicable to the Order.
Customer / data exporter: the organization or person placing that Order. Its name, address and notice contact are identified by its Order/Marketplace account or later designated contact. It operates the Jira Service Management site and directs its users' reports. Its role is controller or processor as applicable to its personal data.
Provider / data importer: Nathan Charles Acree, sole proprietor using UtilityStack Labs as an informal brand, not a separate legal entity or registered DBA. Business/legal notice address: 1 Xebec Rd, Palmyra, VA 22963, United States. Data-protection/legal contact: privacy@utilitystacklabs.com; security-incident contact: security@utilitystacklabs.com. Provider acts as processor for Customer-directed report processing.
EU SCC elections: Ireland for Clause 17 governing law and Ireland as the designated EU Member State for Clause 18 courts. The competent supervisory authority is determined for the actual transfer under Clause 13. Bonterms Exhibit A supplies applicable Module 2 or 3, UK Addendum and Swiss modifications. No Data Privacy Framework certification or fixed data-residency guarantee is claimed.
Processing details
Service, subject matter and purpose: on demand, use the signed-in user's Jira permissions to find requests in one selected Jira Service Management project and bounded created-date range; retrieve native approval stages and approver decisions for those requests; display the report; and allow a CSV after a complete scan. The app is read-only and does not maintain a permanent approval ledger or app report database.
Data subjects: users, employees/other personnel, Customer business contacts, and other people identifiable in Customer-controlled request summaries or approval metadata, as applicable. Customer Personal Data: approver account IDs/display names and decisions; request summaries and keys; service-project identifiers/names; approval-stage IDs, names, decisions and stage timestamps; request creation dates/links; site URL and report filters. Data categories include account information, user-generated content, unique identifiers and associated metadata. The app does not request issue descriptions, comments or attachments for reports.
Sensitive/special-category data: None/Not Applicable for the Service's intended scope. Such data is not sought or needed; Main Agreement Section 7.2 prohibits Customer submission of Sensitive Data. This does not guarantee that a Customer-controlled request summary can never contain sensitive information contrary to intended use.
Frequency: on demand when a user runs a report, not continuous. Nature/purpose: permission-scoped read, transient handling/display and Customer-directed CSV generation to provide the Service under Customer Instructions. Duration: an active report session and provision of Service under the Main Agreement, with end-of-processing treatment under DPA Section 8. The Customer controls downloaded CSVs. Atlassian platform logs and publisher-controlled support/Marketplace records are described separately in the privacy policy.
Subprocessors, notices and security
Provider Subprocessor List and transfers: Atlassian Pty Ltd (Australia) for Forge hosting/compute and Jira Service Management API delivery of the report. Atlassian's current subprocessor list identifies downstream providers, functions and processing locations. Its corporate address does not mean all processing occurs in Australia. GitHub Pages hosts public documentation, not customer reports. There is no external report-data backend or app report storage.
Subprocessor Notice Method: email to the Customer's Marketplace Order, billing or technical administrator contact, or a replacement data-protection contact designated to Provider. Provider maintains its subscription to Atlassian's subprocessor-change notices. Customer notice delivery for this app has not yet been exercised.
Technical and organizational measures: Atlassian-hosted Forge and Jira authentication; signed-in-user API calls; only read:jira-work and read:servicedesk-request; no external report backend/storage; validation of project/date/request keys and cursors; bounded pagination; no CSV on incomplete scans; validation of the HTTPS Jira site origin supplied by Forge context for request links; text-only rendering; CSV formula neutralization; and no intentional logging of report rows, filters or credentials by app code. Atlassian's own platform measures are described in its published Forge materials. No separate certification or deletion-automation claim is made.
Additional Term
Solely for a new or replacement downstream subprocessor engaged by Atlassian Pty Ltd in providing Forge for the Service, and not engaged directly by Provider, Section 4.3's 30-day advance-notice minimum is replaced with a 7-calendar-day advance-notice minimum. Provider will maintain its subscription to Atlassian's subprocessor-change notices and notify affected Customers by the Subprocessor Notice Method as soon as reasonably practicable after receiving Atlassian's applicable notice and, in all cases, at least 7 calendar days before that downstream subprocessor begins Processing Customer Personal Data. For those Atlassian-controlled downstream changes only, the period in Section 4.4(a) for Customer to object in writing on reasonable data-protection grounds is 7 calendar days after Customer receives Provider's notice. Section 4.3's 30-day advance-notice period and Section 4.4(a)'s 30-day objection period remain unchanged for Subprocessors engaged directly by Provider. Section 4.4(b)'s resolution and termination remedy and the DPA's 48-hour Specified Notice Period for Security Incidents remain unchanged. This term does not limit mandatory EU Standard Contractual Clause, UK or Swiss rights or their precedence under the DPA.
The 7-day customer advance notice is a firm Provider commitment for the Atlassian-controlled downstream Forge changes described above. Operational delivery has not been tested with a production Customer.