Privacy Policy
How Live Face Swap handles account data, uploads, payments, cookies, and privacy requests.
Last updated: 2026-10-24
1. Scope and contact
This policy covers the Live Face Swap website at live-face-swap.net and its available account, billing, content, and support features. “We” refers to the team operating Live Face Swap. For privacy questions or requests, email support@fovuno.com.
Current product status: real-time face swapping, webcam capture, desktop software, and virtual-camera output are not available. This policy describes the website as it works today. We will explain any new camera or AI processing before making those features available.
2. Information processed by the current website
- Account and sign-in data: your name, email address, profile image, account preferences, session records, and sign-in information. If you choose Google sign-in, we receive the profile and account identifiers needed for authentication. If email-and-password sign-in is enabled and you use it, authentication includes a stored password hash.
- Orders, subscriptions, and credits: plan and order identifiers, payment status, subscription dates, credit grants and usage records, and billing information needed to reconcile transactions. Stripe handles payment details; our application does not store full card numbers or card security codes. Checkout currently uses the Stripe test environment.
- Content you provide: profile images, submitted posts, support messages, attachments, and email correspondence. Only provide information necessary for the feature or request.
- Technical and security data: IP addresses, browser or device details, request times, error information, and account activity where needed for authentication, rate limiting, troubleshooting, and abuse investigation.
- Preferences and optional analytics: language, theme, cookie choices, and, when enabled on the production website, browsing and interaction information described below.
3. Images, faces, and webcam access
The current website does not request webcam permission or run live camera sessions. It has no face swap reference library, live video storage workflow, or facial identity-verification feature.
General image uploads are not private face storage. Images submitted for profiles, posts, or support can be served through accessible image URLs. Anyone who obtains such a URL may be able to view the image. A support ticket being account-protected does not necessarily make its attachment URL private. Do not upload private face photographs, identity documents, intimate images, or other sensitive material through these features.
Facial images can be personal information and, depending on their processing and applicable law, sensitive or biometric information. Before introducing a camera feature, we will explain where processing happens, who receives reference images and camera frames, whether anything is retained or used for model training, and how to stop processing and request deletion. We make no present claim of local-only processing, zero retention, or a specific AI provider's practices for an unlaunched feature.
4. Purposes and legal grounds
We use information to provide requested account and website features, maintain orders and credits, respond to support requests, secure the service, diagnose problems, and meet legal obligations. Optional production analytics helps us understand website use.
Where applicable law requires a legal basis, we rely on performance of a contract for requested services, legal obligations for required records, legitimate interests for proportionate security and operation subject to your rights, and consent where required for optional processing. You may withdraw consent for future processing without affecting the lawfulness of earlier processing.
5. Cookies and website analytics
Essential cookies support sign-in and website preferences. If the cookie banner is enabled, your accept or reject choice is stored for up to 365 days, unless you clear it or change the choice sooner. You can reopen Cookie Settings from the footer when that control is available, and manage stored cookies through your browser.
When enabled on the production domain, Google Analytics can receive page and device information, and Microsoft Clarity can collect interaction information, heatmaps, and session replays of website interactions. Session replay is separate from a webcam recording. These integrations are disabled in local and preview environments.
Rejecting optional storage does not necessarily stop all analytics network requests. The current consent integration communicates storage preferences to Google and Microsoft; their consent modes may still send limited measurements without analytics cookies. Browser privacy controls may provide additional restrictions. Do not put sensitive personal information in page URLs or unnecessary support attachments.
6. Providers and disclosure
Providers receive information needed for the features they support:
- Cloudflare: website delivery, hosting, database, security, and configured object storage.
- Google: authentication when you choose Google sign-in, and website analytics when enabled.
- Stripe: checkout, billing, subscriptions, and payment-related verification, currently in test mode.
- Microsoft Clarity: website interaction analytics when enabled.
- Configured email or support providers, when used to deliver messages or handle your request.
Provider processing is also subject to their applicable privacy notices: Cloudflare, Google, Stripe, and Microsoft.
We do not sell account information or uploaded images. We may disclose relevant information to comply with law, respond to valid legal requests, investigate abuse, or protect people and the service. A business transfer may involve necessary records, subject to applicable privacy obligations and any required notices.
Providers may process information outside your country. Applicable transfer requirements and safeguards depend on your location and the provider arrangement; contact us for information relevant to your data. We do not represent that every user’s data stays in one country.
7. Retention and security
Retention depends on the purpose: account records while needed to maintain an account; billing and credit records for reconciliation, disputes, and applicable recordkeeping duties; support records for resolving and following up on requests; and security records while needed to investigate incidents and prevent abuse. General uploads do not currently have a guaranteed automatic deletion schedule. Contact us to request their removal.
Account closure does not automatically erase billing records, provider-held records, or copies in backups. We assess deletion requests against legitimate retention needs and applicable law, explain relevant exceptions, and remove data that no longer needs to be kept.
We use safeguards including access controls, authentication, protected production connections, and encryption of configured credentials. Public image links have the limitations described above. No internet service can guarantee absolute security.
8. Your choices and rights
You can edit the profile fields available in your account, change browser permissions and cookie choices, and stop using the website. Depending on applicable law, you may request access, correction, deletion, a portable copy, restriction, or objection to processing, and complain to your local data protection authority.
Send access, export, account-closure, or deletion requests to support@fovuno.com, preferably from your account email. Include only enough information to identify the account or content. We may verify your authority before acting. These requests are handled through support; the current account settings do not offer a complete self-service export or deletion workflow. Do not send passwords, full card details, or identity documents unless a necessary, secure verification method has been agreed.
9. Children and updates
The service is intended for adults aged 18 or above who can legally enter into the Terms of Service. If you believe a child has supplied personal information, contact us so we can investigate and address it.
We will revise this page when practices change. Material changes will be communicated through an appropriate website or account notice where required. The date above identifies this version. See also our Acceptable Use Policy.