Data Storage & Security

Overview

This document outlines the data storage practices and security considerations for the STAGIL Tables app for Jira. It provides detailed information about what data is stored, where it is stored, and how it is managed across different aspects of the application.

What Data Do We Store?

1. General Instance Information

   1. Jira host information

      • Client key

      • Base URL

      • Instance metadata

   2. Cloud migration information

      • Migration run status

      • Migration transfer ID

2. Administrative Configuration

   1. Table configuration

      • Table name, context name, project ID and issue type ID

      • Column configuration – For user picker default values we store only the user account ID

      • Display configuration

      • Customer portal configuration – We store only IDs for request types and projects

      • Permission configuration – For groups, we store only their IDs

   2. Automation rules

   3. External data source configuration

   4. API tokens with associated user account IDs

3. Application Usage Data

   1. Table template

      • Template name

      • Row count

   2. Bulk import records

      • File name

      • User account ID of import initiator

      • Start and end time of the import process

      • Number of issues for table import

   3. Column preferences for the table navigator – We store IDs of the shown fields

   4. Manual ordering for rows

      • Order position

      • Issue ID

What Data Do We NOT Store?

1. Table Content – All data entered into tables is stored exclusively in Jira issue properties.

2. Table Default Values – Default values for tables are maintained within Jira app properties.

3. Select List Options from External Data Sources – When using select list columns configured with external data sources, options are retrieved whenever users add or edit table rows.

4. Template Row Values – While template names and row counts are stored, the actual row values from templates are maintained within Jira app properties.

5. User Analytics – We do not collect any browser information, IP addresses, or location data.

What Data Do We Process?

Although we do not store table values, when a user enters data in the Jira UI, the app processes this data on our server before writing it to Jira issue properties.

• This means we act as a data processor, not a data controller (since we do not store or retain user-entered data).

• Data is transmitted securely to our AWS server, processed momentarily, and then sent to Jira’s issue properties without being cached or stored.

• At no point do we access, analyze, or retain the content of user-entered data.

Where Is the Data Stored?

Data is stored on an AWS server in Frankfurt, Germany.

Questions?

If you have any questions about how we handle data, feel free to contact us at support@stagil.com.