Effective date: 2026-06-03
Vega Cache is operated by Ad Astra Computing Inc. The third parties below process data on Vega's behalf. We keep this list current; a material change is reflected here. See the Privacy Policy for what Vega processes and why.
Edge compute, storage, hosting, CDN, DNS
Runs the Vega Worker, stores published NAR artifacts in R2 object storage, hosts the documentation on Pages, and serves the cache and its DNS over Cloudflare's CDN. Processes request metadata and the continent-level geolocation Vega records (never a precise location or retained IP).
United States; global edge network
Reproduction-worker microVMs
Runs Vega-operated reproduction workers: ephemeral, per-job microVMs that rebuild public source from scratch to verify a build. These machines hold no Vega credential and process only public source and build outputs, not user data.
United States; Europe; Asia
Identity, commit checks, eligibility
Verifies builder identity through GitHub Actions OIDC, hosts the Vega GitHub App that posts commit checks, and provides the API Vega queries to check an attester's account age for eligibility. Processes your numeric GitHub user id, login, and build provenance (repository, commit, workflow run). OIDC tokens are verified and not stored.
United States
Vega fetches public build dependencies from cache.nixos.org, the upstream Nix binary cache operated by the NixOS Foundation. Vega sends it no user data; it is listed here for completeness, not as a subprocessor.
When Vega adds or replaces a subprocessor, this page is updated before the change takes effect for new data.
Privacy questions: security@adastracomputing.com.