Last Updated: July 22, 2026
At MurGoo.Click, we take a radical, transparent approach to your privacy. This Privacy Policy details how the OCR Clicker for Android mobile application ("Application" or "App") manages screen captures, on-device text extractions, local configurations, database storage, system permissions, and in-app transactions. The Developer operates from Goa, India.
This Application is built on a foundational philosophy of Privacy by Design (PbD). It is configured with an offline-first, zero-telemetry architecture. We do not operate cloud databases to aggregate your layouts, we do not utilize third-party analytics trackers, and we never transmit, share, monetize, or compile your screen data.
Unlike conventional tools that stream screen coordinates or layouts to external cloud servers, our App operates with extreme local sandboxing:
To perform dynamic character-matching clicks and floating overlay management, the Application requires several advanced Android permissions. Here is a clear breakdown of why these are requested and how they are handled:
| Permission (Android API) | Functional Purpose in App | Data Handling Method |
|---|---|---|
| Accessibility Service ( BIND_ACCESSIBILITY_SERVICE) |
Required to identify on-screen labels and layout structures, and programmatically simulate coordinates-based clicking inputs and swipe gestures on your behalf. | Local Only. Operates ephemerally in RAM. Raw nodes are evaluated against your active Room database rules and discarded instantly. |
| System Alert Window (Draw over other apps) |
Allows the Application to overlay the floating control widget, visual feedback circles, and custom Region of Interest (ROI) selection borders. | Local Only. Renders visual coordinates locally via Jetpack Compose. No data is stored. |
| Media Projection / Screen Capture | Required to programmatically scan your active viewport to execute on-device OCR character extraction. | Ephemeral. Captured frames are evaluated locally in volatile RAM and immediately garbage-collected. No screenshot images are saved, except when explicitly compiled into debug logs by the user. |
| Package Usage Stats ( PACKAGE_USAGE_STATS) |
Enables the App to detect the active foreground application, allowing the click engine to activate or deactivate automatically based on your app whitelist or blacklist filters. | Local Only. Evaluated locally inside the ViewModel to toggle service loops. Never logged or shared. |
| External / Media Storage Write | Allows you to export your saved click rules (backup database) or compile diagnostic logs into PDF format. | User-Controlled. Data is written strictly to your device's local folder. No cloud backup is triggered. |
| Audio & Haptics ( STREAM_MUSIC / Vibrator) |
Provides optional acoustic beeps and haptic vibration feedback when rules are matched or scanning state toggles. | Local Only. Generated locally via system audio and vibration hardware. No audio is recorded or stored. |
Any configuration data, customized click boundaries, exact coordinate settings, application whitelist parameters, and diagnostic telemetry are stored strictly inside your device's isolated storage sandbox via the Android Room SQLite database framework.
Settings > Apps > OCR Clicker for Android > Storage > Clear Data / Clear Cache, or by completely uninstalling the Application.All digital purchases, license keys, and subscriptions within the Application are processed exclusively through the official Google Play Store Billing System (Google Play In-App Purchases). The Developer does not process, store, intercept, or have access to your credit card details, debit card numbers, banking credentials, or billing address. All payment processing is subject to Google Play's Terms of Service and Privacy Policy.
Because the Developer resides and operates in Goa, India, the App is constructed to respect the DPDPA of 2023. Under the DPDPA, we are not classified as a "Data Fiduciary" or "Data Processor" for your screen operations because no digital personal data is compiled, received, or stored by us. All your personal coordinates and screen captures are maintained strictly under your own sovereign physical custody on your personal device.
By operating an offline-first architecture with zero server-side telemetry, this Application guarantees complete privacy compliance by design. We do not collect "Personal Data" (GDPR) or "Personal Information" (CCPA), and we do not "sell" or "share" user metrics with advertising networks, third-party brokers, or cloud analytical firms.
The Application or its documentation website may contain links to external third-party websites (such as Google Play Store or MurGoo.Click). The Developer is not responsible for the privacy practices, privacy policies, or content of external third-party sites.
We reserve the right to modify or refine this Privacy Policy to ensure compliance with updated Google Play developer requirements, newer versions of the Android Operating System, or changes in data privacy regulations. Any updates will be designated with an updated "Last Updated" date at the top of this document.
For any questions regarding our zero-telemetry architecture, on-device OCR pipeline, or to submit a query regarding data security, please contact our support desk directly via email:
Support Email: Support@MurGoo.Click