Privacy
Privacy And Data Handling
LipSyncMyVideo processes uploaded media, account data, and billing records needed to provide waveform editing, transcription, lip-sync previewing, and downloadable renders. This page describes the application-level privacy behavior of the service.
What The Service May Process
LipSyncMyVideo may process uploaded video files, uploaded song audio, derived vocal stems, waveform data, transcript text, word timestamps, account identifiers, and billing activity needed to operate the application.
If you sign in, the service may store basic account information such as your email address and profile details returned by the configured authentication provider. Billing activity may include purchase, reservation, settlement, refund, grant, and credit-balance records.
When Audio Leaves The Host
The normal deployed configuration keeps transcription on the host by using the local Whisper backend.
If an operator explicitly enables the experimental OpenAI transcription backend in a particular environment, prepared annotation audio may be sent from the worker host to OpenAI for speech-to-text transcription. That prepared annotation audio is the same alignment-focused audio artifact used by the app for lyric timing, typically preferring isolated vocals when available.
The OpenAI backend remains an implemented experimental option for evaluation and future re-validation. It is not the recommended deployed path for lyric alignment today. The configured model for that backend is whisper-1.
What This Is Used For
That transcription result is used to produce transcript text, word timestamps, and diagnostics that support lyric alignment and waveform word markers inside the application.
Uploaded and derived media may also be used to prepare browser previews, lip-sync previews, and downloadable outputs requested through the application.
In the normal deployed configuration, transcription stays on the host and this external API path is not used.
Retention And Access
This application-level notice does not promise a fixed retention period across every deployment. Operators may configure storage, cleanup, logging, and access controls differently by environment.
If you need environment-specific retention, deletion, access, or compliance details beyond this notice, contact the operator of the deployment you are using at [email protected].
Questions And Requests
Operators can switch between the local and OpenAI transcription backends through deployment configuration. This means the exact transcription path depends on the environment where the service is running.
For support, privacy questions, billing issues, or copyright concerns, contact Robert Soliday at [email protected].