Data and privacy

Product telemetry

fx does not send product telemetry or usage analytics to a separate fx service. fx usage reads local usage records, and /trace assembles diagnostics locally.

When automatic updates are enabled, native fx reads static release metadata after startup and every 30 minutes until an update is ready. The request contains no fx-generated machine or installation identifier.

Inference APIs

fx sends model requests using the AI SDK Language Model Specification, a standard interface across inference providers. AI Gateway receives that request and routes it to the selected model provider.

Model request data

Each model request includes your prompt and the context assembled for that turn. Context can include conversation history, applicable AGENTS.md and skill instructions, attached images, and file or tool content already loaded into the session.

fx does not automatically package or upload your workspace, Git history, session files, traces, or recordings. That data can still leave the machine when it is loaded into model context or sent by a networked tool. Web search, web fetch, remote MCP servers, and other networked tools send inputs to the services they call when invoked.

AI Gateway controls

AI Gateway does not retain prompts, outputs, or sensitive data after a request completes. It does record request metadata such as the model, token counts, latency, and cost for billing and observability. Model and tool providers can have separate retention policies.

Pro and Enterprise teams can enable team-wide Zero Data Retention, which routes requests only to ZDR-compliant providers and also disallows prompt training. fx uses the AI Gateway settings associated with the active Vercel team or API key.

Local inference

fx can use compatible loopback endpoints for model discovery and generation. This supports a fully hermetic setup: with outbound networking blocked, prompts and model context stay local and networked tools cannot make requests.

Local credentials and sessions

Native fx stores private runtime state under ~/.fx/, including settings, the saved Vercel login, sessions, prompt history, usage records, MCP configuration and credentials, managed skills, default debug trace logs, and automatic recordings. On macOS, a saved API key lives in Keychain. On Linux, it lives in ~/.fx/api-key with 0600 permissions.

Session files remain local, but fx sends the relevant conversation context again when you continue a session. Use fx ask --no-save when a one-off request should not create a session.

/trace creates a local diagnostic report and copies it to your clipboard when supported. If clipboard copying fails, fx leaves the report in a local temporary file. /feedback opens the feedback form without uploading diagnostic data.

Review and redact prompts, code, paths, commands, model output, and secrets before sharing a trace or recording. See Share feedback for details.