Terms · Contribution terms

Version 2026-11

Current. Accept it with nox intel consent accept.

SHA-256 of the text: d11ed96d88b62ace6a07224412dc72eee18ba4a6d67ee8d22aa3e8233c9bb86b

nox's tests pin this hash, so a release cannot change these words without changing the version. To check the text your nox shows, nox intel consent show | shasum -a 256 prints the same hash when your nox carries this version.

NOX Intelligence contribution terms, version 2026-11

Contribution is optional. Scanning, and asking NOX Intelligence for
advisories, work the same with it off. It stays off until you turn it on
(scan.intelligence.contribute: true) AND accept these terms on this machine.

What is sent
  For each vulnerable dependency a scan finds, one observation containing only
  the fields printed by "nox intel allowlist": a fingerprint, the package
  ecosystem, name and affected version range, the weakness class, the nox rule
  id, an opaque id for this installation, a timestamp, the nox version, the
  terms version you accepted, and a hash that lets only you erase your id.

What is never sent
  Source code, file contents, file paths, repository names, code snippets,
  secrets, prompts, model output, or findings from any rule other than
  dependency vulnerabilities. Your reporter id is derived from a secret that
  stays on this machine and reveals nothing about you.

What the service does with it
  It counts how many distinct installations reported the same issue, and may
  publish a record derived from many reports. A published record never contains
  a reporter id. Nothing is published without review by a person.

How long identifiers are kept
  By default the service removes reporter ids from unpublished reports 90 days
  after the last activity. A removed report still counts as having been made,
  but is no longer linked to you. A self-hosted service may use another period.

How to erase and withdraw
  "nox intel forget" removes your reporter id from every report on the service
  (including published ones) and turns contribution off on this machine.
  "nox intel consent withdraw" turns it off without contacting the service.

Who is responsible
  NOX Intelligence at intel.klarlabs.de is run by Felix Geelhaar
  (klarlabs-studio), who is the controller of what it receives. Write to
  nox@felixgeelhaar.de with questions, or to see what the service holds about
  you ("nox intel preview" prints your reporter id). The service and its
  backups run on Hetzner servers in Germany and Finland (Helsinki), inside the
  EU. A self-hosted service (scan.intelligence.endpoint) is the responsibility
  of whoever runs it.

Legal basis and your rights
  Your consent (GDPR Art. 6(1)(a)). You can withdraw it at any time; that does
  not make what was sent before unlawful. You may ask for access to, correction
  of or erasure of your data, and complain to a data protection supervisory
  authority.

These terms are published, unchanged, at https://nox-hq.dev/terms/2026-11

If these terms change, contribution pauses until you accept the new version.