Markdown Export for Jira: privacy policy

Publisher: DigiVibeTech (eenmanszaak), the Netherlands, KvK 98384848. Last updated 16 October 2026.

What the app reads. Issues, comments, change history and attachment names in Jira, using the read:jira-work permission. That's the only permission it asks for. It can't create, edit or delete anything.

Whose access it uses. Every request runs as the person using the app (asUser), so you can only export what you can already open in Jira.

Where data goes. Nowhere outside Atlassian. The app runs on Atlassian Forge and has no outbound network permissions in its manifest, so it cannot contact our servers or anyone else's. The Markdown is built in Forge and handed to your browser as a download or copy. We don't see it.

What it stores. Nothing. No Forge storage, no logs of issue content, no analytics or tracking.

Personal data. Exports contain whatever is in the issues, including names of assignees, reporters and commenters. You can replace names with "Person A, Person B" or leave them out, and mask email addresses, phone numbers, IBANs, passwords, API keys and tokens before copying the text into an AI tool. Masking is pattern-based, so check the result before you share it.

Contact. [email protected]