Owl3D Cloud API Terms
Version: v1
Last updated: November 2, 2026
Owl Technologies Inc., doing business as Owl3D ("Owl3D", "we"). 300 Lenora St. #6111, Seattle WA 98121, United States. Contact: support@owl3d.com.
Words used here: "API" = the Owl3D Cloud API and the Owl3D MCP server. "You" = the account holder who makes an API key or authorizes an App. If you accept for a company, you bind that company. "App" = software that connects to the Owl3D MCP server after you sign in with Owl3D, such as an AI assistant. "Content" = the videos and images you upload. "Output" = the converted 3D files that we return.
How these terms fit with our other terms
These terms apply when you use the API. The Software Terms of Service also apply. They include the warranty disclaimer, the limit of liability, the indemnity, and governing law and disputes (sections 15 to 19). They also include export rules (section 21). In those sections, "Services" includes the API. Section 8 of the Software Terms (local processing) does not apply to the API, because the API processes your Content on our servers. If the two documents conflict for the API, these terms control. Mandatory consumer rights are not affected.
1. Your content
1.1 You keep the rights you hold in your Content. We claim no ownership of your Content or your Output. A conversion gives no rights in third-party material.
1.2 You give us a limited licence to store, copy and process your Content and Output. We use this licence only to run the conversion you ask for, to deliver the Output, to prevent abuse, and to meet the law. The licence ends when we delete the Content and Output (section 3).
1.3 You confirm that you have the rights to upload the Content and to have it converted to 3D. This includes films, music videos and other works that belong to third parties. You are responsible for the claims of rights holders against your use.
1.4 Our staff do not look at your Content, with three exceptions:
- you ask us for support on a job.
- we must check a report of abuse (section 6).
- the law requires it.
Automated checks read files for format, size, length and file safety.
2. Personal data
2.1 If your Content contains personal data, you decide why and how that data is processed. We process it for you, as your processor, only to do what these terms and your API calls ask. You must have a legal basis for that data and give the notices the law requires.
2.2 We are the controller of account, billing and security data. Our Privacy Notice covers that data and explains your rights. To make a privacy request, write to support@owl3d.com.
2.3 We use other companies for GPU processing, storage, hosting and sign-in. These companies can process data outside your country, including in the United States. Where the law restricts such a transfer, we use a legally permitted basis. Business customers can ask us for the current list at support@owl3d.com.
2.4 We do not sell personal data in your Content. If a security incident affects personal data that we process for you, we tell you without undue delay.
2.5 If your business needs a data processing agreement, ask us at support@owl3d.com.
3. Retention and deletion
3.1 We schedule deletion of your data within these periods:
| Data | Kept for |
|---|---|
| Uploaded Content | up to 7 days after upload |
| Work files (parts of a conversion) | deleted when the job ends, at most 3 days |
| Output | up to 30 days after the job ends |
| Download links | at most 15 minutes from when you ask for one |
3.2 Download your Output before it expires. You can delete an Output earlier. After deletion we cannot restore it. We cannot delete copies that you or an App already downloaded.
3.3 We keep records about jobs: time, length, credits, status, the key or App used, and the file name of an API job. These records stay after the video expires, for as long as your account exists and then as long as tax law requires. We use them for billing, your usage reports, security and the law. They do not contain your Content.
3.4 We keep security logs for up to 90 days. We keep diagnostic logs only as long as we need them to run and fix the service.
4. No training on your content or outputs
4.1 We do not use your Content or your Output to train, tune or evaluate our models. The only exception is a named project that you agree to in writing.
4.2 You may not use the API, the Output or any data from the API to train, tune or distil certain models. These are models that convert 2D to 3D, estimate depth, or compete with the API. This includes building a dataset of inputs and Outputs for that purpose. This applies only where the law allows us to restrict it.
4.3 You may not try to extract our models, weights or code from the API (for example by systematic queries, reverse engineering or scraping).
5. Apps that connect through MCP
5.1 You connect an App by signing in with Owl3D and approving access on the consent screen. We choose which Apps can connect.
5.2 An App acts for you. You are responsible for what you ask it to do. The App maker's own terms and privacy policy apply to that App. We are not a party to them.
5.3 You can disconnect an App at any time on the API keys page. Access already issued can work for up to 15 minutes after that. Disconnecting does not erase what the App already received.
5.4 We can disconnect an App when it breaks these terms or puts the service at risk (section 6).
5.5 The API has no sign-in for third-party apps. If you build software for other people, each person must use their own API key on their own account. You must not ask them for their Owl3D password or their email codes. To offer more than this, ask us for a written agreement at support@owl3d.com.
6. Acceptable use, abuse and suspension
6.1 You must not use the API:
- for content that you do not have the rights to convert, or that infringes the rights of others.
- for sexual content involving minors, content that sexualizes real people without their consent, or other illegal content.
- to get around credit limits, rate limits, the limits on videos in progress or our security checks.
- to send files made to attack our systems (for example malformed media or playlists that point to other files or addresses).
- to resell raw API access without our written agreement.
6.2 We may limit, suspend or end an API key, an App or an account when:
- we see a breach of these terms.
- a rights holder or authority sends a valid notice.
- the use puts the service or other users at risk.
Our action will match the size of the problem.
6.3 When we can, we tell you first, give the reason and give you time to fix the problem. In urgent cases (security, illegal content) we act first and tell you after. You can ask us to review the action at support@owl3d.com.
6.4 If we suspend or end your account, we refund your unused purchased credits. We do not refund them when the cause is fraud or illegal content, unless the law requires it.
6.5 To report abuse or an infringement, write to support@owl3d.com. For an infringement, give your contact details, the work, and the job id or account if you know it. Also state that you act in good faith for the rights holder. We answer reports within 2 business days.
6.6 If we act on an infringement notice, we tell you. You can reply with the reason that you believe the notice is wrong. We end the accounts of repeat infringers.
7. Keys and security
7.1 Your API keys are like a password for your credits. Keep them secret. Do not put them in software that runs on other people's devices.
7.2 You are responsible for use of your keys until you revoke them, except where a failure in our own security caused the use. If a key leaks, revoke it at once on the API keys page and tell us.
7.3 We show a key only once, when you make it. We cannot show it again.
8. Credits and limits
8.1 A job spends your plan allowance first, then trial credits, then credits that you bought.
8.2 If a job fails, we release the credits held for it. Prices are in the API documentation and on our pricing page.
8.3 We may set limits on the API, for example on videos in progress, daily credits per key and request rates. We publish the current limits in the API documentation. The API has no uptime commitment unless we agree one in writing.
9. Changes and ending
9.1 We may change these terms. We give at least 14 days' notice of a material change, by email or in the API documentation. For a security or legal need, the notice can be shorter. If you do not accept a change, stop using the API.
9.2 You can stop using the API and revoke your keys at any time. Your data then follows section 3.