Trust
Know where the work runs and where the data goes.
Privacy as an architectural choice: execution location, data class, retention and connector scope should all be visible before work starts.
On the roadmapยท 0.1.0-foundation
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
Privacy should be a setting you can see, not a promise you have to trust.
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.