Config Watch for Jira Cloud
Config Watch Security Policy
Security practices for Config Watch for Jira Cloud.
Provider: Daniel Aparicio, trading as Daniel Aparicio Apps
Contact: support@fresto.app
1. Scope and application identity
This Security Policy describes the security practices for Config Watch for Jira Cloud.
Config Watch monitors Jira configuration changes and presents human-readable audit information. The provider is Daniel Aparicio, trading as Daniel Aparicio Apps.
2. Read-only boundary
Config Watch observes and compares configuration. It does not modify workflows, custom fields, permission schemes, projects or other Jira settings. Monitoring does not replace administrative action, backups or internal audit controls.
3. Architecture and tenant isolation
Config Watch is a Jira Cloud application that depends on Jira Cloud, Atlassian Forge and Atlassian APIs.
Data is stored in Atlassian Forge Storage and isolated by Jira installation. The current product documentation states that Config Watch does not use its own external database and does not sell data; no additional subprocessors are listed in this policy without verification.
The authenticated Jira and Forge installation context is the authority for tenant identity; browser-supplied tenant identifiers are not treated as an authorization authority.
4. Authentication and authorization
Jira and Forge permissions control access to the monitored configuration and administrator-only settings. Config Watch does not grant additional Jira privileges.
The app uses the authenticated context to read configuration available to the authorized user.
5. Data handled
Config Watch may process:
- Workflow definitions, statuses and transitions.
- Custom-field metadata and schemas.
- Permission-scheme grants.
- Configuration identifiers and names.
- Baselines, normalized snapshots and technical differences.
- Change events and actor information when supplied by Atlassian.
- Watchlists, exclusions and monitoring preferences.
6. Storage, retention and deletion
Configuration data, snapshots and events are stored in Atlassian Forge Storage. Retention depends on the selected plan and configuration; Free history is limited and Pro history is extended according to the Marketplace listing.
Administrators can delete available monitoring data. On uninstallation, Atlassian removes associated Forge storage according to its policies. Config Watch does not sell customer data.
7. Security controls
The verified security boundary is read-only monitoring, Jira and Forge permission checks, installation-level isolation and data minimization. Config Watch does not perform write operations against Jira configuration.
Config Watch does not store issue descriptions, comments, attachments, Confluence content, passwords, personal access tokens or unrelated user data.
8. Vulnerability disclosure
Report suspected vulnerabilities to support@fresto.app with the subject “Security – Config Watch”. Include a concise description, reproduction steps, the affected configuration area, the expected security impact and safe evidence.
Do not include passwords, API keys, access tokens or unnecessary customer data. Please do not publicly disclose a suspected vulnerability before coordinated review.
9. Security incident response
Reports are triaged and investigated. Where appropriate, the provider works to contain the issue, remediate the affected behavior and communicate material developments to affected customers. No fixed response time is promised by this policy.
10. Dependencies and monitoring limitations
Config Watch depends on Jira Cloud, Atlassian Forge and Atlassian APIs. It may not detect every possible configuration change when Atlassian does not expose the relevant information or when permissions, API limits or service availability change.
11. Related documents
Terms of Use: https://www.fresto.app/legal/config-watch/terms
Privacy Policy: https://www.fresto.app/legal/config-watch/privacy
Customer Support: https://www.fresto.app/support/config-watch