Privacy & Safety
Understand Raydo's local-first model, permissions, and side effects.
Raydo is local-first, but some workflows still use providers, runtimes, app connections, browser sessions, or cloud features. Users should know the boundary before running work.
Practical rules
- Local projects and local artifacts should remain inspectable on your machine.
- External providers may receive prompts, context, or task content needed for a run.
- App Connections should be treated as permission boundaries.
- Side-effecting actions should be visible and approval-aware.
- Diagnostics should be redacted before sharing.
Permission checklist
Confirm what Raydo needs to read.
Confirm what Raydo may write or change.
Confirm whether an external provider or app connection is involved.
Inspect the result and diagnostics before sharing.