Privacy Policy

Scope and privacy contact

This policy covers the website, creation workspace and support features. Upload an authorized photo and the system generates a video with preset AI prompts. The studio and checkout show current availability.

For questions about your information or an image depicting you, use Support Tickets. Provide the account, task or media link needed to identify the issue and explain your connection to it. Do not send passwords, provider keys, identity documents or unrelated private images. We may need additional information to establish authority over a request.

You can also email support@burningbridgesstudio.com without an account. See Support for contact details and Safety for reports about unauthorized likeness use or harmful content.

Information we handle

• Account and sign-in: account identifiers, name, email, profile image and session information. Google authentication can return provider identifiers and tokens used by the sign-in system. Sessions can include IP and browser information.
• Creation: the submitted photo, stored photo reference, provider request identifiers, task status, credit charges or returns, and video results or storage references. An authorization declaration is required before submission; it does not verify identity or age.
• Purchases: products, amounts, currency, payment status and provider references needed to settle orders and grant credits. Payment information is entered with the provider shown at checkout. The application does not store complete card numbers or card security codes.
• Support and operation: ticket messages, images you attach, technical error information and product events such as encountering a credit limit. Sign-up records can include referral, campaign and country information derived from the request.

Photo selection and generation

Selecting a creation photo produces a local browser preview. That selection alone does not upload it. Starting a task sends the photo to our server, which saves it to configured media storage before directly starting generation. The original photo is not stored as image bytes in the application database; the task stores its object reference.

Tasks retain the stored photo and request identifiers needed to resume processing. Your photo and the preset text prompt are sent to fal.ai and its model provider to generate your video. Completed MP4 files are copied to the configured application storage.

Removing a browser preview changes the local selection. It does not cancel a submitted task or delete material already sent to a provider. New tasks proceed directly to generation and cannot be canceled through the studio after submission. Older tasks already waiting for confirmation can still be canceled to return reserved credits; cancellation does not establish that earlier copies have been deleted.

Providers and storage

Google handles authentication, including One Tap where available. Sign-in requests basic identity information, not access to Gmail, Drive or Calendar.

fal.ai and its model providers process your photo and preset text instructions to generate the video. Older saved tasks may also include a separate image-generation step. Their data handling is subject to their own terms, including fal.ai's privacy policy. We do not promise zero provider retention or processing in a single country.

Waffo content screening, when enabled, receives the studio's preset text prompt before generation. In that flow, fal.ai also checks the uploaded image for NSFW content before video generation proceeds. These checks do not verify identity, age, ownership or permission.

Cloudflare R2 stores uploaded creation photos and generated cloud media, and Cloudflare delivers files through the studio's media domain. Local development may instead retain completed videos in local application storage. Account, credit, task and support records are kept in the configured application database. Enabled payment, email, analytics or support integrations also involve the relevant provider for that function.

Who can access media

The application checks the signed-in account when listing tasks and handling the video download route. An account check on that route does not make a public storage URL private.

The current R2 configuration serves media through public file URLs, including uploaded creation photos and generated results on the studio's CDN domain. Anyone with a file URL may access or share it without signing into the studio. An enabled R2 development domain can expose the same object. Uploaded profile or support images may also use directly accessible storage links. Do not submit confidential, intimate or otherwise sensitive material.

Public concept artwork is separate from user task history. Creating a task does not itself publish a public gallery entry. Authorized operators may access records and material needed for support or an investigation of a reported issue.

Retention and deletion requests

This version has no fixed automatic deletion schedule for saved task records, generated media or support messages. Showing only recent tasks in the interface is not a deletion policy. Account, payment and credit records may remain necessary for service operation, accounting and dispute handling.

You can delete completed, failed or canceled tasks in My Videos. After confirmation, the studio removes the related uploaded photos and generated videos from its storage before removing the task from your list. If cleanup does not finish, the task remains available for another deletion attempt. Deletion does not return generation credits, remove payment or credit records, delete data retained by providers, or recall files already downloaded, shared or cached elsewhere.

You can ask support for access, correction or removal. Handling a request may require confirming the related account and locating database records, stored objects and provider references. We do not promise a fixed completion deadline or immediate deletion by every provider. Deleting an application record alone does not remove a stored object. Removing an object cannot recall files already downloaded, shared or cached elsewhere.

Cookies, preferences and analytics

Essential session cookies support sign-in. Cookies or browser storage can also hold language, interface preferences and referral information. Google sign-in is subject to Google's browser and account controls.

If enabled, analytics or advertising integrations can receive visit, device and network information under their settings and policies. Where cookie-choice controls are enabled, use them to manage the available non-essential integrations. In-app product events provide operational history and are distinct from third-party analytics. Creation photos pass through the generation workflow, not a product-event payload.

We also collect first-party visit and interaction statistics using a signed browser cookie (up to 90 days). These include approved page paths, sanitized paths that display a 404 page, country, normalized source/campaign tags and photo-selection, generate, plan-selection and download clicks. For 404 diagnostics, query strings and fragments are omitted and sensitive path segments are redacted. We do not include your photo, prompt, file name or task ID in these statistics. Raw events are retained for 90 UTC days; source attribution lasts 30 days. Collection respects Do Not Track, Global Privacy Control and, when enabled, your cookie choice.

Your choices and updates

You can browse public pages without selecting a photo, decline to start a task, change a photo before submitting it or request help with stored information. Generation is for adults using photos of consenting adults; see the acceptable use rules.

We update this page when processing changes. The date above identifies this policy text. Describing a feature does not establish that it is enabled or that a requested deletion has completed.