Privacy Policy
DataForte AB · Tant Gröns väg 54, 147 60 Uttran, Sweden Contact: hello@dataforteab.com Last updated: 13 August 2026
This policy describes how the Atlassian Marketplace app Crashdesk for Jira (“the app”) handles data. The app is built on Atlassian Forge and runs on Atlassian’s infrastructure.
What the app does with your data
Crashdesk connects a Sentry organisation to a Jira Cloud site. To do that it processes:
- Sentry issue metadata received from the webhook you configure in Sentry: issue id, title, culprit, level, environment, event count, short id and the link back to Sentry.
- Jira issue data needed to create and update issues: project key, issue type, issue key and the comments the app itself writes.
- Configuration you enter: your Sentry organisation slug, the project mapping rules, and the Sentry credentials described below.
The app does not collect analytics, does not profile users, and does not sell or share data with anyone. DataForte AB has no access to your Jira site or your Sentry organisation.
Where data is stored
All app data lives in Forge Key-Value Store, inside Atlassian’s cloud infrastructure, scoped to your installation. DataForte AB operates no servers and stores no copy of your data.
Stored per installation:
| Data | Purpose |
|---|---|
| Sentry organisation slug and API base | knowing which Sentry org and region to talk to |
| Sentry API token and webhook client secret | authenticating to Sentry, verifying webhooks — stored encrypted in Forge secret storage |
| Project mapping rules | deciding which Sentry projects create issues in which Jira projects |
| Link index (Sentry issue id ↔ Jira issue key, event count, timestamps) | deduplicating recurring errors and syncing status both ways |
| Sentry snapshot per linked Jira issue (title, level, event count, URL, short id) | rendering the Sentry panel without calling Sentry on every view |
Data sent outside Atlassian
The app calls the Sentry API at us.sentry.io, de.sentry.io or sentry.io, depending on your
organisation’s region. What is sent: your Sentry organisation slug, the Sentry issue id, your Sentry
API token for authentication, and — when you close a Jira issue — the instruction to resolve that
issue. No Jira content is sent to Sentry.
No other external service receives any data.
Personal data
The app does not intentionally process personal data. Two indirect cases are worth naming:
- A Sentry error payload may contain personal data if your own application puts it there. The app copies the issue title, culprit and level into a Jira issue in your own site.
- If a rule assigns issues to a Jira user, that user’s Atlassian account id is stored in the rule.
DataForte AB acts as a data processor for whatever passes through the app; you remain the controller. There are no sub-processors: nothing leaves Atlassian’s infrastructure except the Sentry calls described above, and Sentry is your own provider under your own agreement with them.
Legal basis for processing
Where the GDPR or UK GDPR applies, we process data on two bases: to perform the contract under which the app is provided to you (Art. 6(1)(b)), and the legitimate interest (Art. 6(1)(f)) you and we share in operating the integration you configured — creating, deduplicating and synchronising issues — which cannot be achieved less intrusively, because the app handles only the data those functions require. As processor we act on your documented instructions as controller; you determine the legal basis for the underlying error and issue data.
International transfers
Data is stored and processed within your Atlassian Cloud tenant, in the region Atlassian assigns to it. The only cross-border flow is to your own Sentry organisation, in the region you chose with Sentry (US or EU). Any transfer of personal data outside the EEA is covered by the standard contractual clauses and safeguards that Atlassian and Sentry maintain under their own agreements with you; DataForte AB introduces no additional transfer of its own.
Retention and deletion
Data lives for as long as the app is installed. Uninstalling the app deletes its Forge storage, including the encrypted credentials. Jira issues the app created remain in your Jira site, because they are your issues.
To request information or deletion at any other time, write to hello@dataforteab.com. We answer within 30 days.
Your rights
Under the GDPR you may request access to, correction of, or deletion of personal data, and you may lodge a complaint with the Swedish data protection authority (Integritetsskyddsmyndigheten).
Security and incident notification
The Sentry API token and webhook client secret are held in Forge encrypted secret storage and are never returned to the admin UI or written to logs. Incoming webhooks are verified with an HMAC-SHA256 signature when a client secret is configured. Because the app stores data only inside your Atlassian tenant, a breach of that stored data would be an Atlassian platform event handled under Atlassian’s incident process; where we become aware of an incident affecting data the app processes, we will notify you at the vendor contact on your installation without undue delay.
Children
The app is a business tool for software teams. It is not directed to children, and we do not knowingly process children’s data.
Changes
Material changes to this policy will be published on this page with a new “last updated” date.