Scope
OmniaPixels (Android)
OmniaPixels · Privacy
This page explains how the OmniaPixels Android app handles your photos, the disabled default ad gate, and Play Data Safety matching.
Quick summary
OmniaPixels edits your photos on your device and never uploads them. The current Play candidate does not request or show ads by default; if an ad-enabled build ships, Google Mobile Ads/UMP data processing and the Play Data Safety form must match the exact build.
Scope
OmniaPixels (Android)
Publisher
Omnia Creata
Effective date
June 22, 2026
Document
Review the sections below and contact us directly at founder@omniacreata.com if you need a specific answer.
OmniaPixels is a privacy-focused, on-device photo editor. Photos you select are read only so you can edit them on your device, edited copies are saved as new files, and your originals are not modified. Your photos are never uploaded to Omnia Creata or to any third-party image service; core editing works fully offline. Temporary files used for sharing may be written to the app cache on your device and can be cleared by clearing the app cache.
We do not maintain user accounts and we do not run our own servers for your content. The app stores small settings and local records on your device only (for example: privacy consent choice, interface preferences, export options, saved feedback drafts, and local work/recovery records). These leave your device only when you choose to share an export or send feedback. The Google Mobile Ads and Google's User Messaging Platform (UMP) gate is currently disabled; disabled builds do not request or show ads.
When you choose to send feedback, OmniaPixels opens your mail app with your note and basic app context such as app version, build number, screen, selected tool, ad setting, language, and device platform. OmniaPixels does not attach photos automatically and does not send feedback silently. You can review and edit the email before sending it.
When an ad-enabled build is released, Google Mobile Ads and UMP may process advertising identifiers, IP address, device/app information, diagnostics, consent status, and ad interactions for ads, consent, fraud prevention, measurement, and service operation. The Play Data Safety form must match the exact uploaded APK/AAB before submission.
When an ad-enabled build is released, Google UMP is used for users in the European Economic Area, the United Kingdom, and Switzerland. Required consent forms are shown before ads are requested, and ads are only requested after the runtime allows them. Google's privacy options can be opened from app settings when required.
The current Play candidate does not include a billing SDK or active in-app purchase flow. If in-app purchases are enabled later, those features will use Google Play Billing, this policy and the Play Data Safety form will be updated in the same release, and ads or purchases will never be required for editing, exporting, or opening your existing work.
Photo/media access is used only through the system picker, to open the photos you choose and to save your exports. Network access is not required for editing; it exists only for future, clearly-announced optional features, policy links, and support links.
OmniaPixels is a general-audience utility app intended for users 13 and older. It is not directed to children and does not knowingly collect personal data from anyone, including children.
We do not collect, sell, or share your photos or account data. When an ad-enabled build is released, Google Mobile Ads and UMP data processing may occur under Google's policies; the Play Data Safety form must match the exact uploaded build.
Local settings on your device are kept until you clear them (or uninstall the app). Retention of ad-related data is governed by Google's policies.
When an ad-enabled build is released, you can manage Google's required privacy options inside the app when they are available. Contact founder@omniacreata.com with privacy questions.
Related page
If you have a more specific privacy question, you can contact us directly.