Privacy Policy for OBSS Apps on Atlassian Cloud Platform

Overview

This document explains the privacy policy employed by OBSS Teknoloji A.Ş. (“OBSS”) (http://www.obss.tech/) about customer data and information and is effective starting from January 12th, 2026

The policies described in this document cover the operation of Cloud apps for Atlassian products that are built, maintained, and operated by OBSS, as well as related services provided by OBSS.

Definitions

In this document:

• Product Data refers to data of your Atlassian host products on Atlassian Cloud. This data might include your Jira issues, Confluence pages, or any other Atlassian host product data.

• Settings Data refers to your app settings for OBSS products. This type of data is specific to OBSS apps and does NOT include your Product Data. It also does not include any Personally Identifiable Information.

• Customer Data refers to Product Data or Settings Data as a whole.

• License Data refers to transaction data that is created by your purchase of our licenses. This data might include the username, contact information (e-mail, address, phone number), and company information for technical and billing contacts. This data does NOT include any payment methods information like credit cards and bank accounts.

• Support Data refers to the data you provide as part of our support engagement. This data includes the username and e-mail address you provide while reaching us; as well as log files, screenshots, and other information you might share with us during the support process.

• Web Traffic Data refers to the data gathered by anybody's use of our website or cloud services. This data might include your IP address, the pages you visited, and error messages/logs. It does NOT include Product Data or Settings Data. It does NOT include any Personally Identifiable Information.

• CRM Data refers to your License Data, Support Data, or Web Traffic Data as a whole.

• Data refers to any data that is related to a customer, including but not limited to the above.

How do we access & gather your data?

We might access & gather your data from a number of different sources:

• We access Product Data through customers' use of our cloud app services (since cloud apps need to access Product Data in order to perform their functions). 

• We gather Settings Data through customers' use of our cloud app services (since cloud apps need to access Settings Data in order to perform their functions). 

• We gather License Data from Atlassian about customers who purchase or evaluate our products. 

• We gather Support Data through the customer's use of our support channels. 

• We use cookies or other tracking technologies, Google Analytics Services, Amplitude, Hubspot, and Sentry.io for collecting Web Traffic Data about our visitors to our website, public documentation portals, service channels, and cloud services. 

How long do we store your Product Data and/or Settings Data?

For Timepiece - Time in Status for Jira Cloud,

Timepiece - Time in Status for Jira accesses and processes your Product Data, but it does NOT permanently store your Product Data. The data is discarded as soon as the processing is completed. Only the Product Data needed for the requested report is read from your Jira instance. (For example, the value of an issue field is read by our service only if that field is selected to be included in the report by the user). Any file exports requested by the user are kept on our servers for 24 hours for the user to download and then automatically deleted. Beyond that, Timepiece only keeps Settings Data specific to itself. Even in the case of Settings Data, we do NOT keep any personal data that references you by username, title, or e-mail. We only store the user accountID's provided by Atlassian. 

For TicketBook - Service Contract Management for Jira,

TicketBook is a “Runs on Atlassian” app. It does NOT store any Customer Data outside of Atlassian systems. TicketBook accesses and processes your Customer Data only on the Forge platform, which is hosted and managed by Atlassian. TicketBook keeps Settings Data related to its operation on Forge platform storage, also hosted by Atlassian. TicketBook may send Web Traffic Data to outside of Atlassian systems, but this data does not contain any Customer Data.

For Baselines for Confluence,

Baselines for Confluence does NOT store any Product Data or Settings Data on its servers. Baselines for Confluence accesses and processes your Product Data on its remote backend, but it does NOT permanently store your Product Data. The data is discarded as soon as the processing is completed. Baselines for Confluence keeps Settings Data related to its operation on the Forge platform storage, hosted by Atlassian. 

For Historian - History Explorer for Jira,

Historian is a “Runs on Atlassian” app. It does NOT store any Customer Data outside of Atlassian systems. Historian accesses and processes your Customer Data only on the Forge platform, which is hosted and managed by Atlassian. Historian keeps Settings Data related to its operation on Forge platform storage, also hosted by Atlassian. Historian may send Web Traffic Data to outside of Atlassian systems, but this data does not contain any Customer Data.

For SearchMate - Advanced JQL Search for Linked Issues,

SearchMate is a “Runs on Atlassian” app. It does NOT store any Customer Data outside of Atlassian systems. SearchMate accesses and processes your Customer Data only on the Forge platform, which is hosted and managed by Atlassian. SearchMate keeps Settings Data related to its operation on Forge platform storage, also hosted by Atlassian. SearchMate may send Web Traffic Data to outside of Atlassian systems, but this data does not contain any Customer Data.

How do we use your data?

We might access and process your Data for ...

• Providing the functionality of our cloud apps

• Running and improving our business

• Developing our products

• Responding to your support requests

• Communicating with you about important changes to our products

• Promotion and marketing of our own products and services

• Achieving regulatory compliance, fulfilling legal obligations, or supporting law enforcement agencies

We do NOT sell or share your Data with third parties for their marketing purposes.

Your Product Data is classified as "Customer-Only". This means OBSS personnel DO NOT access your Product Data.

Who has access to your data?

OBSS personnel and outsourced personnel hired by OBSS might access your CRM Data and Settings Data for running our business and services.

We may share your CRM Data with our subsidiaries or service providers for our operational, promotional, or marketing needs.

We may share your Data with third parties at your request.

We may share your Data with authorities to support legal processes.

Your Data might be transferred to a new party as part of a sale, a merger, or an acquisition of assets that are related to our Atlassian products and services.

Data Location

Your Product Data is transferred to our systems for processing in the USA, on Amazon Web Services Data Centers (us-west-2, Oregon).

As stated above, we do NOT permanently store your Product Data. Any cached/temporary data is stored on our systems in the USA, on Amazon Web Services Data Centers (us-west-2, Oregon).

Some Settings Data is stored on our systems in the USA, on Amazon Web Services Data Centers (us-west-2, Oregon). Some Settings Data is stored in Forge platform storage, hosted by Atlassian.

Some Web Traffic Data is stored on our systems in Atlassian Jira Cloud and in the USA on Amazon Web Services. The Web Traffic Data related to Google Analytics is stored on Google systems. The Web Traffic Data related to Sentry.io is stored on Sentry.io servers. The Web Traffic Data related to Amplitude is stored on Amplitude servers.

Some CRM Data is stored on HubSpot servers.

The Support Data is stored on our systems in Atlassian Cloud.

Your License Data is stored on Atlassian systems and is in Atlassian custody.

Data Retention

As stated above, we do NOT store your Product Data.

For other types of data, we will keep your Data as long as it is reasonably necessary for the business use it was collected for (as described in this document) or as long as it is required by the law.

Data Security

OBSS employs reasonable technological, organizational, and procedural measures to protect the integrity and security of your Data.

Only users who need access to your Data to perform their business function will be granted access.

Rights

Customers have the following rights concerning their data stored by OBSS:

Please note that OBSS is storing customer data to enable its operation. Deletion or restriction on the use of these data can create impediments in OBSS operations. For example, if the customer asks for the deletion of his/her personal data, we will not be able to respond to support requests since we do not have the contact information.

Acceptance

By using OBSS products and services, you agree that your Data is collected and processed by OBSS and agree to be bound by the terms and conditions of this policy.

If you do not agree with this policy, you are expected not to use the products and services provided by OBSS.

Policy Change

This policy might be subject to change at any time. The updated policy will be published here on this page, and a link to this page will be available on our product pages on Atlassian Marketplace.

Communication

For any questions, issues, or requests about our Privacy Policy, you can contact us through appsupport.obss.tech support portal or by sending an e-mail to mailto:appsupport@obss.tech