Architecture and data flow
ErrorLink uses Atlassian Forge for UI hosting, compute, queues, tenant-scoped KVS secret storage, and SQL. VENTURE VD LLC operates no separate ErrorLink service or database. The full product performs declared backend HTTPS egress to hosted Sentry and therefore is not represented as Runs on Atlassian. Browser assets are bundled locally and make no app-authored request to Sentry.
Implemented controls
- HMAC-SHA256 over the exact webhook body with strict signature validation and constant-time comparison before parsing or storage.
- Jira administrator authorization for configuration, mappings, diagnostics, export, and purge; issue operations require Jira issue-edit permission.
- Forge secret storage for the Sentry token and webhook secret; secret-free queue jobs; no credential returned to the UI after save.
- Bounded schemas and payload fields, common-secret redaction, allow-listed structured logging, and no raw webhook logging.
- Structural deduplication, remote reconciliation, append-only runtime journals, persisted echo suppression, bounded retries, queue concurrency, and consumption guards.
- Server-side inactive-license gates before Jira creation, configuration mutation, retry, manual link, and status propagation.
- Administrator customer-data export and exact-confirmation purge after disconnect and a 15-minute queue-drain window. Queued consumers reject disconnected or replaced connection IDs.
Customer responsibilities
Use a dedicated least-privilege Sentry internal integration, restrict Jira access appropriately, configure Sentry data scrubbing, rotate suspected credentials promptly, and avoid unnecessary sensitive data in error payloads. ErrorLink is not a backup, monitoring replacement, or incident-response service.
Incident response and reporting
For suspected credential exposure, forged traffic, duplicate issue creation, status loops, or data exposure: disable the Sentry webhook, rotate credentials if necessary, preserve redacted identifiers and timestamps, and contact support@venturevd.com. Do not send active secrets or raw signed payloads. We will contain, investigate, remediate, and notify as required by applicable agreements and law.
Known limitations
There is no time-based or per-record deletion UI; Jira administrators can purge the complete ErrorLink customer dataset. Pattern redaction cannot guarantee customer-controlled stack traces contain no sensitive data. Signature-rejection spikes currently require Forge/Sentry delivery-log review. Availability depends on Atlassian Forge, Jira Cloud, and Sentry.