Operational subprocessor
| Provider | Purpose | Data involved |
|---|---|---|
| Atlassian Pty Ltd and relevant Atlassian group entities | Jira Cloud APIs, Forge hosting, storage, authentication, logging, licensing and platform security | Authorised Jira data, app context, temporary cache, usage records, operational logs and licence information |
Communications provider
| Provider | Purpose | Data involved |
|---|---|---|
| Zoho Mail | Support, privacy, legal and security communications | Information voluntarily included by the sender in email |
Customers should avoid emailing unnecessary Jira issue data or confidential exports.
Services not processing StatusDeck Jira data in normal operation
- Google Firebase Hosting — public qtilabs.com website only
- GitHub — private source-code repository; customer data must not be placed in repositories or issues
- GoDaddy — domain registration and DNS
- PptxGenJS and jsPDF — open-source libraries executed in the browser
Changes
QTI Labs will update this page before introducing a new subprocessor that materially changes how StatusDeck customer data is processed.
Effective date: upon first public availability of StatusDeck on the Atlassian Marketplace. Review at least annually and after material product, scope, storage, subprocessor, security or legal changes.