Cuka
Privacy Policy
Effective October 9, 2026
Cuka is designed to organize media without uploading your photo library to Cuka servers. This policy explains what the app processes.
1. Media and on-device analysis
Cuka may access photos, videos, Live Photos, metadata, and folders you explicitly authorize. Smart Score, people and expression signals, duplicate detection, similarity grouping, video frame analysis, and location grouping run on your device. Cuka does not upload your photo library to its own servers.
2. Local data
Indexes, thumbnails, analysis results, favorites for external sources, and cleanup records are stored on your device. External-source indexes are stored locally. Removing an external source removes Cuka’s authorization and local index, not the source files or its Cuka Trash contents.
3. Cloud and file providers
If an original exists only in iCloud Photos or a cloud-backed folder, Apple or your selected file provider may download it when needed. Their processing is governed by their policies.
4. Diagnostics
Cuka may use Apple MetricKit summaries for crashes, hangs, CPU, disk writes, and launch issues. Application logs are designed not to include photo identifiers, file paths, media metadata, full diagnostic payloads, or call stacks.
5. Purchases
In-app purchases are processed by Apple through StoreKit. Cuka receives purchase entitlement information but not your payment card details. Purchase records are handled under Apple’s policies.
6. Optional sharing rewards
We receive sharing reward submissions only when you voluntarily send an email to rewards@cuka.app. Only the notes, posts, screenshots, and contact details you choose to include in that email are sent to the Cuka team for reward review. The Cuka team reviews the submitted evidence to verify that shares are genuine. This optional workflow is separate from photo-library analysis.
7. Your choices
You control photo and folder permissions in system settings. You can delete Cuka’s local data by removing sources, rebuilding the local index, or deleting the app. Media moved to Cuka Trash remains recoverable until you empty that trash.
8. Changes and contact
We may update this policy as the product changes. Material changes will be reflected on this page. Questions or deletion requests for optional reward submissions can be sent to support@cuka.app.
Effective October 10, 2026
Cuka for Android is provided by Mitoo Tech LLC and is designed to organize media without uploading your photo library to Cuka servers. This policy explains what the Android app processes and when third-party services receive information.
1. Media and on-device analysis
Cuka may access photos, videos, Motion Photos, metadata, and folders you authorize. Smart Score, face and expression signals, duplicate detection, similarity grouping, video frame analysis, and location grouping run on your device for both the system photo library and external sources. Cuka does not upload your photo library to its own servers.
2. Permissions
Android media permissions determine which system photos and videos Cuka can read; selected-photo access is supported where Android provides it. You choose external folders, SD cards, and USB drives through the system file picker. Media-location permission lets Cuka read location already embedded in media for location displays and grouping; it does not grant access to your live device location. You can change media permissions in Android settings and remove folder access in Cuka. Denying or revoking access may limit the related features.
3. Local data
Indexes, thumbnails, analysis results, cleanup records, settings, and reward drafts are stored on your device. External-source favorites are saved as metadata in the selected folder so they remain available when you reconnect it or use another device; your file provider may sync or back up that folder. Removing an external source removes Cuka’s authorization and local index, not the source files, folder metadata, or its Cuka Trash contents. Android backup may copy app settings through your system backup provider. Media indexes, purchase caches, cleanup records, and reward drafts are excluded from Cuka’s configured cloud backup and device transfer.
4. Private Vault and sharing
Private Vault content is encrypted in app storage. Android’s configured device transfer may copy the encrypted Vault to a new device, where the recovery code is needed to unlock it and set a new PIN; Vault content is excluded from automatic cloud backup. You can export an encrypted backup to a location you choose. Cuka does not receive your Vault PIN, recovery code, or biometric data; optional biometric authentication is handled by Android. If you export or share media, the destination app or file provider receives the files you select under its own policies. Exported media may be unencrypted, and copies or backups outside Cuka remain until you remove them separately.
5. Cloud providers and maps
A cloud-backed folder or media provider may download originals when you access them; that provider’s policies apply. Location grouping uses on-device data. When you view a photo’s location map, Cuka requests map tiles from OpenStreetMap: the requested tiles reveal the displayed area, and the service receives your IP address and Cuka app version, but no photo or video. Opening a location in another map app passes the selected coordinates to that app. Those services handle requests under their own policies.
6. Diagnostics and Google ML Kit
Cuka’s local analysis timing logs are limited to debug builds and omit photo identifiers, file paths, and media metadata. The bundled Google ML Kit face-detection SDK processes images and results on your device, but sends SDK diagnostics and usage metrics to Google over HTTPS. These include device and app information, per-installation identifiers, performance, API configuration such as image format and resolution, input and output sizes, SDK version, event types, and error codes. ML Kit may also contact Google for updates and compatibility information. Google uses this data to operate, maintain, improve, and protect its SDK under Google’s Privacy Policy; images and detection results are not sent to Google by ML Kit.
7. Purchases
In-app purchases are processed by Google Play Billing. Cuka receives product, purchase-token, purchase-state, and entitlement information to verify and restore Pro access, but does not receive your payment card details. Google handles your account, payment, and purchase records under its policies.
8. Optional sharing rewards
We receive sharing reward submissions only when you voluntarily send an email to rewards@cuka.app. The notes, posts, links, screenshots, contact details, and locally generated application code included in that email are sent to the Cuka team for reward review. The code identifies the application and includes its platform, language, and creation time. The Cuka team reviews the evidence to verify that shares are genuine. This optional workflow is separate from photo-library analysis; preparing a draft does not upload it to Cuka.
9. Your choices and deletion
You control media access through Android settings and folder access through Cuka. You can remove sources or rebuild indexes to remove the corresponding local index data. Clearing app storage or uninstalling Cuka removes app-local data, including the local Vault, so keep an encrypted Vault backup and recovery code first. Original media in the system library or external folders, folder Cuka Trash, exported files, and separately saved backups are not deleted by removing the app. Cuka Trash items can be restored while their originals remain available, until you choose permanent deletion. Contact support@cuka.app for questions or deletion requests concerning optional reward submissions.
10. Changes and contact
We may update this policy as the product changes. Material changes will be reflected on this page with an updated effective date and communicated where required by law. For privacy questions, contact Mitoo Tech LLC at support@cuka.app.