Offline Local Mode
No cloud AI provider is contacted for the supported local workflow.
Private processing choices
Choose the processing boundary for the workflow.
Chameleon separates supported local workflows, user-approved hybrid processing, and server-routed cloud requests so privacy claims remain specific to the actual processing path.
Processing choices
Three clearly defined paths.
Hybrid Mode
Only user-approved content is sent to approved cloud AI infrastructure.
Cloud Mode
The approved request payload is processed through server-side provider routing.
Why the distinction matters
Privacy depends on the workflow that is actually running.
A local-capable workflow should not be described as cloud processing, and a cloud-backed workflow should not be marketed as if every part remained on-device. Chameleon documents the boundary by mode.
Supported local work
Use local execution where the installed capability supports it.
User-approved cloud step
Hybrid workflows send only the content approved for the cloud step.
Server-side routing
Cloud requests use server-side routing so provider credentials are not exposed to the browser.
Workflow-specific claims
Availability and data behavior depend on the product, feature, and enabled processing path.