This page describes the current release of Jean Phil Studio. Last updated: October 12, 2026.
Google sign-in
When you sign in with Google, we receive your Google account identifier, name, email address, email verification status, and profile picture URL. We request only the openid, email, and profile permissions. We do not request access to your Gmail messages, Google Drive files, or Google Calendar, and we do not receive your Google password.
We use this information to create or link your studio account, authenticate you, and display your account profile. Our authentication system stores your linked Google account identifier and the authentication tokens returned by Google, together with their scope and expiry information. Account and session records may also include IP addresses, browser information, language, and campaign attribution. Authorized administrators can access account records to operate the service and handle account requests.
Google processes the sign-in interaction under its own privacy policy. Signing in does not upload a photo or video or submit an AI generation job. Media uploads, generation, and moderation are separate actions described below. We use Google account information for the account features described here, and do not sell it or use it to target advertisements.
For the planned cloud deployment, Cloudflare hosts the studio and its D1 database stores the account, linked Google authentication, and session records described above. Cloudflare processes these requests and stored records to provide the hosting and database service. Local development uses a separate database on the operator’s computer.
Your Google connection and account records
You can remove this app’s connection in your Google Account’s third-party connections settings. Removing that connection does not automatically delete your studio account, existing session, or records previously stored by this app. You can sign out to end the current studio session.
This release does not provide self-service account deletion or a published automatic deletion schedule for account records. For privacy questions or account-data requests, email lonelytony.chan@gmail.com.
Preparing prompts
When you choose “Build my prompts,” your selected template, scene description, and aspect ratio are sent to our server to prepare the text. Prompt preparation does not submit a generation job to an AI provider. Selecting a photo or video previews it locally on your device and does not automatically upload it.
Optional live generation
Live rendering is disabled by default. If it is enabled, signed-in generation requests are associated with your account. The application records the prompt, task identifier, status, and result information so you can view or resume your job.
For live jobs, the configured Kie generation service receives the generation prompt and, for video, the approved portrait URL. When live generation is configured and you explicitly click Upload, your selected photo or motion video is sent to Kie’s upload service. Uploaded assets are associated with your account, and other accounts cannot retrieve them through this app. A motion reference may retain its audio. The provider processes uploads and jobs under its own terms. Avoid putting sensitive personal information in your scene description.
Video content checks
When video processing is enabled, uploaded motion references and generated videos are sent to SeeAPI for content moderation before this app allows their use or playback. SeeAPI receives the provider-hosted video URL and checks sampled frames for unsafe content. This is a frame-sampling check; it does not assess every moment of a video. Photos are not sent to this video moderation service.
The app records the moderation task identifier, status, and a summary of checked and flagged frames with your asset or generation record. While a check is pending, fails, or blocks a video, this app does not expose its provider-hosted URL for playback or use in a new generation. SeeAPI processes submitted videos under its own terms and retention policy. Selecting a file for local preview does not send it to SeeAPI.
Cookies and browser storage
Account features may use session cookies when sign-in is enabled. A visit with a utm_source parameter may store that campaign label in a cookie for up to 30 days. The studio can store the last generation job identifier and pending request parameters in browser session storage to recover accepted tasks and avoid duplicate submissions.
Retention and contact
Uploaded references expire in this app after 23 hours. Kie documents a 24-hour lifetime for temporary uploads; provider retention is governed by its service. Removing a reference from the scene clears this app’s selection and does not immediately delete a file already sent to the provider.
Removing a reference also does not withdraw a video already submitted for moderation. Provider retention and deletion are governed separately by Kie and SeeAPI.
This release does not promise an automatic deletion period for generation records or provider-hosted outputs. Before enabling public generation, the operator must publish the applicable retention and deletion process. Current contact availability is listed on the contact page.