Referral Program Terms — Mic to Headphone | Cibru

Referral Rewards Terms | Mic to Headphone · CIBRU **CIBRU · Mic to Headphone** # Referral Rewards Program Terms **Mic to Headphone · com.mictoheadphone** **Effective Date**: October 20, 2026 **Developer**: CIBRU · **Support**: support@cibru.in ## 1. Program Overview The Mic to Headphone Referral Rewards Program lets eligible users invite friends and earn Premium ad suppression and extended-session/background benefits. Rewards have no cash value, are not transferable, and remain separate from Google Play subscriptions. Inviting friends is optional. The current Android client initializes referral synchronization by default on a fresh installation; you can turn it off through the Unsync flow. No email address, password, phone number, or social-login form is required. The referral service uses an anonymous Supabase Auth session and pseudonymous app-scoped identifiers. ## 2. Five Reward Milestones When the backend accepts eligible, non-duplicate referral installations, rewards are applied once at these referral-count milestones: Verified referrals Reward at milestone Days credited at this milestone **3** 1 Month Premium 30 days **5** 2 Months Total 30 more days (60 credited across milestones) **10** 6 Months Total 120 more days (180 credited across milestones) **15** 1 Year Total 185 more days (365 credited across milestones) **100** Lifetime Premium 36,500 days, the program's 100-year grant Days are added to the later of the current time or existing referral expiry. The month/year labels summarize milestone grants, not the amount of time remaining today. **Lifetime Premium** is the program name for the 36,500-day grant, not a promise of an infinite expiry or perpetual service availability. Referral-based access requires a successful server response and a fresh cache, valid for up to **24 hours offline**, within the server-provided expiry and on the same Android boot. This differs from the purchase verification cache. A verified paid subscription takes priority for access while both exist, but does not erase referral reward records or pause their expiry. Earning a referral reward does not cancel or refund a paid subscription. ## 3. Attribution, Identifiers and Eligibility - **Install Referrer:** The app reads the Google Play Install Referrer value and install/click timestamps. A referral code is accepted only when it matches the app's expected `REF-[0-9A-F]{32}` format. - **Hashed installation identifier:** The app derives an app-namespaced SHA-256 value locally from Android's app-scoped ID. The legacy request field named `android_id` carries that derived value, not the raw Android ID. The backend further derives a one-way HMAC device key for duplicate checks; hashing does not make the installation untraceable. - **Integrity-bound registration:** The app sends the app ID, derived installation identifier, referrer payload/timestamps, fresh request ID/hash, and Play Integrity proof to Supabase over HTTPS. The anonymous Auth session authenticates the request. Play Integrity is an app/device check, not proof of a person's identity. - **Duplicate and abuse checks:** The backend can reject a repeated device registration, an invalid or self-referral, an ineligible install, an unresolved click timestamp, an invalid Integrity result, or rate-limited requests. A referral link alone does not guarantee credit. - **Reward scope:** Approved rewards grant ad-free Premium-style access in this app only. They do not transfer to another CIBRU app, account, device, or person and cannot be redeemed for money. ## 4. Anti-Fraud and Program Changes Self-referrals, emulator or device spoofing, bot networks, click fraud, automated installation scripts, and attempts to bypass Play Integrity or the referral service are prohibited. CIBRU may decline, reverse, or stop rewards that the backend marks as invalid or fraudulent. Referral counts, eligibility, and reward expiry are determined by the service response, not by a client-side claim. ## 5. Unsyncing and Deletion Before unsyncing, note your referral code if you need support with server deletion. Use our Referral Unsync Tool to turn off synchronization on this installation. Unsync invalidates/cancels local sync work, clears local referral cache/preferences and the anonymous Auth session, and keeps a disabled flag across restarts. Referral benefits stop on this installation while unsynced. It does not send a server-deletion request, remove the server reward history, or cancel or change verified paid access. To request deletion of the app-scoped referral profile, events, and installations, contact support@cibru.in. A successful backend deletion is required; the service may retain a one-way deleted-device key for 90 days to prevent immediate re-registration, and the shared anonymous authentication identity is not deleted by this app-scoped operation. © 2026 CIBRU · support@cibru.in

Referral Program Terms. Milestones, rewards & anti-abuse rules.

Questions about your referral balance or rewards?