Automation security and data
Polyglot Automation separates check access from publication access, authenticates repository workflows with GitHub OIDC, uploads only the data required for each operation you've opted into, and fails closed when trust cannot be proven.
GitHub App permissions
| App | Repository permissions | Boundary |
|---|---|---|
| Checks | Metadata read; contents read; pull requests read; checks read/write; actions read/write; administration read/write for merge protection | No contents write. Actions write dispatches only the configured workflow. Administration read inspects effective rules; write is used only after an admin confirms creation of Polyglot's dedicated ruleset. |
| Publisher | Metadata read; contents read/write; pull requests read/write | Separate installation. Writes only after a verified catalog-only result and never directly to the default branch. |
Both Apps can be limited to selected repositories. They subscribe only to the installation, repository, pull-request, push, Check, and workflow events needed for their stated purpose.
OIDC and run credentials
- The registered default-branch caller requests a GitHub OIDC token.
- Polyglot validates issuer, audience, repository identity, owner, event, workflow path and immutable workflow pin, GitHub run and attempt, and requested operation.
- A successful exchange issues a short-lived credential bound to that exact managed run.
- Credentials, policies, manifests, and results are rejected when their immutable identities drift.
The caller contains no Polyglot project API key. GitHub App private keys, webhook secrets, signing material, and installation tokens are never stored in customer repositories or dashboard frontend variables.
Data uploaded by managed checks
Check reports contain repository and run identity, immutable base/head revisions, event and branch, configuration and policy hashes, CLI version, analysis and conclusion, duration, counts, bounded errors, coverage/validation summaries, and findings with path, location, category, classification, confidence, remediation, and HMAC-derived fingerprint. Raw finding values and source excerpts are not uploaded.
Data uploaded after catalog consent
Catalog sync is a separate owner-controlled capability. After explicit consent, the repository workflow uploads catalog document paths, formats, namespaces, keys, source strings, existing translations, languages, hashes, and metadata needed for translation, review, and publication. Revoking consent blocks new uploads.
Publication boundary
- The exact preview binds repository, base commit, configuration, catalog snapshot, values, paths, and verification command.
- Only approved or policy-eligible reviewed translations are included.
- Only configured catalog paths may change.
- The same command runs on the pristine base and exact candidate.
- Any baseline failure, regression, drift, extra path, hash mismatch, timeout, or conflict blocks the write.
- The Publisher App creates a dedicated branch and pull request; it never writes directly to the default branch.
Retention defaults
| Window | Data classes |
|---|---|
| 30 days | Webhook metadata, OIDC exchange records, and run-credential digests. |
| 90 days | Finding detail; superseded unreferenced catalog snapshots; content-bearing publication manifests, reports, and artifacts. |
| 400 days | Bounded CI/publication run and audit identity, funnel transitions, failure reasons, and aggregate SLO snapshots. |
Content-bearing publication data is redacted before the non-content audit record expires. Current catalog and translation data follow the account's product lifecycle where needed to provide the Service. Organization deletion removes tenant-linked projects, automation data, and joinable funnel analytics.
Revocation and degraded operation
- Uninstall or suspend Publisher to stop repository writes without disabling Checks.
- Uninstall or suspend Checks to stop managed analysis and workflow dispatch.
- Disable catalog consent to stop new content uploads.
- Polyglot can disable report ingestion, dispatch, Check writes, OIDC exchange, enforcement, catalog sync, generation, verification, and Publisher writes independently.
- Queued work is re-checked and cancelled with a stable reason when a capability is disabled.
- The local CLI and open GitHub Action remain the safe fallback.
See the public security summary, Privacy Policy, and service status.