Last updated: September 8, 2026
elstar collects no telemetry, no analytics, no usage data, no tracking. Three features can contact a server: license validation, a daily update check, and elstar feedback — which only runs when you run it. Each is described below.
No telemetry, analytics, or usage data — ever. elstar does not automatically upload source files, captured network traffic or crash-report contents. Feedback reports are stored so we can investigate and respond; do not include sensitive information in your report.
There are exactly three times elstar talks to a server.
When you activate a subscription, elstar sends your license key and a machine identifier to Lemon Squeezy, our licensing provider, to confirm your license is valid — on activation, and about once a day while the app is used. This is required to run a licensed copy; it transmits nothing about your work. A license is required; the automatic local trial is temporarily unavailable.
About once a day, elstar asks GitHub's public releases API whether a newer version exists. This is an anonymous read of a public page: no account, no license key, no machine identifier, and nothing about you or your project is sent. Normal CLI update notices are skipped with --json or --quiet and in MCP tool subprocesses. The MCP server can check for updates at startup.
The elstar feedback command sends a bug report or suggestion to us. It runs only when you request it. Interactive use shows the report and diagnostic bundle before asking for confirmation. An explicit --yes or MCP feedback request can send without a separate prompt. It transmits:
--no-diagnose, a diagnostic bundle: toolchain and SDK versions, which simulator is booted, the bundle identifier of the app in the foreground, and the filenames of any recent simulator crash reports — never their contents. Hook configuration is summarized as counts, without raw commands, matchers or environment values.Diagnostic paths replace your home directory with ~; source files are not included automatically. Your report text is supplied by you. Use --no-diagnose or the MCP tool's no_diagnose option to omit diagnostics. Run elstar feedback "…" --dry-run to print the exact report that would be sent, without sending it.
In elstar 1.0.7, network capture masks recognized credentials, cookies, API keys, card numbers and email addresses in displayed output and HAR exports by default. Redaction is best-effort: other sensitive data can remain, so review captures before sharing them.
The CLI's explicit --no-redact option disables this masking. The 1.0.7 MCP net_capture tool does not expose a no_redact option, but an agent with shell access can invoke the CLI with --no-redact. Default redaction is not a restriction on what an authorized agent can capture.
Purchases are processed by Lemon Squeezy, our merchant of record. Lemon Squeezy collects the payment and billing information necessary to complete your purchase and manage your subscription. This is governed by Lemon Squeezy's privacy policy. The Developer does not store credit card numbers or payment details. You can manage or cancel your subscription anytime via the Lemon Squeezy customer portal.
This website does not use cookies. Lemon Squeezy may set cookies during the checkout process.
Questions about this policy: hello@elstar.dev