Your screenshots stay in your hands.
What SnapRecall processes locally, what limited diagnostics may leave your Mac, and how to control them.
Last updated September 30, 2026SnapRecall is a macOS app from Westley Rotolo. Your screenshots and their content are handled on your Mac. The app also uses Google Firebase for usage analytics and crash reporting, with separate controls in Settings. Those services do not receive your screenshot files or their extracted content.
Who is responsible
Westley Rotolo is responsible for SnapRecall and this website. For questions or privacy requests, email westley@outlook.it.
Your library and local processing
You choose the folder SnapRecall monitors. The app reads and organizes screenshots in that folder, and stores a local library with thumbnails, search data, tags, collections and annotations. Original files remain authoritative. OCR and AI analysis run on your Mac; models are downloaded to your Mac before they are used. AI-derived data can be regenerated, and annotations are stored separately from originals. The app does not upload screenshot files, OCR text, AI descriptions, tag text, search terms, file names, full paths, bookmarks or frontmost-app history as telemetry.
When you choose to copy, share or export an image, the destination you select may receive that image. Deleting local content does not remove copies you previously shared or saved elsewhere, including backups.
Usage analytics
Firebase Analytics is enabled by default. It may collect app launches, first opens, active use and sessions, plus counts of successful actions such as a saved capture, manual tag, tag filter, AI activation, completed AI analysis or accepted suggested tag. These custom events have no parameters. Firebase uses an app installation identifier; SnapRecall does not set an app-defined user ID or use an advertising ID for these events. Google may also collect automatic SDK events and platform information.
You can turn off Share usage statistics in SnapRecall’s Settings → Usage & crash reports. This stops new analytics collection through the SDK.
Crash reports
Firebase Crashlytics is enabled by default. It may receive crash stack traces, app and device or OS diagnostics, and SDK breadcrumbs when Analytics is active. Firebase uses installation and crash identifiers. SnapRecall does not attach screenshot content, custom keys or raw application logs to these reports.
You can turn off Share crash reports in the same settings. A restart may be needed before automatic crash collection changes. Reports already uploaded are not removed by switching the setting off; diagnostic reports may remain locally while uploads are disabled.
Third parties and retention
Google Firebase processes analytics and crash data to help us understand use and fix failures. Firebase/Google controls server-side retention and deletion under the project configuration and its applicable policies. To ask about data associated with your installation or request deletion, contact us at westley@outlook.it. We will assess the request and the controls available for the relevant Firebase data. See Firebase privacy information.
Downloading an AI model requires a network request to the model host, which may receive ordinary connection data such as your IP address. Screenshot content is not sent with that download.
This website
This static website has no account, contact form or site analytics script. Your browser requests pages and images from our hosting server, which may process ordinary request data such as IP address, requested URL, time and browser details to deliver the site and maintain security. Following the TestFlight or App Store link takes you to Apple; sending an email uses your email provider.
Your choices
You can choose or change your library folder, manage local screenshot content, and control usage statistics and crash reports separately in the app. Contact us to ask about your data or exercise applicable privacy rights. We may update this policy when the app or its data practices change; the date above shows the latest version.