Privacy policy — Project Blueprints for Jira
Publisher: Matify · App: Project Blueprints for Jira (Atlassian Jira Cloud) · Contact: support@matifyapps.de Effective date: 12 October 2026 · Last updated: 12 October 2026
1. Who this policy covers
This policy explains how the Project Blueprints for Jira app handles data when a Jira Cloud site installs it from the Atlassian Marketplace. The organisation that installs the app decides who may request projects, who approves them and how the app is configured. Matify provides the app, which lets the site's users request new Jira projects (spaces) from blueprints their Jira administrators approved, and creates those projects after a Jira administrator approves each request.
The app runs on Atlassian Forge. Atlassian's handling of your Jira site and of Forge hosted storage is governed by Atlassian's own privacy policy.
2. Products
The app is installed into Jira Cloud. It processes data only from the Jira site it is installed on, and no data from other Atlassian products or other sites.
3. What the app processes
Project and configuration data (read from Jira, partly stored) Project key, name, type, category, lead, description, URL and status; the scheme associations of a reference project (permission, notification, issue security, issue type, issue type screen, workflow and field scheme); project roles with their members; components; versions; selected project properties; project-scoped custom-field contexts; and, for projects created outside the app, the creator recorded in Jira's audit log.
Atlassian account IDs The app stores Atlassian account IDs — never names or e-mail addresses — of:
- people who request projects, and the project leads and owners named in requests;
- Jira administrators who approve, reject, cancel, stop or resume requests, and who create or change blueprints, policies and settings;
- members of project roles and component leads in the reference project a blueprint was captured from, and users named in a blueprint's rules;
- leads, owners and (for projects created outside the app, where Jira's audit log shows it) creators of projects in the catalog;
- owners and administrators who record project reviews or ownership changes;
- the person chosen as assignee of optional tracking work items;
- the person behind each entry of the app's tamper-evident ledger.
Display names People's display names are looked up from Jira when a page is shown and kept only in the browser for that session. Export files contain account IDs, not display names. The app does not store display names, avatars or e-mail addresses.
Group and role memberships A blueprint stores the users and groups (group ID and group name) that are members of each project role in its reference project, so that new projects get the same role members. A blueprint can be limited to certain groups; to decide whether a requester may use it, the app asks Jira which groups that person belongs to at the moment of the request and does not store the answer.
Free text Text people type into the app: the purpose of a request (up to 2,000 characters), metadata values defined by your administrators, reasons for rejecting a request, and notes on project reviews. Please do not enter personal data in these fields beyond what your organisation needs.
Not processed or stored Issue content, comments and attachments (the app reads no work items except the tracking work items it created itself), passwords, API tokens, IP addresses, device data and usage analytics.
4. Why
Only to provide the app's functions to the installing organisation: governed project requests from approved blueprints, naming and key rules, approval by Jira administrators, creating and verifying the approved project, a catalog of all projects on the site with owners and review dates, owner reviews, a tamper-evident record of who requested and who approved, evidence exports, and support diagnostics that an administrator chooses to download.
5. Where the data is stored
Only in Forge hosted storage on Atlassian's infrastructure, separate for each installation. The app uses no external storage: Matify runs no server or database of its own and has no access to the stored data.
Data residency: Forge hosted storage follows the Jira site's data residency and moves with the site. All stored data listed in section 3 is in scope. Forge application logs (section 12) are out of scope; they are operational and contain no personal data by design.
6. Sharing, egress and subprocessors
The app runs entirely on Atlassian's Forge platform; no data leaves Atlassian. It has no external connections, no remote backend and no web triggers, and uses no analytics, telemetry, error-reporting or e-mail service. Its user interface loads no external scripts, fonts or images. Exports are created in the administrator's browser and saved locally. The only subprocessor is Atlassian as the provider of Jira and the Forge platform. Matify does not sell or share data.
7. Data the app writes into your Jira site
When a Jira administrator approves a request, the app creates the project and sets it up: project details and scheme associations, project role members, components, versions, field-context assignments and selected project properties. It also writes two properties of its own on the project:
com.matify.pbj.provenance— request ID, blueprint ID, snapshot hash, the account ID of the requester, the account IDs of the approvers, approval and provisioning dates, app version;com.matify.pbj.governance— owner account ID, review date, the request's metadata values, blueprint ID, date of the last review.
Administrators can also record owners and review dates on existing projects; this writes only the com.matify.pbj.governance property. If your administrators turn on tracking work items (off by default), the app creates work items and comments in one project they choose; a tracking work item contains the requested project name and key, the requester as reporter, the purpose text, and the assignee your administrators chose. Optional review reminders are work items assigned to the project owner.
All of this is your organisation's Jira data. People who can browse a project can read its properties through Jira's REST API. It stays in Jira when the app is uninstalled or its data is deleted. The app never deletes, trashes, archives or renames anything in Jira.
8. Retention
- Requests (including purpose, metadata values and reject reasons) are kept for 24 months after they are completed; your Jira administrators can set 6 to 60 months. A weekly job deletes older requests together with their stored preview.
- The detailed step journal of a request is deleted 90 days after the request reached its final status.
- Catalog entries of projects that were deleted in Jira are kept for 24 months.
- Project reviews (attestations, including notes) are kept for 36 months by default.
- Blueprints and policies are kept until an administrator deletes them; stored blueprint snapshots that nothing refers to any more are deleted weekly.
- The ledger is kept for the life of the installation.
9. Deletion
- Delete all app data (Settings → Data, typed confirmation) deletes every stored blueprint, policy, request, catalog entry, review, ledger entry and other app record, and cancels queued jobs. It does not change Jira: projects, their properties and tracking work items remain. Export the evidence you need first.
- Shortening retention requires a typed confirmation; records older than the new period are deleted at the next weekly run.
- Data the app deletes is removed from its storage at once; Atlassian may keep a deleted copy for a limited time under its own Forge data lifecycle.
- Uninstall: the app records a final ledger entry and stops any provisioning in progress (a project may then be partly set up). Data in Forge hosted storage is retained and deleted according to Atlassian's Forge data lifecycle for uninstalled apps. A reinstallation starts with empty app storage; within 21 days of the uninstall, the old data can be re-linked to the new installation only on a request made with the customer's consent. Nothing is exported or sent to Matify on uninstall. Everything the app wrote into Jira stays.
10. Personal data requests and closed accounts
The app uses Atlassian's personal data reporting API: every week it reports the account IDs it stores. This continues even if the subscription has lapsed. When Atlassian reports an account as closed, the app replaces that account ID everywhere in its storage with a random placeholder that cannot be traced back to the account, removes the person from stored blueprint role members and component leads, clears them as owner in the catalog (the project is flagged as having no owner), updates its own two project properties on affected projects, and removes the account ID from its ledger while keeping the ledger verifiable. A count-only entry records that this happened. Free text that people typed is not searched for personal data; it is deleted with its record under the retention rules above.
Requests to access, correct or delete personal data held in the app should go to the organisation that administers the Jira site, which controls the app's data. Matify will help that organisation; contact support@matifyapps.de. Matify itself cannot see the data in your site.
11. Security
- Every function checks the signed-in person's Jira permissions on the server: administrator functions need Administer Jira, requests need the Jira permission "Request projects (Project Blueprints)" (granted to nobody when the app is installed), the project Governance page needs Administer projects on that project. If a permission cannot be confirmed, access is refused.
- Requests are closed by default. Every project needs the approval of a current Jira administrator (optionally a second, different one) on an exact preview; the app checks the approvers' permission again before it creates anything.
- A kill switch pauses all approvals and provisioning. A hash-chained ledger records who requested and approved what.
- Request data is validated on the server; text is displayed as text; exports are protected against spreadsheet formula injection.
Details: the data security and privacy statement and Permissions and security.
12. Operational logs
The app writes technical logs on the Forge platform: event names, request and job IDs, numeric project IDs, counts, error codes and HTTP status codes, and a random reference for support. They contain no account IDs, names, purpose or metadata text and no error texts returned by Jira. Once a week the app logs anonymous counts (requests submitted, approved, provisioned, projects found outside the app, active blueprints). Matify can see these logs only as far as Atlassian makes them available to app developers, and site administrators can turn off log sharing.
13. Changes to this policy
Material changes are published on this page with a new "last updated" date before they take effect.
14. Contact
Matify · support@matifyapps.de (privacy questions and requests; for security reports put "security" in the subject) · Support