Privacy Notice – ZirvynCL Storage Cleaner

1. Introduction & Acceptance of Terms

This formal Privacy Notice is issued by ZirvynCL Studio (the Data Controller), governing your use of the Android storage cleaning application ZirvynCL (the App). ZirvynCL is designed to scan junk cache, residual application folders, duplicate photographs, unused installation files and oversized redundant media to free device storage capacity.

By downloading, installing, launching ZirvynCL, granting storage permissions, running file or media scans, and carrying out any cleaning operations within the App, you confirm you have fully read, comprehended and unconditionally agree to all data processing practices laid out within this notice. Should you disagree with any provision, you must cease all use and uninstall the application without delay.

This document complies fully with the UK General Data Protection Regulation (UK GDPR), the Data Protection Act 2018, the Privacy and Electronic Communications Regulations (PECR), Google Play Developer Policies, Android permission regulatory standards, the CCPA/CPRA for United States California users, and the COPPA federal children’s privacy rules, alongside the EU GDPR for EEA, Swiss and Northern Irish residents.

2. Full Disclosure of Sensitive Storage Permission

2.1 Legitimate Functional Necessity (Mandatory Justification for Google Play Review)

Android Scoped Storage and MediaStore APIs only deliver restricted access to public media directories, and cannot retrieve hidden application cache folders, uninstall residual directories, external SD card partitions, system concealed storage paths, private download folders and leftover installation packages. Without MANAGE_EXTERNAL_STORAGE full-file access, ZirvynCL cannot deliver its core advertised deep storage cleaning functionality, including detection of duplicate imagery, blurry redundant video footage, long-unused compressed archives and hidden system junk files. Restricted media-only storage APIs are incapable of substituting this permission to provide full-device comprehensive scanning, which constitutes the primary core feature of this storage optimisation utility.

2.2 Strict Boundaries Governing File & Media Access (Privacy Safeguards)

• ZirvynCL only extracts file metadata throughout scanning processes: file name, absolute storage pathway, file format extension, visual resolution and file size. The App never parses, previews, reads, uploads or permanently stores the internal visual, textual, financial or confidential content contained within your private photographs, personal video recordings, encrypted documents and sensitive user files stored locally on your device hardware.
• No file, photograph or video asset shall ever be deleted automatically under any operational circumstance. All identified junk, duplicate and oversized media candidates are displayed fully to you for manual checkbox selection before any deletion routine executes; ZirvynCL shall never remove any user-owned file without your explicit, voluntary manual confirmation.
• All file scanning, duplicate matching, sorting and classification logic operates entirely offline and locally on your device’s central processing unit and memory. No raw image or video binary data, complete file bodies or full media content will be transmitted to remote cloud servers during any storage scan session.
• You retain full unilateral revocable authority to withdraw All Files Access permission at any time via your Android system Application Settings centre. Immediately upon permission revocation, all storage scan, media detection and file cleanup functionality within ZirvynCL will be fully disabled until you manually re-grant the permission.
• ZirvynCL will never scan, collect or upload confidential private documentation such as bank statements, identity photographs, chat history attachments or personal classified files to external servers; all file analysis remains confined exclusively to your local device hardware.

3. Information We Collect

ZirvynCL only gathers anonymous, non-personal technical data without unique user identifiers, alongside voluntary feedback you actively submit via our official support channel. No sensitive personally identifiable information is collected under any operational circumstances.

3.1 Voluntarily Submitted User Information

• Feedback text, scan failure descriptions and device error notes you submit via the in-app support form to report media matching faults, scan crashes or storage detection malfunctions.
• Optional email address you supply solely for our support team to deliver written follow-up replies to your technical service tickets.
• Local custom scan configuration preferences: media filter thresholds, hidden folder exclusion lists and cleaning rules saved exclusively on your device local storage; these preference records will not be uploaded to cloud servers by default.

3.2 Automatically Collected Anonymous Technical Data

• Device hardware metadata: device brand, hardware model identifier, Android operating system build version, ZirvynCL application build version, total internal storage capacity and remaining free space metrics.
• Anonymous Google Advertising ID (GAID): utilised solely to serve non-personalised contextual in-app advertisements, with no user profiling, cross-device tracking or targeted advert construction enabled.
• De-identified crash logs and performance statistics: anonymised error stack traces and scan speed benchmarks used exclusively to resolve media duplicate matching defects and enhance cross-device scan stability; crash logs contain zero private media or user file content extracted from your local storage.
• Aggregated anonymous usage metrics: total scan launch frequency, total junk storage space cleared per session, feature interaction click counts; all aggregate statistical data cannot be linked back to a single unique user or hardware device.

3.3 Data We Never Collect Under Any Circumstance

ZirvynCL Studio will never capture full legal names, telephone numbers, bank or credit card financial data, government-issued identity documentation, contact list address books, real-time geolocation coordinates, biometric authentication data, camera-captured imagery, microphone audio recordings or private chat message history.

4. Lawful Grounds & Purposes of Processing

All data processing activities outlined within this notice operate under the lawful basis of legitimate business interest and contractual necessity to deliver the App’s core storage cleaning service. We shall not repurpose, repackage or reuse your anonymous device metadata and scan statistics for unrelated commercial marketing activities without separate, written, affirmative opt-in consent submitted by you via our official support communication channel.

• Deliver core full-device storage cleaning features: duplicate photograph and video detection, oversized media sorting, hidden junk cache scanning and manual file removal workflow;
• Optimise cross-hardware compatibility and resolve runtime scan crash exceptions across all mainstream Android device brands and API levels;
• Deliver free non-targeted in-app advertisements through Google AdMob to offset development and server operational costs, enabling full-feature free distribution of ZirvynCL to all global users;
• Examine voluntarily submitted user support feedback to troubleshoot MANAGE_EXTERNAL_STORAGE permission detection errors, media matching failures and device compatibility defects;
• Fulfil mandatory legal disclosure, audit and compliance obligations required by the Google Play Store marketplace and global cross-border data regulatory frameworks.

ZirvynCL Studio shall never sell, rent, trade, licence or monetise your device metadata, scanned file metadata, anonymous diagnostic logs or voluntary support feedback information to third-party advertising agencies, consumer data broker platforms, marketing firms or commercial data aggregators for monetary gain.

5. Third-Party Software Development Kits

ZirvynCL only integrates official Google LLC service SDKs. All data shared with these third-party vendors is fully anonymised, non-personal statistical data stripped of all user identity markers. All Google subsidiaries execute legally binding data protection agreements prohibiting unauthorised secondary disclosure or commercial resale of shared device metadata.

5.1 List of Active Third-Party SDK Integrations

• Google Firebase Crashlytics: Purpose – collect anonymous crash diagnostic logs to identify and repair runtime scanning bugs and improve overall App stability; this SDK cannot independently access local private media, encrypted documents or raw full-storage file contents residing on your mobile device without your manually granted All Files Access permission.
• Google AdMob: Purpose – serve free non-personalised contextual in-app advertisements; processes only anonymous GAID advertising identifiers to regulate advert display frequency and limit repetitive pop-up advert interruptions during App usage sessions.
• Google Play Billing: Purpose – process optional one-time ad-free premium purchases and recurring subscription upgrades; all complete payment transaction data is securely stored and managed exclusively by Google LLC. ZirvynCL Studio never caches, retains or stores any user credit card numbers, billing addresses or payment credential details on our backend cloud servers.

5.2 Compelled Legal Disclosure Exception

We may release aggregated, anonymised device statistical data without additional user consent only when responding to valid, formally issued court orders, official national or state government regulatory data disclosure subpoenas, or when data disclosure is reasonably necessary to protect platform operational security, our registered legal intellectual property rights, or the general personal data safety of all ZirvynCL end users.

6. Data Storage & Retention Periods

• Temporary scan cache data: Local file scanning indexes and on-device media preview cache stored within ZirvynCL’s private application sandbox folder are automatically and permanently erased the instant you fully close and exit the App.
• Anonymous crash & usage analytics logs: Anonymised diagnostic data is retained on encrypted Google cloud backend servers for a fixed maximum retention window of twelve (12) calendar months. Upon expiry of the 12-month period, all log records are permanently auto-deleted from all cloud storage systems with no manual recovery option available.
• User voluntary support feedback records: Messages submitted via the in-app help form are stored for ninety (90) calendar days solely to facilitate follow-up technical support enquiries. After the 90-day retention window expires, all feedback text and associated optional email addresses are fully purged from our internal support databases.
• Local user custom scan preferences: Filter rules, storage size thresholds and hidden folder exclusion lists reside solely on your mobile device’s local storage partition. These preference records are permanently deleted when you manually clear ZirvynCL’s application storage cache or fully uninstall the software from your device hardware.

ZirvynCL does not enable automatic cloud synchronisation or silent background upload of local device user files by default. All scanned file metadata information remains confined to your mobile hardware and will not be transmitted to remote external servers unless you voluntarily submit feedback content through the built-in in-app support form.

7. Technical & Organisational Security Measures

We implement layered technical, administrative and operational security safeguards consistent with international information security industry standards to shield anonymous device metadata and local scan cache records from unauthorised access, data leakage, malicious tampering and permanent irreversible data loss:

• All network data transmission pipelines between your device and third-party Google SDK backend servers utilise TLS 1.3 end-to-end encryption protocols to block packet interception and man-in-the-middle data theft during data transfer sessions.
• Third-party SDK data access channels are strictly isolated via Android operating system runtime permission sandbox restrictions; external integrated tool modules cannot independently read full local storage media files without your manually activated MANAGE_EXTERNAL_STORAGE permission grant.
• Internal backend staff data access control protocols mandate multi-factor identity verification and strict role-based access authority segmentation to limit which team members may review aggregated anonymous statistical log data only.
• Quarterly automated vulnerability scanning operations are performed on ZirvynCL’s source code and all outbound data transmission pipelines to identify and remediate potential security loopholes in advance of public release App updates.
• A standardised formal data breach emergency response protocol is fully documented and enforced company-wide. In the event of any unauthorised confidential user data exposure incident, all impacted end users and relevant national and state data regulatory authorities will receive formal written notification within seventy-two (72) hours of breach detection, in full compliance with United Kingdom and United States state-level data breach notification statutes.

No digital storage or internet transmission system can guarantee 100% absolute invulnerability to data security risks at all times. We strongly recommend all users enable secure screen lock passwords or biometric authentication for your mobile device hardware to prevent unauthorised physical third-party access to local private media gallery and document files stored on your device.

8. Your Data Protection Rights Under UK GDPR

All users resident within the United Kingdom, European Economic Area, Switzerland and Northern Ireland hold the following statutory data subject rights:

• The right to access: Request a full copy of all anonymous technical data linked to your advertising identifier held by our third-party service providers;
• The right to erasure: Demand permanent deletion of all anonymous crash and usage log data associated with your device GAID;
• The right to restrict processing: Disable anonymous crash reporting and advertising tracking via your device system privacy settings;
• The right to data portability: Request aggregated anonymous usage statistics in a standard machine-readable format;
• The right to object to processing: You may object to all anonymous telemetry collection at any time;
• The right to withdraw consent: Any consent granted for data tracking may be withdrawn at any point without affecting the lawfulness of prior processing.

Should you wish to exercise any of these rights, please submit a formal request via the privacy email listed within section 12 below. We shall complete mandatory identity validation and issue a formal written compliance response within thirty (30) calendar days of receiving your fully submitted request.

9. CCPA / CPRA Statutory Rights for California Residents (United States)

If you are a permanent legal resident of the State of California, United States of America, you hold supplementary statutory privacy rights established under the California Consumer Privacy Act and California Privacy Rights Act:

• The Right to Know: You may submit a formal written request to receive full written disclosure of all categories of non-personal device technical data we collected linked to your unique hardware GAID advertising identifier over the preceding twelve (12) calendar months;
• The Right to Delete: You may submit a formal written demand requesting permanent full erasure of all anonymous usage statistics and crash log data tied to your device advertising identifier stored on our third-party Google cloud server infrastructure;
• The Right to Opt Out of Sale: ZirvynCL Studio never sells, trades or monetises any personal or anonymous user information to commercial third parties for profit. No separate formal opt-out process for data sales activities is required or available to users;
• The Right to Non-Discrimination: Exercising any of your statutory CCPA privacy rights will not result in discriminatory service limitations, price increases or restricted access to all free core storage scanning and media cleanup feature sets contained within the ZirvynCL application.

10. COPPA Federal Children’s Privacy Protection Rules (U.S. Federal Law)

ZirvynCL Storage Cleaner is designed, marketed and intended exclusively for end users aged thirteen (13) years and older. This App is not targeted, advertised or directed to minors under the age of 13, in full strict compliance with the United States Children’s Online Privacy Protection Act (COPPA) federal regulatory requirements.

We shall not intentionally, knowingly or voluntarily collect any personally identifiable information from children under the age of thirteen without verifiable, written parental consent meeting strict COPPA identity verification standards. If you are a parent or legal guardian and discover your minor underage child has downloaded, installed or utilised ZirvynCL without your formal written approval, contact our dedicated privacy support email listed below. We shall fully delete all child-related stored feedback records and anonymous device usage statistical data within fourteen (14) business calendar days following successful verification of your legal guardian identity documentation.

11. Policy Revisions & Notification Arrangements

We reserve the full unilateral legal right to revise, amend, modify and update this Privacy Notice on a regular periodic basis to align with updated Google Play marketplace platform policies, United Kingdom UK GDPR and DPA 2018 legislation, United States federal and state data protection privacy legislation, global cross-border privacy regulatory frameworks and functional feature adjustments deployed to ZirvynCL via official App updates.

Material policy revisions that alter storage data access control rules, MANAGE_EXTERNAL_STORAGE permission usage boundary standards, third-party data sharing scope limitations or sensitive user data processing compliance rules will be formally announced via in-app pop-up alert notifications delivered to all active App users at least fourteen (14) calendar days before the updated policy officially takes legal effect. Minor textual wording corrections, formatting tweaks and grammatical revisions will only refresh the “Last Updated” date label located at the top of this document without separate advance user notification alerts.

Your continued active usage of ZirvynCL’s storage scan, duplicate media identification and file cleanup functional tools after the revised policy official effective date constitutes your full voluntary acceptance of all updated privacy clauses contained within this revised Privacy Notice.