Zombie Couple Video

Privacy notice

Updated October 26, 2026

This notice describes Story HD and records from previously submitted preview tasks. New free generation is no longer offered. Earlier task processing and retention remain described below until those records expire.

Who operates this service

Zombie Couple Video is operated by Sean, an individual based in China. For order support or privacy requests, contact contact@zombiecouplevideo.ai.

Story HD: private photos, delivery and payment

For Story HD, we save the two prepared JPEG references in private Cloudflare R2 storage before checkout. They are removed after successful submission to the model provider, or within approximately 24 hours for incomplete or exceptional orders. The generated video is copied into private storage. For new deliveries, playback and download remain accessible for 7 days from when the completed file is saved for delivery. The order page shows the expiry in your local time. Earlier orders keep their original access deadline; this change does not restore deleted files. At expiry, access stops and scheduled cleanup removes the media. Paid exceptional orders without a delivered video remain accessible for support review for up to 30 days from creation; this does not promise a completed video or a fresh generation. These files are not published in a public R2 bucket.

A separate Secure, HttpOnly session cookie and a private recovery link control order access. The recovery credential is stored in your browser; our server stores its hash. Anyone holding the full recovery link can access the order, so keep it private. A hashed IP-derived identifier is used to limit recovery attempts. Refund-related records are kept for 30 days in the application for reconciliation; financial records retained by Stripe follow its own policies and applicable requirements.

Stripe handles checkout, payment details and payment receipts. We store payment references, order state, amount and refund status; our application does not receive full card numbers. For new orders prepared with email recovery enabled, we save the checkout email only after the server retrieves and validates a paid Stripe Checkout Session. This address is used for order access, not marketing. New orders do not receive automatic order or completion emails. On your request, we send a single-use sign-in link to that saved address. Links expire after 15 minutes or at the order access deadline, whichever comes first. Entering an email or order number alone never grants access or changes the saved address. Without an order number, we select the most recent accessible matching order; an optional order number selects a specific order. A keyed email hash indexes matching orders and is removed when access expires. Earlier opted-in orders retain their notices and sign-in access; older orders without a saved checkout email cannot be rebound by entering an address. Resend processes the saved address and private sign-in message only when sending these service emails; addresses are not shared with traffic analytics. See the Resend Privacy Policy. Email attempts are limited and do not interrupt video delivery. Contact and notification records are removed with the order, after the later of the video access window and 30 days from creation. Keep your original private recovery link as a fallback. See the Stripe Privacy Policy.

Public-page analytics with Plausible

We use Plausible to measure visits and referral sources on public pages such as the home page, pricing and guide. We send the public page path, recognized campaign labels and only the referring site origin; query values outside our approved campaign labels and all URL fragments are removed. Plausible also measures page engagement and derives device information and approximate location from normal web requests. According to its data policy, it does not use analytics cookies or store raw IP addresses, and processes analytics data in the EU.

We do not load Plausible on the private Story HD creation/order/recovery page or the payment-test site. We do not send photos, prompts, email addresses, order numbers, private links, payment references or revenue to Plausible. We disable automatic outbound-link, form and download tracking. Global Privacy Control, Do Not Track and the browser analytics opt-out below also disable loading Plausible. Existing first-party order and refund measurements remain separate.

Limited traffic attribution

We use first-party, approximate traffic measurements to understand which pages help visitors create a video. A random tab identifier and first-touch labels are kept in session storage for up to 24 hours. We record a recognized source category (such as ChatGPT or Google), an approved campaign label, a public landing-page path and the browser language. We do not send complete referring URLs, raw URL query strings, recovery links, photos or email addresses to this first-party measurement endpoint. Unknown referring domains are grouped as other referrals.

Visits and client-side actions are approximate, not counts of people or AI recommendations. Source labels on a new paid order are frozen at preparation; payment, generation, delivery and refund counts use server-confirmed state. Limited first-party client events include purchase-entry clicks, sample playback, both photos being ready, checkout initiation and download initiation. They contain only a fixed event name and the bounded attribution labels already described. Private attribution summaries and reduced order snapshots are kept for about 30 days, with periodic cleanup. They do not contain photographs, recovery credentials or payment card information.

Global Privacy Control and Do Not Track disable both this traffic-attribution collection and Plausible loading. You can also disable traffic attribution in this browser, or enable it again; this choice is saved on your device. Essential payment, delivery, abuse-prevention and operational records still apply. Attribution is not shared with an advertising network.

Earlier preview tasks: processing and recovery

Earlier preview tasks: photos and video generation

For the earlier preview offering, original photos were displayed in your browser. Before submission, each complete photo is fitted onto a 1024 × 1024 JPEG with padding; it is not cropped. These prepared images and the selected scene are sent through our Cloudflare Worker to fal.ai for model processing.

The free-preview application does not store input photos in its KV database, Durable Object records or application logs. It requests that fal not retain the input/output JSON payloads using its documented retention control. This does not mean every provider copy is immediately deleted. fal’s processing is subject to its own policies and account settings.

Earlier preview tasks: generated files

Generated videos are hosted by fal. We request a 24-hour media expiry and store a temporary result URL/status cache for up to 24 hours. Expiry timing is controlled by the provider. Media URLs may be accessible to anyone who possesses them; avoid posting a link publicly unless you intend to share it. Download promptly.

Session, verification and usage records

An essential, Secure, HttpOnly browser-session cookie helps restrict access to a generation task to the browser that requested it. The cookie expires after 24 hours. The retired preview submission flow used Cloudflare Turnstile to check for automated submissions and may process technical browser information.

The earlier preview flow used a keyed hash of your IP address for daily quotas and event rate limits; the application does not save the raw IP in these records. Per-IP generation counts are stored in Cloudflare Workers KV with expiration shortly after the daily reset. The global allowance and pause state are stored separately in a SQLite-backed Durable Object. Private operational records track submissions, outcomes, anonymous page visits, upload, generate-click and download-initiation events and estimated model costs for approximately 30 days, with daily cleanup. Attempt tokens expire after 24 hours; attempt records are removed by periodic cleanup, ordinarily within the following day. The application’s event payloads exclude photos, prompts, original filenames and video URLs. Browser event counts are approximate and do not identify a person. Session-stage counts group these events using a keyed session hash. Download initiation does not confirm that a file was saved on your device. Costs shown in operational reports are estimates, not provider invoices.

Task recovery on your device

We save the latest task credential, attempt identifier and creation time in your browser’s local storage for up to 24 hours. We do not save selected photos there. Returning in the same browser can resume progress or reopen the result, provided its session cookie and temporary result are still valid. Clearing site data removes access. Use Forget this task on the earlier-task recovery page to remove the saved credential sooner. Our background process checks submitted tasks even when the page is closed; it never submits a new generation.

Your choices

Upload only adult portraits you have permission to use. You can read the guide without uploading photos. Removing a selected photo clears its local preview, but cannot recall a photo that has already been submitted to the provider. Do not upload confidential or sensitive images.

Questions

Use our contact page for privacy questions. Please do not send portraits or API credentials with a support request.

Provider information: fal privacy policy, fal retention controls, Cloudflare privacy policy.