Privacy policy
This service handles your photos, which may contain your face or someone else's. So instead of boilerplate, here is plainly what we receive, where it goes, how long it stays and who can see it.
Last updated: 19 August 2026
What we receive
| Data | How | Used for |
|---|---|---|
| The photo you upload | You choose to upload it | Producing your video, nothing else |
| The generated video | Produced by the system | Showing it to you and letting you download it |
| The motion you picked | Your choice | Deciding which prompt goes to the model |
| A random identifier (cookie) | Issued on your first visit | Letting you find your job again after a reload |
| Your IP address | Inherent to connecting | Counting free runs and preventing queue flooding |
| Country (two-letter code) | Added by the CDN on connection | Knowing roughly which countries visitors come from |
| Email and password | Only if you register | Your account name, logging in, and tying results to your account |
The email you register with is only used as your account name, for logging in and for future password recovery. We do not send marketing email, and we never sell or share it. We never ask for your phone number, real name or payment details.
We currently do not verify email addresses (no confirmation emails are sent), so we cannot confirm that the address is really yours — which also means a typo makes password recovery impossible. If we add verification later, this page will say so first.
Where photos are stored, and for how long
- Photos and videos are stored on this service's own disk, never in cloud storage or a third-party API
- They are kept for 7 days and then deleted automatically. Download anything you want to keep
- Deletion removes the original photo and the generated video together
What we do not do
- We do not use your photos to train anything. This service uses an existing public model; there is no training or fine-tuning step anywhere in it
- We do not sell, share or hand your photos or videos to third parties
- We never put your results in the examples pages or any promotional material
- We do not run facial recognition, identity matching or build any face database
Two automatic checks run on upload
Both run locally and offline — nothing is sent to an external service, and neither result is stored:
- Face detection (OpenCV): only answers "is there a face in this image?". It does not identify anyone and does not compare against any database. It exists to warn you before you apply a portrait motion to a photo with no person in it
- Nudity detection (NudeNet, running on our own machine): photos flagged as containing nudity are never generated and never appear anywhere public. A few frames of the finished video are scanned again before it is handed to you
What happens to a blocked photo
No detector is perfect — false positives and misses both happen. So that false positives can actually be corrected, a blocked photo is quarantined for at most two days, visible only to the site's operator (one person), for one purpose: deciding whether the block was a mistake.
- Once reviewed, the image is deleted immediately; only the "false positive / confirmed" label and the detection score are kept, and they are used to calibrate the threshold
- Anything not reviewed is deleted automatically after two days
- Quarantined photos are never generated, never published, never used for training and never shared
- If you would rather not wait, ask us to delete it now via the contact page and we will
If you would prefer that blocked photos are not retained for review at all, tell us — we can turn the mechanism off, at the cost of never being able to correct a false positive.
Who can see your results
- The "recent results" list only appears after you log in, and only shows your own results
- Ownership is determined by your account or browser cookie — we deliberately do not use network location to decide who is who, because different people on the same network could be mistaken for each other
- Every video URL contains a random identifier that cannot be guessed, and requests without permission are rejected
Cookies
The cookies this site sets itself are functional only (advertising cookies come from Google AdSense — see the Advertising section below):
wf_uid: a random identifier so you can close the page and still find your jobwf_lang: the language you picked- A session cookie, only if you register and log in
You can clear cookies at any time. If you are not logged in, doing so means you can no longer reach earlier jobs.
Analytics
We record the most basic traffic numbers ourselves: how often each page was viewed, how many distinct visitors there were on a given day, how many videos were generated, and which site linked here. We use them to decide whether this service is worth continuing to work on.
- No third-party analytics. No Google Analytics, no Facebook Pixel. Google AdSense on this site is advertising, not analytics — its cookies never feed into these traffic figures
- Visitors are distinguished by a hash of "a random daily salt + IP + browser user agent", truncated to 12 characters. The IP itself is not stored and the hash cannot be reversed
- The salt is regenerated every day, so even we cannot link records across dates
- Traffic from the local network (the operator's own testing and browsing) is not counted
- Country is recorded only as a two-letter code (TW, US…) — never city-level or finer
- Analytics data is kept for 90 days
Advertising
This site participates in Google AdSense. Google's advertising code is loaded on these pages, and Google and its partners may use cookies to serve ads based on your prior visits to this or other sites.
- You can turn off personalised advertising at Google Ad Settings
- Or opt out of several vendors at once at aboutads.info
- Ads never appear on admin pages, and never next to anyone else's results (no such page exists)
- We never give advertisers your uploaded photos or generated videos, and never use them for ad targeting
Apart from AdSense, this site carries no third-party tracking code — traffic statistics are still counted on our own server.
Visitors in the EEA, the UK and Switzerland
Visitors from these regions see a consent choice on their first visit: consent, do not consent, or manage options for item-by-item control. We deliberately chose the version that puts "do not consent" on the same level as "consent" — refusing should be exactly as easy as agreeing, not buried one menu deeper.
You can change your choice at any time by reopening the consent panel, or at Google Ad Settings. Visitors elsewhere (including Taiwan) do not see this panel.
Your rights
- Deletion: you can ask us to delete any result or your whole account, and we will do it promptly
- Access: you can ask what data we hold about you
- Or do nothing: everything disappears by itself after 7 days
Get in touch via the contact page.
Children
This service is not designed for children. Please do not upload photographs of children without the consent of their guardian.
Security
Passwords are stored as PBKDF2-SHA256 hashes with a per-account random salt; there are no plaintext passwords in our database and we cannot recover yours. That said, this service is built and maintained by one person and cannot offer enterprise-grade security guarantees — please don't upload genuinely confidential images.
Changes
If this policy changes, the date at the top of this page changes with it. Significant changes will be announced on the home page.