Bangsy Privacy Notice

About this notice

This notice explains how your photos and account information are handled when you use the service. Purchases are currently unavailable.

Photos and previews

You choose a photo and a hairstyle preset. Your browser may resize and re-encode the photo to at most 2 megapixels and 2048 pixels per side; that processed image becomes the original used for comparison. The uploaded file must be JPEG or PNG and no larger than 5 MB.

Selecting a photo does not start an AI generation. In account mode, upload and recovery require sign-in. If sign-in interrupts your work, a processed draft is recoverable from this browser's IndexedDB for 24 hours. The app removes an expired draft when it next opens; a closed browser cannot run cleanup, so local bytes may remain until that cleanup or a site-data clear. A successful upload clears the draft; you can also clear it with Start over or your browser's site-data controls.

When you explicitly generate a preview, the server sends the processed image and the selected preset to Fal's image model. We request private output and retention controls, but these controls do not establish that Fal or the model operator keeps no logs or copies. Their processing and retention are separate from our file expiry. We do not publish your photos or results as examples without separate permission.

Private storage and expiry

In Cloudflare mode, originals and results are stored in a private R2 bucket and retrieved through account-authorized endpoints. In local development, a private browser session controls access to local test files. Clearing a local session cookie may prevent recovery.

Originals expire 24 hours after upload. Each generated result expires 24 hours after it is successfully retrieved. Expired files cannot be downloaded through the service. Scheduled cleanup removes expired stored files; local cleanup only runs while the development process is running and catches up on restart. Downloads and locally exported reference PNGs remain on your own device until you delete them.

Task identifiers, selected presets, status, and billing records can remain after image expiry to support balances, refunds, recovery, and dispute handling. Keeping these records does not keep the expired image bytes.

Account, payment, and operational data

We store account name, email, authentication records, and session information. Passwords are hashed by the authentication system. Signup attribution may include referring site, campaign parameters, country, IP address, and browser language. Infrastructure providers may also process operational request logs. We do not insert photos, private file URLs, or complete image inputs into general analytics events.

For signed-in accounts, we may record a small set of product actions: viewing prices, choosing an image package, requesting an image download or reference export, and voluntarily marking a preview as a candidate, not for you, or undecided. These records contain only fixed page and style categories, package identifiers, reference-image counts, or the selected feedback option. They do not contain photo bytes, filenames, private task or file addresses, your reference-image question, or chat text. These browser-reported actions are not proof of payment, successful generation, or a file saved to your device. Signed-out visitors are not given a new identifier for this product-event system.

Stripe processes card payments when purchases are enabled. The application keeps order identifiers, amounts, currency, payment status, image-unit grants, usage, reservations, and refund records; it does not store full card numbers. A configured transactional email provider sends verification and password-reset messages. Cloudflare supplies hosting, database, and storage. Processing is not represented as restricted to one country.

Choices and contact

Use only photos you have permission to process. Download results you want to keep before expiry, and protect downloaded copies on your own device. You can update available profile details through your account and contact the operator about access, correction, or deletion requests. Financial or security records may need separate handling from image deletion. No automatic account-deletion or immediate deletion of all transaction records is promised by the current interface.

Purchases are currently unavailable.