Privacy

MeroEngineering is a study site for IOE students. This page lists the data the site stores and what it does with it.

Account

Signing in with Google shares your name, email address, email-verified status, profile picture URL, and Google account identifier. The site stores those values. It does not store Google access or refresh tokens, and it never reads your mail or contacts.

After the first sign-in you choose a department, admission batch, and college. These are stored with your account. Students cannot change them; only an admin can.

Cookies

The site uses two cookies, both required. Signing in sets a signed session cookie that keeps you signed in and is needed for paid access, payments, and your account. The Google sign-in flow also sets a short-lived state cookie that protects the callback and is cleared when sign-in finishes. Neither cookie is used for advertising or analytics, and signing out clears the session cookie.

For up to five minutes the cookie carries a signed copy of your session, so the site can check paid access without reading the database on every request. After that it is refreshed from the database.

Payments and subscriptions

When you submit a payment, the site stores the department and semester you are paying for, the price and discount at that time, the payment method, the transaction ID, the phone number, and the payment screenshot. The screenshot is compressed in your browser, re-encoded by Cloudflare Images, and stored in a private bucket. Only an admin can open it, through the site.

An admin reviews each payment by hand. Approving it creates a subscription with its start and expiry dates. Rejected and cancelled payments keep their row so the history stays complete. Payment screenshots are kept indefinitely.

Email

Resend sends three messages: a payment approval or rejection to the student, and a new-payment notice to the admin. These are the only emails the site sends. A failed email never blocks the action that triggered it.

Hosting

The site runs on Cloudflare Workers, with data in Cloudflare D1 and files in Cloudflare R2. Cloudflare processes requests and may keep standard operational logs under its own policies. The site loads no third-party analytics, advertising, or tracking scripts, and sets no analytics or advertising cookies.

Retention

Account, profile, payment, and subscription rows stay while the account exists. A session ends when you sign out or when it expires.