Privacy Policy
How Bulin47 Maker processes your photo, generated videos, account, and payments.
Last updated: 2026-10-11
Your photo and generation
Selecting a photo creates a local browser preview only. When you submit a generation request, we upload that one photo to private storage and send it, through short-lived signed links, to the processing services needed for your video. Uploads are processed to remove EXIF location and camera metadata before storage. Only upload a photo you have permission to use.
We use Cloudflare for site delivery, private media storage, and application records; Replicate for the video generation and the audio merge; and SeeAPI for content-safety checks on your input photo and the finished video. These services receive only the media or request information necessary for their part of the process. Processing may occur outside your country. We do not claim a particular processing region.
Access, retention, and deletion
Your uploaded photo's access expires 24 hours after upload. Your finished video's access expires six days after it is stored; the result shows your download deadline in your local time zone. Download your video before that deadline. Expired links cannot be renewed to extend access.
You can use Delete video now on a completed result to permanently remove that task's media from our storage. Deletion is available after processing finishes. It removes our media copies and the stored media pointers, while keeping necessary account, credit, and payment records. It does not refund a completed generation. Files you already downloaded to your device are under your control.
Automatic deletion is enabled for our private storage: photos and intermediate files become eligible for deletion after one day, and finished videos after six days. Cloudflare processes these expiration rules asynchronously, typically within the following 24 hours; physical deletion is not guaranteed at an exact time. The access deadlines above still apply while cleanup is pending. You can also use the deletion control or contact us to request removal of our copies.
Our deletion controls do not delete copies held by processing providers. Replicate's API documentation states that API prediction inputs, outputs, and logs are removed after one hour by default. SeeAPI's privacy policy does not specify an API-media retention period. Their policies and applicable model terms govern their handling; we do not promise that all upstream services never retain data or use it for training.
Accounts and payments
Google sign-in provides account information such as your email, name, and profile image. If you use email sign-in, we send a one-time sign-in link to that address. We store account identifiers, generation status, credit transactions, and support requests to operate your account. Stripe processes checkout and payment details. We store order identifiers, payment status, and purchased video credits; we do not receive your complete card number. Payment notifications may include an order reference, amount, and status for operational monitoring.
When optional Google Analytics or Microsoft Clarity is enabled and you allow analytics, the app sends cleaned public page paths and a small set of product steps. Clarity replay and heatmap data is masked in the workspace and account controls. Google or Microsoft may process the technical information needed for the selected service. The app's analytics events omit selected photos, filenames, email addresses, account, task, or order identifiers, and checkout URLs. You can decline or reopen that choice in this browser.
Security and your choices
Media is stored privately and delivered through short-lived signed links without public caching. Treat a signed link as private: anyone you share it with can use it until it expires. No internet service can guarantee complete security.
You can remove the selected photo before submitting, delete completed task media, and request account-related assistance through Support or hello@bulin47maker.app. Authentication and security use essential browser storage; see the Cookie Policy. We update this page when processing or retention practices change.