Privacy Policy
This Privacy Policy explains how Excel to Jira Importer & Updater handles data when used with Jira Cloud.
Who we are
Excel to Jira Importer & Updater is provided by Piotr Mederak, ul. Magnolii 1K/2, 05-500 Nowa Wola, Poland. For privacy or support requests, contact Mederak Apps Service Desk.
Data we process
The app processes data needed to import Excel workbook rows into Jira. Depending on user configuration, this may include issue summaries, descriptions, issue types, estimates, labels, components, dates, user references, custom field values, source file name, sheet name, row identity, import status, issue keys and import reports.
Excel files
The app is designed not to store full Excel files. Excel files are parsed to prepare structured import data. The app stores only information needed for import history, duplicate detection, saved mapping setups and reporting.
Forge hosting and vendor access
The app is designed as an Atlassian Forge app. Product compute and storage are hosted on Atlassian infrastructure, not on a separate vendor-operated product backend. The app creator does not receive customer Excel files or Jira task content on an external server. Data is processed inside the customer's Jira/Forge context according to the scopes approved during installation.
Jira data access
The app accesses Jira data through Atlassian Forge and Jira REST APIs using the permissions granted during installation. It may read project metadata, issue types, fields, users required for picker fields and existing issues needed for duplicate detection. It may create or update Jira issues only when a user confirms an import.
Data storage
Configuration, mapping setups, import reports and duplicate identity mappings may be stored in Forge Storage. Issue import metadata may also be stored as Jira issue properties. These records help the app detect repeated imports, support update mode and generate reports.
Data retention
Import metadata is retained only as needed to provide product functionality. Duplicate identity mappings may be pruned by age and count to limit storage growth. Customers may request deletion of app-stored data by contacting support.
Product analytics and diagnostics
When product analytics is configured for the production environment, the app may send sanitized usage events to Google Analytics through the Forge backend. These events help us understand feature adoption, improve the app experience, monitor reliability, identify common workflow problems and prioritize quality improvements.
Product analytics may include event names such as app loaded, step viewed, workbook uploaded, workbook parse failed, mapping completed, validation started, validation succeeded, validation failed, import started, import completed, import partially completed, import failed, export started, export completed, export failed, modal opened, feedback prompt shown and related workflow actions.
Analytics parameters are limited to operational labels and counts, such as 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. The app uses a browser-generated analytics client identifier stored in local storage. This identifier is not an Atlassian account ID, Jira user ID or email address.
Product analytics is designed not to include full Excel files, workbook cell values, column names, Jira issue summaries, descriptions, comments, issue keys, project names, user display names, email addresses, customer links, JQL queries, support messages or API tokens. Diagnostic logs should focus on operational status and error diagnosis rather than workbook content or Jira issue content.
Website analytics and advertising measurement
This marketing website may use Google Analytics and Google Ads measurement through the Google tag. These tools are used to understand website performance, product page engagement and advertising campaign results. Optional analytics and advertising storage are controlled through the website consent banner and Google Consent Mode. Website analytics does not give Mederak Apps access to customer Excel files, Jira issues or app data inside Jira Cloud.
Sharing
We do not sell personal data. Data is processed to provide the app and may be handled by Atlassian infrastructure as part of Forge and Jira Cloud. If product analytics is configured, Google Analytics may process sanitized product telemetry. See Sub-processors for the current sub-processor summary.
Security
We apply privacy-conscious design principles: data minimization, Forge-hosted execution, Jira permission checks and avoiding unnecessary logging of workbook content. See Security Practices for more detail.
Your rights and requests
For access, correction, deletion or privacy questions, contact Mederak Apps Service Desk. We may need tenant, site URL and app installation context to process a request.