Privacy details

Internal software prototype

The following describes our internal software prototype. The demonstrations on this website are not connected to open-ended AI conversation or hardware control.

The internal prototype stores conversations and confirmed memories in the current browser. Online conversations send selected context to a model service. It relies on online services and is not fully offline.

Internal testing supports memory suggestions, confirmation, editing and removal. The complete privacy center, account isolation and cross-device synchronization are not yet implemented.

Data and access · Product requirements

Planned collection requires user-enabled microphones, visible listening status and separate authorization for additional sensing. Raw audio should not be retained long term by default.

The planned privacy center would cover conversations, memories, characters and devices: viewing, correction, export, deletion and revoking sync. Sensitive intimate information requires separate confirmation; memory sources and revision history remain planned.

Local saving and optional cloud sync are planned choices, separate from online model processing. Online processing should be explained, send only relevant context, and show processing and sync status.

Access requirements include separate authorization for each user, encrypted cloud storage and transport, limited diagnostic access with access records, device unbinding and clearing data before resale. These are development requirements, not completed capabilities.

Planned guest sessions would clear when the visit ends and stay outside long-term memory. App locking, hidden notification content and switching history off are also planned.

Purpose and separate consent

Our formal-product principles exclude selling private conversations, recordings or intimate preferences to advertisers, or using them for ad profiles. Model training is off by default; research or improvement requires separate consent.

Declining or withdrawing research consent should not remove access to basic functions. These principles do not establish the processing terms of an unconfirmed model or service provider.

Deletion, retention and open questions

Deletion requirements cover related records and synchronized copies. Backup retention, clearance periods and completion times still need to be defined and published, and deletion must be verified beyond the interface.

The final privacy policy, deployment arrangements, model and other service-provider processing terms, retention schedules and verified deletion behavior are not finalized. They must be defined before the corresponding formal features become available.

Age, representation and physical validation

ZUO is intended for adults 18 and older. Age access and region-specific requirements will be addressed before commercial availability.

Characters start with original adult identities. Any use of a real person’s face or voice would require permission. Representation testing should include different backgrounds, languages and identities.

Motion limits, contact, materials, electrical safety, stability and stopping require physical validation. Offline stopping and returning to a neutral posture remain engineering goals, not completed hardware capabilities.