/
πŸ”’ Privacy Policy – Stuck Issues Guard

πŸ”’ Privacy Policy – Stuck Issues Guard

πŸ” What We Access

Stuck Issues Guard accesses only the data required to evaluate workflow guardrails.

This includes:

πŸ“„ Issue Data

  • Issue key

  • Status

  • Labels

  • Assignee

  • Due date

  • Created / Updated timestamps

πŸ”„ Status History (when required)

  • Status transitions

  • Transition timestamps

Used to evaluate:

  • Time-in-status

  • Idle time

  • Transition loops

  • Reopen frequency

πŸ‘€ Project Metadata

  • Project key

  • Project lead (for optional notifications)

This data is accessed through Jira REST API v3 and only within your Jira Cloud instance.

πŸ“¦ What We Store

Unlike read-only tools, Stuck Issues Guard uses Forge storage to persist:

  • Guardrail configuration per project

  • Threshold values

  • Scope filters

  • Notification settings

  • Evaluation state per issue

  • Last trigger timestamps

  • Cooldown tracking

  • Audit history

  • Scan metadata

All stored data remains inside Atlassian Forge storage.

No data is stored externally.

✏️ What We Write to Jira

If enabled by configuration, the app may:

  • Add structured comments

  • Mention assignee or project lead

  • Add or remove managed labels

  • Update a custom issue field ("Stuck Issues Guard")

These writes occur only when guardrail conditions change.

No hidden or background modifications occur beyond configured actions.

❌ What We Don’t Do

🚫 No external APIs
🚫 No telemetry or analytics
🚫 No tracking of user browsing behavior
🚫 No access to attachments
🚫 No processing outside Forge runtime
🚫 No cross-instance data sharing

The app does not send data to third-party services.

πŸ” Data Protection

Stuck Issues Guard runs entirely inside the Atlassian Forge platform.

Forge provides:

  • Secure sandboxed execution

  • Instance isolation

  • OAuth2-scoped Jira API access

  • Encryption in transit and at rest

  • No direct database access

  • No custom external infrastructure

Runtime:

nodejs22.x

All evaluation and storage occur inside Atlassian’s cloud environment.

🌍 GDPR & Compliance

Because:

  • No data leaves Atlassian infrastructure

  • No external processing occurs

  • No analytics or tracking are performed

Stuck Issues Guard aligns with:

βœ… GDPR requirements
βœ… CCPA principles
βœ… Atlassian Marketplace data security standards

All infrastructure-level compliance (ISO 27001, SOC 2, etc.) is provided by Atlassian Forge.

🧼 Data Removal

When the app is uninstalled:

  • Scheduled evaluation stops

  • Queue processing stops

  • Stored guardrail configuration is deleted

  • Stored audit data is removed

No residual external data remains.

πŸ“© Contact

If you have questions regarding privacy or data handling:

Email: support@typeswitch.net

We aim to respond within 48 hours.