BevelpineApps

View My GitHub Profile

Data Processing Addendum — Bevelpine Apps

Last updated: 15 September 2026

This Data Processing Addendum (“DPA”) forms part of the agreement under which a customer (“Customer”) uses an app listed in Annex 1 (“App”) obtained through the Atlassian Marketplace (“Agreement”), including the end user agreement shown on the App’s Marketplace listing. It is between Customer and Ben Yamazaki Bosworth, an individual sole trader established in the United Kingdom and trading as Bevelpine Apps (“Bevelpine Apps”, “we”). If the DPA and the Agreement conflict on the processing of personal data, the DPA prevails.

This DPA applies only to the Apps listed in Annex 1, which are Atlassian Marketplace apps built on Atlassian’s Forge platform. It does not apply to any other product or service of Bevelpine Apps, including any Shopify app.

It applies automatically while Customer has an App installed. No signature is needed.

1. Definitions

“Data Protection Laws” means the laws that apply to the processing of Customer Personal Data under the Agreement. Depending on the case, that includes the EU General Data Protection Regulation 2016/679 (“GDPR”), the UK GDPR and Data Protection Act 2018, and the California Consumer Privacy Act as amended by the California Privacy Rights Act (“CCPA”).

“Customer Personal Data” means the personal data the App processes on Customer’s behalf, as described in Annex 1.

“Controller”, “processor”, “data subject”, “personal data breach” and “processing” have the meanings given in the GDPR. “Business”, “service provider”, “sell” and “share” have the meanings given in the CCPA.

“Sub-processor” means a third party we engage that processes Customer Personal Data.

2. Roles and scope

2.1 For Customer Personal Data, Customer is the controller (under the CCPA, the business) and Bevelpine Apps is the processor (under the CCPA, the service provider).

2.2 Each App runs on Atlassian’s Forge platform, on Atlassian’s infrastructure. Bevelpine Apps operates no servers of its own for these Apps, and no App sends Customer Personal Data to Bevelpine Apps or to any other destination outside Atlassian. The App’s code processes the data inside Atlassian’s platform, for Customer’s Atlassian site, as described in Annex 1.

2.3 App logs. Atlassian lets a site administrator share an App’s logs with the App’s developer. The setting is shown as “Logs access” on the App’s page under Connected apps. While it is on, we can read up to 60 days of that App’s log output for Customer’s site. What those logs contain:

Customer can turn “Logs access” off at any time. We use any log output only to support and fix the App.

2.4 This DPA does not cover the relationship between Customer and Atlassian. Atlassian’s own terms and Data Processing Addendum govern that.

3. Processing on instructions

3.1 We process Customer Personal Data only on Customer’s documented instructions. Those instructions are: the Agreement; this DPA; and Customer’s configuration and use of the App. The only exception is where the law requires otherwise. In that case we will tell Customer before processing, unless that law prohibits it.

3.2 We will tell Customer if we believe an instruction breaks Data Protection Laws.

3.3 Annex 1 sets out the subject matter, duration, nature and purpose of the processing, and the types of personal data and categories of data subjects.

4. Confidentiality

Everyone we authorise to process Customer Personal Data is bound by confidentiality.

5. Security

We maintain the technical and organisational measures described in Annex 2. Their purpose is to protect Customer Personal Data against accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access.

6. Sub-processors

6.1 Customer authorises the Sub-processor listed in Annex 3.

6.2 We will not add or replace a Sub-processor without first updating Annex 3 on this page, at least 30 days before the change takes effect. Customer may object on reasonable data-protection grounds within that period. If we cannot resolve the objection, Customer may stop using the affected App and uninstall it.

6.3 Where we engage a Sub-processor, we will impose data-protection obligations on it that are no less protective than this DPA, to the extent the Sub-processor’s standard terms allow. We remain responsible to Customer for its performance.

7. Assistance

7.1 Data subject requests. Every App keeps its data inside Customer’s Atlassian site (Annex 1), so Customer and Customer’s administrators can act on most requests directly. If we receive a request relating to Customer Personal Data, we will pass it to Customer and not answer it ourselves unless Customer instructs us to. Taking into account the nature of the processing, we will reasonably assist Customer in responding to data subject requests.

7.2 Other assistance. Taking into account the information available to us, we will reasonably assist Customer with its obligations on:

8. Personal data breaches

We will notify Customer without undue delay after becoming aware of a personal data breach affecting Customer Personal Data. The notice will contain the information then reasonably available to us. We will notify the contact address Customer gives us, or the technical contact Atlassian holds for the installation.

9. Deletion and return

9.1 Customer Personal Data stored by an App is held in Atlassian’s Forge hosted storage for Customer’s installation. When Customer uninstalls the App, that stored data is deleted by Atlassian under Atlassian’s data lifecycle for Forge hosted storage, which first soft-deletes it and then retains it for the rest of the retention period Atlassian sets out.

9.2 Where an App provides a way to delete stored records, Customer can delete them using the App itself. Annex 1 states, for each App, what can be deleted and when.

9.3 Bevelpine Apps holds no separate copy that would need to be returned or deleted.

10. Audits and information

10.1 On written request, we will make available the information reasonably necessary to demonstrate compliance with this DPA. That includes this DPA, the App’s privacy policy, and the answers in the App’s Marketplace Privacy & Security tab.

10.2 Bevelpine Apps operates no infrastructure for these Apps. For the hosting environment, we rely on Atlassian’s own security reports and certifications. An audit or inspection under Article 28(3)(h) GDPR is therefore limited to our own records and practices. It will be carried out on reasonable notice, at Customer’s cost, and no more than once a year unless a supervisory authority requires otherwise.

11. International transfers

No App’s code sends Customer Personal Data to Bevelpine Apps (section 2.2). The only route by which App-related data reaches us is the App logs described in section 2.3, which are shared only if Customer allows it and which our Apps’ code keeps free of Customer Personal Data. Unhandled error text, as section 2.3 describes, is not under our control and could in principle contain personal data. Where that happens we use it only to diagnose and fix the App, and we keep no copy of it. Customer Personal Data is stored and processed on Atlassian’s infrastructure. Where it is located, and what transfer mechanisms apply, is governed by Atlassian’s terms and Data Processing Addendum and by Customer’s data residency settings with Atlassian. If we ever need to receive Customer Personal Data in a way that is a restricted transfer, we will first put in place an appropriate transfer mechanism, such as the European Commission’s Standard Contractual Clauses and the UK Addendum to them, and update this DPA.

12. CCPA service-provider terms

Where the CCPA applies, Bevelpine Apps:

We certify that we understand and will comply with these restrictions.

13. Term, liability and changes

13.1 This DPA lasts as long as we process Customer Personal Data for Customer.

13.2 Liability under this DPA is subject to the limitations and exclusions of the Agreement, to the extent Data Protection Laws allow.

13.3 We may update this DPA to reflect changes in law or in the Apps. We will post the updated version on this page with a new “Last updated” date. A change that reduces the protection given to Customer Personal Data applies only after the 30-day notice period described in section 6.2.


Annex 1 — Details of processing

Applies to every App below:

App Personal data stored Personal data read and displayed, not stored Data subjects Stored data is deleted
Label Colors for Jira For each label given a colour: the label name, chosen colour, time set, and the Atlassian account ID of the administrator who set it An issue’s labels, when the issue panel loads Jira administrators who set colours When an administrator removes the colour in the App, or on uninstall
Initiative Timeline for Jira Per initiative: name, start and end dates, linked Jira issue keys, created and last-updated times, and the Atlassian account IDs of the creator and last editor. One migration record (time, counts) Issue summaries and statuses, when the page loads Jira users who create or edit initiatives An initiative: when its creator or a Jira administrator deletes it in the App. Everything: on uninstall
User Access Audit for Jira None. No storage permission. The App’s server-side code only checks the App’s licence and receives no site data Site account list, groups and members, product access: display name, account ID, and email address where Jira returns it. Read with the signed-in user’s own permissions and shown in the user’s browser. A CSV is created in the browser only if the user downloads it Accounts on Customer’s Jira site Nothing stored. A downloaded CSV is under Customer’s control
Bulk Excel & CSV Exporter for Jira None. No storage permission. The App’s server-side code only checks the App’s licence Issue data the user chooses to export, read with the user’s own Jira permissions. The export file is created in the user’s browser when the user downloads it People named in exported issues Nothing stored. A downloaded file is under Customer’s control
Hide from Export for Confluence None. No storage and no Atlassian permissions The content an author places inside the App’s macro, which Confluence passes to the App to show on the page. When the page is exported, the App returns nothing in its place People named in that content Nothing stored
Read Receipts for Confluence Per acknowledgement: reader’s Atlassian account ID, page ID, time of the click. Per configured page: whether acknowledgement is required, account IDs of people asked to acknowledge, account ID of the person managing the setting Names, rendered by Confluence from account IDs at display time Confluence users who acknowledge, are asked to, or manage the setting Kept while installed (compliance records, never edited). On uninstall, under section 9

Annex 2 — Technical and organisational measures

Annex 3 — Sub-processors

Sub-processor Service Location
Atlassian (Atlassian Pty Ltd and its affiliates) Forge platform: app hosting, compute and hosted storage As set by Atlassian’s terms and Customer’s data residency settings

Contact

bevelpine.support@proton.me