← Back to home

MEROENGINEERING LEGAL

Privacy Policy

How MeroEngineering collects, uses, protects, and shares information when you use our website and services.

Last updated: 23 August 2026

Looking for the Android app policy? Read the IOE Notices Privacy Policy.

1. Who we are

MeroEngineering provides engineering students with syllabus information, past questions, academic tools, and optional paid access. In this policy, “MeroEngineering,” “we,” “us,” and “our” refer to the operator of meroengineering.com and api.meroengineering.com.

2. Information we collect

Depending on how you use the service, we may collect:

  • Google account information: your name, email address, profile image, and Google account identifier when you sign in with Google. We do not receive your Google password.
  • Academic profile information: college, department, academic batch, calculated semester, back-subject selections, and related profile details.
  • Account information: contact number, profile image, account status, subscriptions, and notification preferences.
  • Payment records: selected plan or subjects, payment provider, payment proof, amount, status, and review history. Payments are manually verified. We do not ask for or store your wallet PIN, password, OTP, card number, or bank credentials.
  • Security and activity information: IP address, device and browser details, approximate location supplied by our infrastructure, sign-in/sign-out events, visited route, subject/chapter/question context, visit start and end times, active-use duration, meaningful actions such as searches, downloads, reports and submissions, and administrative actions. Active-use duration is recorded separately from resource activity. For signed-in resource opens and download requests, administrators can see your account name/email, resource, request counts and timestamps. Public totals group repeat requests by account; guests remain anonymous and their requests are not unique-person counts. Active-use duration is measured from heartbeats while a signed-in page is visible and recently interacted with; inactive, idle, and hidden pages stop contributing time. We do not record passwords, form contents, payment credentials, or every click or scroll.
  • Content and communications: profile or question images you upload, contact messages, support requests, and other information you submit to us.
  • Technical information: request logs, error information, performance measurements, and security signals needed to operate and protect the service.

3. How we use information

We use this information to:

  • create accounts, authenticate users, and maintain secure sessions;
  • provide the correct curriculum, questions, and account dashboard;
  • verify payments and enforce premium and back-subject access;
  • send service notifications about sign-ins, payments, and account changes;
  • respond to support messages and administer user accounts;
  • prevent abuse, investigate security incidents, and enforce our terms;
  • diagnose errors and improve reliability, accessibility, and performance;
  • understand engagement, identify active accounts, and help authorized administrators understand which educational material is being used;
  • and comply with applicable legal obligations.

4. Cookies and authentication

We use essential cookies and similar browser storage to keep you signed in, protect requests, remember interface preferences such as theme, and maintain service functionality. Authentication cookies may work across meroengineering.com and api.meroengineering.com. We do not use these essential technologies to sell your personal information.

5. When information is shared

We do not sell or rent personal information. We share information only when needed to provide the service, including with:

  • Google, for Google OAuth sign-in, subject to Google’s own privacy terms;
  • Cloudflare, which provides website delivery, security, compute, database, logging, and file-storage infrastructure;
  • iLoveAPI/iLovePDF, which compresses uploaded profile photos, educational images, answer attachments, and payment-proof screenshots before they are stored. These files may be processed in countries where that provider operates;
  • payment providers, when you independently use eSewa or Khalti to make a payment, subject to that provider’s terms;
  • authorized administrators and service providers who need access to operate, secure, or support MeroEngineering; and
  • authorities or other parties when required by law, necessary to protect rights and safety, or involved in a reorganization of the service.

6. Storage, security, and international processing

We use access controls, secure cookies, encrypted connections, input validation, rate limits, and other safeguards appropriate to the service. No internet service is completely secure, so we cannot guarantee absolute security. Our infrastructure providers may process information in Nepal or other countries where they operate.

7. Retention

We retain account and academic profile information while your account is active and as reasonably needed to provide the service. Payment, entitlement, security, and administrative records may be kept longer for fraud prevention, dispute resolution, auditing, and legal compliance. Uploaded files and operational logs are removed or anonymized when they are no longer reasonably needed, subject to backups and technical limitations. Detailed authenticated route sessions and meaningful activity events are retained for the lifetime of the account without an automatic time-based expiry. Deleting an account deletes the associated activity history, subject to legally required records and backups.

8. Your choices and rights

You may update information that the service permits you to edit. Some academic identity fields are locked after setup to protect entitlement integrity and can be corrected by an administrator. You may contact us to request access to, correction of, or deletion of personal information. Certain records may be retained where required for security, payment, contractual, or legal reasons.

9. Children’s privacy

MeroEngineering is intended for engineering students and is not directed to children under 13. If you believe a child has provided personal information without appropriate authorization, contact us so we can review and remove it.

10. Changes to this policy

We may update this policy as the service or applicable requirements change. The “Last updated” date identifies the latest revision. Material changes may also be communicated through the website or account notifications.

11. Contact us

For privacy questions or requests, emailsupport.meroengineering@gmail.com.

Try EES, ECT, EM, or a course code.