Cookies and sessions

Technical cookies for operating institutional academic services.

NODOVOX uses technical cookies, sessions and equivalent mechanisms for basic operation, security, forms, portals, institutional access and aggregated usage measurement.

What technical cookies are

Technical cookies are small identifiers or equivalent mechanisms required for a web platform to operate correctly.

At NODOVOX they are used primarily to maintain sessions, operational security and navigation continuity.

How NODOVOX may use them

NODOVOX may use technical cookies or sessions to:

  • maintain an active session;
  • protect forms;
  • operate institutional or administrative portals;
  • remember temporary institutional context;
  • prevent abuse, spam or automated attempts;
  • measure aggregated platform usage.

Institutional sessions

When an institution enables remote access, NODOVOX may create a temporary session to associate usage with that institution.

Authentication, where applicable, takes place in the institution's own systems, such as a campus portal, intranet, virtual library, proxy, SSO or equivalent mechanisms.

Aggregated analytics

Usage measurement in NODOVOX should focus on aggregated metrics, such as searches, opened records, access attempts, provider usage or institutional activity.

The objective is not to build personal profiles of students, faculty or researchers.

Required cookies

Required technical cookies enable basic platform functions. If they are completely blocked, some sections may not operate correctly.

This may affect forms, sessions, portals, security validations or institutional context.

Relationship with privacy

The use of cookies and sessions is complemented by the NODOVOX privacy policy and security and trust page.

Institutional note: this page describes general criteria for technical cookies, sessions and equivalent mechanisms. It does not replace contracts, data-processing addenda, institution-specific configurations or legal review applicable to each jurisdiction.