PULSE

Planned: endpoint signals that device owners can see

Noxtica Pulse is an endpoint client being built for security and observability signals. It is planned to tell device owners what it sends and let them control it.

Planned capabilities

These items describe the design direction. None of them is a commitment on scope or date.

In development

What the tenant sees

  • Chooses which signals to enable
  • Publishes a notice
  • Receives the enabled signals in its console
  • Decides what to do about a flag

Between the two

The notice

Explains what is collected and why.

What the device owner sees

  • A visible indicator on the device
  • A notice before collection
  • A view of what it sends
  • A choice to accept or decline optional purposes

A hidden mode is not planned.

Planned: what the tenant sees, and what the device owner seesIllustration of the planned design. Nothing here is a commitment on scope or timing.
  • Signals about the tenant's own application

  • Visible to the device owner

  • Controls and rights

Planned approach

  1. The tenant

    Choose signals, publish a notice

    A tenant would choose which signals to enable for its own application, and publish a notice on what is collected and why.

    In development

  2. Device owner

    Read the notice, then decide

    The tenant's notice

    A person would sign in with a Noxtica account, read the notice, and accept or decline optional purposes.

    In development

  3. Console

    Signals reach the tenant

    Enabled signals

    The client would send the enabled signals to the tenant's console. What to do about a flag would stay with the tenant.

    In development

Planned approach: the tenant publishes a notice, the device owner decides, signals reach the tenantIllustration of the planned design. Nothing here is a commitment on scope or timing.
  1. The tenant chooses signals

  2. The device owner decides

  3. Signals reach the tenant

Status and boundaries

  • Pulse is in development. Nothing on this page is a commitment on scope or date.
  • Signals would be indicators, not proof. They are probabilistic and can be wrong. The tenant decides what to do, and no protection outcome is promised.
  • The client is planned to notify the device owner and report signals. It is not planned to end sessions or stop programs on the device.
  • Customers would be responsible for notices and a lawful basis for their own use. Watching people without a lawful basis is not permitted.