Privacy Policy
This Privacy Policy explains how Excel to Jira Importer handles data when used with Jira Cloud.
Who we are
Excel to Jira Importer is provided by Piotr Mederak, ul. Magnolii 1K/2, 05-500 Nowa Wola, Poland. For privacy or support requests, contact support.jira@mederak.app.
Data we process
The app processes data needed to import Excel backlog 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 backlog 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 in the Forge app
The installed app may send privacy-conscious product usage events to Google Analytics 4 through the Forge backend and Google Analytics Measurement Protocol. These events help us understand app usage, workflow completion and reliability, including app load, viewed workflow step, workflow button clicks, sample workbook use, workbook upload or parse failure, saved mapping template use, mapping completion, validation start and result, import start and result, history use, Excel preview opening, partial report opening and scroll cue clicks.
Product analytics events use a random browser client ID stored in local storage. The analytics payload is designed not to include file names, sheet names, Excel column names, Jira issue keys, project keys, account IDs, user names, email addresses, workbook content, issue summaries or field values.
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, secure and improve the app and may be handled by Atlassian infrastructure as part of Forge and Jira Cloud. Product analytics events may be processed by Google Analytics 4 as described above. 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 backlog content. See Security Practices for more detail.
Your rights and requests
For access, correction, deletion or privacy questions, contact support.jira@mederak.app. We may need tenant, site URL and app installation context to process a request.