Atlassian Marketplace Blueprint Automation\nDocumentation\n\nGetting started\nTroubleshooting\nSupport & policies\nPolicy\n\nPrivacy policy\nWhat data the app processes, where it lives, and how it is deleted.\nLast updated 11 October 2026\nWho we are\nBlueprint Automation ("the app") is published by NishiQA ("we", "us"). This policy explains what data the app processes and how. For questions, contact support@nishiqa.com.\n\nOur role\nThe app is an Atlassian Forge app that you install into your Atlassian Cloud site. You, the Atlassian site's organisation, are the data controller for the content you and your users put into the app. We act as a data processor on your instructions. Atlassian operates the Forge platform and storage the app uses, as a sub-processor.\n\nWhat the app processes\nContent you create: the blueprints your users author, including stage, role and dependency definitions, SLAs, the Jira issue and Confluence page templates (with any text or files a user adds), and automation rules attached to stages.\nLaunch records: for each launch, the target Jira project and Confluence space, the Jira issues and Confluence pages created, per-stage progress and SLA timestamps, and the Atlassian account identifiers of the person who launched it and the people assigned to its roles.\nActivity log: a record of blueprint and launch changes, being the action, a timestamp, the item affected, and the acting user's Atlassian account identifier.\nSettings: site-level configuration such as the administrator group, calendar and presentation preferences, synchronisation policy, and (Advanced edition) the AI provider choice.\nIntegration credentials: if an administrator or blueprint author configures a Slack or Microsoft Teams notification, the incoming-webhook URL they provide is stored with the automation rule.\nExisting content a user asks the app to copy in\nA user can build a blueprint from work that already exists: an existing Jira epic, an existing Confluence page, or a Jira project the app analyses. When they do, the app reads that content and stores the parts that become the template - an issue's description, a page's body, titles, headings, field values. That is the explicit purpose of those features; it happens only when a user asks for it and identifies the source; and the result is then held as ordinary blueprint content, exactly as though the user had typed it.\nContent the app reads but does not keep\nContent Quality Analysis reads the body of each Confluence page a launch created in order to score it against the template it came from. The project analysis reads issue summaries, dates and field values in order to find what recurs across past releases. In both cases the text is examined in memory and discarded: only the resulting score, checklist, or draft blueprint is stored.\nWhat the app does not process\nThe app does not process or store user names, email addresses, profile photos, or IP addresses. Where the interface displays a user's name, it is retrieved from Atlassian at that moment and not retained. The app does not read your Jira or Confluence content at large: every read described above is either content a user explicitly pointed it at, or content one of its own launches created.\nAtlassian account identifiers\nThe app stores Atlassian account identifiers to attribute blueprints, launches and actions. An account identifier is opaque and stable; on its own it does not reveal a person's identity, which is held by Atlassian. If a user is removed from your Atlassian organisation, Atlassian removes their personal data; identifier references that remain in stored blueprints or launch records carry no personal information.\nWhere data is stored\nAll app data is held in Atlassian's Forge hosted storage, within Atlassian's cloud infrastructure, scoped to your Atlassian site. We do not operate any servers or databases, and we do not receive a copy of your data. Data residency follows the Atlassian Forge platform.\nRetention\nThe app does not delete your data on a schedule. Blueprints, launch records and activity entries are retained until a user deletes them in the app or the app is uninstalled from your site. When the app is uninstalled, Atlassian soft-deletes the app's storage for your site immediately and permanently deletes it after a retention period set and operated by Atlassian (currently approximately 28 days), under Atlassian's data retention policy. Jira and Confluence content the app created remains in your Jira and Confluence.\nSub-processors\nAtlassian, Inc. hosts the Forge runtime and storage and provides the Jira and Confluence APIs. All app data is processed within Atlassian's platform.\nAnthropic, PBC is used only if your organisation has the Advanced edition and a site administrator has selected Anthropic as the AI provider and an API key has been configured. In that case, the text a user enters into an AI feature (and, for blueprint suggestions, blueprint names and short description extracts) is sent to Anthropic's API to generate a response. No Jira or Confluence content, attachments, personal data, or account identifiers are sent. Anthropic does not use API data to train its models. If none of these conditions is met, no data is sent to Anthropic.\nBuilding a blueprint from existing work, and Content Quality Analysis, use no AI and contact no third party. They are deterministic and run entirely inside Atlassian's platform.\nIntegrations you can enable\nIf you configure a Slack or Microsoft Teams notification, the app sends a short status message (trigger, stage name, project key, blueprint name) to the incoming-webhook URL you provide. These messages contain no Jira issue or Confluence page content. You control whether these integrations are enabled and can remove them at any time.\nYour rights\nBecause all app data is stored within your Atlassian site's Forge storage and consists of content your users created plus opaque identifiers, you can exercise access, correction and deletion directly: export a blueprint as JSON, view or delete blueprints and launch records in the app, or uninstall the app to remove all app data. For assistance, contact support@nishiqa.com.\nSecurity\nThe app runs entirely on Atlassian Forge, using the minimum set of Atlassian permissions it needs, with server-side authorisation on every state-changing operation. Credentials such as an AI API key or a webhook URL are stored encrypted or redacted in logs. The app makes no outbound network connections other than to Atlassian, to a Slack or Teams webhook you configure, or (Advanced edition, opt-in) to Anthropic's API. See the Security & data handling page for detail.\nChanges\nWe will update this policy as the app changes and post the revised version at this URL with a new last updated date. Material changes affecting how data is processed will be noted in the app's release notes.\nContact\nNishiQA, support@nishiqa.com\n\nBlueprint Automation • Privacy policy\nA factual disclosure of the app as built. Have counsel review before publishing.