Original photos and thumbnails are not sent to or stored on a separate PicKip-operated server.
PRIVACY POLICY
PicKip
Privacy Policy
PicKip performs photo-cleanup work on your device whenever possible. It does not upload photo files to a server operated by the developer. Advertising is separate: Google Mobile Ads may process advertising and device-related data. This policy explains both parts of the app’s actual data flow.
Keep history, recent cleanup history, settings and similarity fingerprints remain in the app’s local storage.
AdMob may process IP addresses, device identifiers and other advertising-related data.
1. Scope
This Privacy Policy applies to the Android app PicKip, provided by the independent developer KangJung. PicKip does not offer sign-up, a developer-operated user account, a photo-storage server or photo cloud synchronization.
Google Play, Android, Google AdMob and external websites are governed by their own privacy policies.
2. Data the app accesses or handles
| Category | Examples | How it is used | Sent to developer server |
|---|---|---|---|
| Photos and media metadata | Photos and thumbnails you allow, asset identifiers, filenames, relative folders, dimensions, capture and modification times, favorite/trash state and file size | Read on-device to display and sort photos, compare similar photos, find exact filename matches and prepare final deletion review | No |
| Local app records | Identifiers of photos marked to keep, up to 30 recent cleanup sessions with date/count/size/source, language and cleanup settings | Stored in app-specific local storage | No |
| Similarity analysis data | Perceptual hash and average brightness calculated from a small thumbnail, asset identifier and modification time | Cached in an on-device SQLite database to reduce repeated analysis | No |
| Same-name search data | Exact full filename and related photo metadata | Grouped in memory during the scan; PicKip does not maintain a separate persistent filename history | No |
| Advertising and device data | IP address and approximate location inferred from it, app launches/taps and other interactions, diagnostic/performance data, advertising ID, app set ID and applicable device/account identifiers | May be handled automatically by Google Mobile Ads and consent tools for advertising, measurement, analytics and fraud prevention | May be sent to Google and advertising partners |
| Support inquiries | Your email address, message and anything you voluntarily attach | Used only when you email the developer for support or a privacy request | Handled through the email service |
Selected-photo access: When Android grants access to selected photos only, PicKip can use only those photos. You can revoke or change access at any time in Android app settings.
3. Why the data is used
- Show photos in sessions of 20, 50 or 100 and record Keep or deletion-candidate choices.
- Create similar-photo candidates using capture time and visual features.
- Group exact filename matches across different dates and folders for manual comparison.
- Show a final review and then invoke Android’s trash or deletion flow for photos you confirm.
- Avoid repeatedly showing kept photos and provide a local cleanup summary.
- Preserve settings, reduce repeated analysis and provide advertising/privacy controls.
- Answer support and privacy inquiries.
PicKip never deletes a photo automatically because it looks similar or has the same filename. You make the final choice and Android performs the system confirmation flow.
4. On-device processing and deletion
Similar photos
PicKip first narrows candidates using nearby capture times, then compares image features calculated from small thumbnails. A stored fingerprint is not an image from which the original photo can be reconstructed. Results are comparison candidates, not a byte-for-byte duplicate determination.
Same-name photos
PicKip reads exact full filenames from accessible photos and groups equal names. Equal filenames do not prove that image content or file bytes are identical, so the app also shows thumbnails, folder, dimensions, capture time and file size for your review.
Trash and permanent deletion
The default action is to move selected photos to the Android system trash. If you choose permanent deletion, the photos may bypass the trash. PicKip has no photo-recovery feature. Trash support and retention periods depend on your device and gallery app.
5. Advertising, consent and third parties
PicKip uses Google AdMob for top banner ads and Google’s User Messaging Platform (UMP) for applicable privacy choices. The app checks consent status before deciding whether ads can be requested. Where required, a privacy-options entry point is available in PicKip Settings.
Google states that the Google Mobile Ads SDK may automatically collect and share the following information for advertising, analytics and fraud prevention:
- IP address, which may be used to estimate general location.
- Product interactions such as app launches, taps and ad interactions.
- App and SDK diagnostic/performance information.
- Android advertising ID, app set ID and applicable device/account identifiers.
The exact processing may vary by region, consent state, Android settings, limited-ad settings and the configuration of Google or its ad technology providers. The developer does not provide original photos, thumbnails, keep history or cleanup history to Google for advertising.
6. International processing
Original photos and local cleanup records are not transferred to a developer-operated server. Advertising and consent requests, however, may send advertising-related data to servers operated by Google and advertising technology providers in countries where they maintain facilities. The actual countries and providers can vary by region, consent and ad configuration.
Google states that data sent by the Google Mobile Ads SDK is encrypted in transit using TLS. Retention and deletion of advertising data are governed by Google’s and the relevant provider’s policies and user controls.
7. Retention and deletion
| Information | Retention | How to remove it |
|---|---|---|
| Photos, thumbnails and photo metadata | Accessed from the device library only as needed; no server copy is kept by the developer | Revoke Android permission or manage the media in your gallery. PicKip has no developer-server copy |
| Keep history | Until you reset it, clear app data or uninstall PicKip | Use “Review kept photos again,” clear Android app data or uninstall |
| Cleanup history | Only the latest 30 sessions, until you clear it, clear app data or uninstall | Use the delete option in Cleanup history, clear app data or uninstall |
| Settings and similarity cache | Until app data is cleared or the app is uninstalled; cache entries may be replaced after a source photo changes | Clear Android app data or uninstall |
| Same-name scan results | Used in memory while scanning/displaying results; no separate persistent filename history | They disappear when the scan/page or app process ends |
| Support email | Up to one year after the inquiry is closed, unless longer retention is required for an active dispute or by law | Deleted after the retention purpose ends |
| Google advertising data | According to Google’s/provider policies, consent state and user settings | Use ad privacy controls, Android advertising-ID controls and the relevant provider request process |
Resetting local records does not delete or restore original photos. Conversely, deleting a photo in your gallery may not immediately remove every local cache entry; clearing app data or uninstalling PicKip removes all PicKip local data.
8. Your choices and controls
- Photo access: choose full, selected-photo or no access in Android settings and change it later.
- Keep history: reset it from PicKip Settings.
- Cleanup history: delete it from the Cleanup history screen.
- All local app data: clear PicKip storage in Android app info or uninstall the app.
- Advertising consent: where available, reopen “Ad privacy settings” in PicKip Settings.
- Advertising identifier: reset or delete the advertising ID in Android privacy/ads settings.
- Support information: email the address below to request access, correction or deletion.
PicKip creates no developer account, so there is no separate account-deletion or membership-cancellation process.
9. Security measures
- Photo cleanup and analysis take place on-device, without uploading originals to a developer server.
- The app relies on the Android sandbox and permission system and declares photo and internet access needed for its features.
- Photo removal requires a final review and Android system processing, not merely an in-app candidate choice.
- Google states that data sent by its Mobile Ads SDK is encrypted in transit with TLS.
- The developer does not intentionally include user photos or local identifiers in public repositories or support responses.
Device security, Android, gallery apps, Google and ad providers remain within the security responsibility of their respective operators.
10. Accounts and children’s data
PicKip does not ask for a name, date of birth or age through a sign-up flow and does not create a developer-operated user profile. The app is not designed to directly request separate personal records from children.
Parents and guardians can manage photo permission and advertising choices through device settings. The target-audience and families-policy settings shown on Google Play are governed by the store listing.
11. Changes to this policy
This policy may be updated when app features, SDKs, applicable law or Google Play policy change. Material changes will update the effective date on this page and, where appropriate, be communicated in the app or store listing.
First effective and current version: September 30, 2026
12. Privacy contact
For questions about this policy, PicKip’s data handling or a privacy request, contact:
Privacy contactKangJung
Emailaaggf1112@gmail.com