Every IDBridge run can report aggregate counts — runs, creates, deactivates, duration. Never names, usernames, IDs, or any directory record. Pulse turns those counts into fleet health and, for districts that opt in, a run timeline for their own install.
The ingest API rejects any payload containing fields outside the published schema — the privacy promise is enforced server-side, not just documented. See PRIVACY.md.
Enhanced-tier installs get a run history — results, durations, and error classes for their SiteID. Sign in and claim your install to see yours.
Run IDBridge with -TraceLogging and the exact payload appears in your log
before it's sent — byte for byte what leaves your network.
Set once in IDBridgeConfig.psd1; silence any single run with
-DisableTelemetry.
Nothing is sent. No exceptions.
Telemetry = @{ Tier = 'Off' }
Anonymous aggregate counts with no identifier of any kind. Runs can't be linked to each other, or to you.
Adds a random install-scoped SiteID (your runs form a timeline) and the error class name on failed runs. Still no personal data, ever.
Sign in and enter your SiteID to see your run timeline. Find your SiteID any time:
Import-Module IDBridge Initialize-IDBridge Get-IDBridgeSiteID