Your privacy matters.

Honest feedback about teaching is only possible if giving it does not expose the student who gave it. At the same time, feedback nobody can be held to becomes a place for abuse. The platform is therefore built around public anonymity together with internal accountability: a review is anonymous to readers, but it is not anonymous to the system that has to moderate it.

Account details

Your institution, your institutional student email address and a password you set. A personal email address may be recorded as a recovery contact.

Verification

One-time codes sent by email during sign-up and sign-in, and whether a verification step succeeded.

Review content

Your answers to the questionnaire, any written comment, the teacher the review is about and the courses it relates to.

Activity on your own account

Reviews you have submitted and their status, and whether you marked a review as helpful.

Technical and security data

Ordinary request information needed to operate and protect the service, such as timestamps and derived values used for abuse limits.

Public on a teacher profile:

• The questionnaire answers of published reviews, grouped by dimension.
• Any written comment in a published review.
• The courses a published review relates to, and the questionnaire version it used.
• A public alias for the reviewer, and the date the review was published.

Never public:

• Your name, your student email address or any personal email address.
• Your password, session information or verification codes.
• The link between your account and the reviews shown under your alias.
• Reviews that have not been published, and reports you submit about other reviews.

Published reviews are attributed to an alias rather than to you. The alias is what a reader sees, so a teacher or another student cannot identify the reviewer from the public page. Internally the review remains associated with your verified account, which is what makes moderation, duplicate prevention and abuse handling possible.

Some information exists only to keep the service usable. Anti-abuse limits on public actions, for example, work from a derived, non-reversible value rather than from a stored address, and the details of those limits are deliberately not published or surfaced in error messages.

Administrative access to the platform is separate from student accounts, and administrative interfaces are not indexed or publicly reachable as ordinary pages.

When a review is submitted or reported, moderators see the review, the report reason and the details needed to make a decision under the community guidelines. That access exists for moderation and abuse handling, not for browsing.

Like most web platforms, the service runs on third-party infrastructure: application hosting, a managed database, caching and rate-limit storage, email delivery for verification codes, file storage, error monitoring and product analytics. These providers process data on the platform’s behalf in order to deliver those functions.

Review content is not sold, and it is not shared with anyone for advertising.

You can see the reviews you have submitted, and their status, from your own account. Removing a published review from public view is a moderation outcome rather than a self-service action today, and can be requested by reporting the review.

A published contact address for privacy requests will be added here before public launch; placeholder addresses are deliberately not listed. Until then, the in-product report action on a review is the working channel for content concerns.