Privacy Policy for Crazy Downloader | Cibru

Privacy Policy - Crazy Downloader Legal • Privacy Policy # Privacy Policy **Application:** Crazy Downloader | **Package:** `com.crazydownloader.app` | **Effective Date:** October 20, 2026 | **Version:** 3.0 **Summary:** Media extraction, file handling, and conversion run on your Android device. Downloading still connects to source platforms and their media/thumbnail providers. Download history and settings stay in app storage; saved public media is not encrypted by the app. Google AdMob/UMP can process advertising and consent data, Google Play handles payments, and the configured Supabase backend receives purchase verification data and optional referral data. Referral participation is disabled by default. Private app storage is not the same as application-level encryption, and deleting local data does not delete server records or cancel billing. ## 1. Introduction & Scope This Privacy Policy explains how **Crazy Downloader** (referred to herein as "the Application", "we", "us", or "our", package name: `com.crazydownloader.app`) accesses, collects, uses, stores, and discloses information when you use our mobile application distributed via the Google Play Store. The Application is published and operated by **CIBRU**. This policy explains the available features and data flows; optional referral participation and advertising choices are handled separately through the controls described below. A build with unconfigured services may not offer all connected features. ## 2. Information Collection & Data Types We believe in minimal data processing. The Application handles the following categories of information: ### A. User-Provided Media URLs & Download History (App Activity) - **Data Processed:** Media URLs you enter, paste, or share to the app; source metadata and thumbnails; selected formats; local media chosen for conversion; and download records such as title, source URL, file location, and status. - **Purpose:** The local extractor queries source platforms, media hosts, and their service providers for metadata and files. Those services necessarily receive the requested URL, device IP address, headers, and any applicable platform session cookies. On-device processing does not mean that downloading works without network connections. - **Storage & Retention:** History and core preferences use the app's Android Keystore-backed `EncryptedSharedPreferences` helper; if that storage cannot be initialized after recovery, the helper falls back to temporary in-memory preferences. Purchase/referral preferences and WebView data have the specific storage protections described below. The app does not send media files, download URLs, or local download history in its Supabase purchase/referral payloads. Source platforms have their own retention policies. - **Saved Files & Exports:** Downloaded media is saved to device media/storage locations and can be visible to other apps that have access. History exports or media you share are copies under your control. Clearing history or uninstalling does not erase public media, exports, or copies already shared. - **Temporary & Resumable Files:** The app keeps temporary processing files and private, backup-excluded partial-download files/receipts to support resuming work. These files are not promised application-level encryption. Some reside outside Android's cache directory, so Clear cache is not a complete cleanup. Scheduled cleanup attempts to remove inactive partial-download work after seven days; OS scheduling and file-operation failures can delay it. Clear app storage for a full private-data reset. ### B. Advertising Identifiers & Device Information (Google AdMob) - **Third-Party Service:** The Application includes the **Google Mobile Ads SDK (AdMob)** for banner, native, interstitial, and optional rewarded ads for free-tier users. Ad availability depends on configured ad units, network availability, and Google's consent status. - **Data Processed by Google:** Depending on SDK behavior, device settings, and consent, Google may process the Advertising ID or other device/app identifiers, IP address (including an approximate location derived from it), app/ad interactions, device information, and diagnostic/performance data. Some SDK data processing can occur without personalized ads. This is separate from media processing; we do not provide media files or download history as ad-request payloads. - **Purpose:** Ad delivery, frequency capping, anti-fraud verification, and ad performance reporting. - **Consent Management:** The app requests consent information through **Google User Messaging Platform (UMP)** and asks UMP to show a form when required. The form, regions covered, and choices offered depend on Google's requirements and the publisher's deployed UMP configuration. Including the SDK does not by itself establish a certified or correctly configured consent deployment. - **Choices:** Use **Settings > Ad privacy choices** to request UMP's privacy-options form when available. Android also provides Advertising ID and ad privacy controls. Premium access suppresses ad loading/display in the app, but the AdMob/UMP SDKs remain included and may initialize or update consent status; Premium is not a promise of no Google SDK communication. - **Test & Release Configuration:** Debug builds use Google's test ad units. Release ad-unit values are configurable and missing or invalid values skip the corresponding ad load. A test AdMob application ID or other placeholder is not a production publisher credential. ### C. Financial Information & Subscriptions (Google Play Billing) - **Third-Party Service:** Weekly, monthly, and annual subscriptions, when available, are billed by **Google Play Billing**. No separate CIBRU email, password, or Google Sign-In inside the app is required. This does not mean purchase verification occurs only on-device. - **Data Handled:** Google handles payment-card and bank details; the app does not collect them. The app reads Play purchase tokens, product IDs, purchase state, and an order ID when supplied. Verification/deletion requests send the app ID, product ID, purchase token, request ID, action, and a request-bound Standard Play Integrity token to the configured Supabase `play-subscription` endpoint over HTTPS. The service also receives ordinary connection metadata such as IP address. The current client keeps an available order ID locally; the server may obtain order information through Google. - **Server-Side Verification Assumption:** The backend is expected to verify Integrity proofs and purchase status with Google Play Developer APIs and return authoritative status, expiry, and server time. The client grants paid access only after a completed purchase receives a valid active verification response; pending payments do not unlock it. Those server checks depend on a correctly deployed/configured service and cannot be established by a client build alone. - **Storage & Freshness:** Purchase tokens, order/status information, and the local cache namespace use the Keystore-backed encrypted-preferences helper in private, installation-scoped storage, with the helper's recovery/in-memory fallback. A separate private, unencrypted sync-control preference stores the deletion pause/epoch rather than purchase tokens. These preferences are excluded from backup/device transfer. Verified paid access is usable offline for at most 72 hours and never beyond its verified expiry; a reboot requires fresh verification. The 72-hour access limit is not a record-deletion deadline. Locally observed tokens are retained for recovery and deletion until their deletion succeeds, app storage is cleared, or protected-storage recovery loses the records. Recognized purchases can be verified automatically at startup/foreground unless the saved purchase-sync pause is in effect. - **Restoration & Account Separation:** You can restore purchases at any time using **"Restore Purchases"** under the same Google Play account. Google Play subscriptions and referral rewards are strictly separate; restoring or deleting purchase records does not alter referral rewards. **Backend retention assumptions:** The shared integration's documented defaults are 90 days after verified expiry for expired/revoked purchase records, 30 days for failed jobs, one day for request-protection hashes, and purchase deletion markers until 90 days after the later of deletion or verified expiry. These are server configuration/cleanup targets, **not deletion guarantees enforced by this Android app**. The backend is managed separately from this repository; the deployed schema, retention jobs, provider logs/backups, and support-record retention require operator confirmation. Contact support@cibru.in for the applicable scope and outcome. Fresh valid verification, including from another installation, can recreate purchase records. Deletion never cancels Google Play billing or deletes Google's own transaction records. ### D. Local Platform Session Cookies (Optional Login) - **Purpose:** Optional supported-platform sign-in uses an in-app WebView. Login input is handled by the platform page, and cookies/WebView site storage remain in the app's private sandbox. This is not a separate CIBRU account and does not create a referral or purchase identity. - **Use & Removal:** The app supplies applicable cookies directly to the selected platform for authorized requests and creates temporary private cookie-export files for its local extractor. Those cookies are not included in the Supabase verification/referral payloads. **Settings > Connected Accounts > Disconnect** attempts to clear that provider's local cookies, site storage, and exports. It does not delete your account at the platform or log out other apps/devices. Clear app storage for a full local reset. ### E. WhatsApp Status Saver (Local Storage Access) - **Purpose:** The optional WhatsApp Status Saver reads status files already cached on your device using a folder you grant through Android's Storage Access Framework (SAF), or accessible legacy storage on older versions. Selected files are copied to public device media storage. - **Data Handling:** Saving/scanning does not upload status files to CIBRU or Supabase. If you explicitly use Share or open a file in another app, that recipient handles the file under its own practices. The app does not provide WhatsApp message, contact, or account access through the folder grant. ### F. Optional Referral Rewards Program (Supabase Backend) - **Optional & Default-Off:** Referral participation is disabled by default. Open the referral / Get Free Premium card and confirm **Enable rewards** after reviewing the disclosure to enable referral communication. It is separate from core downloading and paid purchases. Use **Settings > Purchase & Referral Data > Unsync referral** or the Unsync page to turn it off. - **Data Collected & Processed:** - **Pseudonymous User ID:** An anonymous/pseudonymous user authentication identity created via our backend provider (Supabase) without requiring your email, name, or phone number. - **App-Scoped Device Hash:** The current client reads and normalizes `Settings.Secure.ANDROID_ID` locally and derives a domain-separated SHA-256 hash using the app ID. It sends that `device_hash`, not the raw Android ID, in its version-2 referral registration payload. The hash is used for installation attribution and duplicate/abuse checks; a persistent hash is pseudonymous, not guaranteed anonymous. The deployed backend must support this versioned device-hash contract before registration can work. - **Google Play Install Referrer:** Installation attribution metadata (raw referrer string, referral code, install timestamp, and click timestamp) provided by the Google Play Store to credit the referrer when you install via a shared invite link. - **Google Play Integrity API Token:** A request-bound token, app ID, and random request ID are sent for app/device verification. Server verification of signing, app recognition, and device verdicts depends on deployed rules. No particular verdict level or anti-fraud outcome is guaranteed by the client. Media files and download URLs are not included in referral payloads. - **Purpose:** To securely register referrals, attribute free PRO reward days, verify genuine app installations, and prevent multi-account abuse or fraud. - **Storage & Freshness:** Referral authentication tokens, profile/code, counts, status, referrer data, and reward timestamps use the Keystore-backed encrypted-preferences helper in private app storage, including its recovery/in-memory fallback, and are excluded from backup/device transfer. Cached referral access is limited to 24 hours and verified expiry, is bound to the saved referral session, and is invalidated by a reboot. The configured Supabase service stores referral identity/profile, attribution, device-key, and reward records. An access-cache limit is not a server deletion deadline. - **Turning Off / Unlinking Locally:** Disabling participation cancels the local refresh job, stops new automatic referral sync attempts, clears the local reward/code/install-referrer cache, and removes local referral Premium access. The saved referral auth session is retained so you can request deletion or reconnect. It does not erase stored backend data or guarantee cancellation of a network request already sent. A confirmed deletion operation also clears that saved referral session and leaves participation off; this local unlink is distinct from deleting the shared server Auth identity. - **Deletion & Retention Assumptions:** The intended app-scoped server deletion removes referral profile/reward/attribution records while retaining a device-key anti-abuse marker for a documented 90-day target; the shared Supabase Auth identity is outside that deletion's scope. Actual server deletion, retained fields, and cleanup require confirmation from the deployed service/operator. If a deletion control is absent, a request fails, or the original local session is unavailable, use the Data Deletion guide and support rather than assuming all historical server records were removed. ## 3. Android System Permissions & Why We Need Them The current source manifest and SDK-merged permissions cover the following functions. Runtime prompts depend on Android version and the feature used; declaring a permission does not mean every feature uses it on every device. Permission Target Android Versions Purpose / Justification `INTERNET` All Versions Connects to source/media hosts, downloads metadata/media, and supports configured ads, Play-related verification, and optional referral services. `ACCESS_NETWORK_STATE` All Versions Checks whether an active Wi-Fi or Cellular connection is present, respecting the user's "Wi-Fi Only" preference. `POST_NOTIFICATIONS` Android 13+ (API 33+) Displays persistent download progress bars, completion alerts, and background service controls in the notification shade. `FOREGROUND_SERVICE` & `FOREGROUND_SERVICE_DATA_SYNC` Android 9+ / Android 14+ Runs user-requested downloads in a data-sync foreground service. Android background-execution rules and user controls still apply. `WRITE_EXTERNAL_STORAGE` Android 9 and below (API ≤ 28) Legacy writing of saved media to shared device storage. Newer Android versions use MediaStore for app-created downloads. `READ_EXTERNAL_STORAGE` Declared through Android 12L (API ≤ 32) Legacy shared-media reading where required/available. It is not declared for Android 13+. Folder/file selections and MediaStore paths are used for supported modern operations. `SET_WALLPAPER` Supported Android versions Sets a selected downloaded image as wallpaper when you invoke that action. SAF folder/file grants System picker, where supported Accesses selected status folders or local media files. A persisted grant may remain until revoked or app data is cleared; this is not all-files access. `com.android.vending.BILLING` / `com.google.android.finsky.permission.BIND_GET_INSTALL_REFERRER_SERVICE` Added by Google Play SDKs Connects to Play Billing and retrieves install attribution for the referral flow; no payment-card details are exposed to the app. `com.google.android.gms.permission.AD_ID` / `ACCESS_ADSERVICES_AD_ID`, `ACCESS_ADSERVICES_ATTRIBUTION`, `ACCESS_ADSERVICES_TOPICS` Added by the ads SDK; OS support varies Supports advertising identifiers and Android ad services subject to platform/consent controls. The app does not request precise-location access for ads. `WAKE_LOCK` / app-scoped receiver permission Added by AndroidX dependencies Supports scheduled/background work and non-exported internal receivers; neither grants access to personal media or accounts. AndroidX dependency manifests can also contribute `RECEIVE_BOOT_COMPLETED` for rescheduling background work after reboot; inclusion depends on the final merged app manifest. Package-visibility queries detect supported installed platform apps and compatible handlers for opening/sharing or wallpaper actions; ad dependencies also query compatible browser, calendar, SMS and dial handlers. These queries do not grant access to contacts, messages or calendar records and are not a request to enumerate all installed apps. Camera, microphone, contacts, SMS, calendar, location, all-files access and Android 13 broad media-library permissions are not declared in the reviewed app manifest. ## 4. Data Retention & Deletion (Google Play Data Deletion Policy) Local deletion, backend deletion, and Google Play cancellation are separate actions. The Data Deletion guide is available without installing the app. The current Settings > Data Deletion link opens that guide; exact in-app deletion controls can vary by app version. - **Purchase Data:** Use **Settings > Purchase & Referral Data > Delete purchase verification data** or the same control in the PRO dialog. The operation pauses automatic verification syncing and removes local paid access before contacting the server. Confirmed successful responses remove the locally known purchase records in scope; failures can leave tokens/records for retry while sync stays paused. If no local purchase record is available, the operation can complete local cleanup without a server request; this does not establish deletion of older server records. Email support for those records. See Purchase Data Deletion. While this installation's app data is retained, only explicitly tapping **Restore Purchases** resumes syncing and may recreate records; starting a purchase does not clear the pause. **Clearing storage or reinstalling removes the local pause**, so automatic verification can run again after the app starts. This does not cancel payments or alter referral rewards. - **Referral Data:** Use **Settings > Purchase & Referral Data > Delete referral data** and confirm. The operation turns participation off; a confirmed deletion clears local referral cache/session and requests app-scoped server removal under the retention assumptions above. Without a recoverable local session, local cleanup cannot establish deletion of older server records. If unsuccessful, request assistance using your referral code. It does not cancel a paid subscription. - **History:** The Downloads screen's **Clear History** removes completed entries from the displayed list but retains a local restore backup. It does not securely erase every record or delete saved media. Clear app storage for a full local reset; remove media and any exported copies separately. - **Platform Sessions:** **Settings > Connected Accounts > Disconnect** clears the selected provider's local session data as described above, rather than deleting the remote platform account. - **Cache:** Android **Settings > Apps > Crazy Downloader > Storage & cache > Clear cache** removes cache-directory files, not all private partial-download/cookie-export files, preferences, history backups, verification tokens, server records, or subscriptions. - **Full Local Reset / Uninstall:** Android **Clear storage / Clear data** or uninstalling removes private app data, including local preferences and sessions. Public downloaded media and exported/shared copies may remain. Neither action sends a backend deletion request or cancels Google Play billing. Complete server requests first where possible, because resetting can lose the anonymous referral session needed to identify a profile. - **Assistance & Inquiries:** If you have any questions or require assistance regarding data deletion, email our privacy team at support@cibru.in. **Support requests:** When you email support, you choose what contact details, order/referral reference and issue information to provide. That correspondence is handled outside the app by the operator and its email provider. It is not removed by app deletion controls. Ask support about access/deletion of correspondence and applicable retention; do not send passwords, payment-card details, session cookies, purchase tokens or Integrity tokens. ## 5. Children's Privacy (COPPA & Google Play Families Policy) Our Application is intended for adults aged 18 and older and is not directed to children. We do not knowingly collect personal information from children. If you believe a child has provided personal information through the Application, contact us using the details below. ## 6. Third-Party Service Providers & Open-Source Libraries The Application relies on trusted third-party SDKs and open-source tools to deliver core capabilities: - **Google Play Billing, Google Play Services & Google AdMob:** For payments/entitlements, platform support, and advertising. Governed by Google Privacy Policy and Google Ads Policy. - **Google Play Integrity & Install Referrer APIs:** Integrity is used for purchase verification/deletion and referral registration; Install Referrer supplies attribution for referral participants. - **Supabase:** For cloud authentication, secure edge function execution, and PostgreSQL database storage for purchase verification and the optional Referral Rewards Program. Governed by the Supabase Privacy Policy. - **Google User Messaging Platform (UMP):** For consent information/forms and advertising privacy choices according to the deployed Google configuration. - **youtubedl-android / yt-dlp & FFmpeg:** Embedded local extraction, download, conversion, and muxing engines. Extraction/downloading contacts source servers; conversion/muxing executes on-device. These are not CIBRU cloud media-processing services. - **gallery-dl, Python & HTTP libraries:** Bundled locally for supported photo/gallery extraction. They contact the selected source platform and media hosts with the requested URL, connection metadata and applicable platform cookies; images are downloaded to your device rather than processed by a CIBRU media server. Coil similarly requests source thumbnails. These libraries do not make downloads a wholly offline operation. ## 7. Data Security Measures The current app uses the following protections, with limits that matter to your choices: - **Network Transport:** Supabase and platform-login endpoints use HTTPS. The Android manifest/network-security configuration disallows cleartext traffic for Android-managed connections. The app also uses embedded extractor/native networking; this setting alone is not proof that every third-party URL, redirect, or native-engine request is encrypted. - **Local Storage:** Core history/preferences, the purchase verification cache, and referral preferences/authentication use the Keystore-backed encrypted helper. Recovery may purge and recreate the affected preference file; if that fails, the helper uses temporary in-memory storage. Local records or sessions may therefore be lost during recovery. Purchase sync-control flags use separate Android private SharedPreferences without extra application-level encryption. WebView cookies, temporary cookie exports and partial-download work files are private sandbox files; public downloads are not encrypted by the app. Backup is disabled and purchase/referral/WebView exclusions are configured, but these protections are not a guarantee against every device or OS compromise. - **URL Validation:** The downloader validates input and blocks known unsafe/private-network destinations. Validation reduces risk; it is not a guarantee about every third-party server, redirect, or future source change. ## 8. Your Rights Under GDPR & CCPA/CPRA Depending on your geographic location, you may have rights under applicable privacy laws (such as GDPR in Europe or CCPA/CPRA in California): - The right to know what personal data is processed. - The right to access, rectify, or erase your data. - The right to withdraw consent for personalized advertising at any time. - The right to non-discrimination for exercising your privacy rights. Core downloading does not require a CIBRU account. Referral and purchase verification records have the separate scopes and retention limits above. Use our Data Deletion or Purchase Data Deletion instructions, or contact support for access, correction, withdrawal, or deletion requests. Provider logs/backups, shared Auth identities, and Google's transaction records are not erased by clearing local app storage. Optional-service processing may involve Google/Supabase infrastructure outside your country, under their applicable terms and safeguards. **Service configuration:** Supabase endpoints/public client keys, the Play Integrity cloud project number, Play products/base plans, paid-sales enablement, and AdMob IDs are configurable build/deployment values. Empty, test, or placeholder values do not certify a live service. No server secret or real user token belongs in these pages. Ask support to confirm the deployed service's data handling and retention if needed. ## 9. Updates to This Privacy Policy We may update this Privacy Policy to reflect changes in our legal obligations, features, or Google Play policies. Updated versions will be published with a revised "Effective Date" and version number, with any additional notice or consent required by applicable law. Check the published policy and app version when reviewing a change; this page does not promise an automatic in-app policy-update notification. ## 10. Contact Us If you have questions, concerns, or requests regarding this Privacy Policy or our data practices, please contact us at: - **Privacy Email:** support@cibru.in - **Support Email:** support@cibru.in - **Operator:** CIBRU (Proprietorship operated by Krishna moni Borah). - **Postal Address:** Kakojan, Jorhat, Assam - 785107, India. - **Developer Website:** https://cibru.in © 2026 CIBRU. All rights reserved. Legal Home • Privacy Policy • Terms of Service • Refund Policy • Purchase Data Deletion

Privacy Policy. Respect for your autonomy.

Have questions about your personal data?