Legal
Provider Specific Terms
Provider terms supplementing the Bonterms Standard End User Agreement.
1. Standard agreement
The Marketplace listing selects the Bonterms Standard End User Agreement (Version 1.0). These Provider Specific Terms are a separate supplement. Atlassian supplies the Marketplace contracting process; this page requires no separate acceptance.
The standard agreement governs other contractual matters, including liability. Mandatory law continues to apply.
Source: Bonterms Standard End User Agreement, sections 3.3, 14 and 19.2 · Retrieved 6 October 2026.
2. Provider and support
Provider: RELMOS AG; address: Weieracherstrasse 4, CH-8184 Bachenbülach, Switzerland; UID: CHE-376.329.563. Support, privacy and security reports: support@relmos.net.
English support operates Monday–Friday, 09:00–17:00 Europe/Zurich, excluding Swiss public holidays. A first substantive response within two Swiss business days. Critical security reports are escalated immediately on receipt. See the support SLA and security policy. Service requests are handled only in writing by email.
3. Governing law and courts
Swiss law applies. The agreed courts are in Bülach, Switzerland, as the provider-specific law and courts under section 19.2 of the standard agreement.
4. Data processing and DPA
For app processing, the provider acts as a GDPR processor solely on the customer’s instructions within Atlassian Forge. Anchor Audit, JQL Stabilizer and Page Properties Check read content with the permissions of the person using them. Page Acknowledgements reads pages, groups and page markers with the acting person’s permissions and checks their editing permission before every management or report action. It checks whether other recipients can open a page, and reads page versions and availability in its weekly check, as the app. It does not determine independent purposes and is not a GDPR controller for that processing. The corresponding CCPA roles are service provider, not business. There is no app-controlled storage outside Atlassian and no content logging. Page Acknowledgements provides CSV and summary text to copy in the browser; Anchor Audit, JQL Stabilizer and Page Properties Check have no app export.
Anchor Audit and JQL Stabilizer store only identity-free monthly usage totals in Forge. Page Properties Check stores site-wide check schemas, their index, short mutation leases and aggregate counters without account IDs. Page bodies, extracted values and results are transient; schema free text may contain personal data supplied by users. The privacy policy describes the categories; voluntary support records are separate.
Page Acknowledgements stores recipient, confirming-reader and request-creator account IDs; page, space and group IDs; version and round numbers; times; counts and technical recovery/coordination information in installation-scoped Forge storage at Atlassian. Account IDs are personal data. No names, email addresses, avatars, page titles, group names or page content are stored in records or app logs. The purpose is to request and record version-specific acknowledgements, display permission-checked status and support privacy requests. Names and page titles are retrieved only for a current display or browser CSV copy.
Only editors manage and see reports, with current page editing permission checked before each action. Readers see only their own requests and confirmations; hidden pages contribute a count without titles. Only people who can open the page count as open; an inconclusive access check appears separately as Access not checked. The request creator’s deletion route and Confluence administrator privacy settings are separate from report access. Data stays in Atlassian, with Atlassian as the sole direct app subprocessor. The app writes only page-marker properties on explicit actions, never page text; it provides CSV text to copy in the browser and sends no automatic reminders.
DPA available on request from support@relmos.net. The App Data Processing Addendum is the separately identified provider DPA incorporated under standard agreement section 3.3. It contains the processing details and obligations, including confidentiality, subprocessors, assistance, audits and deletion. Atlassian’s Forge DPA governs platform subprocessing and is separate.
Hosting and data residency follow Atlassian. The provider in Switzerland receives no customer app data. The Forge DPA supplies the applicable platform transfer safeguards, including EU Standard Contractual Clauses; Switzerland has EU adequacy under GDPR Article 45.
Source: Atlassian Forge DPA · Retrieved 6 October 2026.
Source: European Commission adequacy decisions · Retrieved 6 October 2026.
5. Deletion and uninstall
Anchor Audit, JQL Stabilizer and Page Properties Check retain only identity-free usage totals beyond the open session, alongside saved check schemas in Page Properties Check; closing or reloading discards session results. Confirmed JQL changes remain in Jira. For all four apps, Atlassian retains Forge-hosted data for 28 days after uninstall: minimum 28 days, maximum 28 days. Reinstallation does not restore data automatically. With customer consent, a relink/recovery request must be raised within 21 days. This is a request deadline, with no immediate physical-erasure deadline promised by the app. Review or delete shared checks before uninstall; Anchor Audit, JQL Stabilizer and Page Properties Check have no app export.
Page Acknowledgements records are never deleted automatically because a page is deleted, moved to trash or restricted. The app marks pages it cannot see; it cannot reliably distinguish a restriction from deletion. Closing a request, cancellation and license expiry keep its records. A request creator can use Delete records in Requests I manage; an editor can use Delete acknowledgement records on the page. Confluence admins can explicitly delete records on pages unavailable to the app for at least 30 days, and find or delete a person’s records across all pages. An Atlassian privacy-report response of closed triggers erasure of that account’s recipient records, confirmations, creator references and temporary recovery references. Weekly processing and deletions are bounded and may need continuation. Temporary recovery records are removed when an operation completes or when an interrupted operation is recovered; they are distinct from acknowledgement history. Remove page markers before uninstalling; this keeps records, and pages the admin cannot edit or copied pages without a saved request may retain markers. Forge retains hosted data for 28 days after uninstall. Reinstallation does not restore it automatically; a recovery request with customer consent must be raised within 21 days. Customer-created CSV and summary copies remain under the customer’s control.
Source: Forge Storage: Data recovery for apps with hosted storage (updated 28 September 2026) · Retrieved 11 October 2026.
6. Standard agreement source and licence
Bonterms Standard End User Agreement (Version 1.0), © 2025 Bonterms, Inc., is supplied through Atlassian under CC BY-ND. The unchanged standard is linked, not reproduced or modified here. These Provider Specific Terms are separate provider text.
Source: Atlassian: Standard End User Agreement and its licence · Retrieved 6 October 2026.