About PhotoCompact and contact
This policy applies to PhotoCompact version 1.1. Version 1.0 has no ads and is covered by our version 1.0 privacy policy. PhotoCompact is provided by Beijing Longtao Entertainment Culture Co. Ltd. For privacy questions or support, contact kim.jc.ren@gmail.com.
PhotoCompact 1.1 may display Google AdMob ads before saving. The three optional Firebase services below remain separate choices and are off by default. Image processing remains on your device.
Your images stay on your device
PhotoCompact compresses and resizes images on your device. It does not upload your selected photos or their image metadata to the developer or an image-processing server, and it does not require an app account. Images already on your device can be processed offline.
You choose an image through the system photo picker, Files, Paste, or drag and drop. The app receives that image to prepare a preview and processed copy. It does not request permission to browse your entire photo library. iCloud Photos and other file providers may download a selected image under their own settings and privacy policies.
Saving requests permission to add a new copy to Photos. The original is not modified or deleted. JPEG and PNG retain their selected format; saving a WebP result creates a PNG copy. Processed copies omit original EXIF, GPS, and XMP metadata. Photos may add its own information, such as the date added. Any cloud synchronization of your library is controlled by your photo service and settings.
Advertising and privacy choices
PhotoCompact may show an ad after you tap Save to Photos. Saving continues when the ad is closed. When no ad is available, saving proceeds directly. Images already on your device can still be processed and saved offline.
PhotoCompact requests non-personalized ads from Google AdMob and disables the publisher first-party identifier. It does not request access to Apple's advertising identifier or send your photos, filenames, file paths, or image metadata with ad requests. Non-personalized does not mean anonymous or no data collection.
Google's advertising and consent services may process device and app information, app-scoped identifiers, IP addresses and approximate location, ad impressions and interactions, and diagnostic or performance information. These uses support ad delivery, measurement, fraud prevention and service operation. Advertising data processing is separate from the three optional Firebase switches; turning those switches off does not stop advertising operations.
The app updates advertising consent information before requesting ads and shows required regional privacy messages. Where Google requires an ongoing privacy-options entry, you can reopen it at Help → Privacy & App Improvements → Ad Privacy Choices. Declining or withdrawing a choice does not stop local image processing or saving. Depending on your region and choices, ads may be limited or unavailable. The app requests non-personalized ads even when a consent form allows a broader choice.
Google may process advertising data outside your country. Advertising data retention follows Google's applicable services and policies; the Firebase retention periods below do not apply to AdMob. Read Google's Privacy Policy and Google's advertising information.
You can report an inappropriate ad using Report an Ad in Help, which opens an email for you to review and send. Please include the advertiser name and when you saw it, and remove personal information from any screenshot. Nothing is emailed automatically.
Three optional services
You can independently choose Crash Reports, Usage Statistics, and Updated Default Settings under Help → Privacy & App Improvements. Declining any or all of these services does not prevent image processing or saving. When all three choices have remained off, PhotoCompact does not initialize Firebase.
When you enable a service, Google processes the data needed to provide that service. Installation and app-instance identifiers are pseudonymous, not anonymous: they can associate reports or activity across sessions. PhotoCompact does not attach photo contents, filenames, file paths, dimensions, file sizes, or original image metadata to its custom reports or usage events.
Crash Reports
If enabled, Firebase Crashlytics receives crash stack traces, app and operating-system state, device information, timestamps, and associated identifiers so that we can diagnose reliability problems. PhotoCompact also reports limited categories of import, compression, and saving failures using fixed operation names and error codes, without forwarding original error messages. User cancellations are not reported as failures.
If Usage Statistics is also enabled, recent Analytics events can accompany a crash as an activity trail, and crash occurrence information can contribute to Analytics reports.
Crash reporting uses explicit pending-report submission. Previously enabled permission allows pending reports to be sent on a later launch while permission remains enabled. First-time opt-in discards earlier pending reports. Turning Crash Reports off stops new app-defined error reports and requests deletion of pending reports; the change takes full effect after restarting the app. A transfer already started cannot be recalled.
Usage Statistics
If enabled, Google Analytics for Firebase helps us understand feature usage. Custom events record successful imports, completed compressions, successful saves to Photos, and Help opens. The only optional custom event parameter is the image format: JPEG, PNG, WebP, AVIF, or HEIC.
The SDK can also collect automatic lifecycle and engagement events, app and device information, crash occurrence and advertising interaction events when applicable, and an app-instance identifier. Google Analytics can derive approximate geographic information from network information. PhotoCompact does not request precise location access or assign an account user ID.
PhotoCompact uses Analytics without advertising-identifier collection, disables vendor-identifier collection and automatic screen reporting, and keeps advertising storage, advertising user data, and advertising personalization consent denied. These optional Firebase reports are used for app improvements, separately from AdMob advertising.
Turning Usage Statistics off disables Analytics collection, denies Analytics storage consent, and resets local Analytics data. It does not automatically erase reports already received by Google.
Updated Default Settings
If enabled, Firebase Remote Config can download initial compression-quality and target-size settings for a future editing session. It uses a Firebase installation identifier and app/device configuration information, including locale, country code, time zone, and software version information. This service communicates with Google even when the other two choices are off.
Downloaded values are checked before use, and accepted defaults are cached on your device. Updates cannot replace settings in your current editing session. Turning the service off stops future refreshes and restores built-in defaults for the next session. A request already in progress may finish, but its result is ignored after you turn the service off.
Storage, retention, and deletion
PhotoCompact does not keep a persistent image-history library or server account. The selected image and processing results are used for the current app session. Backgrounding the app may leave that session in memory. iOS and file providers may manage temporary representations; the app also cleans up its own abandoned export files from older versions. Saved Photos copies remain until you delete them in Photos. Removing the app does not delete originals, saved copies, or cloud backups.
For Google Analytics, the current property settings retain event-level data for 2 months and user-level data for 14 months. The user retention period resets when new activity is received. These settings do not govern most aggregated standard reports, which may be retained longer.
According to Firebase, Crashlytics retains crash traces and associated identifiers for 90 days before beginning removal from live and backup systems. Remote Config installation identifiers are retained until a deletion request is made; removal from live and backup systems can take up to 180 days after that request.
When all optional services are turned off after use, PhotoCompact attempts to delete the Firebase installation registration after any outstanding settings request finishes. This needs a connection and can fail. It is separate from deleting uploaded Analytics or crash history.
For access or deletion requests, contact kim.jc.ren@gmail.com. Because reports use pseudonymous identifiers and there is no app account, an email address alone may not identify particular service records. We will explain what can be located and handle applicable requests through the available provider processes. You do not need to send personal photos to identify diagnostic data.
Service providers and international processing
Google processes optional-service data on its infrastructure and may process it outside your country. Availability in the US App Store does not mean all processing occurs only in the United States. Further details are available in Privacy and Security in Firebase (https://firebase.google.com/support/privacy) and Google Analytics data retention guidance (https://support.google.com/analytics/answer/7667196).
This support website is hosted using OpenAI Sites. When you visit it, the hosting service may handle ordinary connection information needed to deliver and protect the website. The site has no image-upload feature or embedded Firebase/Analytics scripts.
Support correspondence and your choices
If you email support, we receive your email address, message, and any attachments you deliberately send. We use them to answer and investigate your request. They are not sent automatically by the app. Correspondence is kept as needed to resolve the request and meet applicable recordkeeping obligations; you can request deletion using the same email address.
You choose each image and whether to save it. You can decline or revoke Photos add-only permission in iOS Settings. Processing remains available without that permission, but saving a new copy to Photos requires it. Cloud copies and backups are managed through their respective services.
We will update this policy if PhotoCompact’s data practices change. The three optional services remain separate choices.