Phumble: Photo Swipe Cleaner
Privacy Policy
Last updated:
Your gallery media is processed on your device. Phumble uses the photo and video access you grant to review media, create local suggestions, and ask the operating system to delete only the items you confirm.
1. Scope and operator
This policy describes Phumble: Photo Swipe Cleaner, provided by the developer identified in the app's store listing ("we", "us", or "our"). It covers the mobile app and support correspondence you choose to send. Contact sm.labs@rediffmail.com with privacy questions.
The current app has no developer account system, developer backend, advertising, or purchases. We do not sell gallery information or use it for advertising. Google MediaPipe Tasks sends performance and utilization metrics on iOS and Android, and the Android Google ML Kit SDK collects limited technical diagnostics and usage metrics, as described in Section 5.
2. Gallery access and permissions
Phumble: Photo Swipe Cleaner asks your operating system for permission to read photos and videos because reviewing and cleaning a media library is the app's core purpose. Depending on your device, you can grant access to the full library, selected items, or no items. The app works only with media the operating system makes available under your choice.
You can change or revoke gallery access in system settings. Limited access produces limited counts and results. On Android, broad photo and video access supports repeated gallery review; on supported versions you may instead grant selected-media access, with reduced coverage.
3. Information processed on your device
The app reads gallery identifiers and media metadata such as media type, creation time, dimensions, duration, size when available, filename, album or folder hints, favorite state, and modification information. It creates temporary thumbnails and uses local media references where needed to show media smoothly.
Swipe choices, the review queue, deletion outcomes, settings, scan progress, and derived analysis records are stored in the app's private local database. Derived photo records can include a cryptographic file hash, perceptual hash, color statistics, a general image embedding, and duplicate or similarity groups. These values help compare photos; they are not uploaded to us.
Face categorization detects whether a face may be present and can store a local present, absent, or unknown result and a count. It does not identify people, compare identities, store face rectangles, or create a face-recognition profile. Source labels use system media types and metadata hints, such as screenshot, screen recording, camera folder, or download folder; a folder hint is not proof of who created or sent a file.
Analysis uses bundled on-device components. It does not fetch cloud-only originals for hashing, similarity, or face analysis, so unavailable items can be skipped or marked unknown. The app does not send photos, videos, thumbnails, hashes, embeddings, classifications, face results, or review choices to us or a developer-operated server. Google states that MediaPipe Tasks processes its image inputs on the device and does not send those inputs to Google servers.
4. How media deletion works
Swiping or selecting an item only adds it to a local review queue. Nothing is deleted at that point. Before deletion, you can review the queue and remove items from it. The app then asks the operating system to delete the confirmed media, and the operating system may show its own confirmation.
A successful system deletion changes your photo library. Clearing app history, cache, analysis results, or the review queue does not delete original gallery media. We cannot remotely view, delete, restore, or recover your media.
5. Platforms and on-device libraries
The app uses operating-system photo-library APIs and bundled software libraries for its interface, local database, images, video, similarity analysis, and face-presence detection. The audited release does not include advertising, account, cloud-storage, or payment SDKs.
On Android, bundled Google ML Kit face detection performs detection on the device, but its SDK collects technical information for diagnostics and usage analytics. Google's current disclosure lists device information such as manufacturer, model, operating-system version, build, and available ML hardware; app package name and version; a per-installation identifier that is not intended to identify a user or physical device; performance metrics such as latency; API configuration such as image format and resolution; input and output sizes; feature version; event types; and error codes. Google says this data is encrypted in transit with HTTPS and is not transferred by ML Kit to third parties. See Google's ML Kit Android data disclosure. This technical collection does not include your photos, videos, thumbnails, hashes, embeddings, face-detection results, or review choices.
On iOS and Android, Google MediaPipe Tasks performs image-embedding input processing on the device and, according to Google's MediaPipe Privacy Notice, does not send those image inputs to Google servers. MediaPipe Tasks does send API performance and utilization metrics to Google. Google uses those metrics to measure performance and usage and to debug, maintain, and improve MediaPipe Tasks under Google's privacy policy.
Apple, Google, your device manufacturer, and any gallery or backup service you enable may separately process media, app downloads, diagnostics, backups, or deletion activity under their own terms and privacy policies. Those platform activities are outside our control and are not uploads performed by Phumble: Photo Swipe Cleaner to us.
6. Information you send for support
If you email us, we receive your email address, any name supplied by your email service, your message, and attachments you choose to include. We use them to respond and investigate your request. Do not send private photos, videos, passwords, or other sensitive information unless it is necessary and you intend us to receive it.
We keep support correspondence only for as long as needed to respond, maintain necessary support records, and meet applicable legal obligations. You may ask us to delete it. If an obligation requires us to retain part of a message, we will explain that when responding.
7. Retention and deletion
Local database records remain until the relevant in-app reset or clear action removes them, app storage is cleared, or the app and its data are deleted. Thumbnail and playback caches can be cleared in the app or evicted by the operating system. Current iOS and Android builds disable backup of the app's private local database. Your separate photo-library and device backups follow your platform settings.
To remove local app records without deleting gallery media, follow Data Deletion. To remove gallery media, use the app's review-and-confirm flow or your system gallery. Deleting the app does not itself delete photos or videos in the shared gallery.
We do not receive or maintain a user profile for Google ML Kit's Android SDK diagnostics or MediaPipe Tasks metrics and cannot retrieve or delete those records for you. Google controls their retention and applicable privacy choices under its policies.
8. Security and your choices
Local records use the app's private storage and device protections. No storage method is completely secure. Keep your device updated, use a device passcode, and review the final deletion selection carefully.
Depending on where you live, you may have rights concerning personal information we hold, such as support correspondence. Contact sm.labs@rediffmail.com to ask about access, correction, or deletion. Because the app has no user account or developer backend, we cannot retrieve local gallery or app records from your device.
9. This website
This policy describes the mobile app and support process. Visiting the website that hosts this page sends ordinary connection information to the website host. Website hosting logs, cookies, and any website services are separate from Phumble: Photo Swipe Cleaner's local gallery processing. Contact sm.labs@rediffmail.com with questions about this page.
10. Changes
We will update this policy and the date above if the app's data practices change. Accounts, developer cloud processing, additional analytics, advertising, or purchases would require this policy and the applicable store disclosures to be revised before release.