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
- The app's code runs in Atlassian's Forge runtime. Its interface is built with Forge UI Kit, so it renders no custom HTML or scripts in Jira.
- Its only storage is Forge app storage, which Atlassian keeps separately for each installation.
- It exposes no web triggers and no public API, and it uses no Forge Remote back end.
Access and permissions
| Scope | Why |
|---|---|
read:jira-work | Read the issue, its project and type, and worklogs, to build and match entries. |
write:jira-work | Create, update and delete the person's own worklogs, and store the link on each worklog. |
read:jira-user | Read the person's time zone, and check the Administer Jira permission for the settings page. |
storage:app | Keep mappings, links and sync status in Forge app storage. |
- Requests from the issue panel, settings page and Rovo agent call Jira as the signed-in person, so Jira's own permissions apply.
- The settings page checks the Administer Jira permission on the server for every request, not only when the page is shown.
- People can change and delete only their own entries. Ownership is checked on the server.
- The worklog event handler runs as the app only to read the issue a worklog belongs to, and acts only for the worklog's author when that person next uses Otter Hours.
- Inputs from the panel and from the Rovo agent are validated on the server; record ids must be well-formed numbers before any request is made. Rovo actions that write need the person's confirmation.
Harvest sign-in and tokens
- Each person connects their own Harvest account through Harvest's OAuth 2.0 sign-in, using Forge's external authentication. There is no shared admin key.
- Forge stores and refreshes the tokens. The app's code never reads, stores or logs them.
- The Harvest client secret is held in Forge's provider configuration, not in the source code.
- Otter Hours never asks for Atlassian passwords or API tokens.
Network egress
- The app connects to two hosts only:
api.harvestapp.comandid.getharvest.com. They are declared as exact hosts in the app manifest, with no wildcards. - All traffic uses HTTPS. Both Harvest hosts negotiate TLS 1.2 or 1.3 and send HTTP Strict Transport Security headers.
- Data sent: the hours, date and notes of each entry, the issue key, title and link, and the Jira worklog id. See the privacy policy.
Storage and retention
- Stored in Forge app storage: admin settings, Atlassian account ids, each connected person's Harvest account and user ids, link records (Jira worklog id, Harvest entry id, issue key, minutes, date and a content hash), a queue of Jira changes waiting to sync, and sync failures.
- No names, email addresses or entry notes are stored. Failure messages carry only the duration, date and reason.
- Sync failures are deleted after 30 days. Records for closed Atlassian accounts are erased after Atlassian's personal data reporting marks them closed, which the app checks weekly.
- Uninstalling the app deletes everything it stored.
- A data processing addendum is available on request at support@stubbornotter.com.
- Forge app storage follows the Jira site's data residency location.
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
- Automated tests cover the sync rules, permission checks and input validation, and run before every release.
- A white-box security review of the app was completed before its first Marketplace release, and its findings were fixed.
- Dependencies are kept to Atlassian's Forge packages and React, and are audited before each production release.
- The source history is checked for secrets.
Certifications and programs
- Otter Hours holds no independent security certifications, such as SOC 2 or ISO 27001. The Forge platform it runs on is operated by Atlassian; see the Atlassian Trust Center.
- Otter Hours does not have the Runs on Atlassian badge, because its purpose is to send time entries to Harvest.
- Otter Hours does not currently take part in the Marketplace Security Bug Bounty program. Please report issues directly as described below.
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.