Privacy Policy
Last updated: 2 July 2026
Plumbline Apps ("we", "us") builds Worklog Courier, an app for Jira Cloud, and operates the website plumblineapps.com. This policy explains what data we process, what we do not store, and your rights. It covers both the app and the website.
Plumbline Apps is operated by Nelson Jordan, based in the United Kingdom. Contact: support@plumblineapps.com.
The short version
- Worklog Courier reads your Jira (and optionally Tempo) worklog data, formats it into a report file, and emails it to recipients you choose. That data is processed in memory during each run and is not stored on our servers. We do not have servers; the app runs entirely on Atlassian's Forge platform.
- The only credential we hold is the optional Tempo API token you paste in, stored encrypted in Atlassian's Forge secret storage.
- Report emails are delivered through Resend, an email provider in the United States. The email and its attachment pass through Resend transiently for delivery.
- We do not sell data, we do not use it for advertising, and we cannot read your worklog data outside of the app's automated runs.
Who is responsible for what (GDPR roles)
For worklog data processed by the app, your organisation is the data controller and Plumbline Apps is a processor acting on your configuration (schedule, recipients, grouping). For the limited data we collect directly (support emails), Plumbline Apps is the controller.
We process personal data under UK GDPR and EU GDPR. The legal basis for processing worklog data is the performance of our contract with your organisation (the Atlassian Marketplace terms under which you install the app). The legal basis for support correspondence is legitimate interest in responding to you.
Data the app processes
Worklog and Jira data (in transit only, not stored by us). During each scheduled or manual run, the app reads: worklog entries (date, time spent, author, description/comment, billable time and work attributes if Tempo is connected), issue metadata (key, summary, project, issue type, configured custom field), and user display names (to show real author names instead of account IDs). This data is fetched from Atlassian's and Tempo's APIs, assembled into a CSV or Excel file in memory, delivered, and discarded. It is not written to any database or server operated by us.
One cached export file. To power the "download last export" button, the app may keep a copy of the most recent export file (only when it is small, roughly under 1 MB) in Atlassian Forge storage, inside Atlassian's infrastructure. It is overwritten by the next run and deleted when you uninstall the app.
Your Tempo API token (optional). If you connect Tempo, the token you paste is stored in Forge secret storage: encrypted at rest, not queryable, inside Atlassian's infrastructure. We never see it. You can remove it at any time from the app's admin page, and it is deleted when you uninstall the app. We recommend creating the token with the read-only "Worklogs (View)" scope; the app never needs more.
App configuration and run history. Your schedule, format, grouping choice, recipient email addresses, and Slack webhook URL, plus a short history of runs (when, how many rows, success/failure), are stored in Forge storage inside Atlassian's infrastructure. Recipient email addresses are personal data your admin chooses to enter; enter only addresses that should receive worklog reports.
What we never process. Atlassian account passwords or API tokens (prohibited by Atlassian policy and not needed), payment details (billing is handled entirely by Atlassian), or any Jira data outside the worklog, issue, and user fields listed above. The app has read-only Jira permissions and cannot modify your data.
Data the website collects
plumblineapps.com is a static informational site. It does not have accounts, forms, tracking cookies, or analytics. The site is hosted on Vercel, which processes visitor IP addresses transiently to deliver the site and protect it from abuse. The domain's DNS is provided by Cloudflare.
If you email support@plumblineapps.com, we keep the correspondence for as long as needed to help you and for a reasonable period afterwards for context on follow-ups.
Subprocessors
| Subprocessor | Purpose | Location | Data involved |
|---|---|---|---|
| Atlassian (Forge platform) | Runs the app; stores configuration, the encrypted Tempo token, and the cached export | Atlassian cloud infrastructure | All app data at rest |
| Resend | Email delivery of report files | United States | Report email content and attachment, recipient addresses, transiently for delivery |
| Slack (only if you configure it) | Summary notifications to your own Slack webhook | Per your Slack workspace | Run summary text (period, totals, group subtotals); never the report file |
| Tempo Software (only if you connect it) | Source of worklog data via the Tempo REST API | Per your Tempo region (universal, EU, or US endpoint) | Your Tempo token authenticates requests; worklog data flows from Tempo to the app |
| Vercel | Hosts and serves plumblineapps.com | Global CDN | Website visitor IP addresses, transiently |
| Cloudflare | DNS for plumblineapps.com and forwarding of inbound support email | Global network | DNS queries; inbound email to our addresses, in transit |
International transfers
Report emails are delivered through Resend in the United States, so the report content transits the US. This transfer is covered by our agreement with Resend incorporating appropriate safeguards for international transfers under UK and EU GDPR. If your organisation cannot send worklog data through a US email processor, do not install the app in its current form (or contact us; regional delivery options are on the roadmap).
All other app data stays inside Atlassian's infrastructure. Note that the app does not currently pin data to a specific Atlassian region (see the data residency section of the Marketplace Privacy & Security tab).
Retention
- Worklog data in reports: not retained by us. It exists in memory during a run and in the delivered email.
- Cached last export: overwritten each run; deleted on uninstall.
- Tempo token, configuration, run history: kept while the app is installed; deleted when you uninstall, subject to Atlassian's Forge platform storage lifecycle.
- Emails delivered via Resend: subject to Resend's own operational retention of sent mail and logs; see Resend's privacy documentation.
- Support correspondence: kept while relevant, reviewed periodically.
Your rights
If you are in the UK or EU you have rights of access, rectification, erasure, restriction, portability, and objection over personal data we control. For worklog data inside your Jira/Tempo instance, direct requests to your own organisation (the controller); we will assist them as processor. For anything we control (support emails), contact support@plumblineapps.com and we will respond within one month. You can also complain to the ICO (UK) or your local supervisory authority.
Security
The app runs on Atlassian Forge, inheriting Atlassian's platform security (TLS 1.2+ in transit, encryption at rest). Credentials use Forge secret storage. The app requests the minimum Jira scopes needed (read-only work data, read-only user lookup, app storage). We report and handle security incidents per Atlassian Marketplace security requirements; to report a vulnerability, email support@plumblineapps.com with "SECURITY" in the subject line.
Changes
We will update this page when the policy changes and note the date at the top. Material changes affecting app data handling also require a new app version with admin re-consent on Atlassian's side.
Contact
Plumbline Apps, United Kingdom.
support@plumblineapps.com