Privacy Policy
How Hotel Lobby AI handles account, media, payment, and analytics data.
Last updated: 2026-10-05
Information we process
Hotel Lobby AI processes the information needed to provide the service, including your Google account identity when you sign in, the one or two source images you upload for a generation, scene and personalization choices, generated video files, generation status and usage records, and payment/credit records.
We do not receive or store your full payment-card number. Stripe processes checkout and payment information and sends us transaction and payment-status metadata needed to grant credits and maintain order history.
Source images and generated videos
When you start a Hotel Lobby AI generation, the selected source images are uploaded to Cloudflare R2 so the video-generation service can access them. Generated videos are also copied to Cloudflare R2 so completed results remain available in your account history instead of depending on temporary provider URLs.
Generation task metadata, media URLs, credit usage, and account relationships are stored in the application database hosted on Supabase Postgres.
AI processing
Hotel Lobby AI sends the source-image URLs, selected scene instructions, and the generated verse used for the video request to APIMart for AI video generation. When the Hotel Lobby scene is selected, the request also includes the server-controlled Hotel Lobby motion reference. APIMart receives the information required to process the generation request and returns task status and generated-media URLs.
When you provide personalization details, Hotel Lobby AI sends the short text needed to create the verse to MiniMax. MiniMax returns the generated verse, which is then included in the video-generation request.
Do not upload images that you do not have permission to use.
Authentication
Google OAuth is used for sign-in. Google provides the account information required to identify and authenticate your account. Hotel Lobby AI does not receive your Google password.
Analytics
We use Google Analytics and a first-party analytics system to understand website usage, acquisition sources, landing pages, and product-funnel events such as preview generation, photo upload, checkout start, payment return, generation start, and generation completion.
The first-party system stores an anonymous visitor ID and session ID, traffic source and referrer domain, landing page, UTM campaign fields, country or region supplied by the hosting platform, device/browser/operating-system category, language, timezone, coarse screen-size range, and limited product-event fields such as tool, model, credits, product ID, and purchase value.
We do not store full IP addresses, precise GPS or city location, browser fingerprints, complete referrer URLs, account email addresses, prompts, uploaded images, or generated media contents in the analytics tables. Google Analytics may set cookies or similar identifiers according to Google's policies.
Service providers
The service currently relies on:
- Google for authentication and analytics;
- Stripe for payment processing;
- Cloudflare for application hosting and R2 media storage;
- Supabase for the application database;
- APIMart for AI video generation.
These providers process information according to their own terms and privacy policies when providing their services.
Retention and deletion
Account, order, credit, generation, and media records may be retained for as long as needed to provide account history, operate the service, prevent abuse, resolve payment issues, and satisfy applicable legal obligations. Where deletion is requested and legally permitted, associated personal data may be removed or de-identified, subject to records that must be retained for payment, security, or legal purposes.
Security
We use server-side credentials for payment, storage, database, and AI providers. Secret API credentials are not intentionally exposed to the browser.
Changes
This policy may be updated when the product, service providers, retention practices, or legal requirements change.
