Data Deletion Policy. Transparent control over your information.

Data Deletion Policy | Mic to Headphone · CIBRU **CIBRU · Mic to Headphone** # User Data Deletion Policy & Instructions **Mic to Headphone · com.mictoheadphone** **Effective Date**: October 20, 2026 **Developer**: CIBRU · **Support**: support@cibru.in Mic to Headphone does not create a user-facing CIBRU account. Its live microphone audio is processed in ephemeral device memory and is not recorded or uploaded. Optional purchase and referral features can still create local service state and network records, so deletion is described by data type below. ## Data Retention and Deletion Overview Data category Storage or provider What the available control does **Microphone audio** Volatile audio buffers on the device only No recording is created; buffers are discarded as the session runs and closes. **Play purchase verification** Private app preferences and the Supabase purchase service Delete Purchase Data pauses local Play sync and requests deletion for purchase records known to the installation. A one-way backend deletion marker may remain for safety/retention. **Referral profile and installation data** Private referral preferences/session and Supabase Unsync disables referral synchronization and clears this installation's referral cache/preferences and local Auth session. It does not delete server records. Contact support to request an app-scoped server deletion review. **Local preferences and temporary files** Android DataStore, shared preferences, and cache **Clear storage** or uninstall removes the app's local settings and service state. **Clear cache** removes temporary cache files but does not remove DataStore/shared preferences or server data. **Google Play and AdMob data** Google Play / Google AdMob App controls do not erase Google Play order history or Google's ad-service records. Use Google's account, Play, and advertising privacy controls. ## 1. Purchase Verification Deletion In the Premium Subscription sheet, tap **Delete Purchase Data** and confirm, even if the purchase is pending, expired, or inactive. The app persists a Play-sync pause before making deletion requests and invalidates in-flight verification results. It requests deletion for purchase tokens it can identify locally. If all requests are confirmed, local purchase tokens/order IDs and paid entitlement state are cleared; the sync pause, generation counter, and separate random cache-scope identifier remain. If a request fails, local records may remain for retry using the same control. With no locally known tokens, only local cleanup can be performed; contact support for server records on other installations. Automatic syncing stays paused until you explicitly tap **Restore Purchases**. The Supabase purchase endpoint verifies the purchase with Google before processing the request. It removes the app-scoped purchase row and billing job when successful, but keeps a one-way purchase-token hash deletion marker until 90 days after the later of the deletion time or verified subscription expiry. Cleanup depends on backend maintenance. This does not erase Google's purchase history or cancel billing. See the Purchase Data Deletion Guide. ## 2. Referral Unsync and Server Deletion Request Before unsyncing, note your referral code if you intend to request server deletion. The Referral Unsync Tool opens `mictoheadphone://referral/unsync` in the app. The app turns referral synchronization off, invalidates and cancels in-flight referral work, clears local referral preferences/cache and the local anonymous Auth session, and resets the displayed referral status. A stored disabled flag remains across restarts. Referral benefits stop on this installation while unsynced; separately verified paid access is unaffected. The deep link does **not** call the server deletion endpoint. To request app-scoped referral deletion, email support@cibru.in with your referral code and a description of the request. A successful authenticated backend deletion can remove the app's referral profile, referral events, and installation records, but the service may retain a one-way deleted-device key for 90 days to prevent immediate re-registration. The shared anonymous authentication identity is not deleted by the app-scoped referral endpoint. We cannot promise deletion until the relevant service confirms it. ## 3. Local Storage Erasure - Open **Android Settings** > **Apps** > **Mic to Headphone** > **Storage & cache**. - Choose **Clear storage** to remove local DataStore preferences, subscription/referral shared preferences, cached service state, and the locally stored anonymous referral session. - Choose **Clear cache** only when you want to remove temporary cache files. It does not replace Clear storage and does not affect Google, Supabase, or other server records. Uninstalling the app also removes its local sandbox. It does not cancel Google Play subscriptions, erase Google Play order history, delete AdMob records, or automatically request Supabase deletion. A full storage reset also removes local sync-pause choices. After reinstalling or clearing storage, normal default referral and Play initialization may run again. Complete any needed server-deletion request before erasing the identifiers needed to locate it. © 2026 CIBRU · support@cibru.in