SafeShare Privacy Policy

Last reviewed: August 9, 2026

This policy explains how the SafeShare mobile app, provided by AICleanify, handles photos, files and metadata. It applies to the app identified by package com.aicleanify.safeshare; the separate AICleanify website privacy policy covers the main website.

App: SafeShare
Developer: AICleanify
App ID: com.aicleanify.safeshare
Privacy contact: support@aicleanify.com

What SafeShare accesses

SafeShare accesses only the photos or files you choose through a system picker. It reads the file bytes and supported embedded metadata needed to inspect or clean the item, including location, device and camera details, timestamps, EXIF/TIFF fields, XMP, IPTC, color/orientation data and recognized Content Credential containers. During a task, it also creates local technical values such as the source filename or provider reference, file size, a SHA-256 file hash, task path, status and validation result. An output filename is derived from a sanitized form of the source name plus the first eight characters of that hash.

Why the app uses that data

The selected content is used to show privacy findings, apply the cleaning and output choices you request, create a new copy, and re-read that copy to check supported requested changes. SafeShare does not open your selected original for writing.

What can remain in or be added to an output

SafeShare removes or changes supported metadata according to the options you select; it does not promise that an output contains no metadata. Orientation, color-profile information and recognized Content Credential containers can be preserved. Content Credentials are preserved by default. SafeShare does not cryptographically validate a C2PA manifest, signature, certificate, issuer or trust status; it checks recognized container bytes. A separate opt-in advanced output profile can add generated timestamps, camera or device fields, built-in virtual GPS coordinates and software tags. Post-write checking confirms recognized requested behavior, not anonymity or the absence of every hidden signal.

Local processing, collection and sharing

Selection, parsing, inspection, rewriting, optional encoding and post-write checking run on the device. SafeShare does not upload images or metadata to AICleanify, and the Android source audited for this policy does not include app analytics, advertising SDKs or image-content telemetry. Its Android main/release source manifest does not request INTERNET permission. When you deliberately open the system share sheet or save to Photos, the completed output is handed to the app or system library you choose; that recipient then handles the copy under its own terms.

Google Play Data safety summary

Based on the source audited for this policy, SafeShare does not collect user data for Google Play’s Data safety form because the app does not transmit selected content or app activity off the device. It also does not share user data for that form: the only transfers are the specific save or share actions you deliberately initiate to a destination you choose. These statements must be rechecked against the signed app bundle and every active Google Play version. Read the plain-language Data Safety page for the current summary.

Temporary files, saved outputs and deletion

SafeShare streams a selected item into a task-owned copy in application cache. Rejected imports, partial outputs and failed outputs are removed when possible, completed task files are cleared when the task ends, and abandoned task directories are cleaned on the next launch. Cleanup is best effort: a failed deletion can remain until a later cleanup attempt, operating-system cache eviction, app-data clearing or uninstall. On Android, the app’s sharing integration can keep a temporary share copy in app cache until the next share, operating-system cache eviction, app-data clearing or uninstall. A copy you explicitly save to Photos remains in your system library until you delete it, and a copy sent through the share sheet is retained according to the destination you selected.

Saved preferences

After cleaning starts, SafeShare can store a versioned allowlist of cleaning, output and advanced-profile preferences on the device. It does not store selected photos, picker identifiers, task paths, hashes, metadata values or processing results in that preferences file. You can remove saved settings from SafeShare’s cleaning-options screen, clear app data or uninstall SafeShare through your operating system.

Permissions and provider-backed files

SafeShare uses platform photo and document pickers instead of broad Android storage access. Android saving uses scoped MediaStore. On iOS builds, selecting photos with full metadata can prompt for Photo Library access, while saving an output can prompt for add-only Photos access. A picker can materialize an iCloud, Google Drive or other provider-backed item before giving SafeShare a local reference. That provider interaction is controlled by the operating system and provider; SafeShare itself performs no network request. SafeShare can read embedded GPS fields present in a selected file, but it does not request your device’s live location or Android ACCESS_MEDIA_LOCATION permission, so the operating system may already redact location fields from a gallery-selected file.

Security

SafeShare limits processing to app-controlled temporary storage, uses platform-scoped file selection and saving, and checks supported requested metadata behavior before enabling save or share actions. The app does not add a separate at-rest encryption layer to task files. No software can promise absolute security, so keep originals or backups until you confirm that an output meets your needs.

Accounts and account deletion

SafeShare does not create user accounts or store account data. Because there is no SafeShare account, there is no account-deletion workflow. Local app data can be removed through your device settings or by uninstalling the app; saved or shared copies must be removed from their destination separately.

Policy changes

If SafeShare’s data practices materially change, this public policy and the Google Play Data safety answers must be updated to match the released app. The review date at the top identifies the current policy version.

Privacy contact

For a SafeShare privacy question, email support@aicleanify.com or use SafeShare support. If you contact support, AICleanify receives the email address, message, device or diagnostic details, and any attachment you voluntarily provide so the support team can respond. Support email and the AICleanify contact form operate outside the SafeShare app and are covered by the separate AICleanify website privacy policy. You can also review the app-specific Data Safety summary and Terms of Use.