ScriptlinePrivacy
Effective 03/11/2026. Scriptline for Jira is provided by Wattlebrooks Apps, Australia.
The short version
- Everything stays inside Atlassian. Scriptline runs on Atlassian Forge. No data is sent to Wattlebrooks Apps or any third party.
- We operate no servers for Scriptline and cannot see your scripts or your Jira data.
- What is stored is your automation: the scripts your administrators write, their versions and their run history, kept on your own Jira site and encrypted at rest by Atlassian.
1. Data the app accesses
Scriptline is an admin-only automation tool. A Jira administrator writes TypeScript or JavaScript scripts and Scriptline runs them against your Jira site within the permissions granted at install. The data it reads is therefore decided by the scripts your administrators write:
- Jira work items: the fields a script searches for, fetches or updates.
- The current user profile, when a script asks for it, and to check that the person using the app is a Jira administrator.
- Jira events: for listeners, the details Jira provides about the event (for example the affected work item and what changed), passed to the script.
Scriptline reads nothing else: not group memberships, not Confluence, not billing, and no account data beyond what a script requests.
2. Data the app stores
Stored in Atlassian-hosted app storage on your Jira site, encrypted at rest by Atlassian and following your site's data residency:
| What | Contents | Kept |
|---|---|---|
| Scripts | Name, code, kind, enabled flag, current version | Until an administrator deletes the script |
| Versions | Earlier copies of each script's code | The last 20 per script |
| Run history | Status, trigger, duration, the script's own log lines, its returned value (up to 100 KB) and any error | The last 50 runs |
| Bulk jobs | Job status, counts and up to 20 error samples | The last 50 jobs |
Run records contain only what a script itself logs or returns. Scriptline keeps no per-user records and no deliberate store of personal data. Personal data can appear in a run record only if an administrator's script logs or returns it.
3. Sharing
None. Scriptline makes no external network calls of any kind: no analytics, no error reporting service, no AI, no telemetry, no third-party code. The only service it talks to is your Jira site, through Atlassian.
4. Changes the app makes
Scriptline can change Jira work items (add comments, update fields, transition work items, or call other Jira write endpoints) only when an administrator's own script does so. It ships with no automations of its own, and every run is recorded in Run history so what a script did can be reviewed. Scriptline cannot manage user accounts, groups, licences or Jira configuration.
5. What we do not collect
- Usage analytics or telemetry about how anyone uses the app.
- Passwords, API tokens or other credentials.
- IP addresses or location.
- Cookies. The app runs inside Jira; this website sets none either.
6. Retention and deletion
- Versions and run history roll off automatically at the limits above.
- Deleting a script removes it and its versions.
- Uninstalling Scriptline removes all of its stored data, under Atlassian's Forge data lifecycle.
7. Your rights
Everything Scriptline stores is visible to your Jira administrators in the app. For access, correction or deletion requests under GDPR, the Australian Privacy Act or similar laws, email support@wattlebrooks.com. Because the data lives on your own site, your administrators can usually act on a request immediately.
8. Children
Scriptline is a business tool for Atlassian Cloud organisations and is not intended for anyone under 18.
9. Changes to this policy
We update this page when materially new features ship. The date at the top shows the latest change, and material changes are noted in the release notes.
10. Contact
Wattlebrooks Apps, Australia · support@wattlebrooks.com · wattlebrooks.com