> For the complete documentation index, see [llms.txt](https://docs.toolsplus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.toolsplus.io/trust/logging-and-log-retention-statement.md).

# Logging and Log Retention Statement

This statement explains the operational logs and diagnostic telemetry that ToolsPlus collects for its Atlassian Marketplace apps. It covers Forge-hosted components and the separately hosted remote services.

### Information we record

Depending on the component and operation, records may contain:

* **Application logs:** timestamps, severity, operation names, outcomes, error messages and stack traces, request or invocation identifiers, and trace and span identifiers.
* **Integration context:** Atlassian site URLs, cloud and installation identifiers, app version, environment, module, license information, identifiers of Atlassian product entities such as Jira spaces and work items, and identifiers from connected services such as Intercom workspaces and conversations. Some remote-service records also include Atlassian account identifiers.
* **Infrastructure logs:** HTTP request metadata, response status, latency, IP addresses, service health and platform events.
* **Error and performance telemetry:** browser and backend errors, diagnostic context, and traces describing application operations and their duration. Browser telemetry may also include an automatically generated session identifier.

### Purpose and access

We use these records to diagnose failures, monitor reliability and performance, investigate security incidents, and assist customers with technical support.

Our security policies require restricting access to logging systems to authorized personnel based on their responsibilities and business needs, and require protection against unauthorized access and modification.

Access to Forge app logs is subject to Atlassian’s customer log-sharing controls. Disabling developer access to Forge logs does not disable telemetry separately collected by our remote services or Sentry. See [Atlassian’s app-log documentation](https://developer.atlassian.com/platform/forge/view-app-logs/).

### Retention periods

The following periods apply to records held in the listed systems:

| Record category                                    | System               | Retention |
| -------------------------------------------------- | -------------------- | --------- |
| Remote-service application and infrastructure logs | Google Cloud Logging | 30 days   |
| Remote-service traces                              | Google Cloud Trace   | 30 days   |
| Forge backend app logs                             | Atlassian Forge      | 30 days   |
| Error events                                       | Sentry               | 90 days   |
| Performance traces and spans                       | Sentry               | 30 days   |

Sentry retention follows Sentry's fixed retention periods: [event retention guidance](https://www.sentry.help/en/articles/13964940-how-long-are-my-organization-s-audit-logs-stored) and [trace retention guidance](https://www.sentry.help/en/articles/13965032-how-is-my-team-plan-changing-august-27-2025). Google Cloud Trace follows [Google’s documented retention](https://docs.cloud.google.com/trace/docs/quotas).

### Providers and related documents

We use Atlassian Forge, Google Cloud and Sentry for the logging and telemetry described above. Details of external providers are available in our [subprocessor list](https://toolspl.us/subprocessors).

This statement supplements our [End User License Agreement](https://docs.toolsplus.io/legal/end-user-license-agreement), applicable [Data Processing Agreement](https://docs.toolsplus.io/legal/data-processing-agreement), and [Privacy Policy](https://docs.toolsplus.io/legal/privacy-policy). It describes operational logging, rather than retention of all customer data processed by the app.