Access Governance for Jira · Version 1.0 · Last updated 15 June 2026
Your use of Access Governance for Jira is governed by the
Bonterms Cloud Terms (Version 1.0),
incorporated by reference, as supplemented by the Cover Page below. Capitalized terms not defined here
have the meanings given in the Bonterms Cloud Terms.
Name of Agreement
“Cloud Service Agreement between Customer and Kade Schemahorn (Access Governance for Jira)
dated as of the Effective Date.”
Key Terms
Overview
Access Governance for Jira is a cloud application for Atlassian Jira Cloud, built on Atlassian
Forge. It helps Jira administrators see who can do what, preview the impact of permission changes,
identify inactive or reclaimable licenses, and run access reviews. The Cloud Service runs entirely
on Atlassian’s infrastructure using read-only permissions and stores no Customer Data outside
the Atlassian platform.
Effective Date
The date Customer installs the Cloud Service via the Atlassian Marketplace (click-through
acceptance).
Governing Law
The State of North Carolina, United States of America.
Courts
The state and federal courts located in Durham County, North Carolina.
Initial Order
Not applicable. Orders, billing, and payment are administered by Atlassian through the Atlassian
Marketplace; there is no separate order form.
Attachments
Acceptable Use Policy: None / not applicable.
Support Policy:Support (email support@citizenkade.com).
The Agreement is entered into by Customer’s installation of the Cloud Service through the
Atlassian Marketplace; such installation constitutes acceptance of this Agreement in lieu of
signatures.
All ordering, licensing, invoicing, payment, renewals, cancellations, and refunds are
administered by Atlassian through the Atlassian Marketplace; Provider does not issue Orders to,
invoice, or refund Customer directly. Where the Bonterms Cloud Terms or DPA reference an
“Order,” “Fees,” “Subscription Term,” or refunds, those matters
are administered through Atlassian’s Marketplace terms.
Customer Personal Data is stored solely within Atlassian-hosted Forge storage; deletion is
effected through the Atlassian Forge platform upon uninstallation, and Provider’s deletion and
certification obligations (including under DPA Section 8) are satisfied by, and limited to, the
Atlassian platform’s data-deletion behavior.
Provider
Kade Schemahorn, Owner (sole proprietor), “Access Governance for Jira”
Notice email: legal@citizenkade.com
101 Short St, Chapel Hill, NC 27517, United States
Acceptance occurs on installation through the Atlassian Marketplace (click-through);
wet signatures are not collected.