Beta privacy notes

ThreadCast Privacy Notes

Updated August 29, 2026

These notes describe the current paid-beta architecture, including local processing, OpenAI API use, Android connections, and checkout.

Local Codex activity

ThreadCast reads local Codex task metadata and task activity needed to identify selected tasks, prepare spoken playback, follow updates, and detect completion. That processing occurs on the Windows computer.

OpenAI API requests

Selected task text can be sent to OpenAI services using the buyer's own API key to prepare and synthesize spoken playback. The buyer's OpenAI account, settings, and API terms govern that processing and cost.

Secret storage

The OpenAI API key and the Android prompt token are stored in an app-local file under the Windows user profile. ThreadCast avoids using a machine-wide OpenAI key by default. Stronger operating-system-backed secret storage remains a pre-release hardening item.

Android connection

The Android companion connects directly to the buyer's Windows computer over loopback or a private Tailscale address. Playback data, selected task identity, status, and submitted prompts travel through that private connection; Hominocentra Systems does not operate a relay server for it.

Purchase information

Ko-fi and the connected payment processor handle checkout and digital delivery under their own policies. Hominocentra Systems will receive the order details those services provide to the seller for fulfillment and support.