Trust
Know where the work runs and where the data goes.
Privacy should be an execution choice you can see. OYYO is designed to show where a task runs, which data it touches, which connectors are permitted, what is retained and what is logged.
Capability scope
The full surface, stated plainly.
Each item is described as designed. Status labels on this page show what is shipped and what is planned.
User-facing model
- Where the task executes
- Which data class it touches
- Which connectors are in scope
- What is retained
- What is logged
Privacy modes direction
- Local-only execution
- Hybrid with explicit boundaries
- Cloud with declared providers
- Per-project data class rules
The portable workspace direction keeps the approved workspace as the source of truth without mandatory cloud synchronization. OYYO Privacy ONE is the planned mobile client, not a released product.
This capability is part of the published OYYO roadmap. It is described here as designed and planned, not as shipped software.
Continue
Related parts of OYYO.
Every OYYO layer shares one context, one memory and one permission model.
Think. Create. Execute.
One intelligence. One workspace. One place for everything.
OYYO is being built in public against a versioned release line. Join the early access list and follow the roadmap.