Current app data practices
SafeShare data safety
Last reviewed: August 11, 2026
This page summarizes the SafeShare Android source audited for package com.aicleanify.safeshare. Release builds collect limited technical app-performance data through Firebase Crashlytics but do not collect selected photos or their metadata and do not share user data for Google Play Data safety purposes. The signed app bundle and every active Play version must match these practices. User-directed save and share actions are explained below, and the complete store-facing notice is the SafeShare Privacy Policy.
- Collected by AICleanify
- Technical app dataCrash logs, diagnostics, limited session/app-interaction metrics and installation identifiers are collected through Firebase Crashlytics.
- Shared by AICleanify
- NoneOnly you can start a system save or share handoff.
- Accounts
- Not usedSafeShare has no sign-up, login or cloud profile.
- Ads & behavioral analytics
- Not includedNo advertising or Google Analytics SDK is included. Crashlytics is used only for app stability.
What “collected” means here
For the Google Play Data safety form, collection means transmitting user data off the device. SafeShare accesses the photos or files you deliberately select, but inspection, cleaning, encoding and verification remain local. Crashlytics separately sends limited technical app-performance data off the device, so SafeShare declares that collection even though photo processing remains local.
On-device photo and metadata processing
SafeShare reads selected file bytes and supported metadata to show findings and create the output you request. It does not upload photos, metadata, hashes, task paths or processing results to AICleanify. Selected originals are not opened for writing. Output names use a sanitized source basename plus the first eight characters of the locally calculated SHA-256 hash.
Output metadata is controlled, not promised to be empty
SafeShare removes or changes supported metadata according to your selected options. Orientation, color profiles and recognized Content Credential containers can remain; Content Credentials are preserved by default and are not cryptographically validated. A separate opt-in advanced profile can add generated timestamps, camera or device fields, built-in virtual GPS coordinates and software tags. Post-write checking covers recognized requested behavior and does not prove anonymity or that every possible metadata signal is absent.
User-directed save and share handoffs
Nothing is sent to another app until you choose Save to Photos or open the system share sheet. The completed output is then handed to the system library or recipient you select, and that destination handles its copy under its own terms. For Google Play Data safety, this specific user-initiated transfer to a destination you choose is excluded from developer sharing. A cloud-backed picker can also download an item before SafeShare receives a local reference; that provider interaction belongs to the operating system or provider, not SafeShare.
Retention and deletion
Task files live in app-controlled cache while a task is active. Failed, abandoned and completed task files are removed on a best-effort basis; a failed deletion can remain until a later cleanup, operating-system cache eviction, app-data clearing or uninstall. On Android, the app’s sharing integration can retain a temporary app-cache copy until the next share or another cache-cleanup event. A copy you explicitly save or share remains at its chosen destination until you delete it there. Saved preferences can be deleted inside SafeShare, by clearing app data or by uninstalling the app.
Firebase states that Crashlytics keeps crash traces and associated installation identifiers for 90 days before beginning removal from live and backup systems. SafeShare has no account and does not set a Crashlytics user ID, so the developer normally cannot associate a technical report with a particular person.
Permissions and network access
SafeShare uses system photo and document pickers instead of requesting broad Android photo-library or storage access. The audited Android main/release source manifest requests Internet and network-state access for Crashlytics and Firebase Sessions but does not request broad storage, media-location, live-device-location or Advertising ID permission. Android saves through scoped MediaStore only after you choose to save an output.
Accounts and deletion requests
SafeShare does not create accounts or keep server-side user profiles, so there is no SafeShare account to delete and no account-deletion URL is required for the current app. Local task data, destination copies and Crashlytics retention are described above. If account or data practices change in a future release, the app, Privacy Policy and Google Play declarations must be updated before release.
Keeping the Play declaration accurate
Google Play’s Data safety form must match every active SafeShare version and every included SDK. The signed Android App Bundle, merged manifest, dependencies and runtime behavior must be rechecked before each submission. This public summary does not replace the declaration submitted in Play Console.
Questions about SafeShare data
Email support@aicleanify.com, visit SafeShare support, or read the complete Privacy Policy and Terms of Use.