Privacy policy
This policy covers FRAME apps and the website provided by HUANGBSOLO. Available features vary by platform and version.
Local projects and permissions
FRAME requires no account. Images you select, editing copies, thumbnails, project settings, titles and credits are processed and stored on your device. The app does not upload them to the developer or advertising SDKs. Only still photos are imported from Live Photos and Motion Photos, not paired or embedded videos. Features use system file or photo pickers and photo access or saving permissions as needed; Android 9 may request storage write access when exporting.
Existing camera details, exposure settings, capture dates, GPS coordinates and photographer credits may be read locally for editing and watermarks. The app does not request live location, contacts, camera or microphone access. Supported previews and live wallpapers use motion sensors for immediate perspective effects without recording motion history or transmitting sensor data.
Online materials and network information
Online catalogs, thumbnails and selected images are downloaded over HTTPS and cached locally. Services delivering materials and webpages, including Cloudflare, process IP addresses, requested resources, request times and device or browser request information for delivery, operation and security. The app may use network information to determine an approximate country or region for ad availability. This requires no GPS access and does not upload local projects.
When you request online materials in the Android app, your membership status may be sent to content-delivery service providers to provide the requested service. These requests also involve the network information described above.
Mobile advertising
Ads use publisher-configured ad units or Google’s official demo ad units. The app selects demo units when it detects an emulator, identifies the user as being in mainland China, or cannot confirm the region. On Android, demo units are also used when Google Play services are unavailable. SDK requests for demo ads still contact Google and may process data as described below; demo IDs do not mean zero data collection.
Mobile versions with ads use Google Mobile Ads (AdMob). FRAME requests non-personalized ads. Google may process IP addresses and approximate location, advertising, app-set and applicable account-related identifiers, app and ad interactions, and diagnostic information for ad delivery, measurement and fraud prevention. Non-personalized ads still involve data processing. Availability of identifiers depends on system settings and permissions.
Use system privacy settings to manage advertising identifiers and applicable tracking permissions. See the Google Privacy Policy, Android SDK data disclosure and iOS SDK data disclosure for data practices and controls.
Where required, the Android and iOS apps provide Advertising privacy options in Settings to review or change your advertising privacy choices.
Firebase usage and diagnostics on Android
The Android app integrates Google Analytics for Firebase, Firebase Crashlytics and Firebase Performance Monitoring. Analytics and performance data collection and automatic crash-report uploads are off by default. You can voluntarily enable all three through “Usage and diagnostics” in Settings and turn them off at any time. The iOS and macOS apps do not integrate these Firebase services.
When enabled, these services process app interactions, session and purchase events, installation and app-instance identifiers, device and app information, crash reports, performance and network metrics, and approximate location inferred from network information to improve FRAME. Analytics advertising-ID collection, advertising storage, use of data for advertising and ad personalization remain disabled. Photos, EXIF metadata and project content are not submitted as custom analytics or diagnostic data. Crashlytics may store reports locally while uploads are disabled; FRAME requests deletion of unsent reports when starting with this setting off and when you turn it off. Crashlytics opt-out may fully take effect on the next app launch. Data may already be queued or in transit when you disable collection; disabling does not erase information already received by Google.
Google retains this information under the relevant service rules and settings. Crashlytics generally retains reports and associated identifiers for 90 days before starting deletion; Performance Monitoring retains IP-associated events for 30 days and other installation-associated performance data for 60 days. Analytics retention depends on the project settings. See Firebase privacy and security and Analytics data collection. Clearing app storage or uninstalling does not automatically delete information already received by providers; contact us about applicable data rights.
Purchases and membership
App Store and Google Play purchases are processed by the respective store. FRAME uses product, transaction and purchase-status information returned by the store to verify, enable and restore membership. The developer does not receive full payment-card details or store account passwords. Store processing follows the Apple Privacy Policy or Google Privacy Policy.
Protection, retention and deletion
The developer does not collect, share or sell your local projects. Private app data is protected by operating-system access controls; Android automatic backup is disabled. Delete projects in the Library and use platform app-data controls to remove caches and preferences. On Android, clear app storage; on iOS, delete the app and its data. Original files and exported images or videos are separate and must be deleted in your file or photo app.
Exports may contain credits, locations or other watermarks you enable; review them before sharing. File providers, system backups and apps receiving shared files operate under their own policies and your system settings. FRAME provides no server accounts or cloud project backups.
Network requests use HTTPS. Network and advertising providers retain network, advertising and diagnostic information for the purposes above under applicable law and their policies; see Cloudflare's Privacy Policy. Providers may process data outside your country or region.
Website, contact and policy updates
Visiting the website or online policies sends the hosting service the network information needed to deliver pages, without uploading local projects. Emails and contact details you send are used to answer and follow up on inquiries, and retained only as needed for that support and legal obligations. Contact the developer with policy questions or applicable requests to access, correct or delete personal information you provided. Cloudflare may also process website request and page-visit information for traffic and performance statistics. The website does not currently integrate Firebase monitoring or analytics.
This policy is updated when data practices change; the latest date appears above. Privacy contact: joseph.petzval@gmail.com.