Lips / privacy
Privacy information
Last updated October 12, 2026
Account information
When you sign in with Google or GitHub, Lips receives your account identifier, email address, display name and profile picture through Firebase Authentication. Lips uses this information to authenticate you, create your customer profile, secure your account and connect sign-in methods you choose. Google account information is not used to train AI models. Customer profiles and hashed API-key records are stored in Google Cloud Firestore. Plaintext API keys are shown only when created or rotated.
Media and processing
Lips collects the video and audio you upload, processing settings and generated outputs to perform the lip-sync workflows you request. Google Cloud stores this media; RunPod processes it with your selected engine when you request a render. Sign-in profile data is not used as model input. Signed upload and download links are short-lived. Render records expire after 29 days and output objects have a 30-day retention policy. Assets and preparations expire after six days. Cloud storage lifecycle deletion is asynchronous.
Usage and security
Lips records processing status, per-engine usage and request information needed for security and troubleshooting. Google Firebase and Google Cloud provide authentication, database, storage and hosting infrastructure. Firebase keeps your signed-in session using browser storage. HTTPS connections, tenant-scoped authorization and private storage protect access to your account and media. Usage estimates are observations, not invoices. The website does not require advertising trackers or send your API keys to analytics services.
Your controls
You can edit your profile, rotate or revoke API keys, manage sign-in security with Google or GitHub and sign out. Account profiles are not automatically deleted when you sign out. For account deletion, access, correction or other data requests, email markelog@gmail.com.