01
Data Processed Locally (On-Device)
The App is designed to process your data locally. We do not operate user accounts, and we do not host a central database of your personal information.
- Image Metadata: When you grant permission, the App reads EXIF metadata (camera settings, GPS coordinates, timestamps, thumbnails) from your photos. This data is processed in your device's memory and is never uploaded to our servers.
- EXIF Editing & Stripping: When you edit or strip EXIF tags, the modified image is written back to your device storage only. No photo data is sent to any server.
- Bulk Processing: When processing multiple images at once, all EXIF reading, editing, and stripping is performed locally on your device.
- Export (CSV / JSON): Metadata exports are generated as local files in your device's temporary directory and are shared only when you explicitly choose to share or save them. We do not transmit export files to any server.
- Sharing Intent: The App can receive images shared from other apps (via the Android share sheet or iOS "Open In"). Received files are processed entirely on-device and are never uploaded.
- Recent Files: We maintain a local list of up to 10 recently opened file paths using a local database (Hive) to help you quickly access files. This stays on your device.
- App Preferences: Your theme selection (System / Light / Dark) and "Rate App" status are stored locally via Hive.
02
Information Collected by Third Parties
To provide functionality and monetize the App, we use third-party SDKs that may collect data:
- Google AdMob: We display banner, interstitial, and rewarded ads. AdMob may collect and use device identifiers (such as Android Advertising ID or iOS IDFA) to personalize ads and analyze ad performance.
- Firebase Analytics: We use Firebase Analytics to understand how the App is used. Events are logged anonymously — they contain numerical counts and feature flags but never your photo content or Personally Identifiable Information (PII).
- Firebase Crashlytics: Crash reports (including device model, OS version, app version, and a stack trace) are sent to Firebase Crashlytics to help us fix bugs. No photo data or PII is included in crash reports.
- Firebase Remote Config: We use Remote Config to deliver app configuration values without requiring an app update. No personal data is collected by this service.
- Firebase Cloud Messaging (FCM): We use FCM to send push notifications. Firebase assigns your device an FCM registration token — a pseudonymous device identifier. We do not link your FCM token to any personally identifiable information.
- OpenStreetMap: When you view a photo's GPS location, the App fetches map tiles from OpenStreetMap servers. These requests include geographic coordinates from the photo's EXIF data but contain no user-identifiable information.
03
Permissions Requested
| Permission |
Platform |
Purpose |
READ_MEDIA_IMAGES / READ_EXTERNAL_STORAGE (API ≤ 32) | Android | Access images from gallery for viewing and editing metadata |
WRITE_EXTERNAL_STORAGE (API ≤ 29) | Android | Save edited images back to device storage |
ACCESS_MEDIA_LOCATION | Android | Extract GPS coordinates embedded in photo files |
INTERNET / ACCESS_NETWORK_STATE | Android | Load map tiles and deliver advertisements |
NSPhotoLibraryUsageDescription | iOS | Access photos for reading and editing metadata |
NSLocationWhenInUseUsageDescription | iOS | Display GPS coordinates embedded in photo files |
| Notification Permission | Both | Receive push notifications from the App |
Important: We do not track your live device location. The location permission is used solely to read GPS coordinates that are already embedded inside the photo file's EXIF data.
04
Data Retention
Since we do not upload your images or metadata to a server, we do not retain your personal files. Specific retention policies for third-party data:
- Analytics & Crashlytics: Anonymous event data and crash reports are retained by Google/Firebase according to their standard retention policies.
- FCM Token: Your FCM registration token is managed by Google Firebase. Tokens are rotated by Firebase and are not stored in any backend database owned by us.
- Local App Data: All local data (recent files list, preferences, rate-app status) can be deleted by clearing the App's cache/storage or uninstalling the App.
05
Children's Privacy (COPPA)
Exif Tool is not directed at children under the age of 13. We do not knowingly collect personal information from children. If we become aware that a child has provided us with personal information, we will delete it immediately.
06
Your Rights & Opt-Out
- Personalized Ads: You can opt out of interest-based advertising in your device settings (Android: "Opt out of Ads Personalization"; iOS: "Allow Apps to Request to Track").
- Push Notifications: You can disable push notifications at any time in your device's system settings (Settings → Notifications → Exif Tool).
- Data Access & Deletion: Since all user-specific data is stored locally on your device, you can delete it by clearing the App's cache/storage or uninstalling the App.
- Firebase Analytics Opt-Out: On Android, you can opt out of personalized advertising via Google's settings, which also limits some analytics collection.
07
Third-Party Privacy Links