Legal

Subprocessors and data flows

The app data path and separate website and support channels.

Version 1.0 · Effective 6 October 2026

Responsible provider

RELMOS AG · Weieracherstrasse 4, CH-8184 Bachenbülach, Switzerland. Data questions: support@relmos.net.

Direct subprocessor inventory

App processing: one identified direct subprocessor
ProviderPurposeData and location
AtlassianForge compute, Jira/Confluence APIs and hosted app storage.Authorised transient content. Anchor Audit, JQL Stabilizer and Page Properties Check store identity-free monthly usage totals. Page Properties Check also stores shared configuration and technical metadata without account IDs. Page Acknowledgements stores personal account IDs and version-specific acknowledgement records in Forge. Storage residency follows the host product. Email support is separate from app processing.

This lists relmos’s direct app service provider, including its infrastructure supply chain through Atlassian’s subprocessor list and Atlassian’s Forge DPA.

App data flows

  1. Anchor Audit: user → Forge → Confluence → user session. Read visible pages and targets, return digests and findings. Anchor Audit stores only identity-free monthly usage totals in Forge.
  2. JQL: user → Forge → Jira → user session. Read visible catalogs/filters and validate proposals. After explicit confirmation and eligibility checks, Apply/Revert updates an owned Jira filter. Undo history stays only in the open session.
  3. Page Properties Check: user → Forge → Confluence → user session. Read visible tables; findings and extracted values are not persisted. Shared schemas, their index, leases and aggregate hourly and monthly counters use site-scoped Forge storage without account IDs. Schema free text is shared with all app users on the site.
  4. Page Acknowledgements: user → Forge → Confluence → user. An editor requests a page version; recipients confirm and editors review permission-checked results. Forge retains account IDs and version/time records; display names and titles are transient. A weekly Atlassian privacy report processes closed accounts. CSV and summary text are copied in the browser only.
  5. Voluntary sanitised support → monitored support mailbox. Contact identity and issue details are separate from app storage. No customer-content forwarding to AI.
  6. Marketplace billing → Atlassian. Licensing, trials, cancellation and refunds follow the linked Marketplace process and platform timeframes.
  7. Session close / schema deletion / uninstall. See app-specific deletion and Forge recovery limits. Jira updates remain in Jira; deleting Page Properties Check schemas leaves its identity-free usage counter.

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.

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-hosted storage data lifecycle · Retrieved 5 October 2026.

Separate website, support and business records

Cloudflare delivers the website and processes IP addresses and request data only for delivery and protection against abuse. No app-owned website access logs, analytics or cookies are used. Email support is handled through the provider’s monitored mailbox; mailbox copies are deleted after the period stated in the privacy policy, with mail-provider backups expiring under that provider’s schedule. Statutory business records are retained for 10 years under Swiss Code of Obligations Article 958f. These channels are separate from Forge app processing. No external app backend or external AI is used. An additional processing path must be reviewed and reflected in this inventory before use.

Privacy policy · Security policy · Support SLA