- Overview
- Getting started
- User guide
- Admin guide
- Requester and owner guide
- Permissions and security
- Privacy and data
- Large sites
- Troubleshooting
- FAQ
- Known limitations
- Changelog
Privacy and data
What Project Blueprints stores
| Data | Contains personal data? |
|---|---|
| Blueprints and their captured snapshots (schemes, roles and members, components, versions, field contexts, selected project properties) | Yes: Atlassian account IDs of role members and component leads in the reference project (and any inside copied property values), the fixed lead and fixed role members set in the blueprint, and the admins who captured and last changed it |
| Naming & key policies and metadata forms | Only the account ID of the admin who last changed them |
| Requests and their previews | Yes: requester, approver, lead and owner account IDs, the admin who cancelled a request, the people the preview adds to roles or as component leads, and the free text people typed: purpose, metadata values and reject reasons |
| Provisioning steps and verification results | Not by design: they keep Jira object IDs, statuses and error codes; a failed step also keeps a shortened Jira error message |
| Catalog rows (one per project) | Yes: lead, owner and last reviewer account IDs, and for projects created outside the gate the creator's account ID if Jira's audit log names one |
| Reviews (attestations) | Yes: the reviewer's account ID (usually the owner), a proposed new owner, the confirming admin and the optional note |
| Ledger | Yes: actor account IDs per entry |
| Settings | The tracking work items' default assignee, if set (who changed settings is recorded in the ledger) |
| Locks, cursors, counters, scan and queue state | Mostly no. Some keys carry an account ID: short-lived permission caches, duplicate-submit guards, validation counters and bulk-action jobs, the ledger's actor mapping, and the list of account IDs reported to Atlassian |
Not stored: display names, avatars, e-mail addresses, work item content, comments, attachments, credentials and tokens. The names you see in the app are looked up from Jira when a page is shown.
Personal data
The personal data Project Blueprints stores is limited to Atlassian account IDs (of requesters, approvers, leads, owners, people chosen in user fields, role members and component leads in blueprint snapshots, fixed users, creators of projects made outside the gate, reviewers, the tracking work items' default assignee, ledger actors and admins who captured or changed blueprints and policies) and the free text people type (purpose, metadata values, reject reasons, review notes).
Don't put personal data in free text. The purpose, metadata values, reject reasons and review notes are stored as typed and are not scanned for personal data. Metadata values are also written into the new project's property com.matify.pbj.governance, and the purpose and metadata appear on the tracking work item if tracking is on. If it happens anyway, a Jira admin can open the request and choose Redact free text… (not offered while an approved request waits for or runs provisioning): the purpose, reject reason and text metadata values are replaced with [redacted] in the request, in the app's stored plan and in the governance property, and the ledger records the redaction. Jira's project description and a tracking work item are not changed; edit them in Jira.
Where it is stored
Only in Forge hosted storage on Atlassian's infrastructure: seven custom entities (blueprints, policies, requests, steps, catalog rows, attestations, ledger) and the key-value store (settings, locks, cursors, counters, and compressed copies of blueprint snapshots and previews). Storage is separate for each installation. Project Blueprints uses no Forge SQL, no Object Store and no remote storage.
| Category | Where | Notes |
|---|---|---|
| In-scope End-User Data | Forge hosted storage | Everything in the table above. Follows your Jira site's data residency and moves with it |
| Data written into Jira | Your Jira site | Jira data, not app storage (see below). It stays in Jira under your Jira site's own terms and residency |
| Out-of-scope stores | None | The app has no other data store |
- No egress: nothing is sent outside Atlassian. There are no external services, analytics, telemetry or sub-processors besides Atlassian.
- Encryption is provided by Atlassian's Forge platform.
Data written into Jira
These are your Jira data. They stay in Jira after an uninstall and after Delete all app data:
- projects created through the app, with their role members, components, versions and field-context assignments;
- project properties copied from the blueprint;
com.matify.pbj.provenance: request ID, blueprint ID, snapshot hash, requested by, approved by, approval and provisioning time, app version;com.matify.pbj.governance: owner account ID, review date, metadata values, blueprint ID, last review;- tracking work items, their comments and review reminder work items (if turned on).
Like all Jira project properties, the two com.matify.pbj.* properties can be read through Jira's REST API by everyone with Browse Projects on the project, and changed by its project admins.
How long it is kept
| Data | Kept for |
|---|---|
| Provisioning step records | 90 days after the request reached a final status |
| Requests (with purpose, metadata, reject reason) | 24 months after the request reached a final status by default (6–60 months), then pruned; their ledger entries remain |
| Previews | Deleted together with their request |
| Catalog rows of deleted projects | 24 months |
| Reviews (attestations) | 36 months by default |
| Ledger | For the life of the installation; removed only by Delete all app data or Atlassian's data lifecycle after uninstall |
| Blueprint snapshots no longer referenced | Removed by the weekly clean-up |
Shortening a retention period needs typing REDUCE RETENTION. Older records are deleted at the next weekly run.
Deleting data
Settings → Data → Delete all app data, then type DELETE PROJECT BLUEPRINTS DATA. Project Blueprints cancels its known queued jobs (other queued jobs do nothing while the deletion runs) and deletes all blueprints, policies, requests, steps, catalog rows, reviews, ledger entries and stored keys. It does not touch Jira: projects, properties and work items remain. Export the ledger and the evidence report first if you need them. This works whatever the licence state, so you can remove the data after a subscription ends.
Data the app deletes is gone from its storage. Atlassian may keep deleted copies for a limited time for recovery, as described in Atlassian's Forge documentation.
Personal-data reporting and closed accounts
Project Blueprints reports the account IDs it stores to Atlassian every week through the Forge personal data reporting API. This run continues even when the licence is inactive. Account IDs inside project-property values copied from a reference project are included when they use Atlassian's current ID format; older 24-character IDs inside such values can't be told apart from other IDs and aren't detected.
When Atlassian reports an account as closed, Project Blueprints:
- replaces that account ID everywhere in its storage with
closed-account:followed by a random token generated for that erasure (not derived from the account ID); - removes it from role members and component leads in blueprint snapshots and recalculates the hashes of affected snapshots;
- clears the owner on affected catalog rows (they get the No owner flag);
- scrubs the account ID from its own properties
com.matify.pbj.governanceandcom.matify.pbj.provenanceon affected projects; - deletes the account ID from the affected ledger entries in a way that keeps the hash chain verifiable;
- writes a
TOMBSTONEledger entry with counts only.
Free text is not scanned for account IDs or names. When a new project is provisioned, deactivated or closed accounts in the blueprint are skipped with a note.
Logs
Forge logs contain event names, IDs (for example of requests, jobs and projects), counts, error codes, HTTP status codes and correlation references. They contain no account IDs, names, project names, purposes or metadata values. Anonymous weekly demand counters (counts only) are logged. Matify sees Forge logs only as far as Atlassian makes them available to app developers; site admins can turn log sharing off.
The diagnostics file (Health → Download diagnostics) contains no personal data and no project names.
Uninstalling
Before the uninstall completes, Project Blueprints writes an UNINSTALL ledger entry and asks Forge to cancel the job of each provisioning that is running. A provisioning in progress can stop part-way, so that project may be partially set up. The stored data is retained and deleted under Atlassian's Forge data lifecycle for uninstalled apps. A reinstall starts with empty storage; Atlassian can re-link the old data only on a request made within 21 days of the uninstall. Nothing is exported or sent anywhere on uninstall, so export first what you need as evidence. Everything the app wrote into Jira stays.
Exports
Exports are built in your browser and saved on your computer. They contain account IDs, not display names, and the free text stored with requests and reviews. Handle them like any other admin data.
Contacts and policies
- Privacy policy
- Data security and privacy statement
- Privacy questions: support@matifyapps.de