Should I opt in?
You run vouchfx and want to know exactly what vouchfx telemetry enable
would send, what it never sends, and how to check for yourself before you decide.
Opt-in, allowlist-only by construction, deletable on request — and off until you say otherwise.
Start here
This repository is the server half of a two-sided system: the vouchfx engine collects the events, this service ingests and eventually forgets them.
You run vouchfx and want to know exactly what vouchfx telemetry enable
would send, what it never sends, and how to check for yourself before you decide.
You want to operate an ingest endpoint — for a team, or just to see the whole loop working — without depending on a hosted instance that does not exist yet.
The guarantees
Each of these is enforced by what the code physically does — an allowlisted C# record, a partition-drop job, a fail-silent transport — not only by a paragraph in a policy document. Follow each link to the page that owns it.
vouchfx telemetry enable
Allowlist Allowlist-only, structurally — unlisted fields have no property to bind to
90 days Default retention — partitions past the window are dropped automatically
30 days Forget, on request — telemetry disable deletes your install's data
Fail-silent Never affects a run — unreachable or misconfigured, the run still completes
Trust, verified
Every event the engine would send is written first to a local NDJSON file on your own machine, before
any endpoint is configured. Nothing is transmitted until you set VOUCHFX_TELEMETRY_ENDPOINT
— until then, the outbox is the whole story.
Inspect %APPDATA%\vouchfx\telemetry-outbox.jsonl (Windows) or
~/.config/vouchfx/telemetry-outbox.jsonl (macOS/Linux) line by line — each line is
exactly what would be POSTed if a backend were configured.
Documentation
The pages below are generated from this repository's own source of truth, so they never drift from the service they describe.