Security

Last updated 18 November 2026

Otter Hours runs entirely on Atlassian Forge. It has no servers of its own, talks to Harvest only, and acts as the signed-in person.

Architecture

Access and permissions

Jira permissions requested
ScopeWhy
read:jira-workRead the issue, its project and type, and worklogs, to build and match entries.
write:jira-workCreate, update and delete the person's own worklogs, and store the link on each worklog.
read:jira-userRead the person's time zone, and check the Administer Jira permission for the settings page.
storage:appKeep mappings, links and sync status in Forge app storage.

Harvest sign-in and tokens

Network egress

Storage and retention

Logging

App logs stay in Atlassian's Forge logging. They record function names, outcomes, counts, Jira worklog and issue ids, and error messages. They never contain names, email addresses, account ids, entry notes, request bodies or tokens.

Secure development

Certifications and programs

Report a vulnerability

Email support@stubbornotter.com with the subject "Security report". Include the steps to reproduce and the impact you see. Please do not test against other people's Jira sites or Harvest accounts.

We acknowledge reports within two business days and fix confirmed vulnerabilities within the timeframes of Atlassian's Security Bug Fix Policy for Marketplace apps. If a security incident affects your data, we notify affected customers and Atlassian without undue delay.