Security

Last updated: 12 November 2026

How our apps are built

• Built on Atlassian Forge and hosted by Atlassian. No Rowmill servers.
• No external network calls. Data stays in Atlassian's cloud, inside your site's installation.
• Rowmill staff cannot read your data. We have no access to your Jira or Confluence content or to the app's storage.
• Only the permissions each feature needs. They are listed per app below.
• Dependencies are checked with npm audit before each release.

Rowmill Table Grid for Jira

• Data: table rows are saved as the value of a Jira custom field. No separate app storage.
• Permissions:
  • Read and write the field's own column settings (custom field contextual configuration).
  • Read Jira work items, to find issues to import into.
  • Write app data, to save imported rows into the field.

Rowmill SOP Acknowledgement for Confluence

• Data: rounds, page IDs, titles and versions, reader account IDs and display names, group IDs, permission results and acknowledgement times. Stored in Forge SQL for your installation. No page bodies, no email addresses.
• Data residency: Forge SQL follows your Confluence site's data residency region.
• Closed Atlassian accounts: checked weekly through Atlassian's personal data reporting API. Identifying fields are removed.
• Permissions: read pages, spaces, users, groups, page permissions and page details. Report personal data.
• Readers can only acknowledge pages Confluence lets them open.

Report a vulnerability

Email [email protected] with "Security" in the subject. Include the app, steps to reproduce and impact.

• We reply within 2 business days.
• We share a fix plan within 10 business days.
• Please give us reasonable time to fix before disclosing publicly. We will credit you if you want.

Incidents

If a defect affects customers, we ship a fixed Forge version and email affected customers where we can identify them through Marketplace licence data.