Data Policy
Training and inference
We do not use customer prompts, uploaded media, or generated outputs to train or fine-tune OrcaRender's general-purpose models, or sell them as training datasets. Rendering and automated quality checks use model inference. Separate training use requires a separate, explicit agreement.
Agent-assisted planning, opening-image generation, and revisions may send relevant instructions, conversation context, and reference content to external AI services, including OpenAI. Their processing and retention terms also apply. Direct render execution uses assigned local or remote render hosts. We do not claim that all features have identical subprocessors or retention, or that upstream services are zero-retention.
What is stored and for how long
| Category | Current behavior |
|---|---|
| Integration/API result media | Availability normally expires 24 hours after the underlying job finishes, unless another integration retention period is configured. Access checks enforce expiry; background cleanup removes eligible files asynchronously. Download results promptly. |
| Integration input media | Inputs can remain while referenced by jobs or results. Eligible unreferenced integration files are cleaned in the background. There is no universal promise to erase every input 24 hours after upload. |
| Studio uploads and projects | Retained to support the user's library and project history, subject to storage limits and available deletion controls. No blanket automatic 24-hour deletion. Files referenced by retained jobs may require deleting the relevant jobs first. |
| Prompts, job settings, agent histories, and operation records | Stored in application records for execution, history, support, and diagnostics. Can remain after media expiry. No automatic fixed deletion deadline is currently enforced across these records; request account/content deletion for review. |
| Access, security, and error logs | May contain IP addresses, request metadata, identifiers, and diagnostic information. We do not promise that every error trace is content-free. No single fixed automatic retention limit is currently guaranteed across all hosts. |
| Billing, usage, and account records | Retained for account operation, reconciliation, fraud prevention, disputes, and legal obligations. Deleting result media does not delete the associated usage receipt or automatically reverse a completed charge. |
| Backups and remote working files | Deletion from the application is not synchronous erasure of every backup or remote temporary copy. Cleanup and backup handling are separate. No uniform maximum backup-erasure deadline is currently promised. |
Access and disclosure
Outputs are private by default and require the appropriate account or integration authorization. The person or application holding an authorized credential can retrieve its results, and we send configured callbacks to the customer's endpoint. Protect tokens and share outputs only with intended recipients.
Compute/storage providers, requested AI services, and authorized personnel may process content to deliver requests, troubleshoot failures, investigate abuse, or comply with law. Stripe handles payment processing and Mailgun may deliver account email; those functions do not require sending rendering media to them. See the Privacy Policy for more information.
Deletion requests
Use available project/asset deletion controls or email support@orcarender.com with your account email and relevant operation identifiers. Do not send credentials. We verify ownership and review retained dependencies, billing/security records, backups, and legal requirements. Where you used another company's application to access OrcaRender, contact that company as well.
Processing locations and regulated data
The service uses multiple render hosts and external services. A specific country, regional lock, zero-data-retention arrangement, HIPAA eligibility, or other regulated-data assurance is not included by default. Ask us to confirm processing locations and required contractual safeguards before transmitting restricted or sensitive data. No certification or data-processing agreement is implied by this page.
Provider onboarding summary
OrcaRender performs inference rather than training on customer content. Prompts and operational records are retained; API result-media availability normally expires after 24 hours. Other data classes have separate retention behavior and currently no universal automatic deletion deadline. Zero data retention: not offered. This summary does not override a separately agreed customer retention arrangement.