Legal
Data Processing Addendum
ReleaseProof-specific DPA Details and Additional Terms for B2B customers.
Language and contractual authority
The English contractual text below is authoritative. The German route and German navigation labels are provided for convenience and do not create a separate translated DPA.
1. Status and incorporation
This ReleaseProof Data Processing Addendum (ReleaseProof DPA) provides the ReleaseProof-specific DPA Details and Additional Terms for use with the Bonterms Data Protection Addendum v2.0 (Attachment Version), available at https://bonterms.com/standard/dpa-v2-attachment-version.
If and to the extent SBS Deutschland GmbH & Co. KG processes Customer Personal Data as Processor, this ReleaseProof DPA and the Bonterms Data Protection Addendum v2.0 incorporated by reference here form part of the Main Agreement only when this ReleaseProof DPA is expressly identified and incorporated by the ReleaseProof Provider-Specific Terms or another written agreement applicable to the Customer.
Publication of this page alone does not make this ReleaseProof DPA retroactive. If a Customer's Main Agreement predates valid incorporation of this ReleaseProof DPA, a separately valid incorporation or amendment is required before this ReleaseProof DPA is treated as effective for that Customer.
The English text on this page is the controlling contractual text. Any German-language navigation or explanatory text is provided for convenience only.
2. Main Agreement and DPA Effective Date
Main Agreement: the Agreement formed under the Bonterms Standard End User Agreement applicable to ReleaseProof through the Atlassian Marketplace together with the ReleaseProof Provider-Specific Terms applicable to the Customer's Order.
DPA Effective Date: the Standard Agreement Effective Date for the applicable Customer — the date of that Customer's first Order for ReleaseProof through the Atlassian Marketplace — provided that this final public ReleaseProof DPA is identified in the Provider-Specific Terms applicable to that Order. Otherwise, the DPA Effective Date is the date on which the parties validly incorporate this ReleaseProof DPA by a later written agreement or amendment.
3. Customer details — completion by reference
For purposes of the Bonterms DPA Details, Customer-specific fields are completed by objective reference to the applicable Main Agreement and Marketplace Order.
- Name: the Customer under the Standard Agreement, meaning the party placing the applicable Atlassian Marketplace Order.
- Data protection / notice contact: the Customer's notice address designated under the Main Agreement. If Customer separately supplies a privacy or security contact to Provider, that later-designated contact is used for applicable privacy/security notices.
- Main address: Customer's principal business address associated with the Atlassian customer account through which it places the applicable Order, or a later main address Customer supplies to Provider.
- Customer activities: use of Jira Cloud and ReleaseProof for Customer's business, software-delivery, quality, release-management, or related processes.
- Role: Controller, or Processor to the extent Customer processes the applicable Customer Personal Data on behalf of a third-party Controller.
4. Provider details
Provider / Data Importer: SBS Deutschland GmbH & Co. KG, In der Dell 19, 69469 Weinheim, Germany.
Data protection and security contact: ki@sbsdeutschland.de.
Provider activities: provision and support of ReleaseProof, an Atlassian Forge app for deterministic Jira Cloud release-readiness and evidence analysis.
Role: Processor for the ReleaseProof Customer Jira-data processing path.
5. Subprocessor List
Direct Subprocessor: Atlassian Pty Ltd. Function: provision of the Atlassian Forge platform used by ReleaseProof, including Forge compute, hosted storage, platform security and operations, data-residency capabilities, and related infrastructure.
Atlassian processes End User Personal Data for Forge developers under the Forge Data Processing Addendum. Processing locations, transfer mechanisms, and Atlassian's downstream subprocessors are governed by that DPA and Atlassian's current subprocessor list.
Official Forge DPA information: https://developer.atlassian.com/platform/forge/about-the-forge-data-processing-addendum/.
Current Atlassian subprocessor list: https://www.atlassian.com/legal/sub-processors.
ReleaseProof declares no separate external Forge remote, external product database, generative-AI/LLM provider, or third-party product telemetry provider.
6. Forge-originated Subprocessor changes
For a new Subprocessor introduced through Atlassian Forge (a Forge-originated Subprocessor), Provider will update the Subprocessor List and notify Customer using the Subprocessor Notice Method without undue delay and, under Atlassian's current minimum fourteen (14) day upstream notice period, within two (2) calendar days after Provider receives Atlassian's notice and at least ten (10) calendar days before the stated upstream effective date.
Customer may object on reasonable data-protection grounds within seven (7) calendar days after Provider's notice and in all events before the stated upstream effective date. Provider will consider a timely objection in good faith and use commercially reasonable efforts to identify a lawful alternative that avoids the objected-to processing.
If no such alternative is reasonably available before the Forge-originated Subprocessor begins processing Customer Personal Data, Customer may terminate the affected ReleaseProof Service by uninstalling or otherwise ceasing use of ReleaseProof before that processing begins and by giving Provider written notice.
Provider will not intentionally restore or initiate further ReleaseProof processing for that Customer after termination, subject to the documented Atlassian Forge post-uninstall retention and recovery lifecycle. Uninstallation or cessation of use does not guarantee immediate physical deletion of Forge-retained data and does not override Atlassian-controlled retention or legally required processing during that lifecycle.
This Forge-specific timing replaces the 30-day notice and objection periods in Sections 4.3 and 4.4 of the Bonterms DPA only for Forge-originated Subprocessors. The 30-day defaults remain unchanged for other new Subprocessors.
If Atlassian gives Provider less notice than its then-current documented minimum, Provider will notify Customer without undue delay after receipt and provide the longest practicable pre-change objection period. A material reduction in Atlassian's upstream notice commitment requires Provider to re-evaluate this Additional Term before further reliance on it.
7. Subprocessor Notice Method
For Forge-originated Subprocessor changes, the Subprocessor Notice Method is an in-product notification displayed to ReleaseProof Jira project administrators together with an update to the public ReleaseProof DPA/Subprocessor information. If Customer has separately provided Provider with a privacy or security contact, Provider may also use that contact.
The in-product notice is not a read receipt and does not establish that a specific administrator viewed the notice.
8. Specified Security Incident Notice Period
Provider will notify Customer of a Security Incident without undue delay and no later than 48 calendar hours after SBS Deutschland GmbH & Co. KG becomes aware of the Security Incident, subject to the Bonterms DPA and applicable Data Protection Laws.
The administrator-facing in-product notice surface may supplement an incident communication but does not replace a separately deliverable customer-contact and escalation process for urgent Security Incident notices.
9. Categories of Data Subjects
The following categories apply only to the extent Customer includes their personal data in Jira content that ReleaseProof is configured to process:
- Jira Cloud users whose work or identifiers are represented in in-scope Jira project or release data.
- Customer employees, contractors, and other personnel represented in in-scope Jira records.
- Customer business contacts where Customer places their personal data in in-scope Jira issue content.
- Customer customers or prospective customers where Customer places their personal data in in-scope Jira issue content.
- Other individuals whose personal data Customer includes in Jira fields that ReleaseProof is configured to read.
10. Categories of Customer Personal Data
ReleaseProof may process ordinary personal data to the extent it is contained in Jira data required for the configured analysis.
- Unique identifiers: Jira issue keys and identifiers, project/version identifiers, and field identifiers.
- Professional information: work-related project, issue, status, release, approval, dependency, and workflow information.
- User-generated content: issue summaries and configured acceptance-criteria field content required for ReleaseProof rules.
- Communications or descriptive content only to the extent Customer places such data in the specific Jira fields ReleaseProof reads.
- Configuration data: configured status IDs, issue-type IDs, selected acceptance-criteria field ID, blocker-label values, approval-marker settings/value, release-scope mode, optional project-bound release-scope JQL, and configuration timestamps. These values are intended to contain non-personal technical identifiers only, and Customer must not place personal data in free-text ReleaseProof configuration values.
- Other Customer-provided ordinary personal data only to the extent Customer includes such data in permitted in-scope Jira issue content processed transiently during analysis.
11. Sensitive or Special Categories of Personal Data
None / Not Applicable for permitted use.
ReleaseProof is not designed or permitted for processing Sensitive Data as defined in the Main Agreement, including GDPR Article 9(1) special-category data. Customer must not place Sensitive Data in Jira fields, issue content, labels, JQL values, approval markers, or other content configured or otherwise made in-scope for ReleaseProof.
If Customer discovers Sensitive Data in content that would be processed by ReleaseProof, Customer must remove or redact it before using ReleaseProof for that scope. This ReleaseProof DPA does not provide an Article 9 lawful basis or authorize processing prohibited by the Main Agreement or Atlassian platform terms.
12. Frequency, nature, and purpose of Processing
Frequency: event-driven / on-demand. Processing occurs primarily when an authorized Jira user opens or operates ReleaseProof, when ReleaseProof loads configured Jira project/release metadata, when a user requests a release-readiness analysis or report, or when an authorized project administrator changes ReleaseProof configuration.
Nature: retrieving in-scope Jira data; validating project/release scope; evaluating deterministic readiness rules; generating minimized findings, readiness scores and evidence views; returning results to the ReleaseProof Custom UI; storing and retrieving validated ReleaseProof project configuration in Forge KVS; and producing allowlisted technical diagnostics.
Purpose: to provide ReleaseProof and carry out Customer Instructions under the Main Agreement, including deterministic release-readiness and evidence analysis for the Jira project/release scope selected by Customer.
Provider does not use Customer Jira analysis data for advertising, behavioural profiling, model training, third-party analytics, or cross-customer benchmarking.
13. Duration, retention, deletion, and recovery
Processing is concurrent with the term of the Main Agreement and thereafter according to Section 8 of the Bonterms DPA and the applicable Atlassian Forge hosted-storage lifecycle.
ReleaseProof's persistent product record is limited to project configuration and technical schema metadata in Forge KVS. ReleaseProof does not intentionally persist complete Jira issue copies, complete analysis-report history, Jira user profiles, email-address directories, or Atlassian account IDs as ReleaseProof product records.
Where Customer Personal Data remains in Atlassian Forge hosted storage after uninstallation, deletion is subject to the Atlassian Forge hosted-storage lifecycle. Atlassian currently documents that Forge hosted storage retains data for 28 days after uninstallation and that a recovery request must be submitted within 21 days if Customer consents to recovery. Reinstallation does not automatically restore prior installation data.
Provider will not intentionally restore or further process retained data except on Customer instruction, as required by law, or as necessary to provide a documented recovery requested by Customer. Uninstallation or cessation of use does not represent or guarantee immediate physical deletion of data retained by Atlassian under that platform lifecycle.
Current Forge storage lifecycle information: https://developer.atlassian.com/platform/forge/storage-reference/.
14. Transfers to Subprocessors and cross-border processing
Transfers to Subprocessors occur as described in the Subprocessor List for the purposes stated there.
For the standard Marketplace Customer-to-SBS relationship, Customer contracts with SBS Deutschland GmbH & Co. KG in Germany. Designated EU Governing Law and Designated EU Member State are therefore N/A unless a specific Customer context creates a direct Restricted Transfer to SBS for which Exhibit A of the Bonterms DPA applies.
Downstream SBS-to-Atlassian/Forge international-transfer mechanics are governed separately by the Forge Data Processing Addendum and Atlassian's applicable transfer mechanisms. If a specific direct Customer-to-SBS Restricted Transfer exists, the transfer-specific SCC details and competent supervisory authority must be completed before that transfer.
15. Competent EU Supervisory Authority
N/A for the standard Marketplace Customer-to-SBS relationship where EU SCCs are not invoked for that direct relationship.
If a specific direct Customer-to-SBS Restricted Transfer invokes the EU SCCs, the competent supervisory authority must be determined under Clause 13 of the EU SCCs and completed for that Customer before the transfer.
16. Security Measures
ReleaseProof runs on Atlassian Forge and uses Forge hosted storage for persistent ReleaseProof configuration. No external Forge remotes, external ReleaseProof product database, or external Jira-analysis runtime host are declared.
- Forge scopes are limited to read:jira-work and storage:app.
- Jira API operations execute through the current Jira user context and Jira permissions remain effective.
- ReleaseProof does not request Jira issue write scopes.
- Project-configuration changes require server-side project-administrator authorization.
- ReleaseProof persists validated project configuration and technical schema metadata, not complete Jira issue copies or complete analysis-report history.
- Resolver inputs are validated at runtime; explicit JQL is constrained to project-bound supported syntax and validated client-side and server-side.
- Jira rich-text content is treated as untrusted input and is processed without executing embedded markup.
- Failure diagnostics use allowlisted technical values and intentionally exclude Jira descriptions, comments, acceptance text, JQL, request headers, tokens, response bodies, stack traces, project identifiers, and user identifiers.
- ReleaseProof uses deterministic code-based readiness rules and does not use a generative-AI or LLM processing path for Jira analysis.
17. Provider-specific references
ReleaseProof privacy notice: https://releaseproof.de/legal/privacy.
ReleaseProof security information: https://releaseproof.de/security.
Bonterms Data Protection Addendum v2.0 (Attachment Version): https://bonterms.com/standard/dpa-v2-attachment-version.
Forge DPA information: https://developer.atlassian.com/platform/forge/about-the-forge-data-processing-addendum/.
Atlassian subprocessors: https://www.atlassian.com/legal/sub-processors.
18. Attribution
This ReleaseProof DPA incorporates the Bonterms Data Protection Addendum v2.0 by reference and does not reproduce the full Bonterms standard text. Bonterms Data Protection Addendum Version 2.0 © 2026 Bonterms, Inc., made available by Bonterms under CC BY 4.0. ReleaseProof and SBS Deutschland GmbH & Co. KG are not endorsed by Bonterms.