privacy policy
last updated: may 2026. applies to the gitfix vs code extension (v0.99.0+).
1. what we collect by default
nothing. the extension ships with gitfix.telemetry.enabled: false. when telemetry is off, all instrumentation is a no-op. we log diagnostic information to your vs code output channel only — it never leaves your machine.
2. if you opt in: the five events
when telemetry is enabled, we collect exactly five event types. the schema is fixed for v0.99 and published here.
fires once per session when the extension activates.
fires when you open a conflict preview. no file paths.
fires when a single conflict hunk is resolved.
fires when a resolution is written to disk.
fires on caught errors. error messages, stack traces, and file paths are never captured.
3. what we never collect
- [×]file paths or directory names
- [×]branch names or commit hashes
- [×]conflict content or diff text
- [×]error messages or stack traces
- [×]repository names or remote urls
- [×]your vs code settings (other than the gitfix.telemetry flag itself)
- [×]any personally identifiable information
4. backend status in v0.99
for v1.x, we will decide between application insights, posthog, or keeping the transport stubbed based on dogfood feedback. we will announce the decision and update this page in the same pr that flips the switch.
5. how to disable telemetry
two ways:
- [×]gitfix extension setting: open vs code settings → search
gitfix.telemetry.enabled→ set to false. this is the default. - [×]vs code global switch: vs code → settings → telemetry → set to off. gitfix respects the
telemetry.telemetryLevelsetting and disables all instrumentation when it is set to “off” or “error”.
6. contact
questions about this policy or the extension: ameypawar1237@gmail.com. for bugs or feature requests, open an issue at github.com/ameyypawar/gitfix.