Speech stays local until it becomes text
The Fluent wake listener and command transcription run on the Windows device. A bundled whisper.cpp runtime converts captured command audio into text. No cloud speech API receives the raw audio.
Local transcription does not make the whole task offline. The resulting text request is sent to the hosted planning provider selected by the user. That provider may also receive textual UI context needed to plan the requested action. Users should review the provider's own retention, account, and data-use terms.
Gaze is opt-in context, not activation
Gaze is disabled by default. When enabled, raw samples remain in a short in-memory buffer and are not persisted or included in agent input. WebGazer calibration data may remain in local browser storage.
A stable fixation can be resolved locally to an accessibility element. Structured fields such as accessible name, role, process, bounds, fixation duration, and timestamp may accompany a submitted request. The planner is instructed to treat this target as untrusted context and never as a coordinate-click command.
Visible action does not equal complete safety
Fluent displays action progress, supports cancellation, redacts sensitive action previews, classifies tool risk, and includes confirmation behavior. Those controls are meaningful, but the current product audit found that consequential actions can still bypass the intended approval story through some generic automation paths.
The alpha gate requires all consequential-action fixtures to pause and denial to execute zero times. Until that gate is demonstrated on an installed build, users should avoid sensitive, irreversible, financial, publishing, account, or system-changing tasks.
The release standard is user ownership
The release scorecard requires legible activity, memory, logs, diagnostics, bounded retention, and export and deletion controls before public release. It also requires secure provider setup, signed distribution, update and rollback behavior, and an accurate public privacy contract.
The public website can optionally initialize PostHog when a project token is configured. That setup keeps anonymous visitors out of person profiles and disables session replay, but ordinary page, interaction, browser, and device metadata can still reach the configured PostHog host.
Current developers should keep API keys in an untracked .env file, use the example configuration, avoid sensitive test data, and review generated logs and activity.