Privacy Policy
Effective Date: October 18, 2026 • Version 2.1 (Atlassian Forge Cloud Native)
Our Zero-Data-Egress Architectural Guarantee
EvidenceLog for Jira runs 100% inside your organization's Atlassian Cloud instance using Atlassian Forge. Your Jira tickets, developer names, pull request URLs, Git commit hashes, and security scan logs are processed entirely in-memory within the Atlassian secure sandbox. Langtago operates zero external servers, zero external databases, and conducts zero outbound network egress of your Jira data.
1.Scope & Applicability
This Privacy Policy applies to all users of software applications published by Langtago ("we", "us", or "our"), including our flagship Atlassian Marketplace app, EvidenceLog for Jira, and our website at langtago.com.
By installing EvidenceLog for Jira from the Atlassian Marketplace or accessing our website, you agree to the collection and handling practices described in this document.
2.Data Processed by EvidenceLog for Jira
To provide automated SOC 2 and ISO 27001 evidence verification, EvidenceLog for Jira accesses specific Jira metadata via declared Atlassian Forge APIs:
- Issue Metadata: Issue keys, summaries, issue types, priorities, and workflow statuses.
- Change Traceability: Presence of Acceptance Criteria in descriptions and Git remote links (GitHub, GitLab, Bitbucket, Azure DevOps).
- Segregation of Duties (SoD): Transition history actors and comment sign-offs to verify independent peer review.
- Testing & Security Sign-offs: QA verification labels and security scanner signatures (Snyk, SonarQube, Trivy, Dependabot, OWASP ZAP).
@forge/kvs). They are never transmitted to Langtago or third parties.3.Zero Data Egress & Third-Party Processors
Unlike legacy Jira marketplace plugins that transmit your tickets to external AWS or GCP servers, EvidenceLog operates under a strict Zero Data Egress architecture:
Your code commits, issue descriptions, and tickets are never shared with OpenAI, Anthropic, or external machine learning models.
We maintain zero relational databases, S3 buckets, or logs containing customer Jira ticket records.
4.Data Residency & Atlassian Cloud Sovereignty
Because EvidenceLog runs within Atlassian Forge, your data inherits your Atlassian Cloud Data Residency tier automatically. If your Jira instance is pinned to the United States, European Union, Australia, Germany, or Singapore, all verification calculations and encrypted snapshot storage stay strictly within that geographic boundary.
5.Website Analytics (langtago.com)
When you visit our marketing website (langtago.com), we use minimal privacy-first analytics (Google Analytics) to understand aggregated page views, referral sources, and feature interest. This analytics data is never linked to your Jira instance or enterprise ticket data.
6.Compliance with Global Privacy Standards
GDPR (General Data Protection Regulation): Because we process no customer personal data outside your Atlassian Cloud tenant, Langtago does not act as a traditional data processor storing personal records. You retain full control over right-to-erasure and access requests via Jira Cloud administration.
CCPA (California Consumer Privacy Act): Langtago does not sell, rent, or monetize your personal or company data under any circumstances.
HIPAA Security Rule: EvidenceLog satisfies §164.312(b) audit trail and hardware/software integrity controls while maintaining zero external BAA data transfers.
7.Contact & Privacy Inquiries
For questions regarding this Privacy Policy, enterprise security questionnaires, or Atlassian Marketplace compliance documentation, please reach out to our security team: