Skip to main content

Espresso Privacy and Security

Hosting and external egress​

Espresso is an Atlassian Forge app for Jira Cloud. The reviewed manifest declares no external network egress and no Totesoft-hosted remote application backend.

Data processed during configuration​

The Custom UI requests Jira field metadata and filters the list to numeric schemas. A saved rule contains:

  • Source Field 1 ID and display name;
  • Source Field 2 ID and display name;
  • operator;
  • Target Field ID and display name; and
  • configuration schema version.

Data processed during a transition​

Espresso processes:

  • issue ID and issue key;
  • transition ID and name;
  • the two configured numeric source values;
  • the computed numeric result; and
  • target field ID.

The source values and calculated result are used during execution. They are not explicit fields in the Recent runs record.

Jira writes​

Espresso updates only the configured target field. It does not intentionally create comments, attachments, worklogs, links, users, projects, workflows, or transitions, and it does not transition or delete issues.

The update requests notifyUsers=false. Jira decides whether notification suppression is honored.

Forge hosted storage​

Espresso stores up to 10 recent diagnostic records for each field-triple key. A record may contain:

  • timestamp;
  • issue key;
  • transition ID/name;
  • operation;
  • outcome code, severity, and summary;
  • technical detail;
  • retry count; and
  • duration.

The history is bounded and is not a complete audit log. Diagnostic detail can include technical error text returned by Jira, which may quote content derived from customer data; see the Espresso App Privacy Notice for details.

Logs​

Authorized Totesoft personnel can access Forge application logs.

Normal structured logs can contain:

  • issue key;
  • transition ID;
  • rule key derived from field IDs;
  • outcome, severity, and detail;
  • retry count; and
  • duration.

Technical error text returned by Jira can also appear in normal outcome detail and logs. Debug logging is disabled by default and is enabled only temporarily for an approved support investigation; when enabled, debug logs can additionally include the numeric source values and the calculated result.

External sharing​

The reviewed implementation sends no data to third-party analytics, advertising, AI, or monitoring services. Atlassian provides Jira Cloud, Forge execution, hosted storage, and logs under the customer's Atlassian relationship.

Uninstall and retention​

Forge hosted storage is installation-scoped. Atlassian's newer Storage overview, updated August 21, 2026, states that hosted storage is retained for 28 days after uninstall. A new installation does not automatically recover it. With customer consent, a developer must submit a recovery request within 21 days so Atlassian can process it before retention ends.

Refer to Atlassian's current storage documentation for the authoritative retention period, as Atlassian controls this behavior.

Security reports​

Until a dedicated security address is approved, send reports to info@totesoft.com with the subject Espresso Security Report. Do not include live customer data or secrets in the initial message.