Skip to content
myPeer

LEGAL & POLICIES

myPeer Privacy Policy

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

myPeer (mypeer.in) is a brand owned and operated by CoverPrime Technologies Private Limited ("we", "us", or "our"). This Privacy Policy explains what personal data we process, why we do so, and the rights you hold under India’s Digital Personal Data Protection Act, 2023 (DPDP Act). Under the DPDP Act, Cover-Prime Technologies Private Limited acts as the Data Fiduciary, and you are the Data Principal. myPeer is exclusively for registered medical practitioners aged 18 and above; we do not knowingly collect or process personal data belonging to children.

1. Data We Collect

Your primary account identity is your mobile number, verified exclusively via One-Time Password (OTP) - there is no password and no sign-up form. Beyond this, we collect the personal data you voluntarily provide to complete your profile and use the platform:

  • Onboarding & Profile: Collected through a guided 6-step form - name, date of birth, marital status, medical registration number and council, specialization, degree, years of experience, spoken languages, city, and state.
  • Private Fields: Date of birth and marital status are strictly private, never displayed publicly, and used solely for profile completeness and CoverPrime policy matching.
  • Website & Clinic Details: Clinic name, address, phone, email, hours, “about/philosophy” text, social links, and contact-button targets (call/WhatsApp/booking URL) that you enter through the website builder.
  • “Find Your Clinic” Lookup: When you search for your clinic, your query is sent to the Google Places API through our server - the API key never touches your browser - solely to auto-fill clinic details.
  • Document Uploads: Your medical registration certificate, degree certificate, and other supporting documents, uploaded directly to secure storage via short-lived presigned URLs.
  • Photo Uploads: Your profile photo and clinic photographs. Initial processing (cropping, straightening, background removal) happens locally in your browser; we only store the final images you approve.
  • Cookies: First-party only. An httpOnly session cookie is set on login, and a 30-day referral-attribution cookie is set when a visitor arrives via a /r/{handle} invite link. We use no third-party advertising or cross-site tracking cookies or pixels.
  • Consent & Terms Records: Every consent grant/withdrawal and every Terms of Service acceptance is logged with a timestamp, IP address, user-agent, and device information.
  • Grievance Submissions: Your email, subject, and message when you contact us through the grievance form.

2. Purposes and Legal Bases for Processing

In accordance with all the relevant laws, each category of data is processed for a specific, notified purpose, and only on a valid legal basis:

  • Mobile number & OTP records: Used for authentication - OTP login and session management - on the basis that this is necessary to provide the service you requested.
  • Profile, degree & specialization details: Used for medical identity verification (certificate OCR via AWS Textract, plus human admin review), processed on the basis of your consent and because verification is explicitly requested by you.
  • Profile & clinic details: Used to generate and host your public digital card and personal website, processed on the basis of your consent - you choose what gets published.
  • Date of birth & marital status: Used for profile completeness and CoverPrime policy matching, processed on the basis of your consent; these fields are optional and kept strictly private.
  • Referral cookie / handle: Used to run the referral recognition program, where only verified referrals count and no cash changes hands, processed on the basis of your consent and legitimate service operation.
  • CoverPrime membership data: Used to power “My Policy,” a read-only mirror of your membership, processed on the basis of your consent and performance of the service you requested.
  • Consent ledger & terms-acceptance records: Used to maintain legal proof of consent and DPDP compliance, processed on the basis of our compliance with a legal obligation.
  • Anonymous session-hash events: Used to show aggregate, anonymous usage statistics such as card and website views, with no per-visitor tracking; this data contains no personal information, so it is processed as a legitimate service operation.
  • Grievance submissions: Used to handle grievances and DPDP data-rights requests, processed on the basis of our compliance with a legal obligation.

3. Personal Data We Hold, by Category

For clarity, here is every category of personal data we hold and what it includes:

  • Identity: Your mobile number (the primary identifier) and, your email address.
  • Personal: Your full name, date of birth, and marital status. The latter two are private and never shown publicly.
  • Professional: Your registration number and council, degree, specialization, years of experience, languages, city, and state.
  • Clinic: Your clinic's name, address, city, phone, email, hours, map link, booking URL, and social links.
  • Media: Your profile and clinic photographs.
  • Sensitive documents: Your registration and degree certificates, which contain personal data and signatures.
  • Membership : Your CoverPrime membership number, validity dates, and certificate link.
  • Compliance metadata: Your IP address, user-agent, and device information, stored only within consent-ledger and terms-acceptance records.
  • Security: OTP codes (stored hashed, never in plaintext) and refresh tokens (stored hashed). We do not collect passwords (the platform is passwordless) or payment/billing information (myPeer is free in this phase). Our analytics deliberately store no IP address, name, or phone number.

4. Your Consent, on the Record

Every instance of consent you grant or withdraw - and every Terms of Service acceptance - is permanently recorded in an append-only, versioned ledger, logging what was consented to, the active policy version, a timestamp, your IP address, browser user-agent, and the screen where the action occurred. Withdrawing consent is always one tap within your account settings, and is designed to be as easy as granting it. If you delete your account, ledger entries survive exclusively as an anonymized audit record - the account link is removed and your IP, user-agent, and device information are scrubbed - so we can demonstrate historical compliance without retaining your identity.

5. Communications: Service Messages vs. Promotions

  • Service Messages: OTPs, identity verification results, security alerts, and critical account notices. These are transactional and always enabled, since the platform cannot function without them.
  • Promotional Messages: Our weekly digest, product updates, and special offers. Every notification channel is strictly opt-in and off by default; you can toggle it off at any time with a single tap.

6. Cookies

myPeer sets first-party cookies only: an httpOnly session cookie on login, and a 30-day referral-attribution cookie when you arrive via a /r/{handle} invite link. We use no third-party advertising or cross-site tracking cookies or pixels. For a complete breakdown, please review our Cookie Policy.

7. Where Your Data Is Stored

  • Structured data (profiles, accounts, ledgers): Held in PostgreSQL hosted on Neon, a managed serverless Postgres provider.
  • Files (photos, certificates): Held in AWS S3, in the ap-south-1 (Mumbai, India) region, in a private bucket with Block Public Access enabled and no public reads.

8. Data Processors and Third-Party Disclosures

We do not sell your personal data. We share it only with the following contracted service providers, each engaged for a specific operational purpose, or when disclosure is required by law:

  • Neon: Hosts our managed Postgres database. Currently processed in AWS us-east-1 (USA) - see the data-residency note above.
  • Amazon Web Services (AWS): Provides private file storage (S3) and certificate OCR processing (Textract), in the Mumbai, India region (ap-south-1).
  • Google: Powers the “Find Your Clinic” lookup through the Places API, called server-side only.
  • CoverPrime : Supplies the read-only mirror of your membership shown under “My Policy,” processed in India.
  • MSG91 / CERF: Will handle SMS and WhatsApp delivery once live - processing location to be confirmed.
  • Resend / PinchApp: Will handle email delivery once live - processing location to be confirmed. Each sub-processor is expected to be bound by a data-processing agreement consistent with our DPDP obligations.

9. Security Measures

  • Passwordless authentication: No password store; OTPs are hashed (HMAC-SHA256), single-use, attempt-capped, rate-limited, with a resend cooldown and a per-mobile daily ceiling.
  • Session security: Short-lived access tokens with rotating refresh tokens (stored hashed, with replay-detection), delivered as httpOnly, SameSite=Lax cookies (Secure in production).
  • Account-enumeration guard: Identical responses are returned for known and unknown mobile numbers.
  • File security: Private, presigned-only storage - uploads via presigned POST with a bucket-enforced size cap; reads via short-lived presigned URLs. Certificates are never publicly reachable.
  • Other safeguards: Scheme-validated doctor-authored URLs (blocking script injection), input validation throughout, per-route rate limits on paid/external endpoints, TLS everywhere (including enforced database SSL), server-side and IP-restricted external API keys, and least-privilege IAM.

10. Data Retention and Deletion

  • Profile Data: Retained for as long as your account remains active.
  • Account Deletion: Accounts are status-flipped, not silently erased. Hard deletion runs as a secure 30-day DPDP process; once complete, your profile database records are permanently deleted and access is revoked immediately.
  • Consent Ledger & Terms Acceptances: Retained after account deletion as an anonymized compliance audit record - the account link is removed and IP/user-agent/device information is scrubbed.
  • OTP Codes: Expire within minutes and are single-use.
  • Refresh Tokens: Kept until expiry, protected by a replay-detection tripwire.
  • Notification Logs: Operational records, deleted with the account; the recipient is scrubbed on DPDP deletion. OTP codes are never stored in these logs.
  • Analytics Events: Anonymous session-hash only - not linked to any individual, so no per-person retention period applies.
  • Registration Certificates: Kept securely for verification and audit purposes till the certificate of myPeer is valid. .

11. Data Breach Notification

In the event of a personal data breach, we will take prompt steps to contain and assess the incident. Where the breach is likely to affect you, we will notify you and the Data Protection Board of India in the manner and within the timelines prescribed under the DPDP Act and its rules, describing the nature of the breach, the data affected, and the steps we are taking in response.

12. Children's Privacy

myPeer is an exclusive platform for registered medical practitioners and is strictly prohibited for anyone under the age of 18. We do not knowingly collect or process personal data belonging to children.

13. Grievance Officer

In compliance with the DPDP Act, if you have any questions, concerns, or grievances regarding this Policy or our data practices, please contact our designated Grievance Officer:

  • Name: Nicholas Joseph
  • Designation: Grievance Officer
  • Email Address:
  • Postal Address: Cover-Prime Technologies Private Limited, Plot No. 45, Sector 44, Gurugram, Haryana - 122003 We commit to acknowledging and responding to all formal grievances submitted via the grievance form within 2 days

14. Changes to this 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.