Privacy Policy
What this policy covers
Hotel Lobby AI is a photo-to-video creative tool. This policy describes the behavior implemented in this version. The generator tells you whether you are using the demonstration workflow or live generation.
Photos in demonstration mode
When the generator is labeled Demo, selected photos stay in your browser for local previews. The demo does not send those photos to our server or an AI provider. Its result is a pre-made example clip, not a personalized video created from your images.
Use Remove, Replace, or close the page to discard a local photo preview. A file you deliberately download remains on your device until you delete it.
Photos in live generation
Live generation requires an account. When enabled, your uploaded JPG, PNG, or WEBP images are stored through the site's object-storage service, and image references are sent to the selected video-generation provider to create your result.
Stored images use randomized object names. Their delivery URLs may be publicly accessible to anyone who possesses the URL; randomized names are not the same as private storage. Avoid uploading sensitive images. Generation records can contain input image references, the provider job reference, processing state, and result information.
The upload receipt expires after one hour for starting a new generation. Receipt expiry does not delete the stored image. This version does not implement automatic image deletion or a fixed storage-retention period. Do not assume images disappear after the video finishes or after you remove a preview.
An AI provider processes images only in live generation. The provider's own retention and processing practices also apply. A provider name and its privacy information must be made available before a live service is opened to the public.
Accounts and credits
If you create an account, the service stores the account details needed for sign-in, such as your name and email, along with session information. Credit transactions and generation-job records support your balance, generation history, and failed-job credit returns. Demo use does not require a paid account.
Payments
When credit purchases are available, the payment provider handles checkout and payment details. The application stores order and payment-status information, such as the product, amount, currency, transaction reference, billing email, and invoice reference. This application does not store your complete card number or card security code.
Cookies and analytics
Sign-in uses session cookies. The site may also remember preferences and referral information. If analytics is enabled, the configured analytics service receives page visits and product events such as upload completion, generation success or failure, and downloads. The product-event bridge does not intentionally include photo contents, image URLs, filenames, prompts, account IDs, or email addresses. Analytics providers may independently collect device and network information according to their settings and policies.
Removing information
Before live upload: remove the photo from its upload card or close the page.
After live upload: removing the on-page preview does not delete the server copy. Storage deletion and account-data requests require the site's operator to remove the relevant stored objects and records; there is no self-service server-deletion control in this version. A public support contact, provider details, and an operational deletion process are required before live photo uploads are opened to the public.
Payment and credit records may need to be retained for accounting, dispute handling, or obligations that apply to the operator. No fixed retention period is promised by this version.
Your choices
Only use photos that you have the right and permission to process. You can leave the demo without creating an account, choose not to upload images to live generation, or stop using the service. Do not upload sensitive personal photos until the live service's operator, support contact, provider policy, and retention terms are published.
Updates
This policy must be updated when the operating provider, storage policy, deletion controls, analytics configuration, or legal operator changes. The date at the top identifies this version.