End User License Agreement
Move Work Forward | End User License Agreement
Privacy Policy
Move Work Forward | Privacy Policy
Security practices
Move Work Forward | Security Practices
What data Platypus stores
Platypus stores only what it needs to schedule and audit date changes: issue keys, start/due dates, and the account ID of whoever triggered a change. It does not store secrets, tokens, or any other personal data.
-
Activity log entries are retained for 60 days, then purged automatically.
-
Pending "Preview & confirm" reviews are retained for 14 days; if nobody confirms or cancels one within that window, it expires automatically.
Usage analytics
Platypus sends anonymous product-usage analytics, for example, which settings are changed, and whether a cascade completes, is skipped, or detects a circular dependency, to our analytics provider. This data never includes issue content, issue keys, dates, or any other end-user data, only which features are used and how often.
Permissions Platypus requests
Platypus requests the minimum Jira permissions it needs to function:
-
Read issues: to read due dates, start dates, and dependency links.
-
Write issues: to update dates and post an audit comment when it reschedules an issue.
-
Manage Jira configuration: to read field and link-type metadata for the settings pages.
-
Read Jira users: to show who triggered each change in the activity log.
All Jira access happens using Platypus's own app identity, never on behalf of an individual user, and every stored record is isolated to your own Jira site.
Updated: