Trust & licensing
Local-first Data
The workspace is local-first and BYOK. Model requests follow the Provider connection you configure.
What you will complete
Projects, workflows, prompts, outputs, imported files, templates, and model API keys stay on your device.
In this guide
- 1Projects, workflows, prompts, outputs, imported files, templates, and model API keys stay on your device.
- 2When you run a model step, the request and selected inputs go directly to the Provider you chose under that Provider's terms.
- 3Creating or editing projects, nodes, and templates does not call a model Provider by itself.
Where data goes
Local creative data, Provider requests, and Orqra commercial services have separate authority boundaries.
| Data or action | Main destination |
|---|---|
| Projects, workflows, prompts, outputs, imported files, and templates | Projects, workflows, prompts, outputs, imported files, templates, and model API keys stay on your device. |
| Model API Key | Your API Key is stored locally. Never send it to Orqra support or enter it on the Orqra website. |
| Explicit model run | When you run a model step, the request and selected inputs go directly to the Provider you chose under that Provider's terms. |
| Test Connection and Sync Models | Testing a connection and syncing models are separate Provider network actions. Prompt and selected inputs are sent only when you explicitly run a model step. |
| Email, payment, License, activation, and release metadata | Orqra Server may store the purchase email, payment provider identifiers and status, product identifier, License status, device activation metadata, webhook records, and release metadata. It does not store your projects or creative content. |

Before you start
- Projects, workflows, prompts, outputs, imported files, templates, and model API keys stay on your device.
- Your API Key is stored locally. Never send it to Orqra support or enter it on the Orqra website.
- Orqra Server may store the purchase email, payment provider identifiers and status, product identifier, License status, device activation metadata, webhook records, and release metadata. It does not store your projects or creative content.
Complete the task
- 1
Projects / Templates
Projects, workflows, prompts, outputs, imported files, and templates
Projects, workflows, prompts, outputs, imported files, templates, and model API keys stay on your device.
Expected result
Projects, workflows, prompts, outputs, imported files, templates, and model API keys stay on your device.
- 2
API Key
Model API Key
Your API Key is stored locally. Never send it to Orqra support or enter it on the Orqra website.
Expected result
Your API Key is stored locally. Never send it to Orqra support or enter it on the Orqra website.
- 3
Run
Explicit model run
When you run a model step, the request and selected inputs go directly to the Provider you chose under that Provider's terms.
Expected result
When you run a model step, the request and selected inputs go directly to the Provider you chose under that Provider's terms.
- 4
Test Connection / Sync Models
Test Connection and Sync Models
Testing a connection and syncing models are separate Provider network actions. Prompt and selected inputs are sent only when you explicitly run a model step.
Expected result
Testing a connection and syncing models are separate Provider network actions. Prompt and selected inputs are sent only when you explicitly run a model step.
- 5
License / Release
Email, payment, License, activation, and release metadata
Orqra Server may store the purchase email, payment provider identifiers and status, product identifier, License status, device activation metadata, webhook records, and release metadata. It does not store your projects or creative content.
Expected result
Orqra Server may store the purchase email, payment provider identifiers and status, product identifier, License status, device activation metadata, webhook records, and release metadata. It does not store your projects or creative content.
- 6
Offline / Network
Know what stays local and what leaves the device
The workspace is local-first and BYOK. Model requests follow the Provider connection you configure. Support does not require uploading projects, prompts, outputs, local files, or model API keys to Orqra.
Expected result
The workspace is local-first and BYOK. Model requests follow the Provider connection you configure. Support does not require uploading projects, prompts, outputs, local files, or model API keys to Orqra.
Checks before you retry
- Your API Key is stored locally. Never send it to Orqra support or enter it on the Orqra website.
- Support can explain Orqra setup fields, but provider API keys, billing, rate limits, and model availability remain with your own provider.
- Support does not require uploading projects, prompts, outputs, local files, or model API keys to Orqra.
