Data processing addendum

This page is the Cover Page for the Bonterms Data Protection Addendum Version 2.0 (Cover Page Version), which is free to use under CC BY 4.0 and is available at https://bonterms.com/standard/dpa-v2-cover-page-version. Its text is not copied here. The customer accepts this Cover Page together with the end user agreement when it installs the app, as section 3.3 of that agreement and the provider-specific terms provide, and the vendor accepts it by publishing it. Capitalized terms have the meanings given in the addendum. The entries follow the fields of Bonterms' example Cover Page for version 2.0, read on 3 Oct 2026; the changes the vendor makes to the standard terms are listed under Additional Terms and nowhere else.

Key Terms

ItemEntry
Main AgreementThe Bonterms Standard End User Agreement version 1.0 with the provider-specific terms, accepted by the customer when it installs the app.
DPA Effective DateThe date the customer installs the app.
Subprocessor ListAtlassian Pty Ltd and its affiliates. Function: hosts and runs the apps on Forge and provides the Jira API. Location: the regions Atlassian uses for Forge and for the customer's Jira site; Atlassian's own list of its sub-processors, with their locations, is at https://www.atlassian.com/legal/sub-processors and its Forge data processing addendum governs what Atlassian does. The vendor uses no other Subprocessor.
Designated EU Governing LawIrish law, the same choice as Atlassian's Forge data processing addendum.
Designated EU Member StateIreland, for the same reason. Exhibit A applies only to a Restricted Transfer. The vendor, in Israel, receives no Customer Personal Data. Atlassian may run a Forge invocation outside the EEA; Atlassian certifies to the EU-U.S. Data Privacy Framework and its Forge data processing addendum includes standard contractual clauses.

Processing Details

ItemEntry
Customer (data exporter)The organization that installed the app on its Jira site, identified by its Jira site address. Role: controller. The vendor holds no data protection contact for it.
Provider (data importer)Eitan Plaks, an independent developer in Israel. Contact for data protection: support@cooloffapp.com. Main address: Israel; a postal address is given to a customer on request. Activity: develops and runs three Jira dashboard gadgets. Role: processor.
Categories of data subjectsUsers of the customer's Jira site and the people named in its issues, such as assignees and people who changed a status or a sprint. They are usually the customer's employees and other personnel.
Categories of Customer Personal DataAccount information (display names); unique identifiers (Atlassian account identifiers); user generated content (issue summaries and field values the app reads); change history entries that show who changed a field or moved an issue.
Sensitive or special categoriesNone or not applicable. The app does not look for them.
Frequency of transferOther: each time a user opens a dashboard that holds one of the gadgets.
Nature of the processingReading through the Jira API as the person viewing the dashboard, calculating in memory, showing the result on screen. The data is not stored, copied or sent anywhere else. The vendor does not read the customer's Jira data. The logs the vendor can see hold an error name, a status and a count of API points; for a programming error in the vendor's own code the log also holds the error message, with web addresses and issue keys removed; no code path known to the vendor puts issue content into it.
Purpose of the processingTo provide the app's functions to the customer and carry out the customer's instructions.
Duration and retentionOnly while a gadget view runs. Nothing is kept afterwards, so there is nothing to return or delete under section 8 of the addendum; the vendor will confirm that in writing if asked.
Transfers to SubprocessorsAs described in the Subprocessor List above.
Competent EU supervisory authorityDetermined under Clause 13 of the EU SCCs if they ever apply.
Security MeasuresSee the Main Agreement: the Security Measures are the ones in Security.

Additional Terms

These add to or change the Bonterms Data Protection Addendum and control in the event of a conflict.

  1. Specified Notice Period (sections 1 and 5.2). The definition of "Specified Notice Period" is replaced with: "Specified Notice Period" means 72 hours. The vendor still notifies without undue delay. The longer outer limit exists because the Marketplace Partner Agreement requires Atlassian's approval for any notice to end users that refers directly or indirectly to Atlassian, and the vendor does not control how long that takes. The vendor notifies Atlassian by a P1 ticket within 24 hours, as Atlassian's incident guidelines ask, and asks for that approval in the same ticket.
  2. Subprocessor Notice Method (section 4.3). The Subprocessor Notice Method is a notice inside each gadget and in the Marketplace listing.
  3. How customers are notified of a Security Incident (section 5.2). By a notice inside each gadget and in the Marketplace listing, and by e-mail where the vendor holds a contact.

Signatures

Not signed on paper. The customer accepts this Cover Page with the end user agreement when it installs the app, and the vendor by publishing it.