TriggerSort is a private trail-camera photo organizer for iPhone. This policy explains what the app handles and the choices available to you.
Data collection and tracking
TriggerSort has no account system, advertising, or Ash Apps photo-processing server. Ash Apps does not receive your photos, photo metadata, classifications, labels, locations, notes, settings, or cleanup selections.
TriggerSort uses Superwall for subscription offers, purchases, restoration, and related analytics. Superwall receives an anonymous app user identifier and standard app, device, session, paywall-interaction, purchase, and subscription metadata. When TriggerSort requests an offer, it sends one broad placement key: general upgrade, locked animal results, or photo deletion. It does not send a screen name or other granular in-app source value. It never adds photos, filenames, PhotoKit identifiers, photo counts, classifications, labels, tags, notes, cleanup selections, or other photo-derived information to a Superwall event.
TriggerSort uses Google Analytics for Firebase to understand a small product funnel and find places where people have difficulty. Analytics can receive a pseudonymous app-instance identifier, standard app, device, and session data, approximate location derived from a masked IP address, and deliberately limited events: a coarse Photo Library authorization result; app-section views; scan start, completion, failure, or cancellation; whether first results became available; and broad paywall-placement, checkout, and purchase milestones. TriggerSort does not send photos, thumbnails, filenames, PhotoKit identifiers, photo counts, classifications, labels, camera metadata, locations contained in photos, tags, notes, cleanup selections, or free-form error text to Analytics. Automatic screen reporting is disabled, no Analytics user ID is set, advertising consent and personalization are denied, the Analytics build does not include IDFA support, and IDFV collection is disabled.
TriggerSort shares its pseudonymous Firebase app-instance identifier with Superwall as a user attribute so subscription and paywall outcomes can be associated with the same anonymous product funnel. It is not an advertising identifier and is not used for cross-app tracking.
TriggerSort also uses Firebase Crashlytics to diagnose crashes and improve reliability. Crash reports can include stack traces, relevant app state, device and operating system diagnostics, and pseudonymous Crashlytics/Firebase installation identifiers used to group affected installations. TriggerSort does not attach user IDs, custom keys, custom logs, photos, thumbnails, filenames, PhotoKit identifiers, locations, classifications, labels, tags, notes, cleanup selections, or other photo-derived data to crash reports.
TriggerSort does not use this product, monetization, or crash data for advertising or tracking across other companies' apps or websites.
Photo Library access
TriggerSort accesses only the Photos library content that you authorize through Apple's permission controls. It reads photo thumbnails, image data, and available metadata to discover likely trail-camera batches and organize them for review.
If you choose limited Photos access, TriggerSort works only with the photos you select. You can change that selection or revoke access at any time in the Settings app.
On-device analysis
Wildlife and blank-frame analysis runs on your device using Core ML models bundled with the app. TriggerSort does not upload photos for classification. The app can identify broad categories such as wildlife, people, vehicles, likely blank frames, and uncertain results, and can suggest more specific wildlife labels.
If you enable analysis of photos whose originals are stored in iCloud, Apple Photos may download those originals from your iCloud Photos library. Apple handles that transfer. TriggerSort analyzes the downloaded image locally and does not send it to Ash Apps.
Information stored on your device
TriggerSort stores its library organization, import-batch information, analysis results, confidence values, corrections, favorites, camera names, tags, notes, and preferences locally in the app's container. Exported CSV files are created only when you choose to export them and are handled by the destination you select in Apple's share sheet.
Photo deletion
TriggerSort never deletes a photo automatically. It can present likely blank frames for review, but deletion occurs only after you select photos and confirm the action. Apple Photos then presents its system confirmation and normally places deleted items in Recently Deleted, subject to your Photos settings.
Sharing and sale of information
Ash Apps does not sell personal information from TriggerSort. Superwall and Google process only the limited product, monetization, and crash data described above according to their own privacy terms. Photos and app content are shared outside TriggerSort only when you deliberately use an Apple-provided sharing or export action.
Data removal
Deleting TriggerSort removes its local database and preferences from the device according to iOS behavior. It does not delete your Photos library or files you previously exported. Photos removed through the app remain subject to Apple Photos' Recently Deleted behavior. Previously transmitted anonymous product, diagnostic, purchase, and subscription records remain subject to Google's and Superwall's retention and deletion practices.
Security
TriggerSort minimizes privacy risk by processing and storing app data locally. Device and iCloud security are provided by Apple and depend on your device, Apple Account, passcode, backup, and Photos settings. No storage system can be guaranteed to be completely secure.
Children's privacy
TriggerSort is not designed to collect personal information from children or adults. Questions about children's privacy may be sent to aaron@ashapps.com.
Changes to this policy
This policy may be updated if TriggerSort's data practices change. The effective date above will be updated when a revised policy is published.
Contact
For privacy questions, email aaron@ashapps.com.