ProcureBeacon stores account email, password hashes, alert profiles, scan results and email-delivery metadata needed to operate the service. Passwords are never stored in plaintext. Verification/reset tokens are stored only as hashes.
For basic traffic diagnostics, public pages use a random first-party browser identifier with a 24-hour lifetime. Only its SHA-256 hash, page path, first referrer host and timestamps/page-view counts are stored. The identifier is not an IP address, raw User-Agent or advertising identifier. If the same browser later registers or logs in while that identifier is active, the visit may be linked to the account for conversion diagnostics.
Automated-looking requests are classified best-effort from request headers. Raw User-Agent strings and IP addresses are not stored; only aggregate counts and one-way hashes used for anonymous bot/scanner signatures may be retained.
Procurement data comes from TED. Account email is used for authentication and requested alerts. We do not sell user data.
For account/privacy requests contact admin@procurebeacon.com.
Last updated: October 2026.