Privacy & Data Handling

Pult Presence has a single purpose: detecting whether an employee is in the office. To be transparent about the data involved in Pult Presence, this page separates it into three kinds:

• Presence data -- the attendance records Presence exists to produce.
• Session & connection data -- a strictly limited amount of recent connection information kept to operate and troubleshoot the service.
• Diagnostic & error reporting -- limited technical information sent when something goes wrong.

Only the first is used for attendance. The other two exist to run and support the service.

Presence data

Presence data is the attendance record: which office a user was in, on which day, and the first and last times their device was seen on that office's network.

• How it's determined -- Pult matches a device's network connection against the office networks you configure. A presence record is created only when a connection matches a configured office; connections that don't match a known office produce no presence data.
• What it contains -- the matched office, the connection that matched it, and the first-seen and last-seen times. The connection recorded here is your office's own configured network -- not an employee's personal or home connection.
• Device metadata (WiFi Presence only) -- basic device information (name, model, OS) synced from your existing MDM system, used to identify devices. Pult does not collect this independently.

Presence data powers the Presence Dashboard, automations, and Pult Workplace features like desk booking confirmation.

Session and connection data

When a device or browser signs in to Pult, it opens an authenticated session. This applies to the Pult Agent and to signing in to Pult in a web browser alike.

For each session, Pult keeps a strictly limited number of the most recent connections, including:

• the connecting IP address and an approximate location derived from it,
• the device or browser used,
• connection timestamps.

This exists to operate and troubleshoot the service -- for example, so your administrators can diagnose why an agent isn't reporting from the Pult Agent view, and so Pult can investigate connectivity or enrollment problems. It is not used to determine attendance or presence, and it is kept for any session regardless of location.

Diagnostic and error reporting

When the Pult Agent or Pult's services encounter an unexpected error, they send a diagnostic report to Pult's error-monitoring system. Reports may include limited technical and connection context -- such as the device and operating system, the application version, and connection information relevant to the error. This data is used only to diagnose and fix faults and is not used for attendance.

How this data is protected

• Purpose limitation -- session and diagnostic data are used only to operate, secure, support, and troubleshoot Pult Presence.
• Access -- connection detail is visible to your own administrators by default, for self-serve troubleshooting. Your organization can opt into stricter privacy modes in which this connection detail -- and, separately, attendance detail -- is hidden from your workspace. When hidden, it remains accessible only to authorised Pult staff where required for support, security, or fault investigation. To enable either mode, contact Pult support.
• Retention -- presence records are retained for a period you configure (a fixed duration, or kept indefinitely) according to your organization's settings. Session and connection data are retained in accordance with your agreement and Pult's data-retention terms.

What Pult does not do

• No movement or precise-location tracking -- no GPS, and no tracking of movements or continuous whereabouts. Presence determines only which configured office you're in; any approximate location in session data is coarse (derived from a connection's IP) and used only for operations.
• No work-hours or productivity tracking -- Presence is not used to record working hours or measure productivity. First-seen and last-seen times reflect network connection times, not work start and end times.
• No off-site attendance -- when a device is outside a configured office network, no presence is recorded. The device's session may still record a connection as limited operational telemetry (see above), but this never creates an attendance record.
• No content monitoring -- Pult does not inspect network traffic, monitor application usage, or read files, screens, or keystrokes on the device.

How WiFi MAC address matching works

For WiFi Presence, Pult matches WiFi MAC addresses from your WiFi controller against device records from your MDM system. This matching:

• Happens entirely server-side between your WiFi controller data and MDM data.
• Does not require any software on employee devices.
• Relies on MAC address randomization being disabled on managed devices, so that the MDM-registered MAC address matches the one seen by the WiFi controller.

Employee communication

When rolling out Pult Presence, we recommend communicating clearly with employees about:

• What the system does and does not track.
• Why it's being used (desk booking confirmation, office optimization, safety).
• That no personal location or time tracking is involved.

See the Rollout Guide for communication templates and best practices.

For the technical detail of what the Pult Agent collects, how credentials are stored, and transport security, see Pult Agent -- Security & Data.