Trellixis ยท VaultGuard for Jira
Last Updated: 16 November 2026

Privacy Policy

This Privacy Policy explains how Trellixis handles data within VaultGuard Zero-Egress Compliance for Jira Cloud and Jira Service Management.

1. Zero External Egress Architecture

VaultGuard is built natively on Atlassian Forge and qualifies for the Runs on Atlassian programme. Its manifest declares empty external fetch permissions (permissions.external.fetch.backend: [] and client: []). Ticket content, comments, attachments, and customer data never leave Atlassian's managed cloud infrastructure and are never transmitted to Trellixis servers or third-party AI services.

2. What Data VaultGuard Processes

3. Data Retention & GDPR Right to Erasure (DSAR)

Jira Administrators can configure an Audit Retention Window in the Admin Console and run 1-click DSAR cleanup to anonymise historical issue keys, actor IDs, and receipt metadata older than their chosen cutoff date while preserving cryptographic hash-chain verification. Uninstalling VaultGuard removes access to app storage according to Atlassian Forge lifecycle policies.

4. Jira Cloud Issue History Limitation

For attachments and comments, VaultGuard deletes leaked source files and overwrites comment bodies in place. For standard Jira issue fields (such as Description or Summary), Jira Cloud maintains an immutable issue changelog that Atlassian does not allow any Marketplace app to edit or delete via API. Admins are advised to rotate exposed secrets and clone/delete the original ticket if strict field-history erasure is required.

5. Contact

For privacy enquiries or data protection questions, please contact Trellixis via our Support page or email support@trellixis.co.uk.