Privacy Policy for Refina
Effective date: 17 August 2026
ZPLabs provides Refina (com.zplabs.refina) as a free, ad-free photo-editing application. This policy explains what information Refina processes, why it is processed, and the choices available to users.
Summary
Refina does not require an account.
Refina does not contain ads, purchases, subscriptions, billing, or a premium tier.
Selected photos and edited images are processed locally on the user's device and are not uploaded to ZPLabs or Firebase by Refina.
Refina uses Google Firebase Analytics, Crashlytics, Sessions, Installations, and Cloud Messaging for product measurement, reliability, and notifications.
ZPLabs does not sell or rent personal information and does not use Refina data for advertising.
Photos and on-device processing
Refina can access only media that a user selects through Android's system photo picker or supplies through a camera action initiated by the user. Image decoding, editing, effects, drafts, recent-project information, and export rendering occur on the device. Refina does not upload source photos or edited images to ZPLabs, Firebase, or a remote image-processing service.
An exported image is added to device media only after the user chooses Save. When the user chooses Share, Android's system sharing interface sends the selected export to the destination chosen by the user. The destination service's privacy policy applies after it is selected.
Information processed through Firebase
Refina uses the following Google Firebase services:
Firebase Analytics: processes app interactions and lifecycle events, notification interactions, app and device information, an app-instance identifier, and an approximate region derived by Google Analytics from a masked IP address.
Firebase Crashlytics and Sessions: process crash stack traces, non-fatal diagnostic reports, app and device state, app version, session information, and a Crashlytics installation identifier to diagnose crashes and application-not-responding events.
Firebase Installations and Cloud Messaging: process a Firebase installation identifier, registration token, app version, device/app information, and notification delivery or interaction information needed to deliver notifications allowed by the user.
ZPLabs uses this information only for product analytics, application functionality, reliability, and permitted notifications. Refina does not attach a user's name, email address, account identifier, selected-photo name, file path, photo content, or edited image to Firebase reports. Advertising ID collection, personalized advertising signals, Install Referrer, and Android AdServices permissions are disabled or removed.
Google acts as a service provider for these Firebase services. Additional information about Google's handling of data is available in the Google Privacy Policy and Firebase privacy documentation.
Permissions
Refina uses Android's system media picker and delegated camera flow instead of requesting broad modern access to the photo library or direct camera access. On Android 9 and earlier, Refina may request legacy storage permission only when needed to save an image to shared device media.
On Android 13 and later, Refina may request notification permission. Denying notification permission does not prevent photo selection, editing, saving, or sharing.
Storage, retention, and deletion
Drafts, recent-project information, working files, and temporary share files may be stored locally. Users can remove app-local information by clearing Refina's storage or uninstalling the app. Images already saved to the gallery must be deleted separately with a gallery or file-management application.
Firebase transmits data using encrypted connections. Crashlytics generally retains crash reports and associated identifiers for 90 days before deletion begins. Deletion of Firebase installation data from live and backup systems can take up to 180 days after a deletion request. Analytics event and user-level retention follows the retention setting configured for Refina's Analytics property; aggregated reporting may remain after event-level data expires.
Clearing app storage or uninstalling Refina stops that installation from sending new information, but it does not immediately remove information already held under the retention periods above. Because Refina has no user account and does not send a ZPLabs-defined user identity, ZPLabs may not be able to associate a privacy request with a specific Firebase installation. Users may contact ZPLabs about access or deletion using the address below.
Children
Refina is a general-audience creative tool and is not specifically directed to children. It does not provide account creation, behavioral advertising, a public content feed, or direct user-to-user communication.
Security
ZPLabs limits Refina's network data to the Firebase purposes described in this policy and uses the security controls provided by Android, Google Play, and Firebase. No method of transmission or storage is completely secure, so absolute security cannot be guaranteed.
Changes to this policy
ZPLabs may update this policy when Refina's features, service providers, legal requirements, or data practices change. Material changes will be published with a revised effective date before the affected app version is distributed.
Contact
For privacy questions or requests, contact:
ZPLabs
Email: zplabs.app@gmail.com