docs(privacy): describe the hosted voice and review paths

Merged
DA
2mo ago
+68-19

What

The last piece of the hosted free tier plan: PRIVACY.md (which the site's /privacy page renders verbatim) catches up with #182/#204. It still claimed voice was off without an OpenAI key — no longer true since the signed-in account carries the hosted allowance.

  • New "Hosted voice and review" section, placed right after the account section it depends on: what each endpoint receives (a voice/pace choice from fixed sets for a mint; the bounded review fields for a review — with session identifiers called out as never traveling even to Luke's service), that the service forwards to OpenAI under Luke's key with instructions fixed at build and store: false, that audio never transits Luke's servers (the call is still a direct WebRTC connection to OpenAI), what is kept (per-account daily counters, deleted with the account), that request content is not written to logs, and the launch warmup request that carries nothing.
  • Corrected claims: the microphone section and announcement availability now key on voice being available rather than on a key; the spoken-conversation section names both paths and what deleting a key actually does now (returns to hosted while signed in); the attention-review section names both paths; OPENAI_BASE_URL is scoped to the keyed path; the key's row is placed on the Voice page where it actually lives.

Testing

  • ./scripts/check.sh passes (exit 0) — the web build embeds the markdown, so the build proves it renders.
  • Docs-only change; no UI drawing touched, no visual evidence run.

🤖 Generated with Claude Code

Open workspace in Conductor

Automated visual evidence

Download the deterministic macOS evidence · workflow run

  • Commit: f84d8841ab20f26181626514b23677330f951083
  • Scenario: smoke
  • Physical-notch check: not performed by CI