Privacy Policy for EVON | Cibru

Privacy Policy | EVON · CIBRU **CIBRU · EVON** # EVON Privacy Policy **EVON · com.evon.app** **Effective Date**: October 20, 2026 **Developer**: CIBRU **Contact**: support@cibru.in **Postal Address:** Kakojan, Jorhat, Assam - 785107, India ## 1. Overview EVON shares the host's screen and supported internal device audio with approved receivers over local Wi-Fi or a personal hotspot using direct peer-to-peer WebRTC connections. The media path works without an internet connection; online purchase verification, optional referrals and advertising are separate services. Local sharing does not require email registration or a social login. ## 2. Data We Process ### Local Screen & Audio Sharing Screen frames and supported playback audio are processed in memory and sent directly to approved receivers. EVON does not save recordings or upload this media to CIBRU, Supabase or advertising servers, and does not use a cloud media relay. Local discovery advertises the host display name, local IP address/port, session identifier and pairing availability to devices on the same network; pairing and connection metadata are also exchanged locally. Use a trusted network and approve only intended receivers. ### Android System Permissions - **Screen Capture (MediaProjection):** Android requests your explicit consent before initiating any screen-sharing session. You can stop sharing at any moment from the in-app dashboard or the Android system notification bar. - **Audio Recording:** Android's `RECORD_AUDIO` permission supports AudioPlaybackCapture for permitted device playback audio on Android 10+. EVON's audio feature is not voice recording; the WebRTC microphone input is muted and its outgoing buffer is replaced with playback audio or silence. Audio availability depends on Android and the source app's capture rules. - **Camera:** Used by a receiver to scan the host's pairing QR code. Scanner frames are processed locally and are not uploaded. - **Network State, Wi-Fi State & Nearby Wi-Fi Devices:** Support network detection, local discovery (NSD / mDNS) and direct streaming. Nearby Wi-Fi is declared with `neverForLocation`; EVON does not request precise or coarse location permission. - **Foreground Service, Notifications & Wake Lock:** The media-projection foreground service and ongoing notification support active sharing and its stop controls; wake-lock permission supports keeping the device awake. Android may still stop a service. - **Internet Permission:** Used for local sockets and online services including Google Play Billing, Integrity verification, referral syncing when enabled, and advertising SDK requests. The merged SDK manifest additionally declares Google Play billing and Install Referrer binding, advertising ID (`AD_ID`), and Android AdServices ID, attribution and topics permissions. Google Mobile Ads may use the applicable advertising APIs. Its browser, dialer, SMS and calendar intent queries support external ad actions; they are not permissions to read your messages, calendar or contacts. EVON does not request Bluetooth, storage/media-library, contacts, calendar, SMS or accessibility/keystroke-monitoring permissions. EVON does not independently read files, typed text or calendar entries. Content visible in a shared screen area, including text or notifications, can nevertheless be seen by approved receivers. Receivers are view-only and cannot inject remote input, but may record or disclose content independently. Stop sharing to end transmission; in-app data deletion cannot erase copies made by receivers. ### Referral Rewards System (Optional) Participation is optional. Open "Get Free Premium", read the notice and tap **"Agree & start earning"** to enable referral registration and synchronization. Opening or dismissing the screen alone does not enable it. Before agreement, EVON does not start referral authentication, attribution or registration requests. While enabled, status can refresh on app startup and resume: - We process a pseudonymous Supabase authentication identifier and access/refresh session credentials (no email or password registration is required). Profile identifiers, invite codes, qualifying counts and reward expiry are returned to the app. - An app-scoped SHA-256 installation hash, generated from a random installation identity, is sent over TLS for installation deduplication. The referral identity code does not read Android ID, advertising ID, IMEI or MAC address. - Google Play Install Referrer text and install/click timestamps are processed for attribution. - A request identifier, app identifier and request-bound Google Play Integrity token are sent for registration and anti-abuse verification. Referral requests use the shared CIBRU Supabase backend over TLS and Google services for attribution and Integrity proof. Tap "Unsync" in "Get Free Premium" or visit the unsync page, then use its `evon://referral/unsync` link. Unsync stops referral syncing and local VIP access across app restarts; it does not delete server records or pause reward expiry. You can agree again to resume after unsync. Referral data deletion imposes a separate persisted pause that only an explicit "Restore Purchases" action clears; referral agreement is then required again. ### Subscription Verification (No CIBRU Account) When you purchase, restore, or refresh a Weekly, Monthly or Annual Google Play subscription (including an eligible trial): - The shared CIBRU Supabase verifier receives your Google Play purchase token, subscription product identifier, app identifier, requested action and random request identifier over TLS. - A Google Play Standard Integrity token is bound to a hash of the verification or deletion request to help the backend check request integrity. - EVON stores verification status, expiry and the order identifier supplied by Google Play, when available. A random installation cache identifier stays local; it is not sent as proof of purchase ownership. Purchases are processed directly through Google Play Billing using your purchasing Google Play account. No CIBRU email account, password, OTP, or third-party sign-in is required. EVON does not receive payment card numbers or banking credentials through the purchase flow. Restoring purchases on another device requires the same purchasing Google Play account. Startup and resume can query Play and refresh verification unless this installation's purchase-sync pause is set. ### Advertising EVON integrates Google Mobile Ads (AdMob) for interstitial, native and banner placements for free users. Ads may appear on app screens, on returning to the app, or around viewer pause/resume interactions, depending on the placement. Paid Premium and active Referral VIP suppress EVON ad display. The SDK can collect and share IP address (including approximate location derived from it), advertising or other device identifiers such as app set ID and, where applicable, account-related identifiers, device/app information, diagnostics and app/ad interactions for advertising, measurement and fraud prevention. Ad requests are separate from local screen/audio sharing. Premium ad suppression does not itself disable SDK initialization or guarantee that no SDK network request occurs. See Google's Mobile Ads data disclosure and Google Advertising Privacy. Android advertising-ID controls are available in device settings. Referral agreement, Unsync and deletion controls apply to their named feature; they are not advertising consent or a global switch for Google SDKs. The current app does not provide an in-app advertising-consent or privacy-options form. Release ad loading is off by default and requires configuration. Device/provider privacy controls do not delete CIBRU purchase or referral records. ### Storage & Security Exclusions EVON keeps referral sessions, installation hashes, purchase tokens and entitlement caches in app-private storage excluded from Android backup/transfer. Offline paid access expires before 72 hours from verification and referral VIP before 24 hours, never beyond their verified expiry; a device restart requires fresh verification. Identical verification responses do not renew these limits. Bounded hashed security watermarks remain locally through unsync and deletion to prevent stale-response replay. Purchase deletion clears local plan, order and displayed expiry metadata immediately; failed token/product targets, installation identifiers, settings and security history can remain until deletion succeeds or Android app storage is cleared, as applicable. These access limits are not server-record retention or automatic-erasure deadlines. ## 3. Data Retention and Deletion ### In-App Purchase Verification Data Deletion In the EVON Premium dialog, you can tap **"Delete purchase verification data"** at any time: - Confirmation immediately pauses automatic purchase syncing across app restarts and removes locally verified paid access. Backend deletion targets only purchase tokens known to this installation. - A failed network or verification request is not confirmed deletion. Failed targets remain locally for retry by using the same deletion control online; they are not automatically retried while sync is paused. Older or unavailable purchases need support assistance. - Deletion does not cancel recurring billing, issue a refund, erase Google's transaction records, or delete referral data. Manage renewal in Google Play Subscriptions. - Only Restore Purchases clears the deletion sync pause and can recreate eligible verification records. A new purchase does not clear this pause. See Purchase Data Deletion. ### Referral Unsync & Data Deletion - **Unsync:** Use the unsync page to disable referral syncing and local VIP access on this installation. A valid paid subscription is separate. - **Referral Data Deletion:** Use "Delete Referral Data" in "Get Free Premium" to clear local referral profile/reward state, disable agreement and persistently pause referral syncing. EVON requests app-scoped backend deletion with the stored referral session and clears those local credentials after backend confirmation. Unconfirmed requests retain credentials privately for retry through the same deletion control. Without a usable session, local clearing is not proof that unknown server records were removed. The one-way installation hash remains through deletion; clearing app storage resets it. - **Support:** Email support@cibru.in for unavailable records. Ask support to confirm removal and any retained anti-abuse or legally required records. Clearing storage or uninstalling does not send a server deletion request. Play restoration clears the referral deletion pause, not the deleted reward history, and does not automatically re-enable referral participation. Sync pauses apply only to this installation, not your Google account or other devices. Other installations can continue syncing and may recreate eligible purchase-verification records. Clearing storage or reinstalling removes pause choices and retry credentials without deleting server data. Restore Purchases can clear the referral deletion pause before Play reports a result, even if no purchase is found; it never automatically re-enables referral agreement or restores deleted rewards. ### Support-Assisted Requests For access, correction, deletion or retention questions, email support@cibru.in. We receive your email address and the information you choose to send to handle the request. State whether it concerns referral records, purchase verification or both. Ask for confirmation of deletion scope and any retained security, backup or legally required records and their retention period. This policy does not promise a fixed backend-erasure deadline. Do not send raw tokens, passwords, private screen content or financial credentials. ## 4. Third-Party Services - **Google Play Billing, Integrity & Install Referrer:** Provide store purchases, app/device integrity signals and install attribution under the Google Privacy Policy. Google maintains its own transaction and service records. - **Google Mobile Ads (AdMob):** Displays advertisements for free-tier users under Google Advertising Privacy. - **Supabase:** Hosts CIBRU's authentication, database and Edge Functions for the online flows described here. EVON records are handled on CIBRU's behalf; direct requests about those records to CIBRU. Supabase's Privacy Policy explains its own services and its processor role, rather than replacing this EVON policy. Online service providers receive network connection information such as your IP address and request timing when contacted. Their processing may occur outside your country. Contact CIBRU for deployment-specific storage and retention information. Deleting EVON records does not erase Google's independently held data, provider security records or information you send to an external site or sharing app. ## 5. Contact & Grievance For questions regarding this Privacy Policy or your data: - **Email:** support@cibru.in - **Publisher:** CIBRU (cibru.in) © 2026 CIBRU · support@cibru.in

Privacy Policy. Respect for your autonomy.

Have questions about your personal data?