1. Zero External Servers (Runs on Atlassian)
Customer Context Card is built 100% natively on the Atlassian Forge platform (nodejs24.x runtime and native Forge UI Kit). All application logic executes strictly within Atlassian's cloud infrastructure, and all saved customer and organization fields are stored exclusively inside encrypted, tenant-isolated Atlassian Forge Storage tied to your Jira Cloud instance.
No external egress domains are configured in the application manifest. ClearDesk Labs has no backend access to your Jira tenant or stored customer records.
2. Data Processed by the App
The app requests only three minimal, least-privilege Forge permission scopes:
| Category / Scope | How It Is Used |
|---|---|
Jira Issue & Organization Metadataread:jira-work |
Read on demand via official Jira Cloud REST APIs to identify the ticket reporter, linked JSM Organization, and up to 5 recent tickets by the same reporter. Not exported or stored externally. |
Jira User & Admin Checksread:jira-user |
Used to verify Jira Administrator permissions and to match customer email addresses to Jira Account IDs when an admin runs a Bulk CSV Import. |
User-Entered Profile Fieldsstorage:app |
Custom customer and organization fields (notes, tiers, URLs, dropdown values, and CSV-imported attributes) stored in Atlassian Forge Storage, keyed by Jira Account ID or Organization ID. |
3. Data Retention & Deletion (GDPR / Swiss FADP)
- Individual 1-Click Erasure: Jira Administrators can permanently erase any customer or organization record at any time via the built-in Erase Customer Data (GDPR) and Erase Organization Data actions directly inside the issue context panel.
- App Uninstallation: Uninstalling the app immediately revokes all access tokens; Atlassian automatically purges tenant-scoped Forge Storage data according to Atlassian Cloud retention policies.
- Data Residency: Because all compute and storage run natively on Atlassian Forge, data residency inherits the Atlassian Cloud residency configuration of your Jira site where supported by Forge.
4. Subprocessors
The sole infrastructure provider is Atlassian Pty Ltd (Atlassian Forge Cloud Platform). ClearDesk Labs uses no other subprocessors, hosting providers, error-tracking SaaS tools, or marketing cookies inside the app.
5. Application Security Controls
- Role-Based Governance: Jira Administrators control whether support agents can edit profile data or have read-only access.
- Input & URL Sanitization: All text fields are bounded and sanitized; URL fields restrict protocols strictly to safe
https://andhttp://links (blockingjavascript:anddata:payloads). - No Write Access to Jira Issues: The app holds read-only Jira scopes and never modifies your tickets, comments, or user accounts.
6. Contact
For privacy inquiries, DPA questions, or security reviews, contact support@cleardesklabs.com.