Privacy Policy — Zombie Couple Video

Version 2026-10-15-v1. This policy covers https://zombie-couple-video.io. The service is operated by an individual under the Zombie Couple Video brand. Contact support@zombie-couple-video.io for privacy requests. We do not publish the administrator's private login email, account password or residential information. Production controller-identification disclosures remain subject to merchant/privacy review.

1. What we collect

We process the account name and email you provide, a password hash, session identifiers, order and credit records, support correspondence, selected scene settings and the two adult portrait photos you submit. Generation and review records include task IDs, timestamps, provider identifiers, status, moderation decisions and the generated video.

Hosting/security systems can process IP addresses, browser and device information, request times and error/performance logs. We do not request device location, contacts, microphone or camera access. We do not store full payment-card numbers or card security codes. Facial photos guide fictional character appearance; this is not an identity-verification service. Do not upload someone else's sensitive images without permission.

2. Local previews and drafts

Selecting a photo first creates a browser preview. It does not by itself upload the file. When you continue through sign-in, the draft can be saved in this browser's IndexedDB with a 24-hour validity period. On the next editor visit, an expired draft is cleared. If you never return, browser storage may persist until you clear site data; this is not a guaranteed background deletion timer. You may clear browser site data sooner. People sharing your device may be able to access a local draft.

3. Why we process data

We use account and session data to provide access; photos, prompts and task settings to provide the video you request; order/credit data to fulfill and reconcile purchases; and correspondence to answer support requests. Where applicable, these activities rely on performing the service contract. Safety review, abuse prevention, system security and handling disputes rely on our legitimate interests, balanced against your rights, and legal obligations where applicable. Any processing that requires consent will use the applicable consent process; agreeing to this policy is not a blanket consent to unrelated uses.

We do not sell your personal information or uploaded photos. We do not run an advertising-data business or use your uploads to train our own AI models. We currently send service-related communications rather than a marketing mailing list. If optional analytics or marketing is introduced, we will identify it and provide the required controls before using it.

4. Photos, video generation and content checks

After you confirm adult consent and submit a story, photos are stored in private Cloudflare R2. SeeAPI receives temporary access to each uploaded image for image moderation. Waffo Pancake receives the prepared text prompt for prompt-safety review. Only allowed inputs proceed to fal.ai's Kling reference-to-video workflow, which receives the photos and generation instructions.

Finished model output is first stored privately in quarantine. SeeAPI receives temporary video access to sample frames for NSFW/special-care review. Video review does not examine every frame and can produce false positives or false negatives. A pending or rejected review does not expose the video to other customers. Approved results require your signed-in account to play or download. There is no public customer gallery.

Access links are bearer links limited by purpose, task and expiry; anyone who obtains a valid processor access link could use it until it expires. Do not share them. We keep decisions and identifiers for support/reconciliation, rather than treating a successful API request as proof that content passed. Provider-side storage and model processing are governed by each provider's policies, and deleting our copy does not prove that an external provider's copy has already been erased.

5. Service providers and payment data

• Cloudflare: hosting, D1 records, private R2 media, transactional email and support-email forwarding. Support mail is forwarded to the operator's private verified inbox, whose address is not published.
• Waffo Pancake: hosted checkout/payment processing and prompt-safety checks. We retain necessary transaction identifiers, amounts, currency, payment status and fulfillment records. Card details are entered on Waffo's checkout, not on our server. The payment receipt identifies the applicable payment seller/merchant-of-record details.
• fal.ai and its model provider: reference photos and instructions needed to generate the requested video.
• SeeAPI: temporary source-image and generated-video access for the content assessments described above.
• YouTube: public creator examples and thumbnails. Loading them communicates your IP/browser information to that service, even without a YouTube login.

We may disclose necessary records to comply with valid legal requests, protect users, investigate fraud or handle a legitimate business transfer with continuing safeguards. We do not publish your private account or media as testimonials or examples without separate permission.

6. Cookies, embedded media and cross-border processing

Essential session cookies support login and security. Browser storage holds editor drafts and preferences. You can delete cookies/site data, but doing so may sign you out or remove drafts. Public examples use YouTube's privacy-enhanced embed; it is not a promise of zero cookies or zero third-party data transfer. You can avoid loading the page's examples by blocking third-party media in your browser, or use the credited source links instead.

Cloudflare's network and the named providers may process data outside your country. The applicable locations and contractual safeguards depend on their service arrangements. We do not claim unverified local-only storage, signed transfer clauses or certifications. Where law requires specific transfer safeguards or disclosures, these must be completed before production processing in that market. Ask support about a relevant transfer or provider policy.

7. Retention and deletion

| Data | Retention approach | | --- | --- | | Local editor draft | Valid for 24 hours; cleared on the next editor visit after expiry or when you clear browser data. | | R2 source photos, quarantined clips and delivered videos | Lifecycle expiration is configured for 30 days after each object's creation. Storage-provider deletion is asynchronous. Eligible task/media deletion can remove our copy earlier. | | Account/profile and sessions | Needed while your account is active. After a verified closure/deletion request, we aim to remove account data within 30 calendar days, except records required for billing, security, legal holds or disputes. | | Orders, credits and dispute evidence | Kept for the applicable accounting/tax, payment-dispute or legal-hold period; the operator must confirm jurisdiction-specific periods before production sales. They are not erased merely by deleting a video. | | Support and safety records | Kept while a request, appeal, fraud investigation or unresolved task is active; reviewed on closure or a verified deletion request. Production review must finalize any additional fixed record-retention schedule. |

Unresolved tasks can require reconciliation before task deletion. R2 expiration does not automatically erase their D1 audit or credit records. We do not promise indefinite video hosting. Download approved clips you want to keep. Email deletion requests if an in-app operation cannot remove the relevant record; identify the account/task without sending full card information.

8. Security and incidents

We use HTTPS in production, private media storage, account-level access checks, password hashing, administrator permissions and encryption for provider secrets in the configuration database. No system can guarantee absolute security. We investigate reported incidents and notify affected people and authorities when legally required; where GDPR applies, the regulator's 72-hour notification framework is assessed from awareness of a qualifying breach, with individual notification where required. We do not claim a security certification we have not obtained.

9. Your choices and rights

Depending on applicable law, you may request access, correction, a copy of your information, deletion, restriction, portability, objection to eligible processing or withdrawal of consent. Contact support@zombie-couple-video.io from your account email. We may verify ownership and request only proportionate information. We aim to respond within 30 calendar days, explain any permitted extension or refusal, and preserve your right to complain to the relevant data-protection authority. Withdrawing consent does not make earlier lawful processing unlawful or remove records that must be retained by law. We do not discriminate for exercising applicable privacy rights.

10. Adults only

The service and its portrait uploads are restricted to adults aged 18 or older. We do not knowingly accept accounts or photos of minors. Report suspected minor-related data to support so it can be restricted, investigated and deleted as appropriate. Automated moderation is not a reliable age-verification or consent-verification system.

11. Updates and contact

We will publish material policy changes with a new version/date and, when practicable, announce them at least 14 days in advance through the website or account email. Urgent legal/security changes may require a shorter period. Separate consent will be obtained when required for a new purpose. Contact support@zombie-couple-video.io, use account support, review the Terms and refund policy, or return home.