MetaFrazo Sentinel

Legal: Terms of Service, Privacy Policy, Security, Data Processing Addendum, and Service Level Agreement.

Product: MetaFrazo Sentinel: Access Review & Permission Audit for Jira, an Atlassian Forge app for Jira Cloud.

Vendor: MetaFrazo, Thessaloniki, Greece.

Effective date: 2026-11-17.

Contact: support [at] metafrazo.cloud · website contact form · JSM support portal

Billing and licensing are handled by Atlassian under Paid via Atlassian; the Atlassian Marketplace Terms of Use also apply to your use of the app.

Terms of Service

1. License

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

2. Read-only toward Jira; findings are advisory

The current edition of Sentinel does not change Jira: it reads access configuration and records its own findings, permission change log, review marks and review sign-offs in its own storage. Findings are produced by documented rules and are indicators for review, not a determination that access is wrong or that the customer complies with any standard. The customer decides on, and makes, any change in Jira itself. (If a future edition adds governed changes to Jira, these terms will be updated before that capability is offered.)

3. Customer responsibilities

The customer controls who may use Sentinel by granting its custom permissions in Jira, and is responsible for exporting and retaining the evidence it needs: Sentinel’s stored data is deleted on uninstall.

4. Acceptable use

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

5. Warranties and disclaimer

The app is provided “as is” to the maximum extent permitted by law; MetaFrazo disclaims implied warranties. Coverage depends on what Jira exposes: for example, the permission change log requires a Jira plan that includes the audit log, and covers only what Jira still retained when the app was installed. Nothing here limits liability that cannot be limited by law.

6. 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.

7. Support

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

8. 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 evidence beforehand.

9. Governing law

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

Privacy Policy

1. Scope

This policy covers the Sentinel app. If you separately contact us, via our website contact form, the support portal, or support [at] metafrazo.cloud, we process the details you choose to provide (e.g. 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 organization whose Atlassian site administrator installs 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

Sentinel reads Jira access configuration (permission schemes and grants, project roles and their members, groups, the user directory’s active/inactive status, Jira application seat usage, and the Jira audit log) to show who can do what, flag access that may need review, record who changed access and when, and let authorized reviewers sign off a review. It does not read issue content. All processing and storage happen inside Atlassian’s infrastructure (Atlassian Forge compute + a per-installation Forge SQL database). There is no external server and no egress of any category, including analytics: the app makes no network call to any non-Atlassian host. Data residency follows the customer’s own Atlassian settings. There are no external sub-processors; Atlassian is the sole infrastructure provider. MetaFrazo has no access to installation data.

4. Personal data: Atlassian account IDs only

The only personal data Sentinel stores is the Atlassian account ID: in the permission change log (who made an access change, and whose access it changed), in findings (an account flagged for review, e.g. a deactivated account still holding a role; recomputed on each scan), in review marks and review sign-offs (who reviewed and who signed), and in service-account marks. Sentinel never stores names, email addresses, IP addresses, or other profile data: names are resolved for display at render time and not persisted. From the Jira audit log it keeps only account IDs, configuration identifiers and names, a fixed category/action vocabulary, and the names of changed fields, never summaries, descriptions, changed values, or IP addresses. A signer may add an optional free-text note to a sign-off; that note is customer-authored content.

5. Purpose and legal basis

Data is processed solely to provide the app’s functionality (access review, permission audit, the permission change log, and review sign-off) on the customer’s instruction (performance of the contract / the customer’s legitimate interest in access governance and compliance evidence).

6. Who can see it

Regular Jira users have no access to Sentinel. Jira administrators have full access. Other people see Sentinel data only if a Jira administrator explicitly grants them Sentinel’s custom Jira permissions: “Sentinel: view access audit” (site-wide, read-only) or “Sentinel: review project access” (one project). Authority is re-checked on the server on every request.

7. Retention

Data is stored in the customer’s per-installation database while the app is installed. Findings are replaced on each scan; the permission change log is kept beyond Jira’s own audit-log retention; review sign-offs are append-only. All app data is deleted when the app is uninstalled. App storage is not a long-term archive: export evidence (CSV, print-to-PDF) to your own records.

8. Erasure and data-subject rights

Sentinel runs a tested anonymization routine that replaces an account ID with a fixed, non-identifying tombstone everywhere Sentinel stores account IDs, while preserving the evidentiary structure (that a change happened, when, and to which configuration object; that a then-authorized person signed a review). Sentinel takes part in Atlassian’s personal-data reporting process for apps: stored account IDs are reported weekly, and accounts Atlassian reports as closed are anonymized automatically. Because only account IDs are stored, access / rectification / erasure requests are otherwise served through the customer’s Atlassian administration.

9. International transfers

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

10. Changes and contact

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

Security

Sentinel’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, not even analytics (forge eligibility is a release gate).
  • Read-only toward Jira: the current edition requests read scopes only; it cannot change Jira.
  • Data minimization: Atlassian account IDs only; a build-failing test rejects any email / display-name column; the audit-log parser drops names, emails, IP addresses, summaries and changed values (pinned by hostile-payload tests).
  • Access control: no access for regular Jira users; Jira administrators plus explicit grants of Sentinel’s custom Jira permissions. Every server call re-derives the caller’s authority and fails closed.
  • 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); append-only review sign-offs with a sha256 fingerprint of what was signed; a redacting logger.
  • Erasure: a tested anonymization routine (tombstone), driven by Atlassian’s personal-data reporting.
  • Certifications: MetaFrazo does not currently hold a formal security certification; Sentinel runs on Atlassian and operates no external infrastructure to certify.

Data Processing Addendum

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 / 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, granting its permissions, running scans, reviewing and signing off findings, viewing the permission change log) constitutes your documented instructions to process as described here.

2. Subject matter, nature and purpose

Processing of Jira access-configuration data and Jira audit-log records for the term of your subscription, until the app is uninstalled, to evaluate documented finding rules, keep a minimized permission change log, and record review marks and append-only review sign-offs, solely to provide the app’s functionality. The app is read-only toward Jira.

3. Personal data and data subjects (Annex I)

  • Categories: Atlassian account IDs only (no names, emails, IP addresses or other profile data; resolved at render time, never persisted). They are stored as: the author and the affected user of an access change (permission change log); an account flagged by a finding (recomputed each scan); the reviewer of a review mark; the signer of a review sign-off; and accounts marked as service accounts.
  • Data subjects: your Jira users whose account appears in an access change, a finding or a service-account mark, and your administrators, auditors and reviewers who mark or sign off a review.
  • Special categories: none.

4. Processor obligations

(a) process only on your documented instructions unless required by law (with notice where lawful); (b) bind authorized persons to confidentiality (MetaFrazo personnel have no access to installation data); (c) implement the measures in Annex II; (d) use only the Annex III sub-processor (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 and Atlassian’s personal-data reporting process; (f) assist with security, breach notification, and DPIAs; (g) notify you without undue delay of a personal-data breach; (h) on uninstall/termination, stored data is deleted (export evidence beforehand); (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 (RoA / no external section; read-only toward Jira; account-IDs-only minimization; server-side access control; per-installation isolation; parameterized SQL; append-only sign-offs; redacting logger; tested tombstone erasure), all enforced by automated CI gates on every release.

Annex III: Sub-processors

Sub-processorRoleLocation
Atlassian (the Forge platform, as set out in the customer’s Atlassian agreement)Cloud platform (Forge compute + Forge SQL) hosting all app dataPer Atlassian’s data residency for your instance

No other sub-processors. No external analytics, logging, or storage providers.

This DPA is available on request:

Service Level Agreement

Support via the MetaFrazo customer support portal and support [at] metafrazo.cloud, Monday to Friday, 09:00 to 17:00 Central European Time (CET/CEST), excluding public holidays. For critical issues we aim to provide an initial response within 24 hours. Scope: the Sentinel app; Jira itself and the customer’s Atlassian administration are supported by Atlassian.