The short version
Reads issues only
Key, summary, status, type, priority, project, assignee and reporter names, labels and dates. Nothing else in Jira.
Writes to your table
Into a table the app creates in your own Notion workspace or Airtable base, with the token you pasted.
Keeps almost nothing
Your token, encrypted; which row holds which issue; and a short log of results. All inside Atlassian's own storage for your site.
Nothing sold
No analytics about your people, no advertising, no sharing. The app does one thing.
What the app reads
For each issue: the key and summary, status, issue type, priority, project name, the display names of the assignee and reporter, labels, and the created, updated and resolved dates. The app reads these when Jira tells it an issue was created, changed or deleted, and when a Jira admin presses the button that brings in the 50 most recently updated issues. It uses Jira's read:jira-work permission and nothing broader. It does not read descriptions, comments, attachments, custom fields, or anything about people beyond the names above.
Where it writes
Into the table the app created where you chose: a Notion page in your Notion workspace, or an Airtable base, using the Notion or Airtable token you pasted. That table is yours. Notion's or Airtable's own terms and privacy policy apply to it, you can edit or delete any row, and the app never reads it back except to update a row it created. Deleting an issue in Jira removes its row.
The only two outside services the app talks to are Notion and Airtable, and only the one you connected.
What it keeps
- Your Notion or Airtable token, in Atlassian's encrypted secret store for your site.
- Which row holds which issue (two ids per issue), so an update edits its row instead of adding one.
- A short log of recent syncs: issue key, result, time, and an error message if one happened.
- Your settings: which service you connected and where the table is.
Issue contents and people's names are not stored by the app. They pass through it on the way to your table and are not kept.
Where it runs
Rowly for Jira is built on Atlassian Forge and runs entirely on Atlassian's infrastructure. Its storage is Atlassian's hosted storage for your site, kept in the same region as your Jira data. LMB Technology operates no server of its own for this app and has no access to your site's data.
How long
For as long as the app is installed. When you uninstall it, the app stops at once and Atlassian deletes its stored data for your site after its retention period, currently 28 days. If you press "Disconnect" in the app, the token, the mapping and the log are deleted immediately. Rows already in your table stay there, because they are yours.
People's names
The assignee and reporter columns hold display names as Jira shows them, so that a row in your table reads the way the issue does. No email addresses, account ids or other personal details are read or written. If someone asks to be removed, delete their name from the rows in your table; the app holds no other copy.
What it does not do
- It does not sell, share or use any data for advertising, analytics about your people, or anything other than writing your issues to your table.
- It does not read your table back, except to update a row it created.
- It does not write anything to Jira.
- It does not contact any service other than the one you connected.
Billing
Subscriptions are sold and billed by Atlassian through the Marketplace. The app never sees payment details. The app checks with Atlassian whether your site has an active subscription or trial before it syncs.
Changes and contact
If this policy changes, we will update this page and the date at the top. Questions about the app or your data go to hello@lmbtechnology.com, or through our contact page. Rowly for Shopify, our Shopify app, has its own policy served by that app.
Questions about Rowly?
Email hello@lmbtechnology.com and a person answers, usually the same day.