🛡️ TriageGuard

Privacy Policy

Effective November 18, 2026 • TriageGuard

1. Metadata-Only Durable Storage

TriageGuard is engineered with a strict metadata-only persistence boundary. Durable storage retains only operational metadata needed to enforce guardrails and deduplication: repository owner/name, triage IDs, normalized failure classifications, commit SHA retry counters, anonymized failure fingerprints, and monthly quota counts.

Raw CI build logs, repository source code diffs, build parameters, and LLM diagnostic prompts are processed in-memory only and are never written to persistent storage.

2. Authentication & Short-Lived Credentials

  • GitHub repository access uses short-lived GitHub App installation tokens minted per request via RS256 app authentication.
  • Repository-level .triageguard.yml integrations enforce zero stored secrets and authenticate only via per-request short-lived OIDC Bearer JWTs.
  • Webhook deliveries are authenticated in constant time using HMAC SHA-256 signatures or tenant-scoped tokens.

3. Subprocessors & AI Inference

Compacted error excerpts (<2,500 tokens) and relevant PR diff context are transmitted over TLS to our configured Azure AI Foundry inference endpoint strictly to generate the PR triage diagnosis for that event.

4. Retention, Removal & Contact

Uninstalling the TriageGuard GitHub App immediately revokes repository tokens and halts new webhook processing (installation.deleted). For data deletion requests or privacy questions, contact hello@triageguard.dev.