Version: September 29, 2026 · Applies to Duplicate Photo Cleaner AI
Scope
This privacy policy applies to the Android app “Duplicate Photo Cleaner AI” (package com.optipick.smart.gallery.cleaner, shown on your device as “OptiPick:AI Photo Manager”, called OptiPick on this site), published on Google Play by ITeddy. It explains what the app collects, why, who it is shared with, and how you can have it deleted. It matches the Data safety section of the app’s Google Play listing.
What stays on your device
Scanning, duplicate and lookalike detection, best-shot suggestions (including face detection with Google ML Kit), compression, format conversion and Secret Space all run on your device. The app never uploads your photos, videos, thumbnails, or photo metadata such as capture time and location to us or to any third party. Analytics events do not include file names or file paths as data fields. Error messages are different: a message from Android or a library can quote a file name or path. Scan-error analytics remove most of them before sending, but some may remain, and crash reports send the message as is (see “Crash logs” below). The list of installed apps that App Manager reads, with each app’s size and last-used time, also stays on your device. If you choose to share or export a file, for example from Secret Space, the app or storage service you pick receives it and handles it under its own privacy policy.
What we collect
The following data leaves the device to the services we use. Unless stated otherwise it is collected automatically and contains no name, email address or phone number.
- App interactions and other actions (Firebase Analytics): which screens you open and which features you use (such as scans, cleanups, compression, format conversion, app uninstalls, the paywall and onboarding), plus usage attributes — most recorded only as ranges or tiers (such as premium status, permission level, gallery size and device tier), a few as exact counts (such as how many times the in-app review flow has completed) — together with an app-instance ID, device model, OS version, language and country/region. None of this includes photo content or the names or package names of your installed apps, and file names and paths are not recorded as fields (see above for error messages). Storage figures are aggregate totals — some reported as ranges, some as exact byte counts, such as the total size a scan found or the space a cleanup freed — and are never tied to an individual file.
- Device or other IDs: the Firebase installation ID and app-instance ID, a Crashlytics installation ID, a random anonymous user ID generated by RevenueCat, a per-installation ID used by Google ML Kit, and the advertising ID. None of these identify you by name. The advertising ID is collected by Firebase Analytics solely to attribute app installs and in-app conversions, such as purchases, to our own Google Ads campaigns and to measure how those campaigns perform. It is never used to show ads (the app has none) or for personalised advertising. See “Your choices” for how it is handled in the EEA, the UK and Switzerland.
- Approximate location: Google Analytics derives an approximate location (city, region and country) from your IP address, and Firebase Remote Config reports your country so we can deliver the right pricing and feature settings. The app never requests location permission and never reads the location stored in your photos.
- Configuration requests (Firebase Remote Config): to deliver feature settings and pricing, the app reports country, language, time zone, platform, OS version and app version. Requests also include the Firebase installation ID, the app’s package name and the Remote Config SDK version, and, when available, Analytics user properties and the first-open time, which are used to target settings.
- Crash logs and diagnostics (Firebase Crashlytics): stack traces and exception messages, the last screen name, diagnostic log lines written by the app, and breadcrumbs of the screens and in-app events (with their parameters) from the session before a crash, together with the device model, OS version, app version and the Crashlytics and Firebase installation IDs, used to find and fix faults. An exception message from Android or a library can occasionally quote a file name or path.
- Purchase history (RevenueCat and Google Play Billing): which item you bought or subscribed to, when, its status, your entitlement status and which paywall entry point the purchase came from, used to unlock paid features and restore purchases. RevenueCat also receives the app-instance ID and forwards purchase and renewal events to our Google Analytics so they can be matched with usage statistics. Google Play handles payment; we never see your card or bank details.
- Feedback you choose to send (Firebase Cloud Firestore): when you submit feedback in the app, we upload the category you pick, the text you write, and your device model, manufacturer, OS version, app version and language and region setting, to help reproduce the issue; the record also holds the app’s package name and version code and a submission time set by the server. No logs are attached. The email field is optional: your email address is uploaded only if you enter it, so we can reply. Submitting feedback signs you in to Firebase anonymously, which creates a random ID stored with your message (our security rules require it). This is not an account, and Firebase Authentication records the IP address and user-agent of that sign-in request. If you also give your email address, it sits in the same record as that ID. None of this happens unless you submit feedback.
- ML Kit usage and performance metrics (Google ML Kit): face detection for best-shot suggestions runs entirely on your device, and your images and the detection results are never sent to Google. ML Kit itself sends Google metrics about how the feature runs: device information (manufacturer, model, OS version and build, and available machine-learning hardware accelerators), the app’s package name and version, a per-installation ID that is not intended to identify you or your device, API configuration (such as image format and resolution), feature input and output sizes, the feature version, performance metrics (such as latency), event types and error codes. Google uses these metrics to measure performance, debug, maintain and improve ML Kit, and detect misuse or abuse.
- Updates and reviews through Google Play (Google Play In-App Update and In-App Review): to check whether an update is available and how large it is, Google Play processes your device metadata, the app version and the list of installed modules. If you rate or review the app from the in-app prompt, Google Play receives your rating and review and publishes them on the Play Store; you can delete your review in Google Play. Google Play handles this data under its own terms and privacy policy.
How we use it
- Providing and maintaining app features, such as unlocking paid features, restoring purchases and enforcing free allowances.
- Measuring how features are used so we know what to improve.
- Finding and fixing crashes and faults.
- Measuring our own Google Ads campaigns by attributing app installs and in-app conversions, such as purchases, to them. The app itself shows no ads.
- Verifying purchases and preventing fraud and abuse.
- Replying to feedback you send.
Third-party services and sharing
We do not sell your personal information or share it with advertisers, and the app contains no advertising SDK. Firebase, RevenueCat and Google Play Billing act as our service providers and process data on our behalf under their own privacy policies. The advertising ID is collected through Google Analytics for Firebase and used, via our linked Google Ads account, only to measure our own campaigns. Analytics events are also exported to our own Google BigQuery project on Google Cloud for analysis. The usage and performance metrics sent by Google ML Kit never include your images or detection results; Google uses them under its own privacy policy to maintain and improve ML Kit.
- Firebase Analytics (usage statistics) ↗
- Google Cloud BigQuery (analytics export and analysis) ↗
- Firebase Crashlytics (crash reporting) ↗
- Firebase Remote Config (feature flags and remote settings) ↗
- Firebase Authentication (anonymous sign-in) ↗
- Firebase Cloud Firestore (cloud database) ↗
- Google ML Kit (on-device face detection; sends usage and performance metrics to Google) ↗
- RevenueCat (subscription and in-app purchase management) ↗
- Google Play Billing (payment processing) ↗
- Google Play In-App Review and In-App Update ↗
Permissions
- Photos and videos: to read your gallery for on-device scanning and sorting, and to delete only the items you confirm. Android 12 and below use the storage read permission instead, and Android 9 and below also need storage write access to delete.
- Media management (optional, Android 12 and above): once granted, batch deletions no longer need a system confirmation for every batch.
- Usage access (optional): lets App Manager show each installed app’s size and when you last used it, so you can decide what to uninstall. This list is read on the device and never uploaded.
- Uninstall apps: hands the uninstall request to the system, which always asks you to confirm.
- Network: for usage statistics, crash reporting, purchase verification, remote configuration and feedback you choose to send.
- Notifications (optional): show progress while compression or format conversion runs in the background; declining does not stop the task.
- Biometric unlock (optional): lets you open Secret Space with a biometric enrolled on your device, such as a fingerprint, through the system prompt. The system performs the check; the app never receives your biometric data.
- Google Play Billing: to buy a subscription or the one-time lifetime purchase through Google Play.
Retention and deletion
Uninstalling removes the app’s private data from your device (see “Your choices” for what stays) and stops further collection by the app. It does not cancel a subscription: Google Play and RevenueCat keep processing subscription events such as renewals, and RevenueCat keeps forwarding them to our Google Analytics.
How long server-side data is kept: Google Analytics keeps event-level data for 14 months (aggregated reports without identifiers are kept longer), and we keep the copy exported to BigQuery for as long as we need it for analysis; Crashlytics keeps crash reports for 90 days; feedback and the anonymous sign-in record created with it are kept until we delete them; Google Play and RevenueCat keep purchase records as required for billing and tax purposes.
What you can ask us to delete: feedback you submitted, together with its anonymous sign-in record. If you included your email address, we can find it by that address; if you did not, it is linked only to an anonymous ID that the app does not show, so tell us roughly when you sent it and what it said and we will search for it manually. Analytics and crash data are keyed to installation-level pseudonymous identifiers that carry no contact details, so we usually cannot find them from a request. If you bought a subscription or Premium, send us your Google Play order number: we can look up the linked app-instance ID in RevenueCat, delete the matching Google Analytics data and remove it from our BigQuery copy. Crash reports cannot be looked up this way and are deleted after 90 days.
To request deletion, email dola724gg@gmail.com and mention the app name “Duplicate Photo Cleaner AI”. We handle requests within 30 days. You can also reset or delete your advertising ID in system settings at any time.
Your choices
- Feedback is voluntary and the email field is optional; leave it blank and no email address is collected.
- You can reset or delete the advertising ID in system settings at any time; the app keeps working unchanged. Each time the app starts or returns to the foreground, it checks your mobile network and SIM country; if either is in the EEA, the UK or Switzerland, or neither is available, it sets Google’s advertising consent to “denied”, and while consent is denied the advertising ID is not collected.
- You can turn off “Use ML Kit face scoring” in the app’s Settings; scans started afterwards no longer run face detection, while a scan already in progress finishes with the setting it started with.
- Usage access and media management are optional and can be revoked in system settings at any time; only the related features stop working.
- Subscriptions can be managed or cancelled from the Subscriptions page in Google Play. The lifetime purchase is a one-time payment with no recurring charges; you can find it in your Google Play order history.
- Uninstalling removes the app’s private data, including scan caches, preferences and files still in Secret Space. Your original photos and any files you saved or exported to shared storage, such as compressed copies, stay on the device until you delete them.
Security
All network traffic uses HTTPS or an equivalent encrypted connection. We never store your photos, documents or payment details on servers of our own.
Children
The app is intended for a general adult audience and is not directed at children under 13. We do not knowingly collect personal information from children; if we learn we have done so, we delete it promptly.
Changes to this policy
Updates are published on this page with a new version date; material changes are also noted in the app’s release notes.
Contact
Developer: ITeddy. Email: dola724gg@gmail.com. Back to the app page