ImagePress – Local & Private
Last updated: October 29, 2026
ImagePress processes images on your device. The app has no developer account system or developer-operated server and integrates no advertising, cross-app tracking or developer usage analytics service. Purchases, access verification and credit synchronization use Apple services, so the app is not entirely offline.
Compression and preview take place locally. The app does not upload originals or results to a developer server or store images in the credit ledger. When you choose system sharing, a cloud file provider or saving to a library with system cloud sync enabled, the corresponding system or service may transfer files as you choose.
Photos read access is used for selection, scanning and original-image editing or deletion you request. Saving new photos requests add access when needed. File import and local history viewing do not require Photos read access. Manage limited access or change permissions in iOS Settings.
The app sandbox holds settings, custom templates, task history, compressed files and a cache of verified local access. History may include dates, modes, parameters, filenames, per-image status, sizes and local result references; older records may contain only a summary.
To prevent duplicate settlement or loss of generated results after interrupted purchase or credit confirmation, the app also stores recovery journals and result copies protected by system file protection. A journal may include task and result information, filenames, local result paths and original-image association identifiers. These are used locally for recovery and image operations you choose, and are not uploaded with the credit ledger.
Apple handles App Store purchases, payment and restoration. The app reads verified transaction and original-purchase information, such as transaction IDs, product IDs, purchase, expiry and revocation dates, quantity, store environment and wallet-binding tokens, to determine original paid-download, subscription, pass, lifetime or credit access. The app does not receive your payment card number, banking details or Apple account password.
When you buy, use, sync or restore credits, the app uses your iCloud private database for the records needed to manage transactions and credits: transaction and product IDs, relevant dates and transaction status, quantity, store environment, wallet-binding tokens, virtual balances, random task and reservation IDs, hashed image-usage identifiers and debit records. These records are used only for balance synchronization, recovery and preventing duplicate grants or charges, not for advertising, tracking or analytics.
The private ledger contains no images, original PHAsset identifiers, filenames or image file paths. It is stored in your own iCloud private database, not in a public or shared database for this app, and no developer-operated server receives it. Hashed usage identifiers prevent duplicate charges; hashing does not make account-linked wallet records anonymous.
The credit wallet requires iOS 16 or later and a verifiable original App Store purchase identity. Restore credits using the same iCloud account and App Store purchase account used to buy them. Pro and original paid-download lifetime access do not depend on iCloud sign-in. Pro purchases and restoration of verified original paid-download access remain available on iOS 15.6. Purchase verification and restoration may still contact Apple. Account changes or an unconfirmed cloud write may require another sync. A failed read must not be treated as an empty balance and overwrite the ledger.
Image encoding is local, but Apple purchase verification and restoration, credit ledger synchronization, iCloud original-image downloads, cloud file providers and sharing you select may use network or cellular data. Apple services and system backups follow your system settings and Apple's privacy practices.
Local processing uses Apple ImageIO, CoreGraphics and PhotoKit and components including OxiPNG, ExoQuant and Leptonica; these do not send images to the developer. The app does not automatically send developer analytics or crash reports and does not use advertising identifiers for tracking. Diagnostics you allow the system to provide to Apple are managed by Apple.
The app can remove GPS, EXIF and some PNG metadata. Format support varies, and some system processing paths may not remove every non-image field. Check the actual result before sharing sensitive images.
Delete templates in the template screen and manage exported images in Photos or Files. Deleting the app and its data clears sandbox history, results, access caches and local recovery copies. Whether system backups retain that data depends on your system settings.
Deleting the app does not cancel Apple subscriptions or automatically delete the private iCloud credit ledger. The cloud ledger retains balances and records preventing duplicate settlement; it contains no images and cannot restore deleted local results. Use Apple's iCloud data-management controls to manage cloud data. Deleting the cloud ledger may make remaining credits impossible to reconstruct from finished consumable purchase records. Contact support if you need assistance.
When you choose to email Contact Us in Settings, your email provider delivers the message, contact details and attachments you select to the developer, solely to handle that request. You do not need to send unrelated images or personal information. Do not send Apple account passwords or payment card information.
For Apple's handling of its services, see Apple's Privacy Policy: https://www.apple.com/legal/privacy/ . Contact support in Settings with questions about this app's privacy practices.