Privacy Policy

SnapTask ("we", "our", or "the app") is a privacy-first productivity application for Android. This Privacy Policy explains how SnapTask handles information when you use it.

SnapTask version 1.0 is designed to perform all processing locally on your device. In this version, we do not operate servers, collect analytics, or require an account. This policy describes how SnapTask version 1.0 handles your data.

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

SnapTask processes the following information entirely on your device, using your device's own storage and computing resources:

• 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.

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, no network call, no cloud API.

This is verifiable in version 1.0: SnapTask's AndroidManifest.xml does not declare the INTERNET permission. Without this permission, an Android application is technically incapable of making any network request, regardless of which libraries it includes.

Entity extraction (identifying phone numbers, dates, emails, links, etc.) is performed using deterministic rule-based algorithms written in Kotlin — no machine learning model, no server calls.

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

All processing is performed locally, exclusively to provide the features you have requested:

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.

In version 1.0, we do not use your information for advertising, user profiling, machine learning training, product analytics, or any purpose other than operating the app locally for you on your own device.

The following describes SnapTask version 1.0. If any of these practices change in a future release, this Privacy Policy will be updated and users notified before the change takes effect:

All data created by SnapTask is stored in the app's private local storage on your Android device — a protected directory that only SnapTask can access, enforced by Android's security model.

• 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 a local SQLite 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

You have complete control over all your data at all times:

• Individual screenshots: Swipe to 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: Long-press to 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 simply uninstall SnapTask. Either action permanently removes all data from your device with no residual copies anywhere.

SnapTask version 1.0 declares only the three permissions strictly necessary for its core reminder functionality. The table below lists every permission declared in the application's AndroidManifest.xml. INTERNET is not declared in version 1.0 — the app is architecturally incapable of network communication.

Google ML Kit — Bundled Text Recognition

SnapTask uses ML Kit's bundled Latin text recognition model (com.google.mlkit:text-recognition v16.0.1). With the bundled variant:

• The ML model is shipped inside the app's APK — no download is performed at runtime.
• Recognition runs in your device's memory with no network calls to Google.
• Your screenshot content is never sent to Google's servers for inference.

Google's privacy policy and ML Kit terms of service apply to this SDK at developers.google.com/ml-kit/terms. However, because no data is transmitted, the practical privacy impact for users of SnapTask is zero.

Android Calendar Intent

When you choose "Add to Calendar", SnapTask uses Android's standard CalendarContract.ACTION_INSERT Intent to open your installed calendar app (Google Calendar, Samsung Calendar, Outlook, or any other). 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 version 1.0 is built with open-source libraries including Kotlin, Jetpack Compose, Room, Koin, Coil, kotlinx.coroutines, and others. The full list with license attributions is available in the app's open-source licenses section. These libraries run locally on your device and, in version 1.0, do not transmit data externally.

SnapTask does not knowingly collect, store, or transmit personal information from any user, including 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).

Because SnapTask version 1.0 collects no data whatsoever — not even anonymized analytics or crash reports — there is no personal information of any kind that could relate to a child. All data is stored only locally on the user's own device and is not transmitted anywhere.

SnapTask is a general-purpose productivity application and is not specifically directed at children. Parents and guardians who permit children to use this app may do so knowing that no information about the child will be collected, transmitted to us, or shared with any third party.

Because all data is stored exclusively on your device, you have complete, direct control 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.
• Portability: Your data resides in the app's private storage. Android's built-in backup mechanisms (if enabled by you) may include it in device backups.
• No account to close: There is no user account, no profile, and no server-side record to request deletion of.

If you are a resident of the European Union (GDPR), the United Kingdom (UK GDPR), California (CCPA/CPRA), or any other jurisdiction with specific data subject rights, those rights are automatically and fully satisfied: there is no personal data outside your device to access, delete, restrict, object to, or port.

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

• No network attack surface in version 1.0: With no internet permission declared, there is no data in transit and no remote server that could be compromised to expose your information.
• Private app storage: All data is stored 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.
• Receiver protection: Android broadcast receivers used for alarm delivery are declared non-exported, reachable only via explicit, immutable PendingIntents from within the app.
• No third-party SDKs with network access: No analytics, advertising, or crash-reporting SDKs are present in version 1.0.

While no storage method is completely secure against physical device access, SnapTask eliminates the most common and impactful attack vectors — remote data interception, server breach, and credential theft — entirely by design.

We may update this Privacy Policy when new features are introduced or when required by law. When we do:

• The updated policy will be published at this URL with a new "Last Updated" date.
• Any change that would result in data being transmitted off your device will be announced within the app before the updated version ships, with explicit user consent required.
• 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 a 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.