fresto.

Config Watch for Jira Cloud

Config Watch Privacy Policy

How Config Watch processes Jira configuration data for monitoring, comparisons, timelines and audit support.

Last updated: August 27, 2026Marketplace document

Controller: Daniel Aparicio, trading as Daniel Aparicio Apps

Privacy contact: support@fresto.app

1. Scope

Config Watch analyzes Jira configuration. It is not designed to store issue content, comments, attachments or Confluence page content.

2. Data processed

Config Watch may process:

  • Workflow definitions, statuses and transitions.
  • Custom-field definitions, names, types and schemas.
  • Permission-scheme grants.
  • Configuration object identifiers and names.
  • Normalized configuration snapshots.
  • Change events and technical differences.
  • Actor information when provided reliably by Atlassian.
  • Monitoring preferences, watchlists and exclusion rules.

3. Data not stored

Config Watch does not store issue descriptions, comments, attachments, Confluence content, passwords, personal access tokens or unrelated user data.

4. Purposes

Data is processed to create baselines, compare snapshots, detect configuration changes, show before-and-after differences, display timelines and maintain administrator preferences.

5. Storage and retention

Data is stored in Atlassian Forge Storage and isolated by installation. Config Watch does not use its own external database and does not sell data.

Current retention depends on the selected plan and configuration. Free history is limited; Pro history is extended according to the Marketplace listing.

6. Security and deletion

When Config Watch is uninstalled, Atlassian removes the associated Forge storage according to its policies.

7. Contact

support@fresto.app

support@fresto.app