Matify/Project Blueprints for Jira

Data security and privacy statement — Project Blueprints for Jira

Publisher: Matify · App: Project Blueprints for Jira (Jira Cloud) · Contact: support@matifyapps.de · Last updated: 12 October 2026

1. Overview

Project Blueprints for Jira lets the right people request new Jira projects (spaces) from blueprints that Jira administrators approved. A Jira administrator approves an exact preview of each project; the app then creates the project, sets it up, verifies it and records who requested and who approved it. It also keeps a catalog of all projects on the site with owners and review dates. It is an Atlassian Forge app. This statement explains, technically and plainly, what the app processes, where it keeps it and how it is protected. The formal policy is the privacy policy.

2. Hosting and architecture

3. Data we process

The app does not read or store work item content, comments or attachments.

4. Personal data

The app stores Atlassian account IDs for longer than 24 hours: requesters, project leads and owners, approvers and other administrators acting in the app, members of project roles and component leads captured in blueprints, creators of projects found outside the app, reviewers, the assignee of optional tracking work items, and the person behind each ledger entry.

It also stores free text people type: request purpose (up to 2,000 characters), metadata values, rejection reasons and review notes. Please don't enter personal data in these fields beyond what your organisation needs. It stores no display names, avatars or e-mail addresses.

5. Data storage

All stored data is in Forge hosted storage on Atlassian's infrastructure: seven custom entities (blueprints, policies, requests, provisioning steps, catalog, reviews, ledger) and the key-value store (settings, locks, cursors, counters, and compressed blueprint snapshots and previews). No other storage is used.

6. Tenant isolation

Forge hosted storage is partitioned per installation by the platform. The app uses no global or shared storage across customers, keeps no customer data between invocations outside that storage, and its logs contain no identifiers of other installations.

7. Data residency

Forge hosted storage follows the Jira site's data residency and moves with the site. All stored data in sections 4 and 5 is in-scope end-user data held there. Projects, properties and work items the app writes into Jira are Jira data under your site's own residency. Forge application logs are operational data outside that scope and contain no personal data by design.

8. External data egress

None. The app runs entirely on Atlassian's Forge platform; no data leaves Atlassian. It declares no external domains, no remote backend and no web triggers. It calls only Jira's REST API of your site and Forge platform services (storage, queues, the personal data reporting API, the licence API). Exports are created in the administrator's browser and saved locally.

9. External services and subprocessors

None besides Atlassian (hosting, storage, the Forge platform). No analytics, telemetry, error-reporting, e-mail or content delivery service is used.

10. Permissions and scopes

Seven classic scopes: read:jira-work, manage:jira-configuration, manage:jira-project, read:jira-user, storage:app, report:personal-data, write:jira-work. Creating company-managed projects requires the Administer Jira permission, so with the two manage scopes Jira gives the app user Jira-admin-equivalent permissions (verified: Administer Jira, Administer projects, Bulk change). Jira's global permission settings cannot narrow the app user's own power; the app's own controls (section 11) decide what it does. write:jira-work is used only for optional tracking work items and comments in one project your administrators choose. No board scopes and no webhook scope are requested. Each scope is explained in Permissions and security.

11. Read/write model

12. Data retention

Shortening retention requires a typed confirmation; older records are deleted at the next weekly run.

13. Data deletion

14. Personal data requests

The app reports the account IDs it stores to Atlassian every week through the Forge personal data reporting API; this continues when the licence has lapsed. For a closed account it replaces the account ID with a random closed-account: placeholder everywhere in its storage, removes the person from stored blueprint role members and component leads, clears them as project owner (the project is flagged as having no owner), updates its own two project properties on affected projects, removes the account ID from the ledger while keeping the ledger verifiable, and records a count-only entry. Free text that people typed is not searched; it is deleted with its record under the retention rules, and a Jira administrator can redact a request's free text (purpose, rejection reason and text details) on the request page. Other requests: the organisation that administers the Jira site, or support@matifyapps.de.

15. Logging

Forge logs contain event names, request and job IDs, numeric project IDs, counts, error codes, HTTP status codes and a random reference for support. They contain no account IDs, names, purpose or metadata text, and no error texts from Jira: a failed call is logged with its error code and HTTP status only. Once a week the app logs anonymous counts. The diagnostics file an administrator can download contains no personal data and no project names or keys.

16. Transport and platform security

All traffic between the app, Jira and the browser runs inside Atlassian's platform: the app's functions call Jira through the Forge runtime, and the pages talk to the functions through the Forge bridge. Hosting, storage, transport encryption and infrastructure security are provided by Atlassian's Forge platform; Matify adds no encryption of its own. What Matify adds:

No compliance certification (such as SOC 2 or ISO 27001) is claimed for the app or for Matify.

17. Security contact

support@matifyapps.de with "security" in the subject, or the support page. Please don't report vulnerabilities in a public tracker. Matify follows Atlassian's security requirements for Marketplace apps and notifies affected customers and Atlassian of a security incident affecting customer data.

18. Privacy policy

Privacy policy for Project Blueprints for Jira

19. Documentation

Project Blueprints for Jira documentation · Known limitations · Privacy and data · Support

20. Last updated

12 October 2026.