Privacy Policy
How HotelLobby AI handles photos, generated videos, and account data.
Last updated: 2026-10-03
About this service
HotelLobby AI at hotellobbyai.run lets you submit two photos to create a video. This policy covers our website, accounts, image submissions, video generation, and support features. Generation is available only when the operator has configured the video service.
Photos and video generation
Selecting a photo in the video generator creates a preview in your browser. Photos are not submitted when you select, swap, or remove them. Once you confirm permission and start generation, the two images pass through our server and are staged in private object storage for moderation and generation. After input checks pass, the enabled generation provider, which can include Fal/Kling, Replicate/Pruna, or APIMODELS, receives the approved images and source video. We do not save these input images in our application database or publish them in a gallery.
The generation provider receives the images and source video to perform the request. Its processing and retention are governed by its own terms and privacy policy, such as Fal's policy or Replicate's policy, according to the provider used. We do not promise immediate deletion by the provider. Do not submit images that you are not permitted to send to this service.
Content moderation and SeeAPI
We use SeeAPI as an external content-moderation service when processing generation requests. We send the actual model text, including your prompt and any applicable template text, to SeeAPI. We give it temporary signed URLs so it can retrieve all reference images, input video, and generated video outputs for assessment. This means SeeAPI processes the media itself, including visible faces, clothing, surroundings, and any other information present in those files. Moderation requests do not include your account password or payment card details.
We use the assessment to check sexual explicitness, sexual suggestions, sexual content involving minors, violence, hate, harassment, and self-harm, and to decide whether generation or publication may proceed. Video checks use sampled frames, with returned frame-image storage disabled in our requests; this setting is not a promise that SeeAPI keeps no processing copies. Video audio and subtitles are outside this moderation check. SeeAPI's handling of data is subject to its Privacy Policy. We do not promise immediate deletion, a particular retention period, or exclusion from model training by an external provider unless a separate verified agreement establishes that commitment.
Our server keeps moderation records associated with your generation task, including prompt text, stage, policy version, content digests, file sizes and video duration, temporary request URLs, provider task IDs, decisions, retry information, and reported moderation usage. These records support access control, recovery after service errors, abuse prevention, credit accounting, and support review. Input files, pending outputs, and blocked outputs are kept in private storage rather than a public gallery. A moderation failure does not make a file publicly accessible, and an unavailable or incomplete check does not authorize publication.
Moderation is necessary to process a generation request; it cannot be bypassed by disabling a browser setting. If you do not want your text or media sent to the moderation and generation providers, do not submit a generation request. Selecting a local preview alone does not send it to these providers.
Creem prompt moderation when enabled
When Creem's official Moderation API is enabled, we send the text you enter in the generator and a generation-task reference to Creem before any generation request. This applies regardless of which payment provider you used. We do not include photos, videos, passwords, payment details, or our fixed model templates in this prompt request. Requests that contain no user-entered text still undergo the other input checks, without an empty Creem prompt request.
We retain Creem's moderation identifier, decision, usage units, environment and attempt information with the task to enforce the generation gate, prevent duplicate requests and support recovery. Flagged or denied prompts are blocked, and an unavailable check does not permit generation. Creem's processing follows its Privacy Policy; we do not promise immediate deletion or a specific third-party retention period. SeeAPI's media and output checks described above remain separate.
Accounts and records
We store your name, email address, optional profile image, and authentication records to provide your account. Depending on your sign-in method, authentication records include password hashes or information and tokens from an enabled login provider. Registration and session records can include your IP address, browser information, language, and referral source. We use these records to operate sign-in, maintain account security, and understand registration sources.
For generation, we store your account association, permission confirmation and its timestamp, task and provider request identifiers, model and processing status, output video links, and credit transactions. These records support your video history, status updates, usage accounting, and reversals for failed tasks. New generated videos are copied from the provider to private storage and withheld until output moderation passes. Approved results are retrieved through an account-ownership check and a short-lived signed download URL; anyone who obtains that signed URL may access the file until it expires. Existing historical results may still use provider-hosted links accessible to anyone who has the link. Providers can retain their own copies or output URLs independently. Your account history is access controlled. Download completed results you want to keep because links and stored files can expire.
Profile images and support attachments
Profile images and images attached to support tickets use a separate upload process. Unlike photo previews in the video generator, these files are uploaded when selected and stored on our server or configured file storage. We also store ticket subjects, messages, attachment links, and replies so we can assist you. Stored image links may be accessible to anyone who has the link. Removing an image from a form or replacing your avatar does not automatically delete the previously uploaded file.
Cookies and optional services
Cookies support authentication, language preferences, and registration-source attribution. You can manage cookies through your browser; blocking authentication cookies may prevent sign-in.
Depending on the services enabled on this site, Google Analytics or Plausible may process visit and device information, Google AdSense may use cookies or similar technologies to deliver and measure ads, and Crisp or Tawk may process online chat messages and visitor information. These integrations depend on site configuration; their inclusion here does not mean all are active. Enabled login, email, hosting, and storage providers also process the information needed to deliver those features.
When paid checkout is enabled, the selected payment provider will process payment details. The application can retain order, payment, and subscription records, but does not store full card numbers.
Retention, access, and support
Private generation inputs, approved videos, pending videos, and blocked videos remain stored until removed through configured storage lifecycle rules or a support deletion request. The application does not currently provide a fixed automatic deletion schedule for generation history, moderation records, support records, or uploaded profile and support images. These records can remain stored until they are removed. A temporary signed URL expiring does not delete the underlying file. Blocking content does not itself delete it. Clearing browser data or removing a photo preview does not delete a submitted task or files already uploaded. Third-party processing and storage may take place outside your country, and provider retention rules apply separately.
You can update your name and profile image in account settings. For questions or requests to access, correct, or delete your account information, tasks, uploaded files, or moderation records, use the support ticket page in your account or email support@hotellobbyai.run. If a moderation decision appears incorrect, you can use the same support channels to request review. We may need relevant task records to investigate, and a review request does not automatically release blocked media. Account and task deletion are handled as support requests; there is no self-service deletion control. Deleting an application record does not itself delete provider-hosted files or copies downloaded by others. Do not include passwords or unnecessary sensitive information in a support message.
Updates
We will update this page when the data flow or enabled services change.