SwiPik processes permitted photos and videos locally on your device. We do not operate a developer media or account server.
Only if you separately opt in in SwiPik, Meta App Events sends app-install and app-open information, device and advertising identifiers, and network information to Meta to measure and optimize Facebook and Instagram ads. SwiPik does not send media content, filenames, album names, swipe directions, cleanup details, or custom Meta events. See Meta’s Privacy Policy. This measurement is off by default, has its own Allow / Not now choice, and can be disabled at any time with the Facebook and Instagram ad measurement switch in Settings. It is separate from Google UMP consent and is not personalized-ads consent.
Google services are governed by Google’s Privacy Policy. You can change local permissions, consent, advertising ID, and app data in Android settings.
Your media and app preferences remain on your device. You can delete media with Android controls, clear SwiPik app data, or uninstall the app. For privacy questions or help with deletion, contact leco@lecostudio.dev.
SwiPik accesses only the photos and videos the user permits, including through iOS Limited Photos access. To provide its organization features, the app may use Apple PhotoKit to read photos and videos, creation dates, favorite status, and album membership, and may change favorite, album, or deletion state only after the user confirms their choices.
If an original exists only in iCloud, iOS may download it to the device through Apple Photos. This transfer is between Apple's photo service and the device; it is not an upload to a media server operated by LECO Studio.
Temporary files, hashes, scan caches, and recovery journals used for duplicate or similarity analysis are processed in the app's local sandbox. Temporary exports are removed after comparison. SwiPik analytics events do not contain the photos or videos themselves, filenames, album names, PhotoKit identifiers, or user-authored free text.
The iOS app uses Firebase Analytics to understand app quality and product flows. Firebase may process an app-instance identifier, app/device/operating-system information, app launches and sessions, approximate region inferred from an IP address, interactions, and purchase-related events.
SwiPik's custom events are limited to predefined categories and aggregate values such as onboarding stages, feature categories, permission state, item counts and processing time, advertising stages, and purchase stages. SwiPik does not set a Firebase Analytics user ID. Its Firebase configuration disables IDFV collection and default ad-personalization signals. Photo or album identifiers and StoreKit transaction identifiers are not sent as custom event parameters.
Google Mobile Ads is available only to free users whose premium status has been confirmed. The app first obtains consent information through Google's User Messaging Platform (UMP). It initializes the advertising SDK and requests banner or rewarded ads only when UMP reports that ads may be requested. Where UMP requires privacy options to remain available, the user can reopen them from the app's settings.
This iOS release does not request App Tracking Transparency (ATT) permission and does not include an ATT usage-description string. It also disables the Google Mobile Ads publisher first-party ID and personalized-ad signals before SDK initialization. The app therefore does not obtain permission to access the IDFA; without permission, iOS returns an all-zero IDFA value.
These settings do not mean that the Google advertising and consent SDKs process no information. When consent information is updated or an ad is requested, Google SDKs may process approximate region inferred from IP address, device- or app-instance-related identifiers, ad impressions/interactions/revenue information, product interactions, and crash, performance, or other diagnostic information. The exact processing may vary with the user's consent choices, region, Google SDK and advertising-account settings, and the ad actually served.
Apple StoreKit and the App Store process payment, transactions, and restoration for the lifetime premium entitlement. SwiPik checks the verified non-consumable entitlement and pending state on device and does not operate a separate payment server or SwiPik user account. The current StoreKit 2 implementation does not call Firebase Analytics.logTransaction. SwiPik custom analytics records only closed purchase-stage categories and does not include product IDs, prices, or StoreKit transaction identifiers.
App settings, scan caches, and recovery journals are stored locally and can be removed by deleting the app or its app data. Changes already applied to the photo library follow Apple Photos behavior. Directly deleted items follow the Apple Photos Recently Deleted policy; items staged in a SwiPik deletion album remain subject to that album and the user's later actions.
Google policies and the available consent controls may apply to retention and deletion choices for advertising and analytics data. For questions about iOS privacy, contact leco@lecostudio.dev.