Privacy Policy
How Burning Bridges AI handles account data, photos, video results, payments, and optional analytics.
Last updated October 11, 2026
Account and operational data
Google sign-in supplies account identity information such as the account identifier, email, name, and profile picture. Session and security data are used to authenticate you and protect private resources. We record credit allowances, generation task status, purchases, and relevant transaction identifiers to deliver the service and keep necessary business records.
Photos, video processing, and storage
Your browser can keep a selected photo draft on this device so you can return after sign-in or checkout. The draft expires from the restore workflow after 24 hours and can be removed using Remove. Selecting a photo alone does not upload it. AI Studio keeps a prompt and settings draft in this browser tab so you can return after sign-in or purchasing credits; draft content is not sent to analytics. When you submit a generation, the photo is uploaded to this service and provided to the video-generation provider for processing. Inputs and saved video results are held privately in Cloudflare R2, with access protected by account authorization.
Payments
Stripe processes your payment details. This service keeps the checkout, purchase, and payment identifiers and the purchased credit allowance needed to verify payment and handle billing. Do not send full card information through support. A redirect URL or client event is not used as proof of payment.
Optional analytics
After you consent to analytics, we use first-party analytics, Plausible, and Microsoft Clarity. Plausible measures visits and sources; Clarity records masked page interactions, scrolling, and clicks. Account, administrative, authentication, and payment pages do not start recording. Photos, prompts, and private results are masked from session recording. We collect interaction events and attribution data such as campaign UTM parameters, referring site, page path, language, country, device category, and IP address. Consented events help us understand use and purchases. We do not include uploaded photos, video content, passwords, sign-in tokens, private media links, or raw generation-provider responses in analytics events. Refusing optional analytics does not prevent the core creation workflow.
Analytics retention and withdrawal
Our first-party analytics retention policy is 7 days for IP addresses and 90 days for analytics events and inactive attribution records. Cleanup runs when a subsequent analytics or reporting request triggers it, so physical deletion may occur later if there are no such requests. Reports exclude events older than 90 days and omit IP addresses older than 7 days independently of cleanup. You can decline optional analytics or change the choice in the consent controls. Withdrawing consent stops Clarity recording and future Plausible events; it does not erase previously processed data. Microsoft and Plausible apply their own retention policies, separate from our first-party retention. Necessary authentication, security, payment, and business records are separate from optional analytics and may be retained as needed; withdrawing analytics consent does not erase those operational records.
Providers and requests
Microsoft Clarity and Plausible provide optional website analytics. Google handles sign-in, Stripe handles payment, Cloudflare provides hosting and private storage, and the generation provider processes the submitted photo to make the clip. Their own processing and terms may also apply. Submit requests about access, correction, or deletion through the Contact form. The name, email, and message are saved for review, with no automatic email sent. We may need to verify account ownership, and necessary business or security records may need to remain. We do not promise an unverified blanket deletion deadline or a fixed media retention period.