Privacy & cloud storage

Last updated: September 10, 2026

Cloud studio is an account-based storage feature. Unlike API-only delivery, it saves canvas content and media so you can continue your work on another device. Do not upload material you are not authorized to store or process.

1. Account, billing and technical data

We process usernames, email addresses, password hashes, top-up records, payment references, balance and usage history, referral relationships, IP addresses, and request metadata to operate and secure KinoAPI. Card details are processed by our payment provider, not stored by the cloud studio. Existing billing, moderation, and referral rules continue to apply.

2. What cloud studio saves

When you use cloud studio, we store your project and group names, canvas nodes and connections, viewport, prompts, model settings, uploaded image/video/audio references, generation task receipts and status, result links, and generated media copies when caching succeeds. Data is associated with your KinoAPI account ID. Language and selected API-key ID are saved as preferences. Browser local storage contains only the language preference; session access tokens stay in memory.

Your account's native API key is retrieved only for authorized generation or status queries and may be held temporarily in server memory. Cloud studio does not persist the key secret in its project files or expose it to the browser.

3. API-only requests and generated links

Calling the API alone does not automatically create a cloud canvas or cloud media archive. Generation inputs are processed by our relay and safety screening, then sent to the upstream model service. Provider result links can expire. In cloud studio, a completed task may still lack a cached copy because of storage limits, media size, host restrictions or network failure. Check the task's cloud-copy status and download important results promptly.

4. Storage limits and retention

Initial media allowance: 512 MB per account. Each reference upload and the total references in one generation request are limited to 30 MB. A generated cloud copy is limited to 100 MB. Projects are limited to 100 per account, with 50 groups and 2 MB of canvas data per project. Cloud generation allows 64 KiB of combined prompt text; Seedance 2.5 keeps its stricter 16 KiB limit. Text is rejected if too large, never silently shortened.
Cloud content remains associated with your account until deleted or the account is removed, subject to service availability and the limits above. We keep the latest ten saved project revisions. A separate 128 MB operational allowance covers project metadata and receipts; writes stop before that limit when headroom is needed.
Deleting a project removes it from the workspace immediately. Its archived canvas and revisions are permanently removed by hourly maintenance after seven days. This does not delete its uploaded media or task history.
Deleting an unused media file removes the active server copy. A file referenced by a saved project must first be detached. Task receipts may retain the original provider link after deletion; deleting our copy cannot revoke an upstream link.
The workspace shows the latest 200 task receipts and retains up to 1,000 in its task index. Separate paid-operation receipts are retained for the account's lifetime to prevent accidental duplicate submissions. Completed non-paid editing receipts are pruned after seven days; uncertain receipts are retained for investigation.
Account and billing records may be retained for operational, audit and legally required purposes. Contact us to request account-level deletion or removal of archived records, subject to required retention.

5. Who processes the data

Our cloud infrastructure hosts account and studio data. Upstream model services receive the prompts and reference media needed to fulfill generation requests; payment providers receive information needed to process payments. Authorized administrators may access server data for support, security and service operation. Cloud content is private to your account in the application, not publicly listed, but it is not end-to-end encrypted. We do not sell personal data.

6. Security and backups

We use HTTPS, native account authentication, per-account authorization, private file paths, restricted server access, file-type and size checks, and revision checks to prevent overwriting newer canvas edits. The initial cloud deployment stores data on the service server. Project revisions are recovery aids, not an independent off-site backup or a guarantee against server loss. Export important projects and download important media. No storage or transmission method is completely secure.

7. Access, correction and deletion

You can export projects, download media, edit saved content and remove unused files in the workspace. To request access to, correction of, or deletion of account data, contact privacy@kino-api.com. Additional rights may apply depending on your jurisdiction.

8. Changes and contact

This page describes the current cloud studio behavior. Material changes to data handling will be communicated through the service. Privacy questions: privacy@kino-api.com.