Engineering teams frequently reference Jira ticket numbers (e.g., ENG-4102) and GitHub issues or PRs within code comments, git commit messages, and documentation. Jira & GitHub Linker detects these references and turns them into interactive links with hover summaries.

All operations run entirely in local process memory on your workstation. Delanki operates no external proxy infrastructure and retains zero customer code.

Authentication tokens (Jira API tokens and GitHub Personal Access Tokens) are stored strictly inside VS Code's native SecretStorage API.

This bridges directly into the operating system's hardware-backed credential locker:

• macOS: Apple Keychain
• Windows: Windows Credential Manager
• Linux: libsecret / GNOME Keyring / KWallet

Tokens are never saved to plain text workspace settings, global configurations, or remote cloud servers.

When you hover over an issue key, the extension dispatches an HTTPS request:

• To your configured Atlassian Cloud domain (your-domain.atlassian.net/rest/api/3/issue/...)
• Or to GitHub's REST/GraphQL API (api.github.com or GitHub Enterprise Server)

All network requests travel strictly between your local development workstation and the authorized vendor APIs via TLS 1.3 encryption. Delanki operates zero middleman servers.

The extension uses an optimized regex tokenizer (DocumentLinkProvider) that scans text buffers in your active editor.

Only matched issue identifier tokens (such as PROJ-123 or org/repo#45) are parsed. Your broader source code, file contents, secrets, and architecture logic are never read, indexed, or uploaded.

Jira & GitHub Linker contains zero analytics trackers, telemetry beacons, error logging services, or user tracking packages.

Delanki has no technical capability to see which issue keys you reference, what repositories you work on, or what codebases you maintain.

In accordance with the VS Code Extension Marketplace manifest standards, Jira & GitHub Linker declares only the minimal set of activation events:

You can remove your Jira and GitHub credentials at any moment:

1. Run Jira Linker: Clear Stored Tokens from the VS Code Command Palette.
2. Revoke Personal Access Tokens directly in your Atlassian Security or GitHub Developer Settings dashboards.

Uninstalling the extension instantly and permanently purges all stored secrets from your OS keychain.

Because there are no Delanki backend databases or intermediate processing steps, the extension complies with enterprise IT procurement policies, SOC 2 Type II vendor reviews, and ISO 27001 workstation audits.

Engineering organizations can safely deploy this extension across developer fleets without exposing intellectual property, security tokens, or ticket metadata to third parties.