This Privacy Policy outlines how the **MurGoo Screenshot Capture** application handles information, parameters, device functionalities, and visual metadata. We designed this utility with a strict commitment to the principles of privacy-by-default and local-first execution.
This Application operates at a deep device configuration level, leveraging screenshot capabilities, active overlays, foreground loops, and continuous file scanning utilities. Consequently, **the Application is strictly prohibited and unlicensed for use by anyone under eighteen (18) years of age.** If you are not yet 18, you must completely cease using this software and immediately uninstall all copies and components.
The Application is a fully autonomous utility that operates strictly on-device without any server-side database modules, Cloud API adapters, telemetry metrics, or external ingestion channels. **We do not collect, read, store, compile, upload, intercept, or share your screen contents, personal documents, typed text, or configuration credentials.** All screenshot capturing, annotation layers, and text extraction logic execute entirely within the local sandboxed runtime environment of your physical device.
Note on Third-Party Cloud Backups: The application saves media locally to your device storage (e.g., inside /Download/MurGoo_Captures). If you have enabled automatic cloud backup services (such as Google Photos, Dropbox, or OneDrive) to sync this folder, your screenshots will be uploaded to those third-party services according to their respective privacy policies. MurGoo.Click has no control over, and assumes no liability for, data synchronized by third-party storage providers configured on your device.
To provide completely exhaustive disclosures, we outline the exact localized handling of all built-in capabilities:
The application captures the active pixels displayed on your phone's screen using standard Android MediaProjection APIs combined with a system Foreground Service. These actions run solely within dynamic volatile RAM memory. The captured visual bitmaps are instantly saved directly to your local, device-based Storage Directory (by default, inside /Download/MurGoo_Captures). No network transfers of this media occur.
The in-app editor implements a fully offline rendering canvas. When you highlight, draw shapes, write text masks, blur layout regions, or crop screenshot images, all coordinate math and pixel transformations are performed on-device. No editing sessions, tracking points, brush logs, or original-vs-edited states are logged or transmitted.
When the periodic auto-capture sequence is active, the app checks consecutive screenshot bitmaps to identify and skip duplicates. This pixel comparison and hash matching check run entirely within your local device's CPU context and volatile RAM. No indicators, file states, or match scores are sent to remote services.
The application's capabilities to extract printed text (OCR) or tag imagery are powered exclusively by deterministic machine learning libraries compiled directly within the local offline APK package (such as Android's local ML Kit binaries). Your screenshots are never dispatched to Google Cloud Vision, Amazon Rekognition, or any alternative remote API frameworks for processing. Extracted text remains strictly confidential within your local runtime memory and is dropped immediately once you close the view.
The app offers custom auto-deletion retention choices (e.g., hourly, daily, weekly, or manual cleanups) and storage threshold locks (such as a 2MB default parameter limit file-size check block). The background cleaner loops read native directory sizes dynamically to prevent device memory exhaustion. These folders are located entirely inside user-managed public drives.
When the background service triggers key events (such as storage limits halted warnings, capture loop starting, or image skips), the app utilizes the local, native Android Text-to-Speech engine framework built into your host operating system. The alert phrases, including: "Storage Limit reached, Capturing Screenshot Aborted", are spoke natively and never collected or tracked.
Operational shortcuts like Quick Setting Tiles, Launcher Widgets, and Notification actions are integrated directly with local Android Broadcast Receivers. These hooks perform silent wake-up calls locally on-device without telemetry reporting.
The Application may offer a mechanism for users to voluntarily tip the developer. All financial transactions are securely processed by authorized third-party payment gateways (such as Google Play Billing). We do not collect, process, or store your credit card details, banking credentials, or financial identifiers locally or on our servers. The processing of these payments is entirely subject to the privacy policies of the respective payment providers.
While the core Application functions offline, if you actively choose to contact us for support, feedback, or legal inquiries via email, we will naturally receive your email address and the contents of your correspondence. User email addresses collected for support or communication purposes may be retained for a maximum duration of five (5) years. Following this maximum 5-year retention period, your records and correspondence are securely purged from our active support systems, unless retention is strictly mandated longer by an overriding legal obligation or active dispute.
Although we do not have access to your local on-device files or screenshots, we may disclose your email address and any retained support correspondence if legally required to do so in response to lawful requests by public authorities, court orders, subpoenas, or to protect our legal rights.
Because your screenshots, annotations, and extracted text are stored strictly on your local hardware, the ultimate security of this data relies entirely on your device's operational ecosystem. We strongly advise that you secure your Android device using robust screen locks (PIN, password, or biometric protections) and full-disk encryption. If your physical device is compromised, lost, or subjected to malicious hacking, your locally stored data may be exposed. MurGoo.Click assumes zero liability for data breaches resulting from local device vulnerabilities, missing screen locks, or unauthorized physical access.
To perform its operations legally and functional-wise, the application declares and requests the following specific system access handles:
This Application contains absolutely no third-party analytic components, telemetry trackers, crash-log reporting frameworks that transmit data, profiling kits, or ad-network SDKs (such as AdMob, Firebase SDK, Facebook SDK, or Flurry). Your workspace stays completely isolated from tracking behaviors, device profiling, and pixel scraping.
Because our application architecture mandates local-only storage, we lack the technical capability to extract, package, or delete your data remotely. Consequently, we cannot fulfill traditional "Right to Access" or "Right to be Forgotten" requests on our servers—because our servers hold exactly zero bytes of your captured data. To exercise these rights, you must manually delete the capture folders from your local device storage, which constitutes full and absolute data deletion.
If you procure this application via the Google Play Store or similar generalized hosting platforms, be mindful that these host infrastructures implicitly gather normalized, anonymized metadata to maintain store operations. Metrics such as aggregate installation counts, crash reporting arrays (e.g., ANR logs), and broader device demographics are compiled strictly by the app store platforms under their own terms, independent of our local architecture.
This Privacy Policy is construed, interpreted, and governed under the laws of **Goa, India**. Any dispute, litigation, action, or legal controversy arising out of this utility or our privacy commitments shall be submitted solely to the territorial jurisdiction of the competent courts operating in **Panaji, Goa, India**.
We may modify this document occasionally to reflect framework adjustments in newer Android versions or direct updates to local feature sets. We advise you to review this copy within your package distributions.
This privacy document is archived, maintained, and legally executed under the following official attributes:
© 2026 MurGoo.Click. All rights reserved.