Data & providers
Know where the work lives and where a render request goes.
Velatura keeps local project packages on your Mac. The rendering path you choose determines how an active request is processed.
Plain-language summary
Three parts of the workflow, stated directly.
Local projects
Velatura organizes source images, references, workflows, metadata, and outputs in local project packages and related files on your Mac. You choose the storage location and remain responsible for backups and device security.
Starter: OpenRouter BYOK
Starter uses your own OpenRouter API key and does not include managed-render credits. Your provider relationship, provider charges, account actions, and policy compliance remain your responsibility.
Managed rendering
Selected inputs, prompts, references, metadata, and generated results may be sent to Velatura servers and third-party model or infrastructure providers to process a request, estimate cost, operate the service, and deliver results.
Service use
Managed-render data is used for providing, securing, billing, supporting, and operating Velatura.
Training
Velatura does not use managed-render inputs, outputs, prompts, or metadata to train models or improve products unless that use is separately disclosed and has a valid legal basis.
Temporary service staging. Managed-render uploads and results are temporary service staging; your local Velatura project package remains the canonical project storage. Provider terms, limits, availability, and policies can differ—review them before use.
The full terms