Security and trust

Operational security for institutional academic discovery.

NODOVOX applies data minimization, institutional separation, protected technical documentation and aggregated metrics for universities, libraries, providers and academic organizations.

Data NDX does not request

To operate basic institutional discovery, NODOVOX does not request the following from students, faculty or researchers:

  • National ID or student/employee number.
  • Institutional password.
  • Complete student database.
  • Individual academic history.
  • Campus or internal system credentials.

Aggregated metrics

Institutional reporting should focus on aggregated usage indicators without exposing identifiable individual activity.

  • Searches performed.
  • Zero-result searches.
  • Bibliographic records opened.
  • Access attempts.
  • Usage by provider, collection or institution.

Institutional access

When an institution enables remote access, authentication takes place in the institution's own systems, such as a campus portal, intranet, virtual library, proxy, SSO or equivalent mechanisms.

NODOVOX may receive a valid institutional signal to attribute usage temporarily and in aggregated form.

Operational protection

The platform uses technical controls to reduce public exposure of internal documentation, logs, backups, dumps, test files and sensitive resources.

Institutional portals should filter information by institution and avoid displaying unnecessary internal technical data.

Service scope

NODOVOX provides discovery, metadata, holdings, link resolution and access-intent metrics.

Final access to content may depend on licenses, external providers, repositories, open access, proxies or institutional systems.

Institutional note: this page describes general operational security and trust criteria. It is not an external certification and does not replace contracts, technical addenda, SLAs, confidentiality agreements or specific documents signed with each institution.