// DEVELOPER EVALUATION

Know what runs where before you integrate.

The browser collects available evidence. Your server performs the authenticated read. Your application owns the customer policy and every fallback.

A browser-to-server handoff with explicit ownership.

  1. Customer client

  2. Noxtica processing

  3. Customer server

  4. Customer policy

  5. Investigation and measurement

TRUST BOUNDARIES

The smallest current integration path.

  1. Browser

  2. Collector

  3. Your server

  4. Your policy

  1. The public loader returns a device identifier or an error state.

  2. Your backend calls the authenticated lookup with a server-held key.

  3. Your policy sets the action and the fallback for every result state.

MAINTAINED PATHIllustration of the page’s own integration path, one step at a time.