Release Management Privacy Policy

1. Introduction

This Privacy Policy explains what information Y2 ENGINEERING SP ZO.O. (a provider of downloadable and cloud-based applications under the Release Management Apps (“Release Management“) brand name through the Atlassian Marketplace) collect about you and why, what we do with that information and how we handle the content you place in all our Applications ("Apps" or “App“) which is fully compliant with the Atlassian Privacy Policy.

2. Scope of Privacy Policy

This Privacy Policy applies to the information that we obtain through your use of the Apps. By using Apps you consent to the collection, processing, storage, disclosure and other uses described in this Privacy Policy.

3. Definitions

App: a bundle of code, resources and configuration files that can be used with an Atlassian product to add new functionality or to change the behavior of that product's existing features.

Content: any information or data that you upload, submit, post, create, transmit, store or display in an Atlassian Service.

Information: all of the different forms of data, content, and information collected by us as described in this Privacy Policy.

Customer Data: means any data, content or materials provided to Release Management by or at the direction of Customer or its End Users via the Release Management Products, including from Third-Party Products.

The specific Customer Personal Data we use per Application are defined in https://releasemanagement.atlassian.net/wiki/spaces/TRUSTRM/pages/2615869441/Data+Processing+Addendum+DPA#EXHIBIT-A:-Description-of-the-Processing-Activities-/-Transfer

4. Changes to Privacy Policy

We may change this Privacy Policy from time to time. If we make any changes, we will notify you by revising the "Effective Starting" date of this Privacy Policy.

If you disagree with any changes to this Privacy Policy, you will need to stop using Apps and deactivate your account(s), as outlined below.

5. Information available to us

See https://releasemanagement.atlassian.net/wiki/spaces/TRUSTRM/pages/2615869441/Data+Processing+Addendum+DPA#EXHIBIT-A:-Description-of-the-Processing-Activities-/-Transfer

6. Content

We collect and store Content that you create, input, submit, post, upload, transmit, store or display in the process of using our SaaS Products or Websites. Such Content defined as Customer Data. See https://releasemanagement.atlassian.net/wiki/spaces/TRUSTRM/pages/2615869441/Data+Processing+Addendum+DPA#EXHIBIT-A:-Description-of-the-Processing-Activities-/-Transfer

7. Other submissions

We collect other data that you submit to us, such as surveys, activity or events, requests to customer support, communication with us via third party social media sites or any other form of communicating with us. For example, information regarding a problem you are experiencing with the Apps could be submitted to our issue tracker or sent via email.

8. Information we collect from your use of the Apps

(a) Web Logs. As is true with most websites and services delivered over the Internet, we gather certain information and store it in log files when you interact with the Apps. This information includes internet protocol (IP) addresses as well as browser type, internet service provider, URLs of referring/exit pages, operating system, date/time stamp, information you search for, locale and language preferences, identification numbers associated with your Devices, your mobile carrier, and system configuration information, the URLs you accessed (and therefore included in our log files) include user identifiers as well as elements of Content (for e.g. JIRA project identifiers, project keys, status names, JQL filters, etc.) as necessary for the Apps to perform the requested operations. Occasionally, we connect Customer Data to information gathered in our log files as necessary to improve Apps for individual customers. In such a case, we would treat the combined Information in accordance with this privacy policy.

(b) Analytics Information. We collect analytics information when you use our App to help us improve our products and services. This analytics information consists of the feature and function of the Apps being used, the associated license identifier and domain name, the user id available. The analytics information we collect includes elements of Content related to the function the user is performing. As such, the analytics information we collect may include some elements of Customer Data that the user chose to upload, submit, post, create, transmit, store or display in the Apps.

(c) Analytics Information Derived from Content. Analytics information also consists of data we collect as a result of running queries against Content across our user base for the purposes of generating Usage Data. "Usage Data" is aggregated data about a group or category of services, features or users that does not contain specific Customer Data.

Though we may happen upon Customer Data as we compile Usage Data from Content across user instances, this is a byproduct of our efforts to understand broader patterns and trends. It is not a concerted effort by us to examine the Content of any particular customer.

(d) Cookies and Other Tracking Technologies. We use various technologies to collect information, such as cookies and web beacons. Cookies are small data files stored on your hard drive or in device memory. We use cookies to improve and customize Apps and your experience; to allow you to access and use the Apps without re-entering your username or password; and to count visits and understand which areas and features of the Apps are most popular. You can instruct your browser, by changing its options, to stop accepting cookies or to prompt you before accepting a cookie from websites you visit. If you do not accept cookies, however, you may not be able to use all aspects of the Apps. We may also collect information using web beacons (also known as "tracking pixels"). Web beacons are electronic images that may be used in the Apps or in emails that help us to deliver cookies, count visits, understand usage and campaign effectiveness and determine whether an email has been opened and acted upon.

We also use javascript, e-tags, "flash cookies", and HTML5 local storage to collect information about your online activities over time and across different websites or online services. Many browsers include their own management tools for removing HTML5 local storage objects. To manage "flash cookies" please click here.

For additional information about Analytics tools we use check Sub-processors.

9. How we use Information we collect

(a) General Use. We use the Information we collect about you (including Customer Data to the extent applicable) for a variety of purposes, including to:

(i) Provide, operate, maintain and improve Apps;

(ii) Enable you to access and use Apps, including uploading, downloading, collaborating on and sharing Content;

(iii) Process and complete transactions, and send you related information, including Release Notes and Feature Prompts;

(iv) Send transactional messages, including responding to your comments, questions, and requests; providing customer service and support; and sending you technical notices, updates, security alerts, and support and administrative messages;

(v) Send promotional communications, such as providing you with information about services, features, surveys, newsletters, offers, promotions, contests, events and sending updates about your team and chat rooms; and providing other news or information about us and our select partners;

(vi) Monitor and analyze trends, usage, and activities in connection with Apps and for marketing or advertising purposes;

(vii) Investigate and prevent fraudulent transactions, unauthorized access to Apps, and other illegal activities;

(viii) Personalize Apps, including by providing content that match your interests and preferences;

(ix) Enable you to communicate, collaborate, and share Content with users you designate; and

(x) For other purposes about which we obtain your consent.

Notwithstanding the foregoing, we will not use Customer Data appearing in our Analytics Logs or Web Logs for any purpose. The use of Information collected through our Atlassian Services shall be limited to the purposes disclosed in this policy.

(b) Compiling aggregate analytics information. To better comply with the Atlassian Marketplace, we make extensive use of analytics information (including log and configuration data) to understand how Apps is being configured and used, how it can be improved for the benefit of all of our users, and to develop new products and services. As such we generate Usage Data (as defined above) from the web logs and analytics logs described above, including the Content elements captured in such logs, as well as from the Content stored in the Apps.

(c) Information sharing and disclosure. We will not share or disclose any of our Customer Data or Content with third parties except as described in this policy. We do not sell your Customer Data or Content.

(d) Your Use. When you use Apps, Content you provide will be displayed back to you.

(e) Collaboration. As a natural result of using Apps, you may create Content that other users of your JIRA instance can access for the purposes of collaboration. Some of the collaboration features of Apps display your profile information, including Personal Information included in your profile, to users with whom you have shared your Content.

10. Service Providers, Business Partners and Others

See Sub-processors table and Section 2.9 and 2.10 of DPA.

11. Information we do not share

We do not share Customer Data with third parties that are not listed in Sub-processors table.

12. Data storage, transfer and security

Please refer to Data Processing Addendum (DPA)

13. Contact Information

For communications concerning this EULA, please write to security@releasemanagement.app

If you have any concerns about Release Management’s data protection practices, the contact details of Release Management’s Security & Data Protection Officer are: