You choose the window.
Homa never defaults to monitoring the whole desktop and never silently switches to another application.
SECURITY & PRIVACY
Consent is a product feature.
Homa is designed around selected-source access, visible capture and microphone states, stoppable sessions, minimal retention, and controls that remain understandable while you trade. This describes the intended product standard, not a claim that every production control is already deployed.
You can see when it listens.
Microphone, viewing, capture, analysis, and session states must stay visible and immediately stoppable.
You control what remains.
Transcripts, key screenshots, behavior analysis, reflection, and mentor memory are separate choices.
CAPTURE FLOW
One approved source. One clear purpose.
Visual context is event-driven. Homa should take a bounded snapshot only when you ask for analysis or explicitly enable session awareness.
- 01SelectChoose one supported window or a specific region.
- 02Prepare locallyResize, compress, and remove unnecessary metadata.
- 03Analyze securelySend the bounded context through an authorized backend.
- 04Discard by defaultKeep screenshots transient unless you approve key storage.
Secrets stay off the desktop
Permanent AI keys, service-role credentials, payment secrets, and private prompts that can remain server-side do not belong in the desktop client.
Ownership on every record
Authentication is not enough. Sensitive routes and stored resources require explicit authorization and ownership checks.
No stealth and no execution
Homa is never designed to evade screen sharing, employers, proctors, or platform detection, and it never touches broker controls.
Minimal observability
Reliability data should exclude screenshots, raw audio, secrets, private prompts, and unnecessary transcript content.
PUBLIC DOCUMENTS
Read the policies behind the interface.
The public legal drafts remain subject to qualified counsel review before production launch.