Privacy

Qonsult privacy notice

This product notice explains the data categories used by the current Qonsult platform. It should be reviewed with qualified privacy counsel before a large-scale launch in every target jurisdiction.

What Qonsult processes

Account and authentication information, student profile information you deliberately provide, programme and service activity required to deliver requested features, and optional product analytics when you allow analytics.

Optional product analytics

With analytics permission, Qonsult records a random first-party visitor id, session id, pages, active engagement time, searches, programme and service interactions, approximate location derived from hosting headers, device class, viewport, browser family, operating-system family, language, timezone and limited network-performance signals.

What analytics does not collect

The analytics subsystem is designed not to store passwords, Firebase tokens, document contents, form keystrokes, precise GPS coordinates, raw long-term IP histories, clipboard contents, browser history outside Qonsult, installed-font inventories, canvas/audio/WebGL fingerprints or other cross-site fingerprinting identifiers. Analytics page paths are stored without URL query strings so password-reset codes, verification codes and similar URL parameters are not captured.

Anonymous and signed-in sessions

Before sign-in, an analytics-enabled browser is represented by a random visitor id. If the person later signs in, subsequent consented activity may be associated with the internal Qonsult user record. Qonsult does not claim to know the real identity of a visitor who has not authenticated.

Session timing

Qonsult distinguishes total elapsed session time from active engagement time. A browser close signal is recorded when available. If no reliable close signal arrives, the administration console labels the session end as inferred after the inactivity timeout instead of presenting it as an exact browser-close time.

Choices and withdrawal

Optional analytics is off until the visitor allows it. The Privacy choices control in the site footer can be used to change or withdraw optional analytics permission. Essential storage needed for security, authentication, requested services and remembering privacy choices is separate.

Retention and deletion

The implementation includes a retention workflow for detailed analytics. Retention periods should be finalized in Qonsult policy and operational configuration. Existing account privacy-request infrastructure should be used for access, correction, restriction or deletion requests where applicable.

Security

Analytics APIs are same-origin, consent-gated, schema validated and batch-size constrained. Administrator analytics endpoints require server-verified administrator authorization. Event properties use a server allow-list, ingestion is rate-limited per analytics visitor, likely automated bot sessions are excluded from human reporting, and Qonsult avoids putting credentials or private document contents into analytics event properties.