Privacy Policy

SnapTask ("we", "our", or "the app") is an Android productivity application developed by Saad El Fadil. This Privacy Policy explains what information SnapTask processes, how it is used, and what third-party services are involved when you use the app.

This policy applies to SnapTask version 1.0.0 and covers the application available on Google Play under the package name com.saadelfadil.snaptask. It describes the app's current implementation as of the effective date above.

By using SnapTask, you agree to the practices described in this Privacy Policy. If you do not agree, please do not use the application, or uninstall it at any time.

SnapTask does not intentionally collect or store users' personal information on its own servers. The app has no backend, no accounts, and no user database. The following information is processed locally, on your device, to provide the app's core functionality:

• Screenshots you share: Image files you explicitly share to SnapTask via Android's Share Intent. SnapTask only ever sees images you consciously choose to send it.
• Extracted text: Text recognized by the on-device OCR model from your screenshot.
• Detected entities: Dates, times, phone numbers, email addresses, URLs, prices, and addresses automatically identified within the extracted text.
• Reminders: Reminders you choose to create from recognized content, including their title, date, time, and notes.
• Action history: A local record of actions (calls initiated, emails opened, calendar events created) that you confirmed within the app.
• App settings: Preferences you configure, stored locally using Android's standard storage APIs.

Separately, when the app displays advertisements, Google AdMob and Google User Messaging Platform (UMP) may process certain technical and advertising-related information as described in the Advertising and Google AdMob sections below. That processing is performed by Google, governed by Google's own privacy policy, and is distinct from the locally-stored data described above.

SnapTask does not require an account, and the app's own code does not collect the following:

The application does not include analytics or behavioral tracking SDKs. The only third-party SDKs integrated are Google Mobile Ads (AdMob) and Google User Messaging Platform (UMP) for advertising and consent management, described in detail below.

SnapTask uses Google ML Kit's bundled text recognition model (com.google.mlkit:text-recognition, bundled Latin variant). "Bundled" means the recognition model is compiled directly into the application's APK file — no model download at runtime, and no network call to a Google server for recognition.

Entity extraction (identifying phone numbers, dates, emails, links, addresses, and prices within the recognized text) is performed using deterministic, rule-based algorithms written in Kotlin, running locally — no machine learning model and no server calls are involved in this step.

For Google's own documentation on ML Kit, see developers.google.com/ml-kit/terms.

SnapTask stores data using a local Room database and the app's private storage directory on your Android device — a protected location that only SnapTask can access, enforced by Android's security model. No account or cloud service is used to store this data.

• Screenshot images: When you share an image to SnapTask, a copy is saved in the app's private storage directory. A small thumbnail is generated for display purposes.
• Extracted text and entities: Recognized text and detected entities are stored in the local Room database alongside each screenshot record.
• Reminders: Stored in the local database. Alarm triggers are registered with Android's AlarmManager and are re-registered automatically after device reboot.
• Action history: A record of confirmed actions is stored locally for your reference.

Deleting Your Data

• Individual screenshots: Delete from the History screen. Deleted items enter a 24-hour grace period (allowing undo), after which they are permanently erased, including their image files, from your device.
• Bulk deletion: Select multiple screenshots and delete them together.
• Individual reminders: Delete any reminder from within the Reminders screen.
• Everything: Go to Android Settings → Apps → SnapTask → Storage → Clear Data, or uninstall SnapTask. Either action permanently removes all locally stored data from your device.

Locally stored information is used exclusively to provide the features you request within the app:

1. OCR: Your screenshot is decoded and passed to the on-device text recognition model to extract readable text.
2. Entity extraction: The extracted text is analyzed by rule-based algorithms to identify actionable entities (dates, phone numbers, emails, links, addresses, prices).
3. Action suggestions: Identified entities are ranked and presented as suggested actions for you to choose from — create a reminder, open a link, dial a number, add a calendar event, and so on.
4. Reminder scheduling: If you create a reminder, it is stored locally and scheduled using Android's AlarmManager. No cloud service is involved.
5. Calendar events: If you choose "Add to Calendar", SnapTask launches your device's calendar app via Android's standard Calendar Insert Intent, pre-filled with event details. SnapTask does not write to your calendar directly — you review and confirm within your calendar app.
6. History: A local history of your screenshots and confirmed actions is maintained for your reference and is visible only to you.

We do not use locally stored screenshot, OCR, reminder, or history data for advertising, user profiling, or model training. Advertising served through Google AdMob is requested independently of this data, as described below.

SnapTask uses Google Mobile Ads (AdMob) to display banner advertisements. This is the only form of advertising in the app.

Certain information may be processed by Google AdMob and Google User Messaging Platform (UMP) as described in Google's Privacy Policy when advertisements are displayed. This may include device and advertising identifiers, general technical information, and — where you have consented — data used to personalize ads. We do not control what Google collects to serve ads; that processing is governed by Google's own privacy policy, linked in the section below.

Google AdMob is the advertising network SnapTask uses to display banner ads. When a banner is loaded, the AdMob SDK (com.google.android.gms:play-services-ads) may collect information such as your advertising ID, IP address, general device information, and app interaction data related to ad requests and impressions, for the purpose of serving and measuring ads.

In development and testing, SnapTask uses Google's official test ad unit IDs, which do not generate revenue or personalized data. In production, SnapTask uses a production AdMob ad unit registered to the developer's AdMob account.

Google's data collection and use practices for AdMob are governed by Google's own policies:

• Google Privacy Policy: policies.google.com/privacy
• How Google uses information from sites or apps that use AdMob: support.google.com/admob

We recommend reviewing Google's documentation directly, as it reflects Google's current practices and may be updated independently of this Privacy Policy.

SnapTask uses Google's User Messaging Platform (UMP) to manage advertising consent where required by applicable laws, including the EU General Data Protection Regulation (GDPR), the UK GDPR, and applicable US state privacy laws.

When you first open SnapTask in a region where consent is legally required, the UMP SDK requests your current consent status and, if needed, presents a consent form before any personalized ad request is made. Your response is used to determine whether SnapTask requests personalized or non-personalized ads, as described below. If the consent request itself fails or does not complete, SnapTask proceeds without blocking the app — the app remains fully usable, and ads may simply be limited, non-personalized, or not shown.

SnapTask does not read, store, or process the content of your consent decision beyond passing it to Google's Mobile Ads SDK when requesting ads. Consent state is managed by the UMP SDK itself.

Depending on your location and your consent choice (where consent is required), SnapTask requests either a personalized or a non-personalized ad from Google AdMob:

• Personalized ads may be informed by advertising identifiers and interest signals associated with your device, as determined by Google, when consent has been given or is not required in your region.
• Non-personalized ads are shown when consent for personalization has not been given, is required and has not yet been resolved, or where applicable law otherwise limits personalization. Non-personalized ads may still be based on limited contextual information, such as general app content, without using your advertising identifier for interest-based targeting.

You can review or change how Google personalizes ads across apps generally through your Google Account's ad settings, and, where SnapTask presents a consent form, by responding to that form when it appears.

Google ML Kit — Bundled Text Recognition

SnapTask uses ML Kit's bundled Latin text recognition model (com.google.mlkit:text-recognition). The ML model is shipped inside the app's APK — no download is performed at runtime, and recognition runs in your device's memory with no network calls to Google for this feature. Google's ML Kit terms apply to this SDK: developers.google.com/ml-kit/terms.

Google Mobile Ads (AdMob) & User Messaging Platform (UMP)

Used to display banner advertisements and manage advertising consent, as described in the Advertising, Google AdMob, and Google UMP sections above.

Android Calendar Intent

When you choose "Add to Calendar", SnapTask uses Android's standard CalendarContract.ACTION_INSERT Intent to open your installed calendar app. SnapTask pre-fills the event details but does not write to your calendar directly. You review the event and save it inside your own calendar app. What happens after that handoff is governed by your calendar app's own privacy policy.

Android System Services

When you confirm actions such as calling a number, sending an email, or opening a link, SnapTask invokes Android's standard Intent system to hand off to the appropriate app (dialer, email client, browser). SnapTask does not intercept, read, or log the content of those interactions.

Open-Source Libraries

SnapTask is built with open-source libraries including Kotlin, Jetpack Compose, Material 3, Room, Koin, Coil, and kotlinx.coroutines. These libraries run locally on your device and do not, on their own, transmit SnapTask's screenshot, OCR, reminder, or history data externally.

The table below lists every permission declared in SnapTask's AndroidManifest.xml, matching the current release exactly.

SnapTask's security posture is defined primarily by its architecture:

• Private app storage: All locally stored data (screenshots, extracted text, reminders, history) resides in Android's app-private directory, inaccessible to other apps without explicit system privileges.
• No credentials: SnapTask requires no username, password, or authentication token. There is nothing to phish, leak, or steal remotely related to a SnapTask account, because no such account exists.
• Receiver protection: Android broadcast receivers used for alarm delivery are declared non-exported where appropriate, reachable only via explicit, immutable PendingIntents from within the app.
• Minimal third-party SDK surface: Google Mobile Ads (AdMob) and Google UMP are the only third-party SDKs with network access. No analytics or crash-reporting SDKs are present.

No storage or transmission method is completely secure. While SnapTask's local-first design limits the data at risk from a server breach — because we operate no server storing your content — device-level security (screen lock, device encryption) remains your responsibility as the device owner.

SnapTask does not knowingly collect personal information from children under the age of 13 (or the applicable minimum age in your jurisdiction under laws such as COPPA in the United States, or equivalent legislation elsewhere). SnapTask is a general-purpose productivity application and is not directed at children.

SnapTask's own code does not collect personal information from any user. Advertising is served through Google AdMob; where SnapTask is used by a child, advertising requests are made in the same manner as for any other user, subject to Google's own policies regarding child-directed treatment and applicable consent requirements. We do not knowingly direct SnapTask, or its advertising, specifically at children.

If you believe a child has provided information to us in a manner not described in this policy, please contact us using the details below so we can address it.

Because SnapTask's screenshot, OCR, reminder, and history data is stored exclusively on your device, you have complete, direct control over it at all times without needing to submit a request to us:

• Access: All your data is visible within the app — the History screen shows screenshots, the Reminders screen shows your reminders.
• Deletion: Delete individual items in-app, or erase everything through Android's storage settings or by uninstalling.
• Correction: Detected entities can be edited directly on the Review screen before any action is taken.
• No account to close: There is no SnapTask user account, profile, or server-side record of your app content to request deletion of.

For information Google collects via AdMob or UMP (such as advertising identifiers), you can manage ad personalization through your Google Account settings, and exercise applicable rights (such as access or deletion requests under GDPR, UK GDPR, or CCPA/CPRA) directly with Google as the data controller for that processing.

SnapTask is available to users worldwide. Screenshot, OCR, reminder, and history data processed by the app's own code stays on your device regardless of your location and is not transferred internationally, because it is never transmitted off the device in the first place.

Where Google AdMob and Google UMP process information to serve ads and manage consent, that processing may involve international data transfers governed by Google's own privacy policy and applicable safeguards (such as Standard Contractual Clauses for transfers from the EU/EEA/UK). If you are located in the European Economic Area, the United Kingdom, Switzerland, or a jurisdiction with similar data transfer requirements, Google's consent mechanisms via UMP are designed to address these requirements before a personalized ad request is made.

We may update this Privacy Policy when new features are introduced, when third-party services we use change their practices, or when required by law. When we do:

• The updated policy will be published at this URL with a new "Last Updated" date.
• Material changes to how SnapTask's own code handles your data will be described in the app's release notes.
• The Google Play Store listing will always link to the current version of this document.
• Minor clarifications with no change to data practices may be made without separate notice.

Continued use of SnapTask after a policy update constitutes your acceptance of the revised policy. If you disagree with any changes, you may uninstall the application at any time.