PixWiz
Get the app

Privacy Policy

Effective date: October 26, 2026  ·  App: PixWiz (com.amalantony.pixwiz)  ·  Developer: Amal Antony (solo developer)  ·  Contact: [email protected]

1. Summary

PixWiz is a photo and poster editor that runs on your device. It has no user accounts, no sign-in, and no servers operated by the developer. Your designs and the photos in them are stored only on your device.

PixWiz does not collect your name, email address, phone number, contacts, or location, and it never uploads your photos or designs anywhere.

PixWiz is not, however, fully offline. It includes advertising, purchase processing, usage analytics, crash reporting, and stock-photo search, all of which are provided by third-party companies that receive some data when those features run. Sections 4 and 5 describe exactly which, and why.

2. Your photos and designs

Your photos and designs stay on your device. Specifically:

  • Photos you import (from your photo library, or shared into PixWiz from another app's share sheet) are copied into PixWiz's private app storage on your device.
  • Projects are saved locally: project metadata in the app's local key-value store, and image files in PixWiz's own private app directory. There is no cloud sync, no backup to a PixWiz server, and no way to access your projects from another device.
  • Deleting a project, or uninstalling PixWiz, removes that local data from your device.
  • There is no PixWiz server for your content to be uploaded to. The developer does not operate any backend infrastructure for this app.

Background removal and object erasing are processed entirely on your device. PixWiz's background removal (photo cutout) and Magic Eraser (object removal) features run machine-learning models that are bundled inside the app and executed locally by native code on your phone. Your photo is never transmitted to a remote server, a cloud API, or the developer in order to perform these operations. They work with the device in airplane mode. This is a deliberate design choice and is verifiable in the app: the models ship as files inside the app binary, and the image processing is performed by an on-device native module.

The rest of PixWiz's core editing works the same way: filters, masks, overlays, text, shapes, collage layout, and export all run on your device too, with no third party involved.

Exported images. When you export a design, PixWiz writes two standard PNG text fields into the file: Software (set to PixWiz) and Creation Time (the timestamp of the export). No personal data, device identifier, or account information is embedded in your exports. Because PixWiz re-encodes images during editing, metadata from your original source photo — including any GPS/location EXIF data the original camera file contained — is generally not carried through into the exported file. PixWiz's own code never reads, stores, or transmits photo location metadata.

3. Data PixWiz itself collects

None, in the sense that matters most: there is no PixWiz-operated server, database, or logging system that receives data about you.

Everything described in the rest of this policy is data flowing to third-party services the app integrates, under those companies' own privacy policies, not to the developer.

4. Third-party services

4.1 Google AdMob (advertising) — Google LLC

PixWiz shows ads to fund the free tier. Ad formats used: banner ads, interstitial ads, rewarded ads (watched voluntarily to unlock a feature — for example, watching one rewarded ad removes the export watermark for the current project, and it stays removed for every future export of that same project), and app-open ads.

AdMob may collect device and advertising identifiers (the Android Advertising ID, or Apple's IDFA on iOS where permitted), approximate location derived from IP address, device and OS information, and ad interaction data, in order to select, deliver, measure, and bill for ads. PixWiz declares the com.google.android.gms.permission.AD_ID permission on Android for this reason, and declares Apple's SKAdNetwork identifiers on iOS so ad attribution can work without tracking you individually.

Ad content rating. PixWiz configures AdMob with a maximum ad content rating of "Teen," and declares the app as not child-directed and not tagged for users under the age of consent. See section 6.

4.2 Meta Audience Network (advertising mediation) — Meta Platforms, Inc.

PixWiz uses AdMob mediation, with Meta Audience Network wired in as a mediation partner on both Android and iOS. This means some of the ads you see are served by Meta rather than Google, and Meta's advertising SDK may separately collect device identifiers and ad interaction data to deliver and measure those ads, subject to Meta's own privacy policy.

This is called out explicitly because it is not obvious from the app's behavior: to a user, a mediated ad looks the same as a Google-served one.

4.3 Advertising consent and tracking permission

  • On iOS, PixWiz presents Apple's App Tracking Transparency (ATT) prompt. If you decline, the IDFA is not made available to the ad SDKs, and ads will be served on a non-personalized basis.
  • On both platforms, PixWiz requests consent information through Google's User Messaging Platform (UMP) and displays a consent form when one is required for your region (for example, under the GDPR in the EEA/UK). Your choices there are recorded and honored by the ad SDKs.
  • On Android, you can additionally opt out of personalized ads system-wide, or reset/delete your advertising ID, in Android's Settings under Privacy → Ads.

4.4 RevenueCat (in-app purchases and subscriptions) — RevenueCat, Inc.

PixWiz uses RevenueCat to manage premium purchases and subscription entitlements. RevenueCat identifies your installation by an anonymous App User ID that the RevenueCat SDK generates on the device. PixWiz never supplies, asserts, or links any identity of its own to it — there is no login call in the app, because there are no accounts. The anonymous ID is not derived from your name, email address, or any store account.

RevenueCat receives purchase and subscription events (which product was bought, whether an entitlement is currently active, when it renews or expires) along with technical device and app information, so your premium status can be determined and restored. See RevenueCat's own privacy policy for how long they retain this data and how to contact them about it.

4.5 Apple App Store / Google Play (payment processing)

All payments are processed by Apple or Google through their own in-app purchase systems. The developer never sees or receives your payment card number, billing address, or store account credentials. PixWiz declares the com.android.vending.BILLING permission on Android for Google Play billing.

4.6 Firebase Analytics (usage analytics) — Google LLC

PixWiz logs anonymous feature-usage events so the developer can tell which features are actually used and where people get stuck. Examples of what is logged: a project was created (and its canvas size and type), a design was exported (and whether it carried the free-tier watermark), an element was added (and whether it was text, a sticker, or a shape), a filter or mask or overlay was applied, background removal completed, a paywall was shown (and which feature triggered it), a purchase completed, and ad outcomes (an impression was served, a rewarded ad was completed or dismissed).

What these events do NOT contain: your photos, your designs, any text you typed into a design, file names, or any contact information. PixWiz does not set any Firebase user ID or custom user property, so these events are not associated with an identity supplied by the app. Firebase Analytics does generate its own device-scoped app instance ID, which Google uses to group events from the same installation.

Analytics collection is disabled entirely in development builds.

4.7 Firebase Crashlytics (crash reporting) — Google LLC

When PixWiz crashes, Crashlytics automatically collects a diagnostic report so the bug can be fixed. This typically includes the stack trace, app version, device model, OS version, and device state (such as available memory) at the time of the crash. PixWiz does not attach any custom user identifier or custom keys to crash reports.

4.8 Firebase Cloud Messaging (push notification capability) — Google LLC

The Firebase Cloud Messaging SDK is included in PixWiz, and the app requests notification permission on launch.

In the interest of accuracy: as of the effective date of this policy, PixWiz does not actually send push notifications. There is no campaign infrastructure behind it and the app contains no code that retrieves a push token or handles an incoming message. The capability is present but unused. Because the SDK is linked and initialized, it may still register a device-scoped token with Google.

If the developer begins sending notifications, this section must be updated to describe what is sent and why.

4.9 Pexels (stock photo search) — Pexels GmbH

PixWiz's stock photo search sends your search term to the Pexels API, together with the app's Pexels API key and pagination parameters. Pexels returns matching photos, and when you select one, the image file is downloaded from Pexels' servers to your device.

No personal data, device identifier, or information about your design is included in these requests. As with any network request, Pexels (and any CDN in front of it) will see the connecting IP address. See Pexels' own privacy policy for how they handle API requests.

4.10 App update and review services

  • EAS Update (Expo) — PixWiz checks Expo's update service for over-the-air JavaScript updates. This request includes app and runtime version information.
  • Google Play In-App Updates (Android) — PixWiz asks the Play Store whether a newer version is available and offers to install it. This is handled entirely by Google Play.
  • App Store / Play Store review prompt — after an export, PixWiz may ask the operating system to show the native "rate this app" prompt. The rating and any review text go to Apple or Google, not to the developer, and the developer is not told whether you rated the app.

5. Device permissions

Photo library and media access. PixWiz requests photo library access so you can pick images to edit, and media/storage access so you can save finished designs to your gallery. These are handled by the standard operating system permission prompts and can be revoked at any time in your device's settings. Because there is no PixWiz server, nothing you grant here results in your photos being sent to the developer.

On Android, PixWiz declares READ_MEDIA_IMAGES, READ_MEDIA_VISUAL_USER_SELECTED, READ_EXTERNAL_STORAGE, WRITE_EXTERNAL_STORAGE (the latter two for compatibility with older Android versions), and ACCESS_MEDIA_LOCATION. The ACCESS_MEDIA_LOCATION permission is enabled by the media library component the app uses; as stated in section 2, PixWiz's own code never reads, stores, or transmits photo location metadata.

Permissions that are declared but not used. PixWiz's Android manifest also currently declares RECORD_AUDIO, READ_MEDIA_VIDEO, and READ_MEDIA_AUDIO. PixWiz does not record audio, does not use the microphone, and does not use the camera. A review of the codebase found no microphone, camera, audio, or video recording or capture code anywhere in the app, and no audio/video/camera libraries among its dependencies. These permission entries do not correspond to any feature.

Notifications. PixWiz requests notification permission on launch. See section 4.8 — the capability is currently unused.

6. Children's privacy

PixWiz is not directed at children under the age of 13, and the developer does not knowingly collect personal information from children under 13. The app is configured in its advertising settings as not child-directed, with a maximum ad content rating of "Teen."

Because PixWiz has no accounts and collects no personal information directly, there is generally no personal data about a child for the developer to hold. If you believe a child under 13 has provided personal information through this app, or if you have a concern about a child's use of the app, please contact [email protected] so it can be addressed.

7. Data retention and deletion

The developer runs no servers and holds no database of users, so there is no developer-side record of you to retain or delete. In practice, retention breaks into two parts:

On your device. Your projects, imported photos, downloaded templates, and app settings live in PixWiz's private storage and persist until you delete the project or uninstall the app. You control this directly. Uninstalling PixWiz removes this data.

At the third parties listed in section 4. Each of RevenueCat, Google (AdMob, Firebase Analytics, Crashlytics, Cloud Messaging), Meta, Pexels, Expo, jsDelivr, and wsrv.nl retains data according to its own policies and retention windows, which the developer does not control and cannot delete on your behalf.

This policy deliberately does NOT state specific retention periods for those services, because quoting a number the developer has not verified would be worse than pointing you to the authoritative source. To find out how long a given company keeps data from this app, or to make a request directly to them, consult that company's published privacy policy and data-request process.

To the extent any request can be routed by the developer, it will be — see section 8.

8. Your rights and how to contact us

Depending on where you live, you may have rights over your personal data under laws such as the GDPR (EEA/UK) or the CCPA/CPRA (California), including rights of access, correction, deletion, and objection to certain processing.

Please be aware of what is and is not possible here, so a request isn't sent into a void:

  • The developer cannot look up, export, or delete "your data," because the developer holds none — there is no account, no server, and no identifier linking you to anything the developer can query.
  • Data held on your device you can delete yourself, by deleting projects or uninstalling the app.
  • For data held by the third parties in section 4, requests must generally go to those companies, since they are the parties that actually hold it. The developer will help you identify the right contact and will pass on what can be passed on.
  • For advertising specifically, the most effective controls are the ones in your own hands: the iOS ATT prompt and iOS tracking settings, the Android advertising ID reset/opt-out, and the consent form described in section 4.3.

The developer does not sell your personal information, and does not share it with third parties for purposes beyond the services described in section 4.

For any privacy question, concern, or request, contact: [email protected]

This is also the app's general support address.

9. Changes to this policy

This policy may be updated as PixWiz's features and integrations change. When it is, the effective date at the top of this document will be updated. Material changes — particularly any new data collection, any new third-party SDK, or any change to on-device processing — should be reflected here before the release that introduces them ships.

Continued use of PixWiz after an update constitutes acceptance of the revised policy.