What we process
- Creation inputs — photos, videos, audio, voice samples, and text you submit.
- Generated files — podcast studio scene images, synthesized audio used by a task, and generated videos.
- Strictly necessary cookies — random identifiers used to secure the current session and, after sign-in, the account session.
- Abuse and rate-limit data — a one-way hash derived from network and browser information. We do not store a visitor's raw IP address in the product database.
- Your email address — from Google sign-in, or when you voluntarily write to a contact address.
- Billing records — the product selected, amount, currency, provider transaction identifiers, payment status, and timestamps needed to deliver credits, prevent fraud, and provide support.
Google sign-in and account data
If you choose Continue with Google, Google sends us your account identifier, email address, display name, email-verification status, and profile-image URL. We use this information only to authenticate you, secure your account, attach credits and recent creations to that account, and provide account support. We do not receive or store your Google password, contacts, Drive files, or other Google content.
We do not sell Google user data or use it for advertising. Authentication records are retained while your account is active and as reasonably necessary for security, fraud prevention, and legal compliance. You can revoke UseLipSync access from your Google Account and request deletion from us at the address below.
Why we process it
We use creation inputs only to upload, generate, store temporarily, display to the current session, deliver the requested output, and investigate support or generation problems. During the stated retention period, a limited number of authorized staff may view submitted inputs and outputs in a private admin tool for troubleshooting and abuse review; we do not publish them or use them to train models. Operational records are used for job recovery, credit accounting, reliability, cost controls, and abuse investigation.
For Recreate, the character image and reference video are sent only when you submit an enabled generation and are subject to the same private-storage and deletion rules.
Where it goes
Files are held in private object storage in the Hong Kong region. Depending on the selected workflow, necessary inputs are made available to our contracted AI processing providers through signed links or direct request data. These providers process the inputs to generate speech, scene images, mouth movement, talking-photo motion, or a recreated reference performance. If you choose a paid plan or credit pack, PayPal processes the payment. We do not receive or store your card number, bank account number, or PayPal password.
Voice samples and saved voices
A voice sample is submitted only when you explicitly start voice cloning. A cloned voice is saved to your signed-in account so you can reuse it across Video Lip Sync and AI Pet Podcast; you can rename or delete it at any time, which removes it from your account. Task files follow the input retention policy below, and the sample follows the retention described below, although the processing provider may maintain technical model identifiers subject to its own operational controls.
Product analytics
We use PostHog to count a small allowlisted set of anonymous product steps, such as opening the homepage or a tool, selecting an input, creating a scene, submitting a job, clicking download, or choosing a predefined feedback reason. We also record a coarse, allowlisted acquisition source such as Google, ChatGPT, YouTube, Reddit, another referring site, or unattributed traffic, plus whether that classification came from a tagged link, a referring site, or neither. We record only whether the browser's referring-site category matched that selected source, differed, or was unavailable. We never send the full referrer URL, free-form UTM values, or search terms. For private result playback, we collect only coarse readiness, buffering, seeking, and browser-error buckets to improve delivery reliability. We do not send uploaded media, file names, object keys, job IDs, script text, audio text, voice samples, result URLs, or free-text feedback. Automatic capture, session recording, advertising profiling, and person profiles are disabled. Events are forwarded server-to-server, so PostHog receives our server IP rather than a visitor's IP.
Our own database also keeps counts per creation of playback starts, playback reaching the end, download requests, and full-file server deliveries. Authorized staff can see these counts in the private admin tool to understand product use and troubleshoot delivery. They are not sent to PostHog and do not record what was watched, the playback position, or a device file-save confirmation. Counting begins when this feature is launched; past plays and downloads cannot be reconstructed.
When a signed-in creation finishes, we record when it became ready and when you first viewed its result or card in Your creations. This powers an on-site ready indicator. If you have not viewed the result after about five minutes, we may email your verified account address once with a private link to that creation. The email contains no uploaded content or public media link. You can switch these emails off in Account; switching them off also cancels pending reminders. We use Resend to deliver these service emails.
How long we keep it
Submitted creation inputs—including uploaded photos, source video, audio, and text—are normally deleted after 7 days. Uploaded files never submitted to a creation expire after 24 hours. The sample behind a saved voice is an exception: it is kept for as long as that voice is in your account, and it is deleted when you delete that voice. When a plan does not include saved voices, the sample is deleted as soon as that creation finishes. Guest results created before the account requirement still expire after 24 hours. For a signed-in account, a successful finished video is kept for between 7 and 365 days, depending on the plan in force when it was made, so it can be recovered from the Creations Library. When you explicitly save a creation or pet studio scene, that asset remains until you delete it, close the account, or reach the current storage limit (50 saved creations or 2 GB; 2 to 200 saved pets depending on plan, with up to 5 scenes each). When you delete a creation it leaves the Library straight away; its file is kept for 7 more days so you can restore it, and is then permanently deleted. We may shorten retention when required for safety, abuse prevention, legal compliance, or service operation.
We retain minimal operational records such as timestamps, job status, measured cost, credits reserved or consumed, asset deletion status, per-creation playback and file-delivery counts, and the version of consent accepted. Those records do not contain the raw uploaded media, script text, voice sample, or a permanent public download link.
To evaluate a limited Recreate preview pilot, our own database records the account's randomly assigned pilot group and when eligible inputs were first ready. This is used for aggregate conversion analysis, not advertising or session recording; it contains no uploaded media or file names.
For the limited Recreate preview pilot, we temporarily keep a SHA-256 fingerprint of the submitted character image and reference video for up to 7 days. It is used only to verify that a later re-upload matches the files eligible for the preview credit. Submitted inputs follow the 7-day retention above; the fingerprints are not sent to product analytics and are deleted when the 7-day credit window closes.
Cookies
We set a strictly necessary anonymous-session cookie and, after login, a strictly necessary authentication cookie. Product analytics uses memory-only browser state and does not add an analytics cookie. We do not use advertising or cross-site tracking cookies.
Your choices
You may delete creations and saved pets from the Library or ask us to delete retained account records by emailing [email protected]. A creation you delete can be restored from the Library for 7 days and is permanently deleted after that. Raw inputs normally expire after 7 days; guest result files created before the account requirement still expire after 24 hours.