Data Processing Summary
This page summarizes the data categories processed by Excel to Jira Importer & Updater.
Purpose of processing
To let authorized Jira users import Excel workbook rows into existing Jira projects, update matching Jira issues, validate and transform mapped values before import, save mapping setups, detect duplicates and generate reports.
Categories of data
- Jira project metadata, issue type metadata and field metadata.
- Excel row values selected by users for import.
- Mapped values generated by Description Builder or Value cleanup during preview, validation and import.
- Import metadata: file name, sheet name, row identity, fingerprints, import date, importing user and issue keys.
- Optional user references used for Jira user picker fields.
- Product analytics and diagnostic metadata: sanitized event names, workflow step, action, source, result, surface, status, mode, target, filter, enabled state, Jira locale, row count, column count, created count, updated count and error count.
Storage locations
Forge Storage may store saved setups, import history and duplicate identity maps. Jira issue properties may store import metadata on created or updated issues.
External transmission
The app is designed without a separate vendor-hosted product backend. Workbook data is not sent to servers operated by the app creator. Processing happens through Atlassian Forge and Jira Cloud according to the app scopes approved during installation.
When product analytics is configured, sanitized product analytics events may be sent from the Forge backend to Google Analytics. These events are used to measure product usage, monitor reliability, understand failed workflows and guide product improvements.
Data minimization
The app is designed not to store full Excel files. Only structured metadata required for product behavior is stored. Users should avoid sending raw confidential workbooks to support unless a sanitized sample is explicitly requested.
Product analytics is designed not to include full Excel files, workbook cell values, column names, Jira issue text, issue keys, project names, user display names, email addresses, customer links, support messages or API tokens.
Deletion
Customers can uninstall the app and may request deletion of app-stored records by contacting Mederak Apps Service Desk.