Privacy Policy — Service Project Standards for JSM
Publisher: Matify · App: Service Project Standards for JSM (Atlassian Jira Service Management, Cloud) · Contact: mira.maty@web.de · Effective date: 18 September 2026 · Last updated: 18 September 2026
1. Who this policy covers
This policy explains how the Service Project Standards for JSM app handles data when it is installed
on an Atlassian Jira Service Management Cloud site. The site's own organisation remains the controller of
the Jira and JSM configuration and content the app reads. Matify provides the app that reads and compares
a defined, narrow subset of that configuration on the organisation's instruction.
Atlassian's own handling of your Jira data is governed by Atlassian's Privacy Policy.
2. What the app processes
Read, not stored
- Issue content of any kind. The app holds no issue-content scope and never reads a real issue's
summary, comment, attachment or custom field value.
- Display names, when the interface needs to show who a project lead, exception owner or scan actor is.
Names are resolved by the browser interface at render time and are never sent to or stored by the app.
Read and stored, as configuration
- Service project and request-type configuration: request type names, descriptions, help text, portal
groups and form fields (including hidden and preset fields); queue names, JQL and columns; workflow,
issue type, issue type screen, permission and notification scheme content (as a hash and summary, not the
full scheme body); screens and their fields; project roles and components.
- This is stored three ways: as a captured standard (the reference an admin defines),
as a per-scan snapshot of each compared project, and as a finding (a
detected deviation) or a change (what moved between two scans).
Stored by the app, tied to a person
- Atlassian account ids of: the admin who captured a standard, the admin who triggered
a manual scan, the owner and creator of an accepted exception, the admin who recorded an attestation for
an area the app cannot verify by API, and a project's lead (read from Jira on every scan).
- Atlassian account ids of project role members, but only when an administrator
explicitly turns on role-membership comparison. This setting defaults to off.
Never processed
- Email addresses, profile information, IP addresses or device data.
- Issue content, comments or attachments.
- SLA configuration, automation rules, portal branding, customer/portal permissions, JSM Forms field
definitions, or issue security scheme association — see the app's in-product Coverage tab for the current
list and the reason for each.
- Any data from products or sites other than the Jira site the app is installed on.
3. Why
The app processes this data solely to provide its function: to capture a standard from a reference
service project, to compare every assigned service project against it, to score each one, to log what
changed between scans, to manage time-limited exceptions to a deviation, and to export the result as
audit evidence. There is no profiling, no advertising, no training of models and no secondary use.
4. Where the data is held
Entirely within Atlassian's platform. The app uses Forge hosted storage, pinned to the region of the
Jira site the app is installed on. Matify operates no servers and holds no copy.
5. Sharing and international transfer
The app shares data with nobody. It has no subprocessors, makes no external network calls, and sends
nothing outside Atlassian's platform. Because data stays in the Atlassian region of your site, the app
introduces no additional international transfer.
6. Retention
| Data | Retained |
|---|
| Change log entries | 12 months by default, configurable between 3 and 24 months; older entries are deleted automatically after every scan |
| Scan snapshots (project lead, and role members if enabled) | Newest 4 scans per project by default, configurable between 2 and 12; older snapshots are deleted automatically after every scan |
| Standards, findings, exceptions, attestations | Until an administrator deletes the owning record |
7. Deletion and your choices
- An administrator can delete individual standards, exceptions, attestations and project assignments at
any time.
- Delete all app data removes everything the app stores, in one action that requires
typing a confirmation phrase.
- Uninstalling the app causes Forge to remove its storage automatically. The app never
creates, changes or deletes anything in your Jira site, so uninstalling leaves your Jira configuration
exactly as it was.
8. Personal data requests
The app implements Atlassian's personal data reporting interface. Atlassian can ask the app which
account ids it holds and when each was last updated, and can instruct the app to erase an account id. On
erasure, the app replaces that id with a tombstone value on the record that named it; it does not delete
the record itself, because the record is the audit trail of a decision that remains valid regardless of
who made it.
To exercise a right in relation to data held by the app, contact your Jira site administrator, or
write to mira.maty@web.de.
9. Security
The app runs on Atlassian-hosted compute and storage, requests only 32 permissions — all read-only
except its own storage access and the personal-data reporting interface — validates all input
server-side, checks administrator rights against Jira itself on every call, and holds no credentials or
secrets of its own. It never writes, changes or deletes anything in your Jira or JSM configuration. The
full technical statement is at the Security and Privacy link below.
10. Children
The app is a workplace administration tool and is not directed at children.
11. Changes
Material changes to this policy will be published at this URL with a new "last updated" date, and
noted in the app's release notes.
12. Contact
mira.maty@web.de — privacy questions, data requests and security reports.
Related: Security and privacy statement