Subprocessors
Effective [date of publication]
| App | TuneCraft: Automation & Site Cleanup, a Jira Cloud app built on Atlassian Forge |
|---|---|
| Marketplace listing | Not listed yet. TuneCraft is not on the Atlassian Marketplace yet, and its app key will be added here when it is. |
| Forge app ID | ari:cloud:ecosystem::app/facece90-dfd5-4792-9bff-6a5bd061a341 |
| Vendor | Plugincraft Software Inc., a company incorporated under the laws of Québec, Canada |
The short version
- TuneCraft runs only on Atlassian (Runs on Atlassian, no egress).
- Atlassian is the only subprocessor.
- The app has no analytics, logging or AI service outside Atlassian.
Subprocessors of app data
| Subprocessor | What it does for the app | Data | Location |
|---|---|---|---|
| Atlassian | Runs Jira Cloud and the Forge platform on which TuneCraft runs: its functions, its storage (Forge SQL), its scheduled and queued jobs, its logs, the web trigger that receives the automatic scan, and Rovo for the AI helper. | Everything the app stores and processes. See Data Handling. | Your Jira site's data residency location for Forge storage. App logs are not kept there. |
Atlassian is also the provider of your Jira site, so its handling of your data is covered by your organization's agreement with Atlassian and by Atlassian's privacy policy.
No other recipients of app data
The app declares no outside network access, remotes or Connect modules, and a test fails the build if any is added. Its one web trigger receives the automatic scan from a sender the customer runs, and answers with fixed replies. It uses no outside analytics, logging or AI service. Plugincraft has no servers of its own. So no other company receives the data the app stores.
Two things cross Atlassian's boundary only when a customer chooses. If a Jira admin turns on the automatic scan, a sender the customer runs pushes the scan into the app; data goes in, not out. The customer chooses where the sender runs: on its own systems, or as a scheduled job in ScriptRunner Cloud, a script app from another publisher that the customer has installed on its Jira site, in which case that app reads the flows' real text and holds the customer's API token under the customer's own agreement with that publisher. And an admin can send us a support bundle.
Providers for Plugincraft's own business
Plugincraft uses providers for its website, request logs, email and accounting. They are not subprocessors of app data. They receive app-related data only if a customer writes to us or sends us a support bundle. They are described in sections 1, 4 and 5 of the privacy policy of this website.
Changes
If Plugincraft ever adds a subprocessor of app data, we will update this page before that subprocessor receives any data. Questions: write to info@plugincraft.ca.