Security and privacy

# It sees enough *to notice*

Presence separates continuous coarse perception from deliberate visual inspection. Recording and durable retention are separate capabilities, not consequences of joining a Session.

01 / PERCEPTION

## Signals before pixels

Presence continuously reads coarse state such as present, looking away, screen shared, and engaged. It does not send a continuous video feed to the reasoning model.

02 / INSPECTION

## Frames only when the task calls for them

When reasoning requires visual detail, the model receives a frame. Low resolution is the default; higher resolution is available when the task requires it. Frames are not retained in later conversation history.

03 / RECORDING

## Off by default

The launch demo is not recorded. Other sessions require separate, session-specific authority and applicable participant consent before recording or durable media retention.

04 / CREDENTIALS

## The browser gets a Session, not your API key

Browser clients receive session-scoped credentials. API keys remain outside frontend source, URLs, browser-exposed environment variables, and the embedded Presence client.

The launch demo

## Camera and microphone on. Recording off

The demo processes camera and microphone media live so Presence can see and hear the participant. It is not recorded. Closing the Session ends the embedded client and its session-scoped access.

Public policies

## The facts here are product behavior. The policies remain canonical

[Privacy policy](https://bohita.com/privacy) [Terms](https://bohita.com/tos) [Agent-readable notes](https://presence.bohita.com/llms-full.txt#privacy-and-retention)