Backseat Verse Back to studio

POLICY VERSION 1.1 · LAST UPDATED 7 October 2026

Privacy Policy

How Buildora handles photos, accounts, video requests and related records for Backseat Verse.

Operator
Buildora
Type
Individual operator
Country
China
Contact
[email protected]

Live generation depends on the availability and credits shown in the studio. Purchases remain disabled while the Waffo Pancake merchant application is completed.

Backseat Verse is operated by Buildora, an individual operator based in China. Use the studio-specific support email on this page for privacy questions and requests. This policy covers the studio workflow; third-party services also apply their own policies to their processing.

The studio shows whether live generation is available for your account. Purchases are disabled while merchant setup is completed. Optional Umami analytics follows the consent controls described below. The remaining sections explain processing when the corresponding service is used.

Choosing two separate portraits, one per performer creates local previews in your browser. It does not upload the selected files. Use the two individual upload slots in performer order. Each slot needs a separate clear portrait; the studio sends both references to the provider. JPEG, PNG and WebP files are accepted, with a 4 MiB limit per file. Removing a selected file before submission removes its local preview.

Before upload, your browser resizes and compresses each photo locally; the resulting copy is used for both safety review and video generation. When photo safety review is enabled, Cloudflare Workers AI checks that copy before it is sent to KIE, and our review audit retains decision metadata rather than the image or the raw model response.

After you confirm permission and choose Generate in the live workflow, the studio connects an account or guest session, uploads the required photos to Cloudflare R2 storage, and, once any enabled safety checks pass, sends their URLs, selected duration and scene instructions to KIE through our generation service. The provider receives the image content needed for the video request.

A request may leave an uploaded file in storage even if another upload or generation later fails. Clearing an upload slot, starting another video, leaving the page or clearing browser storage does not delete a file already uploaded.

Account access can involve your email address, name, avatar, sign-in method and the credentials needed for that method. An enabled third-party sign-in provider handles its own authentication and returns the profile information you authorize. Guest access uses a generated guest identifier and a device-derived fingerprint for session and abuse controls.

The guest fingerprint is derived from browser and device characteristics, including language, hardware concurrency, screen size and color depth, pixel ratio and time zone. The service hashes these characteristics; that hash still functions as a persistent technical identifier, so it should not be treated as completely anonymous.

Generation records include the studio and account reference, job and task identifiers, image URLs, chosen duration, status, provider responses, result URL, credit charge or restoration, and timestamps. Necessary operational logs can include request metadata, network information such as IP addresses, errors and security events.

If you contact support, we receive the contact details, message and references you provide. When payments are enabled, records can include buyer email, checkout and order identifiers, selected package, amount, currency, payment status, credit grants and refund information.

Information is used to authenticate access, perform the generation you request, store and deliver media, recover an unfinished task, maintain credits and orders, answer support requests, prevent abuse and meet applicable recordkeeping obligations.

Where applicable law requires a lawful basis, requested account, generation and purchase functions are processed to provide the service or perform a contract; necessary security and fraud prevention may rely on legitimate interests where permitted; legally required records rely on legal obligations. Optional analytics, if enabled, follows your consent choice. Permission to use another person’s photo remains your responsibility.

Necessary cookies maintain authenticated sessions and refresh access. Browser localStorage can cache account profile details, credit balance and the selected active API key so the studio can use your account. The active API key is a credential, not just a hash: keep your device private and do not copy browser storage to others.

To recover an unfinished generation, browser storage retains the studio and account reference, stable job ID, uploaded image URLs, duration, credit limit, API-key fingerprint, attempt and timestamps. It does not save the original local photo files or the verification token. Changing the execution key can prevent recovery of the original paid request.

Browser storage also records analytics consent and relevant preferences. You can delete local data using your browser settings, but this may end access or remove the ability to recover a pending task. It does not erase server or provider copies. Necessary sessions and credit recovery are separate from optional analytics.

Cloudflare provides the configured website and service infrastructure, including Workers request handling, R2 photo storage and database services for account, task and billing records. If verification is required, Cloudflare Turnstile processes the technical signals needed to evaluate that challenge.

Live videos use ByteDance Seedance 2.5, accessed through KIE. KIE receives source image references and generation instructions; its services and the underlying model infrastructure may process that content. The studio does not have a verified provider-wide retention deadline or no-training commitment for API photos and outputs.

If payment becomes available after approval, Waffo Pancake will host checkout and process payment details. The studio receives order and payment information needed for credit delivery and billing review; the studio does not provide a form to collect a full card number or security code. Waffo checkout has its own notices and terms.

Information may also be disclosed as required by a valid legal request, to address abuse or rights complaints, or with your authorization for a specific request. This workflow does not include advertising audience sharing or the sale of your photos.

The production studio uses a separate site identifier in our self-hosted Umami service to measure permitted public-page views, subject to the consent controls and Do Not Track setting. You can decline optional analytics without losing the ability to upload, sign in or generate. Local development and preview domains do not send analytics.

The integration limits page-view payloads to the public page path and site identifier. It removes query strings, fragments and referrers and excludes auth and dashboard routes. It does not send uploaded files, image or result URLs, task IDs, account details or purchase events as analytics payloads. The analytics server can still receive ordinary technical information associated with a network request.

This studio does not enable session replay, advertising pixels or marketing event tracking. If the analytics scope changes, this policy and the corresponding consent controls must be updated.

Uploaded photos use publicly accessible Cloudflare storage URLs. Anyone holding a URL may be able to view that photo. Provider result links can also be shareable and can expire. Treat those links as sensitive and avoid putting unnecessary private information in source photos.

There is currently no automatic deletion or expiry job for uploaded photos. Stored files remain until the operator manually deletes them. Account, task, credit, order, security and support records also require manual retention review; this project has not established a fixed deletion schedule for those categories.

You can request deletion of files and associated account data through support. We may need to verify ownership and retain records where required for a pending task, legal obligation, billing reconciliation or dispute. We will explain any limitation relevant to the request. Deleting a Cloudflare file does not itself remove copies already received by KIE, payment services or someone you shared a link with; external provider deletion must be considered separately.

Production access uses HTTPS, session cookies are configured with security attributes, and account and generation requests are scoped to the relevant studio. No system can guarantee absolute security. Do not send passwords, API keys or full payment-card details in support messages.

Buildora is based in China. Cloudflare, KIE and payment infrastructure may process information in other countries. This policy does not claim a particular storage region, a completed Standard Contractual Clauses agreement, or a compliance certification. Provider arrangements and any required cross-border safeguards must be verified for the live service and its markets.

You can choose not to submit a photo, remove a local preview before generation, decline optional analytics, clear browser data, and contact support about account closure. Withdrawal of permission after submission cannot undo processing that already occurred.

Depending on the law that applies, you may have rights to access, correct, delete or obtain a portable copy of information, restrict or object to processing, and withdraw consent for consent-based processing. You may also complain to the competent privacy authority. These rights are subject to the conditions and obligations of the applicable law.

Send a request to the email on this page and identify the studio, account email and relevant task or file reference. For a likeness complaint, describe the affected person and content without publicly reposting sensitive material. We may request proportionate information to verify the request. Requests are handled manually; this version does not promise an automated deletion function or a fixed response deadline beyond applicable legal requirements.

Users must have the legal capacity and permissions required for the requested use. Do not submit sexualized images of minors or other prohibited sensitive content. A parent or guardian concerned about a child’s information can contact support for review. A market-specific minimum-age policy must be established before the paid launch; this version does not claim an implemented age-verification system.

Updates are published on this page with a revised version and date. Material changes to the actual processing require corresponding notices or consent where applicable. The support email below handles privacy, access, deletion and security questions for this studio.

For service, account, privacy, deletion, rights or billing questions about Backseat Verse, email [email protected]. Identify this studio and include only the references needed to review your request.