Skip to SafeShare content
SafeShareby AICleanify Get the app
SafeShare Live on Google Play

Remove photo metadata before you share.

Inspect hidden EXIF, GPS location, device details, timestamps, XMP and IPTC on your phone—then create verified new copies without changing your originals.

Download SafeShare on Google Play
See the real workflow
  • No image uploads
  • No app analytics
  • Originals stay untouched
SafeShare home screen with Select photos, Choose from Files, and local processing controls.
Local from selection to verification
Parsing, cleaning, encoding and checks run on the device.
No release internet permission
The Android release manifest does not request INTERNET.
Task copies, not originals
SafeShare never opens the selected original for writing.
Explicit handoff
You choose when to open the share sheet or save to Photos.

The real SafeShare flow

Review the private trail first.

SafeShare turns hidden metadata into plain-language categories, gives you controls, then rechecks every new file against your choices before it is ready to share.

  1. Select

    Choose photos or files

    Use the system picker for a batch of up to 50 files, with a 10 MiB limit per file.

  2. Inspect

    Review privacy findings

    See which photos contain location, device identity, timestamps, other metadata, or Content Credential containers.

  3. Control

    Choose what to remove

    Safe defaults remove private categories while orientation and color profiles remain preserved by default.

  4. Verify

    Create checked new copies

    Each completed output is re-read and compared with the requested policy before it can count as a success.

  5. Share

    Save or hand off

    Send verified outputs to the platform share sheet or save copies to Photos. Your selected originals remain unchanged.

Every screen below comes from SafeShare’s current approved 393 × 852 device gallery.

Screen 1 of 4

See what SafeShare finds and cleans.

Privacy findings are grouped by what they can reveal—not buried in a technical tag dump.

Found before cleaning
  • LocationGPS, altitude, direction
  • Device & cameraMake, model, lens, serials
  • Date & timeCapture and edit timestamps
  • Other metadataSoftware, XMP, IPTC, workflow fields
After verified cleaning
  • Chosen private fields removedRechecked against your cleaning choices
  • Color handled deliberatelyICC profiles preserved by default
  • Original remains untouchedOnly a new output copy is shared
SafeShare Cleaning options screen with privacy, provenance, metadata, size reduction, and format controls.

Privacy defaults. Clear output controls.

SafeShare starts with location, device identity, timestamps and other private metadata selected for removal. Optional output settings are separate and clearly labeled.

Content Credentials stay separate

Recognized C2PA container bytes are preserved by default. SafeShare reports “preserved · not cryptographically verified” and never calls that proof of validity.

Compression is opt-in

A percentage size target forces JPEG output. The app reports the physical before-and-after totals, including honest file growth when it happens.

Advanced metadata is not privacy cleaning

Optional camera, timestamp, virtual GPS and software fields live in a distinct three-step output flow and force JPEG re-encoding.

  • Keep original
  • JPEG
  • PNG
  • Lossless WebP
  • TIFF
  • BMP
  • GIF

Formats SafeShare actually supports.

SafeShare checks the file signature, structure and extension before metadata inspection.

Metadata-only Keep original path

JPEG · PNG · WebP · GIF

Inspect and remove supported metadata without rewriting encoded image data when you keep the original format.

Re-encode required

Classic TIFF · BMP

Accepted for inspection and cleaning, but their container structure does not support SafeShare’s metadata-only rewrite path.

Rejected before cleaning

BigTIFF · HEIC/HEIF · AVIF

Not accepted by the current workflow. Unknown, malformed and extension/signature-mismatched files also fail with a per-file reason.

50
files per picker request
10 MiB
maximum per selected file
24 MP
re-encode ceiling
32 MiB
encoded output ceiling

Why on-device matters.

Photo privacy is easier to reason about when the cleaning engine does not need a server.

  • No image-content telemetry. SafeShare does not use app analytics or upload image content.
  • No broad storage access. Platform pickers grant access to the files you choose.
  • Local task lifecycle. Imports and unsaved outputs live in non-backed-up app cache and are cleared when the task ends.
  • Provider boundary disclosed. A system picker may fetch an iCloud or Google Drive item before handing SafeShare a local file; the app itself makes no network request.
Read the SafeShare privacy details

Built for a reviewable privacy workflow.

Different tools solve different jobs. SafeShare is designed for people who want inspection, controls and verification before sharing.

Comparison of SafeShare, built-in gallery sharing, and upload-based web cleaners
ApproachProcessing boundaryReview & controlsBest fit
SafeShareOn the mobile deviceCategory review, batch controls, output policy and post-write verificationRepeatable privacy checks before save or share
Built-in gallery sharingVaries by device and gallery appCapabilities vary; some offer a location-sharing toggleQuick, device-native sharing
Upload-based web cleanerA remote service receives the selected fileInspection, formats and retention vary by serviceBrowser convenience without an app install

SafeShare support when you need it.

Get help with a file, review app privacy details, or contact the team responsible for SafeShare.

App help

Describe the device, file format, and step where you need help. Do not attach a private photo unless support asks for a safe sample.

Open SafeShare support

Privacy questions

Review exactly what the app accesses, what stays local, how temporary files are removed, and what sharing hands off.

Privacy Policy Data safety

SafeShare questions, answered plainly.

Still need help? Open SafeShare support.

Where can I download SafeShare?

SafeShare is live on Google Play. Use any Download SafeShare link on this page to open the official listing for com.aicleanify.safeshare. The Google Play app requires Android 10 or later.

Does SafeShare upload my photos?

No. Selection, inspection, cleaning, encoding and post-write verification run locally. SafeShare does not upload images, use analytics or send image-content telemetry.

Does SafeShare change my original photos?

No. SafeShare works from a task-owned copy and never opens the selected original for writing. Save and share actions use verified new output copies.

Which image formats does SafeShare support?

SafeShare accepts JPEG, PNG, WebP, GIF, classic TIFF and BMP. JPEG, PNG, WebP and GIF support metadata-only Keep original cleaning; TIFF and BMP require re-encoding. BigTIFF, HEIC, HEIF and AVIF are not accepted by the current workflow.

Can SafeShare remove GPS location and camera details in a batch?

Yes. A picker request accepts up to 50 files, with a 10 MiB limit per file. SafeShare groups location, device identity, timestamps and other metadata so you can review and clean the batch.

Does “preserved” mean Content Credentials are valid?

No. SafeShare can preserve detected physical Content Credential container bytes and verify byte equality after writing, but it does not cryptographically validate C2PA manifests, signatures, certificates or trust status.

Can SafeShare add metadata as well as remove it?

Yes, through a separate opt-in advanced output flow. Those controls can add camera, timestamp, virtual GPS and software fields, force JPEG output and are explicitly labeled as output metadata rather than privacy-cleaning controls.

SafeShare app icon

Share the photo. Keep the private trail on your phone.

SafeShare is live on Google Play. Download it and start with a privacy review before your next photo handoff.

Download SafeShare on Google Play