PixTally Privacy Policy

Effective date: September 21, 2026 · Last updated: October 23, 2026
Applies to the PixTally Android application and to the PixTally website.

In one sentence: your photos are processed only on your own device and are never uploaded — not by us, not by any third party. In the current version the only network traffic is anonymous usage and crash statistics via Firebase. Advertising (Google AdMob) and Pro purchases are planned for a future update and are not active in this version; this page already explains what those services will and will not be able to see, so nothing changes on you without notice.

1. Who we are (data controller)

This policy is issued by xiaoniubuniu, an individual developer and publisher of the PixTally Android application ("the App", "we"). For the on-device functionality of the App we act as data controller under the EU General Data Protection Regulation (GDPR), the UK GDPR and comparable laws; "personal data" and "personal information" follow the GDPR/UK GDPR and the California Consumer Privacy Act as amended by the CPRA ("CCPA") definitions. For advertising and purchase data, Google acts as an independent controller / service provider under its own privacy terms (see the links in §3).

Contact us any time by email: xiaoniubuniu@gmail.com

2. What we do not collect, and what our SDKs do

By ourselves: we operate no servers and collect nothing directly — no account, no email list. Usage statistics and crash reports are handled for us by Google Firebase, and only in the anonymous, aggregated form described below. Your photos, their metadata, your workflows, your history and your settings never leave the device and are never visible to any advertising, analytics or billing component; the image-processing engine is pure local computation.

The App is built on the following Google services. In the currently published version, only Firebase is active; the advertising and billing entries describe services that will be enabled in a future update, and this policy will be re-published (with the effective date updated) no later than that release. Each service processes the categories of data listed for it, on our behalf or as independent controllers:

  • Google Mobile Ads (AdMob) — (not active in this version) will deliver ads in the free version and may process: the Android advertising ID (GAID/AAID), device model, OS and app version, IP-address-derived approximate location (country/city level), and ad/launch interactions (impressions, clicks). It can influence which ads you see; nothing from your gallery ever enters this pipeline. See Google Privacy Policy and How Google uses information from sites or apps that use its services.
  • Firebase Analytics & Crashlytics — tells us which features are used and how the App crashes, so we can fix them. Analytics receives only the in-app events we define (e.g. which preset workflow was run, how many steps or images a batch had) plus standard parameters such as an installation identifier, device model, OS and app version, and country — never photo content, filenames, gallery paths or any contact detail. Crashlytics receives a crash stack trace and device context when the App quits unexpectedly. See Firebase Privacy Policy and Google Privacy Policy.
  • Google Play Billing — (not available in this version; Pro has no purchasing entry yet) will handle the Pro purchase: Google processes your payment details; we receive only purchase confirmation (product, order/purchase identifiers) to unlock Pro and restore purchases.
  • If further ad networks or mediation partners are enabled, this policy will be updated with their names, data categories and opt-out links before release.

3. Device permissions

PermissionPurposeNotes
INTERNET In this version: solely to send the anonymous usage/crash events described for Firebase. When the ad and billing versions ship, also to fetch ads and verify/restore the Pro purchase. The App transmits no image, filename, workflow or history content over the network. Nothing else in the App talks to the network.
Read photos
(READ_MEDIA_IMAGES;
READ_EXTERNAL_STORAGE on Android 12 and below)
Used only when you tap Repeat on a record in the History screen, to re-load the exact photos from that past run via the media URIs stored with the record. Requested lazily, after you explicitly trigger Repeat. Everyday image picking uses the system Photo Picker, which requires no permission at all. Declining this permission affects no other feature.

4. Legal basis (GDPR / UK GDPR)

For users in the EEA and UK:

  • Advertising (personalised ads and ad measurement, in versions where ads are enabled) will be shown only on the basis of consent (Art. 6(1)(a)), requested through Google's User Messaging Platform consent flow on first launch. Consent can be withdrawn or changed at any time in the App's settings and in Google's ad settings; declining consent still shows non-personalised ads.
  • Analytics and crash reporting (Firebase) is limited to anonymous product-usage events and stack traces; outside the EEA/UK it runs on the basis of our and Google's legitimate interest (Art. 6(1)(f)) in maintaining and improving the App. Where Google's consent flow covers analytics storage, that consent applies.
  • Purchase verification relies on Art. 6(1)(b) (performance of the contract you enter by buying Pro).
  • On-device processing of your own photos is performed entirely for you, on your device, under your control.

Elsewhere, once advertising is enabled, it will be delivered on the basis of the legitimate interests of Google and of us in monetising the free version, subject to the opt-outs in §6.

5. International data transfers

App feature data (photos, workflows, history) never leaves the device, so it is never transferred. Advertising, analytics/crash and purchase data processed by Google may be transferred to and processed in the United States and other countries, under Google's safeguards — the EU-U.S. Data Privacy Framework, Standard Contractual Clauses and the UK Extension — as described in Google's privacy terms.

6. Your rights and privacy controls

  • Access, rectification, erasure, portability, objection (GDPR/UK GDPR) — email us. Because we hold no server-side profile of you, we can only confirm the categories in §3; data we genuinely cannot link to you is also data we cannot disclose.
  • Delete local data — remove entries in the App, or uninstall it, which erases the App's private database immediately.
  • Opt out of personalised advertising (once ads are enabled) — turn on "Opt out of Ads Personalization" or reset the advertising ID under Android Settings → Google → Ads, or at myadcenter.google.com; EEA/UK users can also change consent in the App's settings. Buying Pro will remove all ads.
  • Firebase analytics and crash data — these events carry no name, email or photo content and are keyed only to a per-installation identifier, so they cannot be linked back to you personally; email us if you want usage data for your installation disregarded.
  • CCPA/CPRA (California) — we do not sell personal information for money. Under the CPRA, disclosure of the advertising ID to ad partners for cross-context behavioural advertising may qualify as "sharing"; you have the right to opt out, which the controls in the bullet above exercise, and we do not discriminate in price or service against you for doing so. The App does not knowingly "sell or share" personal information of consumers under 16.
  • Global Privacy Control / Do Not Track — this website runs no scripts and honours the absence of tracking by design; in the App, the ad personalisation toggle above is the equivalent control.

We respond to and fulfil valid requests within 30 days.

7. What is stored locally, and for how long

  • Output images: processed results are saved to the Pictures/ImageRecipe folder on your device, fully under your control;
  • App database: workflows, run history (including the media URIs referenced in §3) and preferences are kept in the app's private on-device database, which other apps cannot read;
  • Original photos: processing only ever reads your originals; it never modifies or deletes them.

Retention. Local data is retained until you delete it or uninstall the App. Advertising and purchase logs are retained by Google under its own retention practices. If you enabled Android's OS-level backup (the App allows allowBackup), your device vendor's backup service may store a copy of the app database in your personal cloud backup; that processing is governed by your OS vendor's privacy terms.

8. Cookies and similar technologies

This website is fully static. It sets no cookies, uses no local-storage scripts, no tracking pixels, no fingerprinting and no third-party requests (no web fonts, CDNs or analytics are loaded — all assets are self-hosted). Tracking technologies therefore appear only inside the App, via the Google SDKs described in §2.

9. Children's privacy

The App is a general-purpose utility, is not directed at children, and its ads are not configured for child-directed targeting. It collects no personal information from anyone under 13 as required by the U.S. COPPA. In the EU/UK, in line with GDPR Article 8, users under 14 (or the applicable local threshold, up to 16) should use the App only under parental guidance. Teen accounts on Google Play receive age-appropriate ad settings enforced by Google.

10. Changes to this policy

If this policy changes, this page will be updated and the dates above revised; material changes (for example new SDKs or ad partners) will also be announced in the app's release notes.

11. Contact and data deletion requests

To exercise any right or ask any privacy question, contact the developer at xiaoniubuniu@gmail.com. Per Google Play's Data Deletion policy: uninstalling the App erases all app-held data; sideloaded installs and Pro purchase records can additionally be cleared by emailing the same address (purchases are managed by Google and refundable/cancellable through your Google Play account).