Data flow should be boring and inspectable.
Sigil evaluates code in your local or CI environment. This page describes the public website and installer surfaces, plus the product data flows teams should review before gating PRs.
Website analytics are limited to product-funnel events.
The site records page, install-copy, contact, quickstart, and docs-search events only when analytics is configured. The intended properties are route, referrer, CTA, search query, result count, and clicked result URL. Do not send secrets through search or contact forms.
The shell installer delegates to GitHub release artifacts.
https://runsigil.com/install.sh downloads the latest public installer from GitHub releases. Use the installation docs for supported platforms, PATH behavior, verification, pinned versions, and uninstall notes.
Evaluation data stays in the environment you configure.
Sigil runs scenarios against local or CI-deployed services, writes signed ledger events, and may call configured judge providers for LLM-judged scenarios. Provider behavior depends on your [judge] configuration. Review scenario rubrics and provider policies before using judges on sensitive data.
Deletion, security, and privacy questions go to one address.
Email [email protected] for deletion requests, privacy questions, security review, or support. Include the relevant URL, command, or release version.