privacy

Pixels Only — Privacy Policy

Effective date: 2026-09-18 Last updated: 2026-09-18

Summary

Pixels Only shows you what a photo says about you — where it was taken, when, on which phone, and more — and makes copies that carry the picture and nothing else, smaller if you like. Every copy is read back after it is written, to check that it carries nothing but the picture.

Your photos never leave your phone through this app. They are read and rewritten on the device. Nothing is uploaded, there is no account, and there is no server of ours anywhere. A copy only goes somewhere when you send it there yourself: into a folder you choose, or to an app you pick from the share sheet.

The app keeps no history. There is no list of the photos it has seen, no count per photo and no record of what any of them said. A tool that removes what photos say about people should not keep its own record of them.

The only data that leaves your device is what Google AdMob needs to show ads, and no photo, no copy and nothing read out of a photo is any part of that.

Who we are

How photos come in and go out

Location may already be blanked. Because the app does not hold Android’s media-location permission, Android may remove a photo’s location before handing it over. When that has happened, the app says so rather than claiming the photo has no location.

What a copy cannot hide. The app removes what the file says, not what the picture shows. A face, a street sign or the view from a window is still there in every copy. A copy keeps which way up the picture goes and its colour profile, because those describe the picture, not you.

What the app stores on your device

That is the whole list. There is no database, no name, no email, no location and no contact anywhere in it. We hold no copy of any of it: there is no analytics SDK in this app, no crash reporter of our own, and no telemetry of any kind.

The app opts out of Android cloud backup and device-to-device transfer, so none of this is copied into Google’s backup service.

Third-party services we use

Google AdMob (ads)

The app is supported by ads served by Google AdMob. Ads are the only reason the app needs an internet connection at all; reading photos and making copies work fully offline.

The app shows no banner ads, no native ads and no ad on launch. What it shows is an occasional full-screen ad after you close a batch whose copies you saved or shared — never while you pick photos, never while copies are being made, and never over a folder picker or share sheet. There is also an optional rewarded ad you can choose to watch, in Settings → Turn adverts off for a day, to switch ads off for 24 hours.

To serve ads, Google receives data from your device, which may include your device’s advertising identifier (AD_ID), coarse location inferred from your IP address, device and app information, and ad-interaction data. It does not receive any photo, any copy or anything read out of a photo — the app never sends those anywhere, and no ad targeting here is based on them. Google’s processing is done as an independent controller under its own policies:

Where required by law, the app shows Google’s User Messaging Platform consent form before ads are initialised, and records your choice. In the EEA and the UK you are asked about personalised advertising; in covered US states you are offered the opt-out required there. You can change your decision at any time from Settings → Advert privacy options, and if you decline, every feature of the app continues to work exactly as before.

Data we collect ourselves

None. We operate no servers, no accounts and no analytics. We have no database with your name in it, and no way to identify you or your device. We do not sell or share personal information, because we do not have any.

Permissions the app requests

That is all of them, and none is a permission Android stops to ask you about. The app requests no photo or media access, no storage permission, no media-location permission, no camera, no location, no microphone, no contacts and no notification permission. Nothing in it runs when the app is not in front of you: there are no notifications, no alarms and no background work.

A few more permissions are merged into the final app package by the libraries the app is built on, so the list Google Play shows you is slightly longer than the one above. They are the Android Ad Services permissions plus wake-lock and foreground-service, all from the Google Mobile Ads SDK. None is a permission Android stops to ask you about, and none is used by any code we wrote.

Children

This app is not directed at children under 13 and is not designed for use under the COPPA framework. We do not knowingly collect personal information from children — as described above, we hold no personal data at all.

Your choices

Changes to this policy

If we change this policy we will update the Last updated date above and publish the new version at this URL. Material changes will also be noted in the app’s release notes on Google Play. This policy is versioned publicly in the Dash Fusion privacy repository, so any change is visible in its history.

Contact

Questions about this policy or about the app: dash.fusion@outlook.com