Privacy Policy for EchoBridge | Cibru

Privacy Policy - EchoBridge | CIBRU # Privacy Policy EchoBridge · Operated by CIBRU Effective date: October 20, 2026 · Version 1.2 > **Privacy summary:** EchoBridge's audio path is directly between your Android device and the Windows computer you connect to, intended for your local network (LAN), rather than through CIBRU's cloud. This does not make the whole app offline: the Android app also uses external services for Google Play billing, purchase verification, referral rewards, installation attribution, integrity checks and advertising when configured. Referral syncing is enabled by default unless locally paused, without a separate email or password login. ## 1. Operator and scope CIBRU operates EchoBridge, including the Android app (package `com.echobridge.app`), Windows companion and associated services. Contact support@cibru.in for privacy requests. A website hosting these pages may separately explain its own cookies or analytics; this policy describes the application and its associated services. **Postal Address:** Kakojan, Jorhat, Assam - 785107, India. ## 2. Audio and connection information - **Computer audio:** The Windows companion captures the selected playback device's audio and sends it to your connected Android device. This may include sounds from other applications using that output. - **Microphone:** With microphone permission, an audio session can open and read the microphone, including while the microphone toggle is muted. Muting or a free-tier pause suppresses transmission and replaces captured frames with silence; it does not release the microphone recorder. Enabling the microphone or push-to-talk sends audio to the connected computer. Nearby voices may be included. Disconnect or revoke microphone permission to stop capture. - **Live processing:** Audio is encoded, transmitted, buffered and played for the connection. EchoBridge does not provide a built-in recording archive or upload these streams to CIBRU's purchase, referral or advertising services. - **QR camera pairing:** If you choose QR setup, camera frames are processed on your device to read a connection code. EchoBridge does not save or upload these camera images. The decoded host address, port and pairing PIN are used to connect to the selected computer. - **Connection data:** The apps process IP addresses, ports, computer names from LAN discovery, pairing PINs, session keys, selected audio devices and connection status to discover, authenticate and operate the bridge. The intended connection is directly between your devices on a local network. Manual and QR host addresses are not restricted to private IP addresses; traffic follows the address and network route you choose. Audio routed into other programs on the receiving computer may be recorded or transmitted by those programs according to their settings. Choose the correct devices and disconnect when finished; EchoBridge does not control other programs' processing. ## 3. Settings and local records The apps process audio routing, volume, microphone state, connection details and stream statistics. Theme and appearance preferences are stored locally. Android stores purchase-verification state, referral preferences and authentication credentials in app-private storage protected by Android application isolation; these records are not all separately encrypted. Purchase and referral preferences and credentials are excluded from configured Android backup and device-transfer rules. Other eligible settings may be backed up according to your device settings. Technical errors and connection diagnostics may appear in Android device logs. The Windows companion attempts to write `startup.log` and `crash.log` beside its executable; these may contain startup details and exception information. Its Copy PIN and Copy diagnostic logs controls write to the system clipboard. Diagnostics can include network addresses, the connected client, selected audio output, network adapter names and stream statistics. Clipboard history/sync and other apps may retain copied content under their settings. If you send logs, screenshots or a message to support, we receive the information you include and your contact details. Review attachments and remove private content and credentials. ## 4. Google Play purchases Google Play handles payment and the purchasing account. No separate CIBRU login is required to buy or restore subscriptions, and the app does not receive full payment-card details. The app receives and can store raw purchase tokens, product identifiers, purchase status and available order information in app-private preferences. Verification sends the app identifier, product identifier, raw purchase token, a unique request identifier, a request-bound Google Play Integrity token and, when available, the order ID over HTTPS to the configured verification service. Deletion requests also send the raw purchase token and verification proof. The app uses the returned subscription status, expiry and server verification time to determine paid access and cache freshness. These requests do not include audio content. Billing connections, product/purchase queries and automatic verification can occur on app startup or resume, without an audio session. A saved purchase sync pause stops backend purchase verification, not Google Play queries or all provider traffic. The app's deletion control requests deletion from the configured service; a successful response is its acknowledgement, not independent proof that all service logs, backups or Google records have been erased. Contact support for service-side storage and retention details. ## 5. Referral rewards and automatic syncing Unless paused, the app initializes referral syncing automatically. With the referral service configured and reachable, it may create or restore an anonymous authentication session with a Supabase-hosted service when you open the app, without an email or password. “Anonymous” describes the sign-in method: profile and device records are pseudonymous and can still relate to an installation. An unconfigured or unavailable service cannot verify rewards. For referral registration, the app reads Android's signing-key/user/device-scoped Android ID and derives an app-specific SHA-256 device hash on the device. The raw Android ID is not included in the app's referral requests; no shared or random fallback is used when the ID is invalid or unavailable. Requests send that pseudonymous hash, the app identifier, authentication credentials, Google Play Install Referrer information (raw referrer string, any embedded referral code and server-reported installation/click timestamps), a unique request identifier and a request-bound Google Play Integrity token. Authentication can send a refresh token. Status responses contain profile/app identifiers, referral code, referral eligibility/count, reward expiry and verification time. We use these records for installation attribution, reward calculation, verification, rate limits and fraud prevention. Sharing invitations is optional and no purchase is required. A code shown in the app is not proof of successful server verification. **Unsync / Pause referral sync** persistently pauses referral work, clears local profile/code/count and installation/referrer caches, and invalidates verified VIP access; paid subscription access is separate. **Delete referral data** does this before the network request, even if it fails, retaining authentication so the request can identify the existing session. Locally stored referral authentication credentials are cleared after acknowledged deletion. Only explicit **Restore Purchases** resumes saved purchase and referral sync pauses within the app, before the Play result and even if no paid purchase is found. It can reuse retained credentials or create a new anonymous session after their deletion, but does not recreate deleted rewards. Opening Referral Rewards, retrying, sharing or starting a new purchase does not clear saved pauses. Clearing app storage or reinstalling resets local preferences and can enable default syncing or create a new session. See Data Deletion and Unsync. When you choose to share an invitation, the app passes your referral link to Android's share sheet and the app/recipient you select. If sharing is unavailable, it can copy that link to the system clipboard and notify you. This is not general clipboard or keystroke collection; the destination app's processing is separate. ## 6. Advertising The free tier uses Google Mobile Ads (AdMob), including native, app-open and interstitial formats when configured. Google and its partners may process IP addresses, advertising/device identifiers, app interactions, diagnostics and ad-performance information for advertising, measurement and fraud prevention. IP addresses may indicate general location. The app uses the SDK's ad-request APIs; it does not establish a guarantee of non-personalized advertising, zero tracking or zero SDK collection. Personalization and provider processing depend on SDK/provider settings, applicable requirements and available choices. Active verified paid Premium or referral VIP access suppresses in-app ad requests and displays. This does not erase previously collected data or necessarily prevent SDK initialization or all service communication. EchoBridge does not send its audio streams as advertising data. The current app does not provide an in-app advertising-consent or privacy-options screen. Review advertising controls available in Android and your Google account; changing an advertising ID or personalization setting does not stop all provider processing. See Google's Privacy Policy and how Google uses information from partner apps. Advertising choices do not cancel subscriptions or delete purchase/referral records. ## 7. Recipients and international processing Data goes to the device you connect to, Google for billing, installation attribution, integrity verification and advertising, and configured Supabase-hosted services for authentication, purchase verification and referrals. Infrastructure may process IP addresses, request times and operational/security logs. See Supabase's Privacy Policy. Relevant information may be disclosed to providers supporting these purposes, to meet legal obligations, or to investigate fraud and protect rights and security as permitted by law. We do not sell your audio content. Providers may process data outside your country, subject to applicable data-protection requirements and service arrangements. ## 8. Retention - **Audio:** Temporary live-stream buffers, not a CIBRU recording archive. Disconnect stops the recorder and transport; this is not a promise of secure memory erasure. - **Local records:** Until replaced, reset or removed, subject to operating-system backup behavior. - **Referral caches:** Unsync and referral deletion immediately clear local referral profile/code/count, registration/referrer caches and VIP verification, retaining the persistent pause. Unsync retains local referral authentication credentials so you can explicitly request server deletion. Those credentials are cleared after acknowledged referral deletion. Unsync alone does not request service-side deletion. - **Purchase caches:** Local paid access is disabled and syncing is paused before purchase deletion. Known/pending purchase records and entitlement cache are cleared after all requested deletions are acknowledged; failed requests may leave identifiers for retry and some earlier requests may already have succeeded. Pause metadata and a local random cache-namespace identifier remain; clearing app storage removes them. That identifier is not sent as purchase-ownership proof. - **Service-held data:** Contact support@cibru.in for current retention periods, deletion scope and any remaining verification, authentication, security or legal records. No fixed server purge deadline or hash-only storage guarantee is made here. Clearing local credentials is not deletion of a service-side authentication account. In-app deletion does not itself establish erasure of provider logs/backups, Google-held records or support correspondence. These are separate from the app's local caches and deletion requests. Support correspondence is retained as needed to resolve and document requests and meet applicable obligations. Contact us for a broader deletion request or an explanation of retained records. ## 9. Permissions and security The Android app declares these permissions: - **`RECORD_AUDIO`:** microphone capture for phone-to-PC audio. The app requests it at startup; permission does not itself enable transmission. Disconnect or revoke permission to stop capture. - **`CAMERA`:** optional QR pairing, requested when you choose scanning. Manual connection setup is available; camera hardware is not required. - **`INTERNET`, `ACCESS_NETWORK_STATE`, `ACCESS_WIFI_STATE`:** LAN connections, connection monitoring/Wi-Fi state and online billing, referral, integrity and advertising requests. - **`CHANGE_WIFI_MULTICAST_STATE`:** Wi-Fi multicast-lock support for local discovery. - **`MODIFY_AUDIO_SETTINGS`:** audio routing/settings used by the bridge. - **`WAKE_LOCK`, `FOREGROUND_SERVICE`, `FOREGROUND_SERVICE_MEDIA_PLAYBACK`, `FOREGROUND_SERVICE_MICROPHONE`:** power/network locks and the ongoing audio service. - **`POST_NOTIFICATIONS`:** service status and disconnect notification, requested on Android 13 and later. The final merged manifest also includes `com.android.vending.BILLING`, `com.google.android.finsky.permission.BIND_GET_INSTALL_REFERRER_SERVICE`, `com.google.android.gms.permission.AD_ID`, `android.permission.ACCESS_ADSERVICES_AD_ID`, `android.permission.ACCESS_ADSERVICES_ATTRIBUTION` and `android.permission.ACCESS_ADSERVICES_TOPICS` from the billing, installation attribution and advertising SDKs. The app does not request Bluetooth, location, contacts, calendars, accessibility/keystroke access or shared-storage/media access. This does not prevent providers from estimating general location from IP addresses or processing identifiers under their policies. Review the permissions shown for your installed release in Android settings. Background playback and microphone transmission require active verified paid Premium or referral VIP access. Free-user playback and transmission pause when the app leaves the foreground or the screen is locked. Muting/pausing transmission can leave the microphone recorder open, as explained above. Audio payloads use PIN-derived session keys and AES-GCM encryption. LAN discovery and TCP control messages are not protected by TLS and can expose computer names, connection metadata and stream-control state on the network. Purchase and referral requests use HTTPS when configured. These measures do not make compromised devices, exposed PINs or all network metadata private. Use trusted devices and networks and keep software updated. No transmission or storage method is completely secure. ## 10. Choices and privacy rights You can stop microphone transmission, disconnect to stop capture, revoke microphone or camera permission in Android settings, clear local data, pause referral syncing, request referral or purchase-record deletion and manage subscriptions in Google Play. Deletion and cancellation are separate. See Data Deletion for instructions and retained records. Depending on applicable law, you may request access, correction, deletion, a copy of your information, restriction or objection to processing, and withdrawal of consent where processing relies on consent. You may also complain to a competent data-protection authority. Email support@cibru.in. We may need proportionate ownership verification; a public referral code alone is insufficient. ## 11. Children and changes EchoBridge is a general-audience utility not directed to children under 13 or the applicable minimum age in their country. If you believe a child has provided personal information to us, contact support for review and action required by law. We may revise this policy as the app or requirements change, update the effective date and provide additional notice where required. Questions: support@cibru.in. © 2026 CIBRU · support@cibru.in Privacy · Terms · Subscriptions and refunds · Referrals · Data deletion

Privacy Policy. Respect for your autonomy.

Have questions about your personal data?