/
Data Storage & Security

Data Storage & Security

Overview

This document outlines the data storage practices and security considerations for the STAGIL Assets 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. Assets menu configuration – For the searching user, we store only the user’s account ID

    2. Advanced links configuration – For indexing runs, we store only the indexing initiator's user account ID

    3. Advanced link field configuration

      • Context configuration – For the context's project and issue type, we store only their IDs

      • Data logic configuration – When related configurations are filled, we store issue filter ID, custom field ID, project ID, and issue type ID

      • Issue view configuration – We store field IDs for display, sum-up, and default sorting configurations. For fields enabled on the create screen, we store IDs of the synced Forge field and its context

      • Field select configuration – We store only field IDs for display configuration

      • Parent field filter configuration

      • Customer portal configuration – We store IDs for request types and projects, and only field IDs for shown fields

    4. Issue filter panel configuration

      • Context configuration – For the context's project and issue type, we store only their IDs

      • Data logic configuration – For the searching user, we store only the user’s account ID

      • Display style configuration – We store field IDs for display, sum-up, and default sorting configurations

    5. Jira DC connection configuration

    6. QR code configuration – For the context's project and issue type, we store only their IDs

    7. Database synchronizer configuration – For field mappings, we store only Jira field IDs. We store generated logs without field names and values

    8. Project synchronizer configuration – We store IDs for project categories, projects, issue types, and custom fields. For the sync user, we store the user account ID. We store generated logs without field names and values

    9. API tokens with associated user account IDs

  3. Application Usage Data

    1. Linked issue IDs

    2. Import issues records

      • Import process start and end times

      • Number of imported issues

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

What Data Do We NOT Store?

  1. Issue Content – We do not store any Jira issue field values, field names, comments, or attachments

  2. Synchronization Data – All synchronization data is stored within Jira issues

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

What Data Do We Process?

Although we do not store issue content and synchronization data, the app processes this data on our servers before showing it in the Jira UI and writing it to Jira issues.

  • We act as a data processor, not a data controller, processing data only as specified by Jira/Atlassian

  • Data is transmitted securely to our AWS servers, processed momentarily, and then sent to Jira without being cached or stored

  • At no point do we access, analyze, or retain any issue content or synchronization data

Where Is the Data Stored?

Configuration 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.