Privacy policy

Effective date: 28 October 2026 · Last updated: 28 October 2026.

Who is responsible

The service operator and data controller is wen yong, an individual based in China, operating Tiny Desk Video AI at tinydeskvideoai.com. Privacy enquiries go to support@tinydeskvideoai.com. The service is intended for adults 18 or over; do not upload children's portraits.

Information we process

What happens to a photo

Selecting a photo creates a preview on your device; the source file selection limit remains 8 MiB for JPEG, PNG or WebP. When you click Upload photo, a large image may be compressed or converted to JPEG on your device to fit hosted-request limits before it is sent to this service. This does not upload the selected file merely because you chose it. The server decodes the accepted image, applies orientation and creates a JPEG processing copy without retaining the original upload bytes as an archive.

The processing copy is stored privately in Cloudflare R2. Waffo PromptSift receives the generation instructions for a text safety check before a request can consume 100 credits. If that check permits the request, the server makes the photo available to MiniMax through a time-limited retrieval link and submits the instructions. MiniMax's international API, configured with MiniMax-H3-Max, processes the photo and produces the video and native audio. The provider may refuse a request under its own controls. The generated performance is synthetic.

The result is retrieved, checked for technical media and delivery properties, and stored privately. Account-authenticated routes make completed results available to their owner; there is no public sharing link. A technical check or permitted instruction does not establish consent, rights or media safety. Deletion requests and unresolved task-specific restrictions can disable access. Provider roles, international processing and retention are described below.

Providers and international processing

Providers can process data outside your country. The database is currently provisioned in a US region; a storage location hint is not a guarantee of residency. Provider copies, international processing and model-improvement settings depend on the applicable provider arrangement. We do not claim zero retention or that upstream providers never use data for model improvement. We do not sell personal information or portraits, independently train our own models on uploads or treat uploading as permission to use a portrait in our advertising.

Cookies and browser storage

Authentication uses session cookies. Language/theme preferences and verification-email cooldown or unfinished-submission information may be stored in the browser. If a landing link contains a referral source, the current implementation can store a referral cookie for 30 days and attach the source to registration. Blocking storage can affect convenience features; it does not bypass server authentication or sending limits.

At this policy’s effective date, Google Analytics, Clarity, Plausible, OpenPanel and Vercel Analytics are not configured in the current build. Optional tracking or marketing changes require appropriate notice and any consent controls applicable to the selected markets before activation. We do not claim that all cookies are strictly necessary or that a consent centre already exists.

The hosted checkout collects payment-method details under its own terms. This product does not request or store full payment-card numbers or security codes.

Retention and deletion

By default, media is retained for continued account use until a deletion or closure request. Any configured automatic-retention period and changes to the published practice must be reflected in the service notice. An expired access link does not delete its underlying file. Download results you need; media storage is not a permanent-backup guarantee.

While signed in, use Account to request photo or generated-work deletion, inspect deletion status, or confirm account closure. Acceptance first closes access to the affected media and queues physical cleanup. Active generation tasks and uncertain paid-provider results may be held for reconciliation before cleanup, so an accepted request is not proof that every object has already been erased. Removing a source photo does not itself remove a separately retained completed video; select the video too, or close the account to queue both.

Account closure revokes public sign-in credentials and sessions, removes public profile identifiers and associated account/chat data, and queues remaining media for cleanup. Financial records and necessary moderation, deletion and dispute audit records remain separately retained; closing an account does not automatically refund money. For known completed MiniMax tasks, cleanup can request deletion of the provider's task record. That is not a guarantee that all upstream copies, backups or legally retained provider data disappear. Provider retention remains subject to the actual provider arrangement.

You can request access, correction or deletion through support. We may need proportionate account verification, without asking for your password. We aim to respond or explain progress within 30 days, subject to shorter legal deadlines. A response target is not a guarantee that all controlled objects, backups or provider copies are deleted within that time. Legal, financial, security or unresolved-dispute records are assessed separately; the response should explain the affected categories and reasons. No immediate or worldwide deletion is promised.

Security and your choices

We use hashed email-account passwords, separate administrator authentication, private media storage and owner access checks. No security measure guarantees complete protection. You can choose whether to use Google sign-in, refrain from uploading a photo, and manage browser cookies. Do not upload material you lack permission to process.

Depending on applicable law, rights may include access, correction, deletion, account closure, restriction, objection, portability, withdrawal of consent for future processing and a complaint to the relevant authority. These requests do not automatically settle a purchase dispute or erase legally required records. No regulator or universal set of legal rights is invented by this policy.

Making a privacy request or reporting a security concern

Use the support address with the subject “Privacy request” or “Security concern”. State the type of request and the account or relevant task/order reference. We may ask for information reasonably needed to establish that the request concerns your account or a person you can represent; do not send a password, session cookie, verification link or full payment-card data.

A privacy request is distinct from a refund request. Where records cannot be removed because a dispute, security investigation or legal retention obligation remains, the response should explain the affected category and reason. Provider-held copies require separate coordination; downloaded or independently retained copies cannot be promised erased. Reply to the same case for reconsideration.

Changes and contact

We retain financial, security, support, deletion and dispute records as needed for the purposes described in this policy and applicable obligations. The required period can depend on the record and the matter involved. Contact support for the categories and reasons relevant to your request. Provider copies and backups remain subject to their own applicable arrangements; a completed local cleanup is not a guarantee of universal erasure.

We will update this policy when processing arrangements or practices change and communicate material changes through the service or account email where appropriate. Questions: support@tinydeskvideoai.com. Related: Terms, Acceptable use, AI disclosure.