---
title: "End-user data"
canonical: "https://support.appfire.com/space/ScrumPrint/3673751588/End-user%20data"
format: markdown
---
Agile Cards for Jira Cloud is built on Atlassian's Forge platform. This page classifies the data the app reads and stores as either in scope or out of scope for Atlassian's data residency program, so you can assess where your data lives.

## In-scope data

The following data is stored on Atlassian infrastructure and is subject to Atlassian's data residency controls.

| Data store | What it contains |
| --- | --- |
| **Forge SQL** | Card templates, template-to-project mappings, corkboard configurations, installation settings, internal ID sequences, and migration and installation metadata |
| **Jira entity properties** (inherited from Jira) | Print markers on work items and keys recording each user's last print |

## Out-of-scope data

The following data is not subject to Atlassian's data residency controls, either because it never leaves your browser or because it's handled by a separate, optional service.

| Data | Why it's out of scope |
| --- | --- |
| Photos of physical boards | Processed entirely in your browser. Never transmitted to or stored by Appfire. |
| Client error reports | Sent to a third-party error reporting service to help diagnose crashes. |
| Product analytics (optional) | Usage statistics, collected only if you haven't disabled analytics. |
| Contact us feedback | Submitted through the app's feedback form and handled by Appfire Support. |
| Card designer image URLs | External references only; the images themselves aren't stored by the app. |

## Personal data

Agile Cards for Jira Cloud stores no personal data of its own. Work items, users, and boards are referenced only by their Jira IDs.

## Data removal

Uninstalling the app removes its Forge SQL data and the Jira entity properties it wrote. Questions about this classification? Reach out through the [Appfire Support Portal](https://appf.re/support).