Skip to main content

Data retention & GDPR

Exportelier is designed to hold as little data as possible and to give you control over what little it does keep.

What is never stored​

Generated documents are streamed to the browser and deleted — they are not stored long-term. The audit log keeps only metadata about export events, never document content.

Report exports keep no issue snapshot​

Reports store a Saved Filter's numeric id and your display name — never the filter's JQL, and never its results. There is no stored copy of your issues to retain, expose or purge: every export asks Jira again, as the person exporting.

Because report exports run in the background, the generated document cannot be streamed straight to the browser. It is written to temporary storage for the download and then:

  • deleted as soon as you download it, and
  • expired automatically after one hour if you do not.

A cancelled or failed export has its partial output cleaned up immediately. No report document is retained beyond that window, and none is ever attached to an issue or mailed unless you configure that separately.

The audit log records that a report was created, updated, duplicated, deleted, imported or exported, as metadata only — identifiers, counts and outcome. It never records filter names, JQL or issue content.

What a dashboard import keeps​

Importing a Jira dashboard stores one small record beside the report, so Exportelier can later tell you what changed and guarantee the report's completeness notice still matches what was imported.

That record holds only stable, non-secret metadata: the source dashboard's id and name, when and by whom it was imported, and per gadget its id, title, type signature, dashboard position and a hash of the configuration that was read.

It holds no JQL, no issue data, and no raw gadget configuration — only the hash, which cannot be turned back into the settings it was computed from.

Deleting the report deletes its import record and its index entry in the same operation; nothing is left orphaned. Duplicating an imported report produces an ordinary report with no import record at all.

Retention configuration​

Free limits audit-log viewing and CSV/JSON export to the latest 30 days; it does not delete older entries. Standard can set physical retention from 30 to 730 days. A daily automatic purge removes records only after the configured retention period, independently of edition. After an upgrade, older entries may become visible and exportable again if that purge has not already removed them.

Retention settings Standard administrators can set the audit retention period; the daily purge runs automatically.

GDPR data-subject requests​

Because the app stores metadata with pseudonymous IDs and no document content, the surface area for data-subject requests is small. Use the audit log's filters and export to locate and produce relevant records. See Security & compliance.