Privacy Policy

Effective date: 24 October 2026 · Applies to the BatchBooth app for iPhone

The short version

1. Who we are

BatchBooth is published by an independent developer (“the developer of BatchBooth”, “we”, “us”). This policy explains what the BatchBooth app for iPhone (“the app”) does with information about you. If anything here is unclear, email leojiahk@outlook.com.

2. Your photos and items

The app exists to process your item photos, and it does that entirely on your device:

Photo library permission

The app asks for access to your photo library and uses the wording below in the system prompt. You can change the permission at any time in iPhone Settings → Privacy & Security → Photos. If you grant limited or no access, the app copies the photos you pick into its own folder so it still works, but it cannot save exports to your library.

3. What we collect

The app uses the network for two jobs only: to verify purchases and subscriptions, and to collect anonymous usage statistics and crash reports. For the first it uses Apple’s StoreKit and RevenueCat, a subscription-management service operated by RevenueCat, Inc. (United States). For the second it uses Google Firebase (Google Analytics for Firebase, Firebase Crashlytics and Firebase Performance Monitoring), operated by Google LLC (United States). None of these services ever receives your photos, cutouts, item names or file names. Through them we collect exactly the following:

DataWhat it isWhyApp Store privacy label
Purchase history Which plan you bought (yearly, monthly or lifetime), whether a subscription is active or expired, whether you have used a free trial, and the Apple transaction identifiers needed to verify this. App functionality — unlocking what you paid for and restoring purchases on a new device.
Analytics — aggregate revenue and retention statistics that help us run the app.
Purchases → Purchase History
Product interaction Counts of what happens in the app: onboarding completed or skipped, photos imported, photos processed, exports completed (with the marketplaces chosen and the number of files), the paywall being shown and purchases completed, plus app opens and screen views recorded automatically by Firebase. It also includes one yes/no attribute, first_multi_platform_export, stored with RevenueCat. Analytics — understanding which features are used so we can improve them. Usage Data → Product Interaction
Device ID A random app-instance identifier created by Firebase when the app is first opened, and Apple’s identifier for vendor (IDFV). Not the advertising identifier (IDFA), which the app never accesses. Analytics — counting unique users and sessions without knowing who they are. Identifiers → Device ID
Approximate location A country or city-level location that Google Analytics derives from your IP address. The IP address itself is not stored by Google Analytics. The app never asks for access to your location. Analytics — knowing which countries the app is used in. Location → Coarse Location
Crash data When the app crashes: the stack trace, the app version, and the device model and iOS version. App functionality — finding and fixing crashes. Diagnostics → Crash Data
Performance data App start-up time, screen rendering, network request timing and memory or CPU use. App functionality — finding slow parts of the app. Diagnostics → Performance Data
Other diagnostic data Technical context sent with crash and performance reports, such as free disk space, memory, orientation and whether the app was in the foreground. App functionality — reproducing problems. Diagnostics → Other Diagnostic Data

Purchase data and the usage attribute are attached to a random, anonymous app user ID generated by RevenueCat on your device the first time the app runs; it is shown on the app’s Privacy screen (Settings → Privacy). Firebase data is attached to its own random app-instance ID. Neither ID is derived from your name, email, phone number or Apple ID, we never link them to you, and we never combine them with other data to identify you.

What we do not do

Statistics that stay on your phone

The app also keeps a few aggregate counters locally (for example, how many free photos you have used) to show you your remaining free allowance. Those counters stay on your device.

4. Third parties

Because RevenueCat and Google operate in the United States, this data may be processed outside the country you live in. Where EU, UK or similar data-protection law applies, such transfers rely on these providers’ standard contractual clauses and other safeguards.

We use no advertising networks, attribution or ad-measurement SDKs, or social-media plug-ins.

5. How long we keep data

6. Your rights

Depending on where you live (for example the EU/EEA, the United Kingdom, Switzerland, Brazil or California), you may have the right to access, correct, delete or receive a copy of the personal data we hold about you, to object to or restrict certain processing, and to lodge a complaint with your local data-protection authority. We honour these requests for everyone, wherever you live.

To exercise any of them, email leojiahk@outlook.com and include the anonymous ID shown on the app’s Privacy screen (Settings → Privacy), so we can find your record — it is the only way we can link a request to the data, since we hold nothing else that identifies you. Firebase statistics cannot be linked to that ID; to delete them, we delete the app’s analytics data on request or it expires as described above. We respond within 30 days. Requests about Apple’s own purchase records should go to Apple.

7. Children

BatchBooth is not directed at children under 13, and we do not knowingly collect personal data from them. If you believe a child has provided us with personal data, contact us and we will delete it.

8. Security

Your photos never leave your device, which removes most risk by design. The purchase, usage and diagnostic data that does leave is sent over encrypted connections (HTTPS) to Apple, RevenueCat and Google, and is never combined with information that could identify you.

9. Changes to this policy

If we change this policy we will update the effective date at the top of this page. For material changes we will also say so in the app’s release notes on the App Store. Continued use of the app after a change means you accept the updated policy.

10. Contact

Questions, requests or complaints: leojiahk@outlook.com.