MetaFrazo Label Curator

1. License

Subject to a valid subscription (including any free trial), MetaFrazo grants the customer a non-exclusive, non-transferable right to use Label Curator within its Atlassian site for its internal business purposes.

2. Governed writes: customer responsibility

Label Curator modifies Jira labels only through a governed path: every change is admin-initiated, dry-run-previewed, explicitly confirmed, recorded in the append-only audit ledger before it is applied, and reversible. The customer is responsible for the changes its administrators choose to apply; the dry-run preview is provided so those changes can be reviewed first. (The launch edition is read-only; governed writes are an Advanced capability.)

3. Acceptable use

The customer will not misuse the app, attempt to circumvent its licensing or security controls, or use it unlawfully.

4. Warranties and disclaimer

The app is provided “as is” to the maximum extent permitted by law; MetaFrazo disclaims implied warranties. Nothing here limits liability that cannot be limited by law.

5. Limitation of liability

To the maximum extent permitted by law, MetaFrazo’s aggregate liability is limited to the fees paid for the app in the 6 months preceding the claim; neither party is liable for indirect or consequential loss.

6. Support

Best-effort support via the MetaFrazo JSM portal and support [at] metafrazo.cloud (see the Service Level Agreement below).

7. Term and termination

These terms run for the duration of the subscription. On uninstall or termination, the app’s stored data is deleted; export any audit evidence beforehand.

8. Governing law

These terms are governed by the laws of Greece, and the competent courts of Thessaloniki, Greece have exclusive jurisdiction.

1. Scope

This policy covers the Label Curator app. If you separately contact us, via our website contact form or support [at] metafrazo.cloud, we process the details you choose to provide (for example your name, email, and message) solely to respond to you. That is a separate flow from the app, which sends no data to us (see section 3).

2. Roles

The customer (the Atlassian site administrator installing the app) is the data controller. MetaFrazo is a data processor acting on the customer’s documented instructions. A Data Processing Addendum is below and available on request.

3. What we process, and where: Runs on Atlassian

Label Curator reads Jira label metadata (labels, usage counts, per-project breakdown, issue keys) to detect hygiene issues and preview or apply cleanups. All processing and storage happen inside Atlassian’s infrastructure (Atlassian Forge compute plus a per-installation Forge SQL database). There is no external server and no egress: the app makes no network call to any non-Atlassian host. Data residency follows the customer’s own Atlassian settings. There are no external subprocessors; Atlassian is the sole infrastructure provider.

4. Personal data: account IDs only

The only personal data stored is the Atlassian account ID of an administrator who performs a governed action (a cleanup, or an allowlist or exception entry). We never store names, email addresses, or other contact or profile data: those are resolved for display at render time and not persisted. In the launch (read-only audit) edition, no personal data is stored at all.

5. Purpose and legal basis

Data is processed solely to provide the app’s functionality (detecting label issues, previewing changes, applying governed cleanups, and maintaining the audit ledger) on the customer’s instruction (performance of the contract, or legitimate interest in taxonomy governance).

6. Retention

Scan results, findings, and snapshots are stored in the customer’s per-installation database and replaced on each scan; the append-only audit ledger is retained for the evidentiary record. All app data is deleted when the app is uninstalled. App storage is not a long-term archive: audit evidence is exported out (download or Confluence) at period close.

7. Erasure and data-subject rights

An administrator can erase an individual’s personal data on request via a tested anonymization routine: it replaces the account ID with a non-identifying tombstone token everywhere it is stored (the ledger actor, and governance owner plus justification), while preserving the evidentiary fact that a then-authorized admin acted. Because only account IDs are stored, access, rectification, and erasure requests are served through the customer’s Atlassian administration and this routine.

8. International transfers

None beyond Atlassian’s infrastructure; the app performs no independent transfer of personal data.

9. Changes and contact

Material changes will be posted on this page. Questions: support [at] metafrazo.cloud or the MetaFrazo support portal.

Label Curator’s security posture is enforced by automated gates on every release:

• Runs on Atlassian: all compute and storage inside Atlassian; no external section in the app manifest; no network call to any non-Atlassian host (the Forge eligibility check is a release gate).
• Data minimization: Atlassian account IDs only; a build-failing test rejects any email or display-name column.
• Tenant isolation: a separate, per-installation Forge SQL database, namespaced by Atlassian, with no cross-installation aggregation.
• Integrity: parameterized SQL only (hostile input stays inert); an append-only audit ledger whose action facts are immutable; a redacting logger.
• Erasure: an admin-initiated, tested anonymization routine (tombstone tokens).
• Certifications: MetaFrazo does not currently hold a formal security certification. Label Curator’s Runs-on-Atlassian architecture means it operates no external infrastructure to certify. Any certification will be stated here only once it is actually held.

This DPA forms part of the agreement between the parties. Where the app is distributed via the Atlassian Marketplace, the Atlassian Marketplace Partner Agreement and Atlassian’s own data-protection terms also apply; nothing here overrides your agreement with Atlassian for the underlying platform.

Processor: MetaFrazo, Thessaloniki, Greece (“Processor”, “we”). Controller: the customer, the Atlassian site administrator that installs the app (“Controller”, “you”).

1. Roles

You are the data controller; we are a data processor acting only on your documented instructions. Using the app in the ordinary way (installing it, running scans, applying governed cleanups) constitutes your documented instructions to process as described here.

2. Subject matter, nature, and purpose

Processing of Jira label metadata for the term of your subscription, until the app is uninstalled, to detect label-hygiene issues, preview changes, apply governed cleanups, and maintain the append-only audit ledger, solely to provide the app’s functionality.

3. Personal data and data subjects (Annex I)

• Categories: Atlassian account IDs only (no names, emails, or other profile data; resolved at render time, never persisted; none at all in the read-only launch edition).
• Data subjects: your Jira administrators whose account ID is recorded when they perform a governed action.
• Special categories: none.

4. Processor obligations

We will: (a) process only on your documented instructions unless required by law (with notice where lawful); (b) bind authorized persons to confidentiality; (c) implement the measures in Annex II; (d) use only the Annex III subprocessor (Atlassian), no other, and no egress of personal data to any non-Atlassian host, with notice of any intended change and a right to object; (e) assist with data-subject requests, principally via the tested anonymization routine; (f) assist with security, breach notification, and DPIAs; (g) notify you without undue delay of a personal-data breach; (h) on uninstall or termination, delete stored data (export evidence beforehand); and (i) make available information reasonably necessary to demonstrate compliance, consistent with the Atlassian platform’s constraints.

5. International transfers

None beyond Atlassian’s infrastructure. Data residency follows your own Atlassian settings; the app performs no independent transfer and holds no data outside Atlassian.

Annex II — Technical and organizational measures

As listed under Security above (Runs on Atlassian, with no external section; account-IDs-only minimization; per-installation isolation; parameterized SQL; append-only immutable ledger; redacting logger; tested tombstone erasure), all enforced by automated CI gates on every release.

Annex III — Subprocessors

No other subprocessors. No external analytics, logging, or storage providers.

A counter-signed copy of this DPA is available on request:

This section sets out the support commitments for MetaFrazo Label Curator: how to reach us, our target response time, and our support hours.

1. Support channels

Submit and track support requests through our customer support portal, or email support [at] metafrazo.cloud. Every request is tracked as a ticket, and we respond on that ticket.

2. Target response time

For critical issues, the app is unavailable or a core function is broken with no reasonable workaround, we aim to provide an initial response within 24 hours. Other requests are handled in turn during support hours. Response time is the time to a first human reply, not a guarantee of resolution time.

3. Hours and days of operation

Support is staffed Monday to Friday, 09:00 to 17:00 Central European Time (CET/CEST), excluding public holidays. Requests received outside these hours are addressed on the next support day.

4. Scope

These targets are measured during support hours. They do not apply to issues caused by factors outside our reasonable control, including outages of Atlassian or other third-party services. This SLA describes our service-level targets; it does not override the Atlassian Marketplace Agreement or the Terms above.