/
GO! JQL Data Residency and Security Overview

GO! JQL Data Residency and Security Overview

This page documents how the Go JQL Cloud app handles data residency, including what data it processes, where it is stored, and the controls available to customers. It is intended for security, compliance, and technical reviewers.

Purpose

Describe how GO! JQL handles data residency, where data is stored, how it is processed, and what customer controls exist for regional requirements.

Scope

  • GO! JQL Cloud app (Atlassian Marketplace – Connect)

  • All customer data processed by the application

  • Atlassian Cloud environments where GO! JQL is installed

Data Collected and Processed

GO! JQL processes and, where functionally necessary, stores the following data entities.

3.1 Stored Data Entities

A) Issue Field (table)

  • User Account ID (references the user who created/owns the record)

  • Field ID

  • Sequence (number)

  • Client ID (unique per Jira site)

  • Base URL

B) Search Filter (table)

  • Name (user-provided input)

  • JQL (user-provided input)

  • Owner → User Account ID

  • Share → boolean (true / false)

  • View Permission → User Account ID or Group ID

  • Edit Permission → User Account ID or Group ID

  • Client ID (unique per Jira site)

  • Base URL

C) Schedule (table)

  • Enable → boolean (true / false)

  • Installed → boolean (true / false)

  • Config → synchronization day/time configuration (stores the day(s) and hour(s) used for sync)

  • Client ID (unique per Jira site)

  • Base URL

3.2 Notes on End-User Inputs

  • Name and JQL fields are directly provided by users.

  • Permission fields may reference either an individual (User Account ID) or a group (Group ID).

Data Storage Location (Data Residency)

  • Go! JQL is a Connect (Cloud) app.

  • Application and customer data are stored in a database hosted on Heroku infrastructure located in the European Union (EU).

  • Customer data is processed and stored within the EU; Go! JQL does not routinely transfer customer data outside this region.

  • Client ID and Base URL are used as technical site identifiers to operate the app.

Data Processing and Access

  • Data is processed strictly for the purpose of delivering GO! JQL functionality.

  • Access to data is limited to authorized application services and personnel required to operate and maintain the service.

  • GO! JQL does not store application logs containing customer data.

Data Retention Policy

  • Customer data is stored in the application database for as long as it exists.

  • Uninstallation of GO! JQL does not automatically delete stored data.

  • Data may remain in the database unless explicitly deleted by the service provider in accordance with internal policies or contractual obligations.

Security Measures

GO! JQL follows industry-standard security practices, including:

  • Encrypted data transmission (HTTPS/TLS)

  • Role-based access controls and least-privilege principles

  • Regular security maintenance and updates

Contact & Compliance

For questions about data residency, security, or compliance:

Contact: apps@almbase.com

This document may be updated as infrastructure, security, or compliance requirements evolve.