Privacy policy

Browsing universities, professors and reviews requires no account. We do not set cookies on read-only visitors, and nothing we store identifies you.

• •Language preference: if you use the language toggle, we remember your choice in a pk_lang cookie. It holds only bn or en.
• •First-visit notice: when you dismiss the welcome notice, your browser remembers that in local storage. It never leaves your device.
• •Analytics: page views and page-load performance are counted in aggregate, without cookies and without building a profile of you.
• •Our hosting provider necessarily sees your IP address to deliver pages. We never write IP addresses into our database.

Sign-in is Google only. We use it so that each account can review a professor and course once, vote once per review, and report once per review. When you sign in, we store:

• •Your Google account identifier (sub), an opaque number that Google assigns.
• •The display name Google provides. It is never shown on the site.
• •The domain part of your email (for example du.ac.bd), used only to check whether you can review universities that limit reviews to their own students. The part before the @ is discarded during sign-in and never stored.
• •When your account was created and when you last signed in.
• •A signed session cookie that keeps you signed in for up to 30 days.

Anonymity is a property of the database design, not a promise about how we behave:

• •The table that stores review content has no column that refers to any account.
• •A separate table records only that an account has reviewed a given professor and course, so duplicates can be blocked. It holds no review content and no reference to any review.
• •The two tables share no key, use unrelated kinds of identifiers, and the submission table stores no timestamp. Nothing lines them up.

• •Helpful votes are stored with your account so you can vote once and undo it.
• •Reports are stored without any reference to who filed them. To stop duplicate reports, a temporary entry pairing your account with the reported review is kept in our cache for up to 30 days, then expires automatically.
• •If you request a new university, the request is linked to your account so we can limit how many pending requests one account can file.

We do not sell data, show ads, or share anything with advertisers. The services that run the site are:

• •Google: sign-in only.
• •Our hosting provider: runs the servers, database and cache, and processes data only to run the site.

Account data is kept while your account exists. You can delete your account yourself from your activity page (/me). Deleting it removes its identifier, display name, email domain, review-submission records, helpful votes and university requests. Helpful counts on the reviews you voted for go down accordingly.

Reviews are not deleted with the account. Because nothing links a review to its author, we cannot find "your" reviews to delete them, and neither can anyone else. A review can be removed through the report process if it breaks the guidelines.

One thing is kept, so that deleting an account can’t be used to review the same course twice. For each professor and course the account had reviewed, we keep a one-way hash, made with a secret key, of your Google identifier combined with that professor and course. It stores no account, no course, no review and no date, so it cannot be matched to any review. Its only use: if you sign in again with the same Google account, you can’t review those same professors and courses again. Other courses are open as normal.

Cache entries that stop duplicate reports are not removed early. They expire on their own within 30 days and refer to an account that no longer exists.

If you can no longer sign in and want your account deleted, contact the maintainers through the project’s GitHub page. We will never ask for your review content to do it.

If we change what we collect, we will update this page and the date below before the change goes live.