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
- Built on Atlassian Forge only: the app's functions run on Atlassian-hosted compute, and its data lives in Forge hosted storage (custom entities and the key-value store).
- No Forge remote, no external backend, no web triggers. Matify operates no server, database or service the app depends on.
- Three Forge Custom UI pages inside Jira: Apps → Project Blueprints (request a project, my requests, my projects), Jira settings → Apps → Project Blueprints (administration) and Project settings → Governance. All scripts, styles, fonts and icons come from the app's own bundle under Forge's default content security policy; the pages talk to the app only through the Forge bridge.
- Long-running work (blueprint capture, the catalog scan, provisioning, data deletion) runs in Forge queues; provisioning runs one request at a time per site. Scheduled work runs on Forge daily and weekly triggers; project events from Jira keep the catalog current.
3. Data we process
- Project and configuration data read from Jira: project key, name, type, category, lead, description, status; the scheme associations, project roles and members, components, versions, selected project properties and project-scoped field contexts of a reference project; for projects created outside the app, the creator shown in Jira's audit log.
- Input in the app: blueprints, naming and key policies, metadata forms, requests (name, key, lead, owner, category, metadata, purpose), approvals and rejections, project reviews, settings.
- Display names of people, looked up from Jira when a page is shown and kept only in the browser session.
- Group membership of the person requesting a project, checked with Jira at the moment of the request and not stored.
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
- Who may do what is checked on the server for the signed-in person, by asking Jira as the app: administration needs Administer Jira; requests need the Jira permission "Request projects (Project Blueprints)", which is granted to nobody when the app is installed; the Governance page needs Administer projects on that project; owners can act only on projects they own. An unanswered check means "not permitted". If Jira's permission check is unavailable, the app checks as the signed-in person instead, which can show Atlassian's one-time "Allow access" screen.
- Requests are closed by default. Only blueprints an administrator activated can be requested.
- Every project needs approval by a current Jira administrator, checked at the moment of approval (optionally a second, different administrator). The requester cannot approve their own request unless an administrator explicitly allows self-approval. The approver sees an exact preview; if anything changed, the approval is refused and a new preview is shown. A lead other than the requester must be confirmed. Two administrators cannot decide on the same request at once.
- Before the first write, the app re-checks that every approver is still a Jira administrator and that the approval is no older than 24 hours; otherwise it stops and asks for a new approval.
- Writes to Jira happen only on a project created under an approved request (the project, role members, components, versions, field contexts, selected properties and the app's own
com.matify.pbj.provenanceandcom.matify.pbj.governanceproperties), on the app's own governance property of existing projects when owners, review dates or reviews are recorded (or restored after the property was changed outside the app), on the app's own properties when a closed account is scrubbed or an administrator redacts a request's free text, and — if enabled — as work items and comments in the one tracking project. All write calls live in one part of the code and need a ticket created from an approved request or one of these narrow actions; an automated test enforces this. - The app never deletes, trashes, archives or renames a project, scheme or work item and never edits existing work items. The only removal it makes is of default role members on a project it has just created, when a blueprint uses exact role mode (the preview shows this removal step). A partly set-up project stays as it is; an administrator can retry the remaining steps or move it to Jira's trash.
- The kill switch pauses all approvals and provisioning: approved requests wait, and a running provisioning stops after its current step and can be retried later. Nothing is undone.
- Jira's own audit log names the app as the creator of a project; the app's hash-chained ledger and the provenance property record the people who requested and approved it. The ledger has a "Verify integrity" function.
- If the licence is inactive, the app is read-only: nothing new is requested, approved, created or scanned. Open requests can still be withdrawn or cancelled, a running provisioning can be stopped, a request's free text can still be redacted, and all app data can still be deleted.
12. Data retention
- Requests: 24 months after the request reached a final status by default (6 to 60 months); their stored preview is deleted with them.
- Step journal of a request: 90 days after its final status.
- Catalog entries of projects deleted in Jira: 24 months.
- Project reviews: 36 months by default.
- Blueprint snapshots nothing refers to any more: deleted weekly.
- Ledger: for the life of the installation.
Shortening retention requires a typed confirmation; older records are deleted at the next weekly run.
13. Data deletion
- Delete all app data (Settings → Data, typed confirmation) cancels queued jobs and deletes every stored blueprint, policy, request, catalog entry, review, ledger entry and other app record. It does not change Jira. Export the evidence you need first.
- Data the app deletes is removed from its storage at once; Atlassian may keep a deleted copy for a limited time for recovery, under its own Forge data lifecycle.
- On uninstall the app writes a final ledger entry and stops any provisioning in progress (a project may then be partly set up). Stored data is then retained and deleted according to Atlassian's Forge data lifecycle for uninstalled apps. A reinstall starts with empty app storage; Atlassian can re-link the old data only on a request made with your consent within 21 days of the uninstall.
- Projects and everything the app wrote into Jira are your Jira data and stay after uninstall or 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:
- server-side permission checks on every request that fail closed,
- strict validation of every request payload, and safe building of Jira API paths,
- length limits and a bounded-backtracking check for administrator-defined patterns (a stored pattern that fails the check is never run),
- no collected credentials, tokens or secrets,
- text rendered as text in the interface, and CSV exports protected against formula injection,
- a release process that deploys one tagged build only after automated checks pass (no external egress, remote or web trigger, exactly the seven scopes listed, the request permission granted to nobody by default, tests and builds).
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.