Privacy Policy

Publication items to complete: provide the operator’s legal name and privacy contact, set retention periods for account, purchase, generation, and result records, confirm which third-party providers are enabled, and identify the applicable jurisdictions. These details are not specified in the current product code or supplied policies.

About this policy

This policy describes information processed when you use Burning Bridges AI, a service that uses a portrait and a fixed reference performance to generate a short video. The operator’s legal identity and business address have not been provided, so this page does not identify a legal data controller.

Information processed

Depending on how you use the service, it may process:

• Account and sign-in information: name, email address, profile image when provided by a sign-in method, and authentication and session records.
• Security and device information: IP address and request details used for rate limiting and security controls. The site also sets an app_device_id cookie for device-related security checks.
• Attribution and preferences: language preference and, when present in a visit URL, a utm_source attribution value.
• Portrait and generation information: the portrait you upload, temporary-upload identifiers, generation task identifiers and statuses, timestamps, provider status or error information, and the URL and storage reference for a completed video.
• Orders and credits: product or pack selected, order and payment-provider references, amount and currency, transaction status, and credit ledger entries. Payment details are submitted to the payment provider selected for checkout.
• Support messages: information you include if you contact the service through a support channel.
• Optional site integrations: depending on operator settings, the site can load analytics, advertising, sign-in, or customer-support integrations such as Google Analytics, Plausible, Google AdSense, Google One Tap, Crisp, or Tawk.to. The integrations enabled on a particular deployment should be confirmed before publication.

How information is used

The service processes information to:

• create and secure accounts and sessions;
• receive, validate, preview, and temporarily store portrait uploads;
• send the portrait and generation inputs to the configured video-generation provider to produce the requested video;
• store completed video files in the configured object-storage service and associate them with the generation task;
• process orders, maintain credit balances, and return credits when a generation reaches a terminal failure under the configured generation policy;
• prevent abuse, apply rate limits, troubleshoot errors, and respond to support requests; and
• provide optional analytics, advertising, sign-in, or customer-support features when enabled.

When information is shared

Information may be shared with:

• Video-generation providers: the provider selected for a generation receives the portrait and task inputs needed to create the video. The application includes Fal and Kie integrations; which provider is used depends on the deployment’s settings and task routing.
• Object-storage providers: uploaded portraits and completed videos are stored using the storage provider configured for the deployment.
• Payment providers: checkout and payment details are sent to the provider selected for the transaction. The active provider must be confirmed in the deployment settings.
• Optional integrations: analytics, advertising, sign-in, and customer-support scripts may communicate with their respective providers when enabled.
• Authorities or other parties: where disclosure is required by applicable law or is necessary to protect the service, its users, or their rights.

The service code does not establish the independent retention, training, or other data-use practices of these third-party providers. Review the active providers’ terms and privacy notices before launch.

Storage and retention

Temporary portrait uploads are assigned a one-hour expiry and are removed by scheduled cleanup. Cleanup may be delayed if a storage or scheduled-job operation fails.

The product does not currently specify a public retention period for account records, order and credit records, generation-task records, security records, or completed videos stored for users. The operator must decide and publish those periods. Third-party providers may apply their own retention terms.

Your choices and requests

You can avoid uploading a portrait or using optional site features. Browser settings can be used to manage cookies; blocking authentication or upload cookies may prevent related features from working.

Privacy rights and request procedures depend on the laws that apply to you. The applicable jurisdictions and a privacy-request contact channel have not been supplied. Before publication, add the operator’s privacy contact and the process for access, correction, deletion, or other applicable requests.

Security

The application uses technical and operational controls for authentication, access, rate limiting, and temporary-upload validation. No online service or method of transmission can be guaranteed completely secure.

Changes

This policy may be updated as the service or its data practices change. The update date shown above indicates when this page was last revised.

Contact

Privacy contact: to be provided by the operator before publication.