Last updated: July 6, 2026
Privacy Policy
Print Cards for Jira renders Jira issues as printable cards entirely in your browser, without vendor-side storage or any external service calls.
Data the app accesses
The app reads Jira data that the current Jira user can already access: issue fields (key, summary, type, status, priority, story points, assignee, epic, due date, subtasks) plus board, sprint, and backlog membership needed to list the issues you choose to print.
How data is processed
Issue data is fetched inside the Forge app in your browser using Atlassian Forge bridge APIs and Jira REST APIs, as the current user. The app renders the data into a visible card preview and passes it to your browser's print dialog for printing or saving as PDF. All processing happens client-side within Atlassian infrastructure.
Data storage
The app does not store customer data in Forge storage, browser local storage, or any vendor backend. The card preview exists only for the active user session and is discarded when the app closes.
External sharing
The app has no external egress: it does not send Jira content to any third-party server, analytics service, or AI provider. What happens to printed cards or exported PDFs after you print or save them is under your control.
Logs and retention
The app does not intentionally log Jira issue content or end-user data. Because the app does not retain customer data, there is no app-side customer data retention period.
Contact
For privacy questions, email info@janez.tech.