PrunePic

Last updated: April 6, 2026

PrunePic is a photo-cleanup app that works primarily on-device through Apple’s Photos framework. We do not run our own server to upload, process, or store your photo library. This policy explains what data the app accesses, what stays local, and when data may be handled by Apple or third-party services used by the app.

Summary

• Your photos and videos are reviewed and organized through Apple’s Photos APIs on your device.
• We do not upload your photos or videos to our own servers.
• The app stores local app state on your device, including review history, pending trash state, recent albums, onboarding state, preferences, install date, and cleanup statistics.
• Purchases and subscription restoration are handled by Apple through StoreKit and the App Store.
• The current codebase includes Firebase Analytics and Mixpanel for product and monetization analytics. These analytics events are about app usage and purchase flow, not photo content.
• If your library uses iCloud Photos or other Apple cloud-backed storage, Apple may download or stream assets to your device when the app requests previews, video playback, or file-size information.

Data We Access

1. Photo library access

With your permission, PrunePic can access items in your Apple Photos library.

Depending on what you allow in iOS, the app may:

• read photo and video metadata needed to show and sort your library
• request preview images and video playback items
• estimate file sizes for cleanup statistics
• mark items as favorites
• create albums
• add items to albums
• remove items from albums
• delete custom albums
• delete photos or videos when you explicitly choose that action

If you grant limited photo access, PrunePic only works with the items you selected. If you grant full access, it can work across the accessible parts of your library.

2. Data stored locally on your device

The current app stores the following data locally in app storage on your device, including UserDefaults:

• review records keyed by Apple Photos local identifiers
• review decisions such as kept, trashed, or deleted
• review timestamps
• media category labels
• byte-count estimates when available
• pending trash state
• recent album identifiers
• cleanup statistics and event history used to build day, month, year, and lifetime views
• onboarding completion state
• sound-effect preference
• inferred install date

These records help the app remember what you already reviewed, track progress, and render stats. They are not the photo files themselves.

3. Purchase and subscription data

If you purchase or restore PrunePic Pro, Apple processes the transaction through StoreKit and the App Store. The app reads subscription and entitlement state from Apple so it can unlock premium features.

The current codebase does not implement a custom account system or a developer-operated subscription backend.

4. Analytics and product telemetry

The current codebase includes Firebase Analytics and Mixpanel SDKs.

Based on the app code, analytics events may include:

• onboarding step views and taps
• whether onboarding was completed or skipped
• selected cleanup-focus options from onboarding
• paywall views, presentations, and dismissals
• product-loading success or failure
• product IDs and tier IDs related to subscription offers
• purchase start, cancel, pending, success, and failure events
• restore-purchases start, success, and failure events
• paywall entry points and related feature names
• error messages related to monetization flows

Based on the current code, analytics events do not include:

• your photo files
• photo thumbnails
• your photo library local identifiers
• your pending trash queue
• your per-photo review history

Mixpanel automatic event tracking is disabled in code. Analytics services may still collect standard SDK/device/app metadata according to their own implementations and policies.

These analytics integrations only send data if they are configured in the build you install.

Components and Services Used

What Stays Local

PrunePic’s core cleanup flow is local-first:

• photo review happens against your Apple Photos library on device
• review-state tracking and cleanup stats are stored locally on device
• album creation and organization actions are performed through Apple’s local Photos library APIs

We do not operate our own server for photo cleanup, photo analysis, or photo storage.

What We Do Not Currently Request

Based on the current codebase, PrunePic does not request:

• location access
• contacts access
• microphone access
• camera capture access
• App Tracking Transparency permission

The current codebase also does not include an ad SDK.

iCloud Photos and Apple Services

If your Photos library uses iCloud Photos or other Apple cloud-backed storage, Apple may transfer asset data between iCloud and your device when PrunePic requests:

• preview images
• video playback items
• asset resource data used for file-size estimation

That transfer is handled by Apple’s frameworks, not by a PrunePic-operated backend.

Your Choices

• You can grant limited or full photo access, or revoke access, in iOS Settings.
• You can manage subscriptions, renewals, and purchase restoration through your Apple ID and App Store settings.
• You can stop using the app at any time.
• If you do not want analytics sent to third-party providers, the shipped build would need those integrations disabled or removed.

Data Retention

• Your photos and videos remain in your Apple Photos library unless you choose an action that changes them.
• Local app data remains on your device until you delete the app or the system removes its data.
• Analytics data, if enabled in your build, is retained by the relevant analytics provider under that provider’s own policy.
• Purchase records are retained by Apple under Apple’s own policies.

Contact

If you have privacy questions about PrunePic, contact:

• ebapps.customers+prunepic@gmail.com

Changes to This Policy

This policy should be updated whenever the app’s SDKs, data flows, permissions, or backend architecture change.