Effective date: 17 September 2026
SnapAction is provided by TheAppDevs_Team. For privacy questions or support, contact w1lljsb84@gmail.com. This policy covers the Android app com.snapaction.app.
IMAGES AND RECOGNITION
SnapAction reads images you select, share or capture. Text and barcode recognition run on your device. No SnapAction account is required. We do not operate a screenshot-processing server, upload screenshots for recognition or send recognised text to a remote AI service. Only import content you are entitled to use. Recognition may be incorrect: review dates, contact details, prices and destinations before confirming an action.
OPTIONAL SCREENSHOT INBOX
If enabled, Android asks you to select a folder and grant read access. SnapAction periodically checks direct image files whose names contain “screenshot”, within bounded batches. It does not traverse subfolders or request your whole photo library. Choose a local folder for offline use. Stopping monitoring removes the retained folder grant. Android may delay background checks.
LOCAL STORAGE AND SECURITY
Recognised text, records, action history and preferences are stored in app-private device storage. Camera captures may remain temporarily in the app cache. Optional device authentication uses Android’s biometric or device-credential prompt. SnapAction receives the result, not your biometric template or PIN.
Ordinary records are protected by Android’s application sandbox, not individually encrypted by SnapAction. App lock is an access control, not database encryption. Automatic Android backup is disabled. A compromised or unlocked device may expose information.
Encrypted exports use a password you choose, without a password-recovery service. Files remain wherever you save them, including storage providers you select. Protect your password and backups. Import restores records; reminder notifications require review and rescheduling.
GOOGLE ML KIT DIAGNOSTICS
SnapAction uses bundled Google ML Kit text recognition and barcode scanning. Images and recognition outputs are processed on-device. Separately, Google’s SDK collects operational data such as device/app information, installation identifiers, API configuration, input/output sizes, performance timings and error/event information for diagnostics and usage analysis. It may contact Google for maintenance or compatibility information. Local recognition does not mean the app never makes network connections. Core bundled recognition can work offline.
ML Kit privacy terms: https://developers.google.com/ml-kit/terms
ML Kit data disclosures: https://developers.google.com/ml-kit/android-data-disclosure
ADVERTISING AND PRIVACY CHOICES
When advertising is enabled, Google Mobile Ads and Google’s User Messaging Platform support banners and advertising choices. Google may collect or share IP addresses, approximate location inferred from IP, advertising/device or account identifiers, ad interactions and diagnostic information for advertising, measurement and fraud prevention. We do not supply screenshots or recognised text for ad targeting.
Use Advertising choices in the app to check or revisit available privacy options. Ad requests depend on the consent platform’s permission to request ads. Choices and applicable settings affect personalised, non-personalised or limited advertising. You may also manage your advertising identifier through Android settings. Buying ad removal suppresses SnapAction advertisements; it does not disable separate ML Kit diagnostics.
Google privacy policy: https://policies.google.com/privacy
Mobile Ads disclosures: https://developers.google.com/admob/android/privacy/play-data-disclosure
PURCHASES
Google Play handles checkout and payment details. SnapAction reads product identifiers, purchase tokens and status to grant, acknowledge and restore one-time ad removal. It does not receive payment-card numbers. Entitlements are cached locally and refreshed when Play is reachable. Refunds or revocations may not be reflected offline. Google retains purchase information under its policies; erasing local records does not erase Play purchase history.
ACTIONS AND SUPPORT
When you confirm a calendar, contact, email, messaging, maps, browser or sharing action, the selected information is handed to that app and its privacy practices apply. Opening websites can disclose IP address and device information to the destination. SnapAction does not silently send messages or complete purchases for you.
If you email support, we receive your address and included information to respond. Avoid sensitive screenshots, passwords or purchase tokens. Correspondence is handled through our email provider and retained only as needed for the request and applicable record-keeping obligations. Contact us to request deletion of correspondence we control.
RETENTION AND DELETION
Local records remain until you erase them, clear app storage, uninstall or applicable retention settings remove them. Cleanup runs when the app applies retention settings; it is not a guaranteed real-time deletion deadline. Erasing all local records stops monitoring and cancels local reminders. It does not remove originals, exports, Google purchase records or information already handed to other apps.
For a complete local reset, use Android’s Clear storage or uninstall. Manage camera, notification and folder permissions in Android settings or corresponding app controls. The publisher cannot remotely retrieve or delete records held only on your device. Google manages SDK data under its own policies and controls.
Depending on where you live, you may have rights to access, correct, delete or restrict personal information, object to processing, withdraw consent or complain to a data-protection authority. Contact w1lljsb84@gmail.com about information we control. Withdrawing advertising consent does not affect earlier lawful processing or prevent core recognition.
CHILDREN AND POLICY CHANGES
SnapAction is a general productivity utility, not designed specifically for children. Do not provide children’s personal information in support messages. Contact us if you believe a child’s information has been sent to us.
We may update this policy as the app or data practices change. The effective date identifies the current version. Material changes will be reflected in the published policy and, where appropriate, in the app or required consent flow.