Privacy policy
Privacy, in plain language.
ImageFlow is built to help you process images on your Mac, not to
turn routine file work into a remote dashboard by default.
Summary
ImageFlow is designed for local image processing.
In the current app, image import, image processing, preview, and
export are designed to happen on your Mac. ImageFlow is not built
around uploading your image library to a developer-run server for
normal processing tasks.
What is not collected
No third-party analytics or crash-reporting SDK in the current app.
The current codebase does not bundle third-party analytics or
crash-reporting SDKs such as Firebase Analytics, Crashlytics, or Sentry.
The current app also does not implement a normal image-upload flow
to a developer server for processing your files.
Local storage
ImageFlow still stores some data locally on your device.
To work properly, the current app may store settings, templates,
recent directory choices, purchase state, and file or folder access
bookmarks on your Mac.
These local records help the app remember export destinations,
keep folder automation working, restore Workflow Pro state, and
support Finder-related handoff flows.
Permissions
Why file and folder access may be requested
Because of the macOS sandbox, ImageFlow cannot freely read or write
across your disk. The app only works with files and folders you
explicitly choose or authorize.
For repeat workflows, ImageFlow may keep security-scoped bookmarks
locally so the same authorized folders can still be used later for
export memory or folder automation.
Apple services
Workflow Pro purchases are handled through Apple StoreKit.
The current Workflow Pro unlock is a one-time in-app purchase
handled through Apple StoreKit. Restore-purchase behavior also uses Apple systems.
Some local purchase state may be stored on-device so the app can
keep your unlock state consistent.
System logging
Current logging is local system logging.
The current codebase uses Apple system logging APIs for local logs.
That is different from shipping your crash data to a third-party service.
Future changes
If data collection changes, this page should change first.
If a future version adds analytics, crash reporting, or other
third-party services, this policy should be updated to explain what
is collected, why it is collected, and who processes it.
Support contact
Questions about privacy
For privacy questions, contact
support@tryimageflow.com.
Policy date
Last updated
July 8, 2026