Skip to content
myPeer

LEGAL & POLICIES

myPeer Cookie Policy

Last updated: July 20, 2026 • CoverPrime Technologies Private Limited

This Cookie Policy explains the cookies myPeer (mypeer.in) sets when you use our Platform, and should be read together with our Privacy Policy and Terms of Service. It is issued by CoverPrime Technologies Private Limited (“we”, “us”, or “our”). This policy lists every cookie myPeer sets. The list below is complete - if a cookie is not in this table, myPeer did not set it. 1. The Complete Inventory Cookie Purpose Type Lifetime mp_access Keeps you signed in for the current session (access token). HttpOnly - not readable by page scripts. Strictly necessary ~15 minutes mp_refresh Quietly renews your session so you are not asked for an OTP every 15 minutes (rotating refresh token). HttpOnly; scoped to the /auth path only. Strictly necessary 30 days mp_ref Referral attribution. Set only if you arrive via a doctor's invite link (mypeer.in/r/{handle}), so the inviting doctor gets credit if you later join and become verified. Functional (attribution) 30 days 2. What We Do Not Set

  • No advertising cookies: myPeer shows no ads and sets nothing for ad targeting or retargeting.
  • No cross-site tracking: Our anonymous view counting (see the Privacy Policy) uses a salted hash server-side and stores no cookie at all. 3. Why the Session Cookies Have No Opt-Out mp_access and mp_refresh are the account. myPeer is passwordless - these HttpOnly cookies are the only thing keeping you signed in after your OTP. Without them the service cannot function, so they are classified as strictly necessary and are set only when you sign in. They are never used for analytics or marketing. 4. The Referral Cookie and the Upcoming Consent Banner mp_ref is the one cookie that is not strictly necessary. Today it is set only in one narrow case: you clicked a doctor's personal invite link. It contains a referral marker, not your identity. A consent banner is planned. When it ships, mp_ref will be gated behind it: visitors arriving via an invite link will be asked before the attribution cookie is set, and declining will simply mean the inviting doctor does not receive credit - nothing else on the site changes. The strictly necessary session cookies will not be behind the banner, consistent with DPDP-era practice for essential cookies. 5. Controlling Cookies in Your Browser You can view, block, or delete cookies in your browser settings at any time:
  • Chrome / Edge: Settings → Privacy → Cookies and site data.
  • Safari: Preferences → Privacy.
  • Firefox: Settings → Privacy & Security. Notes on the effect:
  • Deleting mp_access / mp_refresh signs you out; you can sign back in with an OTP.
  • Blocking cookies for mypeer.in entirely will prevent sign-in (the session cannot be held), but public cards and doctor websites remain fully viewable - no cookie is required to read them. 6. Changes to This Cookie Policy myPeer reserves the right to amend this User Agreement at any time. In the event of material structural changes, you will receive an active notification inside your dashboard or via electronic mail at least fourteen (14) days prior to the enforcement of the revised terms. Continued utilization of the Platform following the conclusion of the notice period constitutes active consent to the updated terms. 7. Questions Questions about this Cookie Policy can be directed to support@mypeer.in.