Last updated: September 28, 2026
This policy explains how FilmBloom handles information in its Android and iOS apps and browser studio. Some features differ between the current native apps and earlier mobile versions.
FilmBloom processes imported or captured photos on your device. The mobile apps keep rolls, edits, and preferences in local app storage; exported photos may also be saved in your device's photo library. The browser studio stores its local library in your browser. We do not provide a cloud account or photo backup service, and our app does not upload your photos to a FilmBloom server. If you choose to share or export a photo, your device sends it to the destination you select.
The mobile apps ask for camera or photo-library access when a feature needs it. You can change those permissions in your device settings. The browser may ask for access to a selected file or camera through its normal browser controls.
The current native mobile apps offer separate in-app choices for Firebase Analytics and Firebase Crashlytics. We configure their collection as disabled by default until you choose to enable them; their SDKs may still process limited app or device information needed to initialize. If enabled, Firebase may receive app interaction events, app and device information, identifiers used by its services, and crash or performance diagnostics, depending on which choice you enable. We use this information to understand app use and diagnose failures. A changed choice applies to future app sessions and does not delete information already processed by Firebase.
Earlier mobile versions may have different consent screens or telemetry behavior. Review the privacy controls in the version installed on your device. The standalone browser studio does not use Firebase Analytics or Crashlytics.
The current native Android app has no active ad placement. Earlier Android versions and the iOS app may show Google AdMob ads. In the current native iOS app, an ad request can begin only after the first-run privacy choice and when the in-app ad-consent flow permits it. When ads are requested, Google may process identifiers, your IP address, general location inferred from it, app activity, and diagnostics to deliver and measure ads. The iOS app offers an in-app advertising privacy-options action when the consent service requires it. Device privacy settings may also affect advertising. The standalone browser studio has no AdMob ads.
FilmBloom does not require an account and does not ask for your name, email address, or phone number to edit photos. Google provides the Firebase and AdMob services described above. See Firebase privacy information and Google's Privacy Policy for their practices. When you load the browser site or this policy, the hosting service processes ordinary web requests, including your IP address, to deliver the pages.
You can change analytics and crash-report choices in the native app's settings, use available in-app ad privacy options, and revoke camera or photo access in device settings. You can remove local app data by deleting the app, and browser library data through your browser's site-data controls. Photos you already exported to a gallery or shared destination must be removed there separately. For questions or requests concerning information processed through our service providers, contact us at the address below.
FilmBloom does not require an account or ask children to provide contact details. Parents or guardians can contact us about a privacy concern using the address below.
We may update this policy as the app changes. The date above shows the latest revision.