This Privacy Policy describes how Pixora ("we", "us", or "our") handles information on Android and iOS. Pixora enlarges photos and illustrations and offers experimental image recreation on your device.
Pixora has no app account. Android version 0.9.2 adds optional Pixora Pro subscriptions and advertising for free users. Pro removes advertising, includes access to Recreate and adds VIP Customer Support. Image enlargement runs on the device. The enlargement models are included in the app. The optional recreation models are downloaded only after you choose Download model and accept their terms.
You choose one image with the system photo picker. Pixora processes that image on the device and can save a new copy to your gallery or hand it to another app that you pick in the share sheet.
Pixora does not upload photos, file names, file locations, or location data stored inside a photo. It does not copy GPS or other EXIF data into the saved result. It does not use the camera, microphone, contacts, or precise location.
Some information is sent off the device, as described below. It is sent over HTTPS.
Experimental recreation uses two model files totaling 1,881,812,340 bytes, downloaded from Hugging Face over HTTPS after your explicit action. Hugging Face and its delivery providers receive your network IP address and ordinary HTTP request information, including the requested model file and a Pixora app user agent. The request contains no photo, photo filename, local file path, description, seed, or account token. See Hugging Face's privacy policy.
Downloads can be cancelled and resumed. Pixora checks pinned SHA-256 hashes before using the files. The models stay in private app storage until you choose Delete model or uninstall the app. Clearing the cache does not delete these models. Recreation itself works locally, including any optional description you enter. The description remains in the local session and is never sent to analytics or a server. If you submit a result rating with usage analytics enabled, bounded technical processing parameters may accompany that rating as described below.
Google Play handles purchase payment details and subscription transactions under Google's privacy policy. Pixora queries purchases through Google Play Billing and checks their signatures on the device. Purchase tokens and signatures are used only for the local Billing flow and acknowledgement; they are not sent to Firebase, advertising, support, or a Pixora subscription server. Pixora does not operate a subscription-verification server.
The device saves whether Pro was last confirmed, when it was confirmed, and whether automatic renewal is enabled. Pixora checks purchases when you return to the app and approximately once a minute while it is open. An existing confirmation can allow Pro for up to 24 hours offline; a new check is needed afterward. This cache is not an independently verified subscription expiration date or refund record. Losing access does not delete a downloaded model, existing results, or an operation already in progress. VIP support requests carry a Pro topic label; this local label is not server-verified proof of payment. No response time is guaranteed.
Free Android users may see Yandex banner and interstitial advertising. Before the first advertising request, Pixora asks whether you allow personalized advertising. This choice is independent of Usage analytics and Error reports and can be refused or withdrawn in Settings. Pixora applies the saved choice before advertising requests. If restricted advertising is unavailable, advertising is skipped. Pro users do not receive advertising.
Yandex advertising requests can send network information including your IP address, device and application information, and advertising interactions. IP addresses may imply an approximate region. When you allow personalized advertising, the Yandex SDK can also use the Android advertising ID provided by Google Play services, subject to your system privacy settings. You can reset or delete this ID in Android settings. Declining personalization does not stop the network information needed to request restricted advertising. Pixora disables SDK location tracking and does not request geolocation permission or send photos, descriptions, local filenames, paths or support messages to advertising. Withdrawal destroys prepared ads and applies the non-personalized choice to subsequent requests. See Yandex's privacy policy.
The release app sends usage analytics and error reports to Google Firebase by default. You can turn Usage analytics and Error reports off separately in Settings. Turning them off does not turn off the availability check described below. The first launch shows a short notice about this.
Android monetization events include paywall sources, selected plan, catalog/purchase/restore/acknowledgement status, access changes, advertising requests and outcomes, consent decisions, durations, normalized errors and configuration revision. They exclude purchase tokens, signatures, order identifiers, payment details, image content, paths, descriptions, email addresses and support text. Technical purchase events are distinct from SDK automatic purchase metrics. When Usage analytics is enabled, the Firebase Analytics SDK also automatically records in-app purchase and subscription events, including product ID, product name and price.
When Usage analytics is enabled, actual advertising impressions also report the SDK's estimated revenue and currency when available, ad format, advertising placement, network name, estimate precision, app build number and test-build indicators. Missing revenue is not recorded as zero. These measurements contain no advertising ID or raw advertising response. Test impressions are marked separately from production traffic.
Usage analytics can include which screens and features are used, the chosen processing mode, speed, scale, whether processing used the GPU or CPU, a size category of the image, success or failure, durations, export format, and similar product settings. Error reports can include crash details, device model, operating system, and app version.
With usage analytics enabled, submitting a result rating sends the selected stars and a bounded technical summary of that generation: processing mode, model and revision, recommended model and whether it was applied, scale, speed, backend, image dimensions, input format, transparency, duration, and recreation steps/settings. Only whether an optional description was provided is recorded, never its contents. A random processing-attempt token links these events. Rating-dialog and store-link actions may also be recorded. Disabling usage analytics stops these events; local ratings are not uploaded later when analytics is enabled again.
These reports do not include photos, file names, file locations, email addresses, or the text of a support message. Firebase advertising-ID collection and analytics advertising-personalization signals remain disabled. Pixora does not add the Android advertising ID to analytics or crash reports; the separate Yandex advertising use is described above.
Firebase may also receive an app instance identifier, device and app information, and an approximate region derived from the network connection. Google's own policy is at firebase.google.com/support/privacy.
When the phone has an internet connection, Pixora asks Firebase Remote Config which processing modes are available. This check sends a Firebase installation identifier and technical information such as country code, language, time zone, operating-system version and app version. It does not include your photo or support message. Without a connection, the app uses the last saved availability, or enables every mode if it has never connected. Turning off analytics or error reports does not turn off this check.
A support message is sent only when you tap Send. Pixora then sends:
Pixora may show a rating prompt after a successful generation or an eligible app launch, with a limit of two automatic rating episodes. Rate Us in Settings remains available manually. Selecting 1–3 stars opens the support form; the selected stars are sent only if you explicitly send a support message. Selecting 4–5 stars opens the Pixora listing in Google Play, where you choose whether and how to review the app. Later eligible automatic prompts may use Google Play’s In-App Review API; Google controls whether its review window appears. An internal selection does not automatically publish a store review.
The message goes through a Google Apps Script web app to the developer’s support inbox. It does not include a photo, a file name, or a device identifier. Google's policy is at policies.google.com/privacy.
On Android, Pixora can show a notification while an image is being processed. On iOS, Pixora can request notification permission and show a local completion notification. The notification permission is optional. Refusing it does not stop processing. These notifications are not marketing messages.
We do not sell personal information.
The Google Analytics account has Google products and services data sharing turned off. Modelling contributions and business insights are enabled and use aggregated, de-identified measurement data. Google technical support access and account-level business recommendations are enabled. These settings do not add photos or support-message text to analytics.
A share sheet sends the image file only to the app you choose. That transfer is made by you, not by Pixora's analytics.
Photos and working files stay on your phone. You can delete the current session or temporary files in the app, and you can limit how much working data the app keeps between launches. Files you save to the gallery are not deleted by that cleanup.
To limit duplicate requests and abuse, the support service temporarily caches a random request ID for up to 6 hours and, when an email is supplied, a hash of the normalized email address for up to 10 minutes. Google may evict cache entries earlier. Support messages are kept for as long as needed to reply and handle follow-up. As checked on 17 October 2026, the Google Analytics property is configured to retain event-level data for 2 months and user-level data for 14 months. The user-data retention period resets on new activity. These settings do not govern most aggregated standard reports. Google states that Crashlytics keeps crash traces and associated identifiers for 90 days before starting removal from live and backup systems. Remote Config installation identifiers are retained until a deletion API request; Google then removes them within 180 days. Pixora does not currently offer an in-app request to delete all server-side installation data. See Firebase's retention details. You can ask us to delete a support message we still hold.
If you are in the European Economic Area or the United Kingdom, you may also have the right to restrict or object to certain processing and to complain to a supervisory authority. If you are a California resident, you may have the right to know and delete personal information, and to opt out of the sale or sharing of personal information. Pixora does not sell your photos or support content. When you allow personalized Android advertising, Yandex may process advertising information as described above; you can withdraw that choice in Settings.
Pixora is not directed to children under 13, or under the minimum age in your country. We do not knowingly collect personal information from children. If you believe a child has sent us a support message, contact us and we will delete it.
Information that leaves the device is sent over HTTPS. No method of transmission or storage is completely secure.
Google may process Firebase data and a support delivery in countries other than yours. Where the law requires it, those providers use their own transfer safeguards.
The full policy opens in your browser only when you choose its link in Pixora. This website is hosted on GitHub Pages. GitHub logs visitors' IP addresses for security purposes, as described in GitHub's privacy statement. This page contains no analytics scripts or advertising trackers added by us. The link from Pixora contains no photo, filename, email address or other user data.
We may update this policy. The page will show a new “Last updated” date. If a change is significant, Pixora may also mention it in the app.
For questions about this policy or your data, email kirylboriczewski@gmail.com or use the built-in Feedback screen in Pixora. A reply email in the form is optional.