Where voice, text and identifiers are handled

Understand watch storage, transient relay processing and provider-held context.

Robert Szabo

Last Update 11 hours ago

WristVoice AI is in private testing. These instructions describe the current test app. Public checkout and automatic activation remain subject to production verification.

On your watch and in the relay

On your watch, the app keeps settings and access information. When context is enabled it also keeps bounded recent conversation text. Audio can remain temporarily in memory during a request or retry. With context off, the displayed interaction is not saved after the app closes.
Our AWS relay handles audio, transcripts and answers in memory to process the request. It does not save those contents in its databases, files or application logs. It does retain necessary access, subscription, usage, security and conversation-link metadata.
Activation identifiers
During activation or recovery, your Garmin app-specific device identifier passes through the relay in memory to WearCheckout for watch-association verification. The relay does not save or log the raw identifier, and does not send it to OpenAI. Routine voice requests use service credentials and the hashed identifier. Re-verification may be needed after an interruption or during recovery.
The identifier is app-specific, not a Garmin serial number or hardware attestation. Its retained hash is pseudonymous, not anonymous, and can be linked to subscription information. Necessary access and usage accounting cannot be disabled while using the service.
OpenAI, encryption and privacy
OpenAI processes the speech and text. Server context keeps conversation content at OpenAI under its retention rules. Reset conversation de-links the old reference; it does not delete that content.
Connections use encryption in transit, but the relay and OpenAI can read content during processing. This is not end-to-end encryption against those services. Avoid sharing sensitive material unnecessarily and consult the full privacy policy for retention, rights and contact details.

Was this article helpful?

0 out of 0 liked this article

Still need help? Message Us