Scope and roles
ErrorLink is a business-to-business Jira Cloud app that connects customer-selected hosted Sentry projects to Jira. The customer determines the connected projects, mappings, payloads, Jira recipients, retention choices, and purposes and is normally the controller. VENTURE VD LLC processes that data to provide and support ErrorLink. Atlassian and Sentry separately process information under their agreements with the customer.
Information processed
- Jira installation, project, issue-type, issue-key, status-category, and app-owned issue-property identifiers.
- Sentry organization slug, selected project identifiers, error-group and webhook identifiers/actions, title, culprit, environment, release, occurrence count, issue URL, and a bounded stack excerpt.
- Connection, mapping, event, link, sequence, attempt, entitlement, budget, alert, timestamp, synchronization outcome, bounded redacted error, and aggregate operational metadata.
- A Sentry internal-integration API token and webhook client secret supplied by a Jira administrator.
ErrorLink does not intentionally request Jira user-profile data, sell customer data, use it for advertising, or use it to train a general-purpose model. Customer-controlled Sentry text may contain personal or confidential information; customers must configure Sentry data scrubbing and avoid unnecessary sensitive content.
Purposes and processing
ErrorLink authenticates signed webhooks; applies administrator mappings and thresholds; creates, links, and updates Jira issues; propagates resolved/unresolved status; deduplicates and recovers work; provides history and diagnostics; enforces retry/safety limits; and supports authorized customer requests.
ErrorLink UI assets, functions, KVS secret storage, queues, and SQL storage run on Atlassian Forge. VENTURE VD LLC operates no separate ErrorLink server or database. The Forge backend makes declared HTTPS calls to https://sentry.io to validate credentials, list projects, read issue state when needed, and update resolved/unresolved status. There are no app-authored browser calls to Sentry, third-party browser scripts, or advertising cookies.
Disclosure and security
Information is disclosed only to Atlassian as the Forge/Jira provider; Sentry as the customer-selected service; VENTURE VD LLC personnel when a customer intentionally supplies a redacted support record or access is lawfully required through available developer controls; and authorities when legally required. No additional ErrorLink subprocessors are used by the reviewed implementation.
The Sentry token and webhook secret use Forge secret operations and are never returned after save or included in exports. Webhooks use exact-body HMAC-SHA256 verification before parsing/storage. Logs use an allow-list and exclude credentials, raw bodies, signatures, DSNs, and webhook URLs. See the ErrorLink security statement.
Retention, export, and deletion
While installed, connection data remains until rotation, disconnect, administrator purge, or Forge lifecycle removal. Customer mappings, links, normalized events, attempts, statuses, budgets, alerts, and sequences remain until administrator purge or Forge lifecycle removal.
Jira administrators can export customer records and non-secret connection metadata. Exports exclude the Sentry token, webhook secret, and schema bookkeeping. After disabling Sentry delivery, disconnecting, and waiting at least 15 minutes for in-flight work, an administrator can type an exact confirmation to permanently purge ErrorLink customer SQL and connection KVS data. The server rejects purge while connected. Only non-customer schema/migration bookkeeping remains. Purge does not delete generated Jira issues or source Sentry data.
Atlassian states that Forge hosted storage is retained for 28 days after uninstall and that a customer-consented recovery/relink request must be submitted within 21 days. See the Atlassian Forge storage reference and Forge hosted-storage lifecycle. Customers seeking immediate app-level action should export or purge before uninstall.
Choices, requests, and international processing
Jira administrators can control projects/mappings, unlink issues, rotate credentials, disconnect Sentry, export data, or purge ErrorLink customer data. For access, correction, deletion, restriction, portability, security, or privacy questions, contact support@venturevd.com with the Jira site hostname and redacted identifiers. Do not send credentials, webhook URLs, raw payloads, or full stack traces. We may verify identity and authority before acting.
Forge and customer-configured Sentry processing may occur in regions governed by the customer's Atlassian and Sentry plans. ErrorLink does not independently promise a residency region. ErrorLink is a business tool and is not directed to children.
Changes and contact
Material changes to data categories, retention, subprocessors, browser behavior, or backend egress will receive a revised effective date and notice where required. Contact: support@venturevd.com.