Privacy Policy

1. Who We Are

Free Lip Sync Hub (at freelipsynchub.com) is a free web-based tool that uses the open-source Wav2Lip AI model to sync audio to talking-head videos. We built it because the existing options were either too expensive, too complicated, or quietly sent your footage off to a cloud server you know nothing about.

We are the sole party responsible for this website and this Privacy Policy. There's no parent company, no VC-funded data empire behind this. Just a tool, a server running the web interface, and this page explaining how we handle your information.

2. The Big One: What Happens to Your Files

If you're only reading one section, make it this one.

Here's the exact lifecycle of a file you upload:

1. You select a video and audio file in your browser.
2. Your browser sends those files to the local server via an encrypted connection (HTTPS).
3. The server temporarily writes the files to disk so the Wav2Lip Python script can read them — this is a technical necessity, not a storage decision.
4. Wav2Lip processes the files and generates the lip-synced output video.
5. The output is served back to your browser for preview and download.
6. The uploaded files and the output are automatically deleted from the server. They are not archived, backed up, or retained in any form.

We don't access your files. We don't watch your videos. We don't listen to your audio. The only thing that reads your content is the Wav2Lip model running locally — and that model produces a video, not a data record.

3. What We Actually Collect

Since your files are processed locally and never stored, the data picture is quite sparse. Here's what we do pick up:

What you give us directly:

• Uploaded files — temporarily written to disk during processing, then deleted. Not retained. Not analyzed beyond transcoding.

What gets collected automatically:

• IP address — logged briefly for security purposes: rate limiting, abuse prevention, and detecting unusual traffic. We don't tie IP addresses to individual processing jobs or personal identities.
• Browser and device information — standard server logs capture your browser type, operating system, and similar technical details. This helps us diagnose compatibility issues.
• Usage patterns — which pages you visit and roughly how you navigate the site. This is aggregated and anonymized — we see traffic shapes, not individual users.
• Referral source — how you found us (e.g., Google Search, a direct link). Useful for understanding whether our SEO is working.

We don't collect your name. We don't collect your email. We have no payment information because the tool is free. We don't build user profiles. There is no account system and no login.

4. How We Use What We Collect

The limited data we pick up gets used for these purposes and nothing else:

• Running the lip sync — receiving your files, processing them through Wav2Lip, and returning the output to you.
• Keeping the site running — diagnosing errors, monitoring performance, and making sure the tool is actually working.
• Preventing abuse — stopping automated requests, blocking bad actors, and making sure the server stays usable for everyone.
• Understanding aggregate usage — so we know whether the site is growing or broken. We look at traffic numbers, not individual sessions.
• Showing ads — we display a small number of ads to cover hosting costs. More on this below.

We don't use any of this to build advertising profiles, send you marketing emails, or sell data to brokers. There's no email marketing list because there are no email addresses.

5. Cookies & Analytics

We use a small, practical set of cookies. We're not going to pretend we use zero — that would be dishonest. But the list is short.

• Essential cookies — required for the site to work. Things like session handling. Can't be turned off without breaking the tool.
• Analytics cookies — we may use Google Analytics (configured in anonymized mode) or a privacy-first alternative like Plausible Analytics to understand aggregate traffic. We can see "500 visits today, mostly from organic search." We cannot see that you visited, or link a visit to a specific processing job.

You can block cookies through your browser settings. The lip sync tool will still function — we don't gate features behind cookie consent.

6. Advertising

Servers cost money. GPU compute costs money. We cover those costs by running a small number of ads — we'd rather do that than charge you or sell your data. That's the tradeoff we've chosen.

Ads are served by third-party ad networks, potentially including Google AdSense. These networks may use their own cookies to show ads they think are relevant to you, based on your broader browsing history. That targeting logic is entirely theirs — we don't feed them any data about your uploads or your processing jobs.

If you'd rather not see personalized ads, you can opt out at aboutads.info or through your Google account's ad settings. Running an ad blocker is also your call — we understand.

7. Third-Party Services

Here's a transparent accounting of the third-party software involved in running this site:

• Wav2Lip (self-hosted, open source) — the AI model doing the lip sync. Runs locally on our server. Your files are not sent to any external AI API.
• Web server — a privately managed server running Apache and PHP. Not a major cloud platform processing your files through someone else's infrastructure.
• Analytics — Google Analytics or equivalent, configured with IP anonymization. Aggregate traffic data only.
• Ad networks — Google AdSense or similar. They operate under their own privacy policies and set their own cookies.

There is no OpenAI API call. There is no AWS Lambda function. There is no third-party transcoding service. The video processing chain is: your browser → our server → Wav2Lip → your browser. That's it.

8. How Long We Keep Things

The short answer is: not long, and in most cases, not at all.

• Uploaded video and audio — deleted automatically after processing completes. Not archived, not backed up.
• Output video — temporarily available for your browser to download, then deleted from the server. We don't keep a copy.
• Server logs (IP addresses, request metadata) — retained for up to 30 days for security purposes, then purged.
• Analytics data — aggregated and anonymized. Individual session data is not retained long-term.

9. Your Rights

Because we collect very little and hold no accounts, there's not a lot of personal data for us to act on. But you have rights, and we want to be clear about them.

• Right to know — you can ask us what data we hold about you. The honest answer will almost always be "your IP address, probably in a log file, for up to 30 days."
• Right to deletion — you can ask us to delete data we hold. Your files are already gone. Server logs can be purged on request.
• Right to opt out of personalized advertising — via your browser, your Google account settings, or an ad blocker.

EU/UK users: you have rights under GDPR and UK GDPR including data portability, the right to restrict processing, and the right to lodge a complaint with your national data protection authority.

California users: under CCPA you have the right to know what categories of personal data we collect, the right to request deletion, and the right to opt out of the sale of personal information. We do not sell personal information.

To exercise any of these rights, use the contact details in the last section.

10. A Note on Children

This tool is not designed for children under 13. We don't knowingly collect personal information from children, and since we require no account or personal information at all, there's no mechanism through which a child would create a profile or share identifying details with us.

If you believe a child has submitted personal data through this site, please contact us and we'll deal with it promptly.

11. When This Policy Changes

We'll update this policy if our practices change or if we're required to by law. When we do, the "Last updated" date at the top of this page will reflect the change. We won't bury significant changes — if something meaningful about how we handle your data shifts, we'll make it obvious.

Continuing to use the site after a policy update means you accept the new terms. If you check this page periodically, you'll always know where things stand.

12. Contact

Privacy questions shouldn't feel like opening a ticket with a faceless corporation. If something in this policy is unclear, or if you want to exercise a data right, just reach out.