Privacy policy

Last updated: 16 October 2026

This policy covers Slipwatch, an app for Jira Cloud, and this website. Both are made by Morriblaze Ltd, a company registered in England and Wales (company number 16410763). Questions about privacy go to office@morriblaze.com.

In short

Slipwatch runs on Atlassian’s own cloud. It has no servers of its own.
It keeps only what it needs to show how due dates moved: which work item, who changed the date, when, and why, if someone gave a reason.
It sends your data to nobody: not to us, not to anyone else. The only thing we see is the app’s logs, described below.
We don’t sell or share data. There are no ads and no trackers.

What Slipwatch keeps

Slipwatch reads the change history of the work items in the projects it covers, and keeps only the due-date changes. For each change it keeps:

the work item’s key, summary and work type, and its parent, such as an epic
the old and the new due date, and when the date changed
who changed it: their Atlassian account ID and display name
who the work item was assigned to when the date changed, and who holds it today: account ID and display name

When someone gives a reason in Slipwatch, it also keeps the reason, its category, who gave it (account ID and display name) and when. Every version of a reason is kept: nothing is overwritten.

Names are kept as plain text, as Jira shows them. Slipwatch keeps no profile pictures and no email addresses.

For each project, it keeps the project’s Slipwatch settings: whether Slipwatch is on, which mode it uses, and the list of reasons people can choose from.

What Slipwatch changes in Jira

Only due dates. In Enforce mode, when someone changes a due date through Slipwatch and gives a reason, Slipwatch writes the new date to the work item. It changes nothing else.

Where it’s kept

Inside your Jira site’s Slipwatch installation, in storage that Atlassian runs for apps like Slipwatch. Atlassian encrypts it and keeps it in the same location as your Jira site’s data. Slipwatch has no other storage.

Who can see it

People in your Jira: anyone who can open a project can open its Slipwatch report. The report shows who moved which due dates, by how many days, and the reasons given.
Your Jira admins: they can change Slipwatch’s settings, switch it off for a project, and delete everything it recorded for a project.
Us: we don’t see your Slipwatch data. Atlassian shows us the app’s logs for 30 days, so we can find and fix faults. The logs can include project and work item keys and Atlassian account IDs. Your Jira admin can switch off our access to them in Atlassian’s admin settings for connected apps.
Atlassian: Slipwatch runs in Atlassian’s cloud. Atlassian’s own privacy policy covers that.

How long it’s kept

While Slipwatch is installed, it keeps the record, so the report can show the whole history.
When a work item is deleted in Jira, Slipwatch deletes what it kept about it.
When an Atlassian account is closed, Slipwatch replaces that person’s name with “Former user” on every record within 7 days of Atlassian telling it. The account ID stays, so the record of changes stays whole. Slipwatch asks Atlassian about every person it names once a week.
When an admin switches a project off, its record stays, unless they choose to delete it.
When Slipwatch is uninstalled, Atlassian keeps its data for 28 days, then deletes it.

Why personal data is kept

A record of due-date changes is only useful if it shows who moved each date, so Slipwatch keeps names and account IDs. Your organisation chooses to install Slipwatch and decides how it’s used. We use the logs only to keep Slipwatch working, and emails only to answer them.

Your rights

Under UK data protection law, you can ask what personal data is held about you, and ask for it to be corrected or deleted. Email office@morriblaze.com. Slipwatch’s data sits in your organisation’s Jira site, so we may need your Jira admin’s help. You can also complain to the Information Commissioner’s Office at ico.org.uk.

This website

slipwatch.app sets no cookies and has no analytics or trackers. It remembers whether you chose the light or dark look, in your own browser. GitHub hosts the site and keeps a log of visitors’ IP addresses for security. GitHub’s privacy statement covers that.

If you email us

We keep your email so we can answer it, and use it for nothing else.

Changes to this policy

If this policy changes, the new version goes on this page with a new date at the top.