Date: Thu, 28 Mar 2024 11:08:59 +0000 (UTC) Message-ID: <1527048341.25.1711624139286@2181c157916b> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_24_352070930.1711624139286" ------=_Part_24_352070930.1711624139286 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Last updated: June 2023
This Privacy Policy explains what information Y2 ENGINEERING SP ZO.O. (a= provider of downloadable and cloud-based applications under the Re= lease Management brand name through the Atlassian Marketplace) col= lect about you and why, what we do with that information and how we handle = the content you place in all our add-ons for JIRA Cloud ("Add-on") which is= fully compliant with the Atlassian Privacy Policy= .
This Privacy Policy applies to the information that we obtain through yo= ur use of the Add-on. By using Add-on you consent to the collection, proces= sing, storage, disclosure and other uses described in this Privacy Policy.<= /p>
Add-on: a bundle of code, resources and configuration f= iles 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, submi= t, post, create, transmit, store or display in an Atlassian Service.
Information: all of the different forms of data, conten= t, and information collected by us as described in this Privacy Policy.
Customer Data: IDs (references) for Jira Versions, Spri= nts, Epics, Custom JQLs that we use to define Releases in Release Managemen= t, Jira User IDs (references) in case are used as Custom Properties for Rel= eases or to tracking transitions of releases according to workflow, comment= s for releases. Also IDs (reference) of Jira Projects and User/Group IDs to= limit observability and access to Release Boards. By definition Customer D= ata does not include any Personal Information. Sametime we cannot garantee = that the users will not put some PII data into free text fields across the = App.
We may change this Privacy Policy from time to time. If we make any chan= ges, we will notify you by revising the "Effective Starting" date at the to= p of this Privacy Policy.
If you disagree with any changes to this Privacy Policy, you will need t= o stop using Add-on and deactivate your account(s), as outlined below.
Atlassian Marketplace Information
Contact information such as name, email address, mailing address, and ph= one number
Billing information such as name and billing address
JIRA host details (as prescribed by the Atlassian Connect Guidelines)
Details: eventType, productType, baseUrl, pluginsVersion, serverVersion,= sharedSecret, publicKey, clientKey
We collect and store Content that you create, input, submit, post, uploa= d, transmit, store or display in the process of using our SaaS Products or = Websites. Such Content defined as Customer Data, does not include any Perso= nal Information (PII) or other sensitive information we collect. But, we ca= n't protect the users from putting some PII data into free text fields we u= se across the App.
We collect other data that you submit to us, such as surveys, activity o= r event, request customer support, communication with us via third party so= cial media sites or any other form of communicating with us. For example, i= nformation regarding a problem you are experiencing with the Add-on could b= e submitted to our issue tracker or sent via email.
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 w= ith the Add-on. 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, local= e and language preferences, identification numbers associated with your Dev= ices, your mobile carrier, and system configuration information, the URLs y= ou accessed (and therefore included in our log files) include usernames as = well as elements of Content (such as JIRA project names, project keys, stat= us names, and JQL filters) as necessary for the Add-on to perform the reque= sted operations. Occasionally, we connect Customer Data to information gath= ered in our log files as necessary to improve Add-on Services for individua= l customers. In such a case, we would treat the combined Informatio= n in accordance with this privacy policy.
Analytics Information
We collect analytics information when you use our Add-on to help us impr= ove our products and services. This analytics information consists of the f= eature and function of the Add-on being used, the associated license identi= fier (SEN) and domain name, the username and user data available from the J= IRA REST API. The analytics information we collect includes elements of Con= tent 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 Add-on.
As of the date this policy went into effect, we use Google Analytics as = an analytics provider. To learn more about the privacy policy of Google Ana= lytics, refer to Google's Policies and Principles. Use the Google Analytics Opt-out Browser Add-on to pre= vent analytics information from being sent to Google Analytics.
Analytics Information Derived from Content
Analytics information also consists of data we collect as a result of ru= nning queries against Content across our user base for the purposes of gene= rating Usage Data. "Usage Data" is aggregated data about a group or categor= y of services, features or users that does not contain specific Customer Da= ta.
Though we may happen upon Customer Data as we compile Usage Data from Co= ntent across user instances, this is a byproduct of our efforts to understa= nd broader patterns and trends. It is not a concerted effort by us to exami= ne the Content of any particular customer.
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 d= evice memory. We use cookies to improve and customize Add-on and your exper= ience; to allow you to access and use the Add-on without re-entering your u= sername or password; and to count visits and understand which areas and fea= tures of the Add-on are most popular. You can instruct your browser, by cha= nging its options, to stop accepting cookies or to prompt you before accept= ing a cookie from websites you visit. If you do not accept cookies, however= , you may not be able to use all aspects of the Add-on. We may also collect= information using web beacons (also known as "tracking pixels"). Web beaco= ns are electronic images that may be used in the Add-on or in emails that h= elp us to deliver cookies, count visits, understand usage and campaign effe= ctiveness 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 d= ifferent websites or online services. Many browsers include their own manag= ement tools for removing HTML5 local storage objects. To manage "flash cook= ies" please click here.
General Use
We use the Information we collect about you (including Customer Data to = the extent applicable) for a variety of purposes, including to:
Provide, operate, maintain and improve Add-on;
Enable you to access and use Add-on, including uploading, downloading, c= ollaborating on and sharing Content;
Process and complete transactions, and send you related information, inc= luding Release Notes and Feature Prompts;
Send transactional messages, including responding to your comments, ques= tions, and requests; providing customer service and support; and sending yo= u technical notices, updates, security alerts, and support and administrati= ve messages;
Send promotional communications, such as providing you with information = about services, features, surveys, newsletters, offers, promotions, contest= s, events and sending updates about your team and chat rooms; and providing= other news or information about us and our select partners;
Monitor and analyze trends, usage, and activities in connection with Add= -on and for marketing or advertising purposes;
Investigate and prevent fraudulent transactions, unauthorized access to = Add-on, and other illegal activities;
Personalize Add-on, including by providing content that match your inter= ests and preferences;
Enable you to communicate, collaborate, and share Content with users you= designate; and
For other purposes about which we obtain your consent.
Notwithstanding the foregoing, we will not use Customer Data appearing i= n our Analytics Logs or Web Logs for any purpose. The use of Information co= llected through our Atlassian Services shall be limited to the purposes dis= closed in this policy.
Compiling aggregate analytics information
To better comply with the Atlassian Marketplace, we make extensive use o= f analytics information (including log and configuration data) to understan= d how Add-on is being configured and used, how it can be improved for the b= enefit of all of our users, and to develop new products and services. As su= ch we generate Usage Data (as defined above) from the web logs and analytic= s logs described above, including the Content elements captured in such log= s, as well as from the Content stored in the Add-on.
Information sharing and disclosure
We will not share or disclose any of our Customer Data or Content with t= hird parties except as described in this policy. We do not sell your Custom= er Data or Content.
Your Use
When you use Add-on, Content you provide will be displayed back to you.<= /p>
Collaboration
As a natural result of using Add-on, you may create Content that other u= sers of your JIRA instance can access for the purposes of collaboration. So= me of the collaboration features of Add-on display your profile information= , including Personal Information included in your profile, to users with wh= om you have shared your Content
We work with third party service providers to provide website, applicati= on development, hosting, maintenance, back-up, storage, virtual infrastruct= ure, payment processing, analysis and other services for us. These service = providers may have access to or process your Information for the purpose of= providing those services for us. This list includes:
Hetzner =E2=80=94 SSD Cloud Hosting
Spark Post =E2=80=94 For sending transactional emails
Mailchimp =E2=80=94 For sending newsletters and release notes
Google Analytics =E2=80=94 For collecting analytics
Newrelic =E2=80=94 For monitoring the status of the Add-on
We do not share Customer Data with third parties.
Add-on hosts data with hosting service providers in numerous countries (= namely Germany and Finland). The servers on which Customer Data are stored = are kept in a controlled environment. While we take reasonable efforts to g= uard our Customer Data, no security system is impenetrable and due to the i= nherent nature of the Internet as an open global communications vehicle, we= cannot guarantee that information, during transmission through the Interne= t or while stored on our systems or otherwise in our care, will be absolute= ly safe from intrusion by others, such as hackers. In addition, we cannot g= uarantee that any incidentally-collected Personal Information you choose to= store in Add-on are maintained at levels of protection to meet specific ne= eds or obligations you may have relating to that information.
Where data is transferred over the Internet as part of the Add-on, the d= ata is encrypted using industry standard SSL (HTTPS).
For communications concerning this Data Security and Privacy Statement, = please write to support@releasemanagement.app
If you have any concerns about Release Management=E2=80=99s data protect= ion practices, the contact details of Release Management=E2=80=99s data pro= tection officer are:
Yuri Kudin
ykudin@releasemanagement.ap=
p
+380 97 922 76 79