UtilityStack Labs / DPA Details

Bonterms DPA Details for Macro Usage Exporter

Adopted for new customer Orders. Provider has incorporated the Bonterms DPA v2.0 and these completed Details, including the Additional Term below, into the saved Provider-Specific Terms for private Marketplace version 2.2.0. The DPA becomes effective between Provider and a Customer when that Customer enters its first Order for this app under the Bonterms Standard End User Agreement. Publication of this page alone does not create a customer agreement.

These Details accompany the Bonterms Data Protection Addendum v2.0 (Attachment Version) for Macro Usage Exporter for Confluence, private Marketplace version 2.2.0. The Bonterms standard text applies only if this Attachment and these Details are expressly incorporated into the customer-provider Main Agreement.

Main Agreement, parties and dates

Main Agreement: the Bonterms Standard End User Agreement v1.0 for this app between the Customer placing the applicable Atlassian Marketplace Order and the Provider below. Main Agreement date and DPA Effective Date: the date of that Customer's first Order for this app, as provided in Main Agreement Section 1.2, when the DPA and these Details are incorporated in the Provider-Specific Terms applicable to that Order.

Customer / data exporter: the organization or person placing that Order. Its legal name, address and account/notice contact are identified by the applicable Order and Marketplace account, or by a later contact it designates to Provider. Its relevant activities are operating the Confluence site and directing its users' reports. Its role is controller or processor, as applicable to the Customer Personal Data and its relationship with its own data subjects.

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 and legal contact: privacy@utilitystacklabs.com; security-incident contact: security@utilitystacklabs.com. Provider acts as processor for Customer-directed report processing.

EU SCC elections: Ireland is the governing law for Clause 17 and Ireland is the designated EU Member State for courts under Clause 18. The competent supervisory authority is determined for the actual transfer under EU SCC Clause 13, rather than named in advance. Bonterms Exhibit A provides the applicable EU SCC Module 2 or 3, UK Addendum and Swiss modifications when their respective transfer rules apply. No Provider Data Privacy Framework certification or fixed data-residency guarantee is claimed.

Processing description

Service, subject matter and purpose: on a signed-in user's request, search Confluence for pages containing one exact macro key, optionally filtered by up to 20 space keys; display matching page-level metadata; and allow CSV export only after the scan completes. This is read-only. The app does not edit pages, schedule scans, request page bodies, use an external report backend, or retain report contents in an app database.

Categories of data subjects (Bonterms selections): Users; Employees and other personnel; Customer's business contacts; and Other people identifiable in Customer-controlled page titles or metadata. No claim is made that every Customer has all of these categories. Categories of Customer Personal Data (Bonterms selections): Account information (transient Confluence account/author metadata); user-generated content (page titles and identifying macro/space search inputs); unique identifiers (page IDs); and Other: space keys, last-updated timestamps, page links and site URL. The app discards account/author metadata rather than including it in report rows or CSV. Customer-controlled titles can contain names or other personal information.

Sensitive/special-category data: None/Not Applicable for the Service's intended scope. Such data is not requested or needed, and Main Agreement Section 7.2 prohibits Customer submission of Sensitive Data to the Cloud Service. This selection does not guarantee that a Customer-controlled page title can never contain sensitive information contrary to intended use.

Frequency of transfer (Bonterms selection): Other — on demand when a user runs a report, not continuous. Nature and purpose: permission-scoped read, transient handling and display, and Customer-directed CSV generation to provide the Service and carry out Customer Instructions. Duration/retention: during an active report session and provision of the Service under the Main Agreement, and thereafter pursuant to Bonterms DPA Section 8. Provider retains no app report database. The Customer controls any downloaded CSV. Platform logs and publisher-controlled support/business records are addressed separately under applicable platform terms and the privacy policy.

Subprocessors, notices and security

Provider Subprocessor List and transfers: Atlassian Pty Ltd (Australia), which receives Customer Personal Data as needed for Forge hosting/compute and Confluence API delivery for the Service. Atlassian's current subprocessor list identifies its downstream providers, functions and processing locations; its corporate location is not a claim that all data is processed in Australia. GitHub Pages hosts public documentation, not Customer report processing. The app has no external report-data egress or app report database.

Subprocessor Notice Method: email to the Customer's Marketplace Order, billing or technical administrator contact, or a replacement data-protection contact the Customer has designated to Provider. Provider has subscribed to Atlassian's subprocessor-change notices. No notice delivery to a production Customer has yet been tested.

Technical and organizational security measures: Atlassian-hosted Forge and Confluence authentication; permission-scoped search as the signed-in user through api.asUser(); only the search:confluence scope; no external report backend or storage; input/CQL and cursor validation; bounded pagination; no CSV for incomplete scans; HTTPS site-URL validation; text-only result rendering; CSV formula neutralization; and no intentional logging of report rows, queries or credentials in app code. Atlassian platform measures are described in its published Forge materials. No separate certification, location, backup 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.

Atlassian's Forge DPA states that subscribed developers receive at least 14 days' upstream notice. The 7-day customer advance notice above is a firm Provider commitment. Delivery has not yet been tested with a production Customer.

Privacy policy · Support