🔒 Privacy Policy – Issue Delivery Report

🔍 What We Collect

Issue Delivery Report is designed to be lightweight, read-only, and privacy-conscious. We only access the minimum data necessary for generating flow metrics:

• Issue status history
  ↳ pulled via expand=changelog to build a transition timeline

• Issue metadata
  ↳ includes created, key, and status.name to determine total time

• User display names
  ↳ shown alongside status transitions for audit clarity

✅ This data is accessed only while viewing the current issue and is never stored externally.

📦 What We Store

We do not store any user or project data outside your Jira Cloud environment.

Nothing leaves Jira. Nothing is persisted.

The app does not use issue properties or any permanent storage. All computed data — including Flow Efficiency, timeline breakdowns, and sprint logic — is processed in-memory during the current session.

💡 Any exported data (CSV, JSON, Markdown, TXT) is generated in the user's browser and downloaded locally.

❌ What We Don’t Do

• 🚫 No external APIs

• 🚫 No telemetry or analytics

• 🚫 No tracking of user activity

• 🚫 No access to comments, attachments, or descriptions

• 🚫 No persistent writes to Jira (except exports, if user initiates them)

🔐 Data Protection

Issue Delivery Report runs 100% inside the Atlassian Forge platform, which enforces:

• Secure sandboxing for every app

• Isolation by user and instance

• Zero custom backend infrastructure

• Encryption of all data in transit and at rest (handled by Atlassian)

You are always in control. Data only moves when you click Export.

🌍 GDPR & Compliance

Because we don’t collect or store personal data:

• ✅ Fully GDPR-ready

• ✅ CCPA-compliant

• ✅ Aligned with ISO 27001 standards (via Atlassian infrastructure)

You remain fully compliant under Atlassian’s platform security and privacy guarantees.

📩 Contact

Have questions about data use or privacy?

Email: support@typeswitch.net
We’ll respond within 48 hours.