Veribound Agent Privacy
Legal / Veribound Agent privacy. Last updated: September 14, 2026
The Veribound Agent is software an organization asks you to install on a device so that the organization can decide whether that device should have access to its resources. It does nothing until you enter an activation code issued by that organization. There are no user accounts.
The organization that issued your activation code is responsible for this data; Veribound processes it on the organization's behalf. Questions or requests about it go to your organization's administrator.
The Agent is not intended for anyone under 18.
What the Agent sends, on every platform
About the device. Manufacturer, model, operating system and version, and the Agent's version. Identifiers that let the organization recognize the same device from one check-in to the next, listed per platform below. The Agent creates a cryptographic key inside the device's secure hardware; only the public half ever leaves the device, and the key itself never does in any form.
About the network. The device's local network addresses and whether a VPN is active. The Agent does not read the device's public address; the service sees it from the connection, as any web service does, and uses a third-party IP-intelligence service to learn the network operator, the approximate region (country or region, not a precise position) and whether the address is a known proxy or VPN. Your organization uses that, with the other information here, to decide whether the device keeps its access. The Agent does not use location services.
About the device's security state. Whether a screen lock is set, whether the operating system has been modified, whether a debugger is attached, and the platform-specific checks listed below. Time zone and locale.
Administrator tokens only. When an organization's administrator activates an administrator token, the email address the token was issued to is stored with it. Ordinary device tokens carry no name, email or account.
What the Agent does not collect
Contacts, photos, files, messages, browsing or search history, the list of installed apps, keystrokes, screen contents, precise location, health, financial or payment information.
Why
Only so the organization can decide, continuously, whether the device keeps its access, and show the device's status to its administrators. Not used for advertising and not sold to anyone.
How
The Agent checks in at a regular interval and when the device's network changes. Every report is signed with the device's hardware key and sent over an encrypted, certificate-pinned connection; the report contents are additionally encrypted to the service.
Third parties
Third-party services are used for IP intelligence (the connection's public address only) and, on Android, for app-integrity verification (the app's identity and a one-time value only). Nothing else is shared outside Veribound and the organization that issued your activation code.
Android
Identifiers: the Android ID, the Widevine device ID, the system build fingerprint, and a hash of the device's hardware-backed key.
Security state: bootloader lock state, root detection and OS integrity, developer options and USB debugging, whether installs from unknown sources are allowed, whether Google Play services are present, SELinux enforcement state where the device permits it to be read, and the network adapters' hardware (MAC) addresses.
Reporting runs as a background service.
iOS
Identifiers: Apple's per-vendor device identifier, and a hash of a key the app creates on the device.
Security state: whether the device shows signs of being jailbroken, and whether the Agent's background reporting is enabled.
macOS
Identifiers: an identifier macOS assigns to this Mac, and a hash of a key the app creates on the device.
Security state: whether System Integrity Protection is enabled, whether Gatekeeper is enabled and the XProtect version, whether a debugger is attached to the Agent, and whether the Agent's background reporting is enabled.
Windows
Identifiers: the BIOS serial number, the machine GUID, and a key held in the TPM.
Security state: secure boot state, TPM attestation result, and the network adapters' hardware (MAC) addresses.
Questions
The organization that issued your activation code is responsible for this data. Direct questions and requests about it to that organization's administrator. Questions about the Agent software itself can be sent through the contact form.