Legal
Cookies & Analytics Notice
Effective May 26, 2026
This notice explains the first-party cookies, browser storage, and public analytics signals Paybond uses.
Effective: May 26, 2026Last updated: June 2, 2026
1. Overview
Paybond uses cookies and browser storage to keep the hosted console secure, complete SSO flows, remember session choices, measure public page requests, and understand public call-to-action activity. Paybond does not use cookies to let one tenant view another tenant's data.
2. Session and authentication cookies
| Cookie or storage | Purpose |
|---|---|
paybond_access | Helps maintain a signed-in console session and is not readable by ordinary page scripts. |
paybond_refresh | Helps refresh a signed-in console session and is not readable by ordinary page scripts. |
paybond_session_persistent | Records whether the operator selected persistent session behavior. |
paybond_pending_session_persistent | Temporarily carries the pending session-persistence choice during login and SSO initiation. |
paybond_pending_sso_return_to | Temporarily stores the return path for SSO callback handling. |
These cookies are used for security and account access. Blocking them may prevent login, SSO, refresh, or console access from working.
3. Public analytics cookies and storage
| Cookie or storage | Purpose |
|---|---|
pb_vid | First-party public visitor ID used to associate public page requests and call-to-action events. It is configured for up to one year. |
pb_sid | Session storage key used by browser analytics to group public page views within a browser session. |
pb_landing_page | Session storage key used to remember the first public page in a browser session. |
pb_initial_referrer | Session storage key used to remember the initial referrer for a public browser session. |
- Public analytics may include page path, page title, referrer, landing page, UTM fields, ad click identifiers present in the URL, call-to-action label and destination, placement, visitor ID, session ID, screen and viewport dimensions, timezone, language, device pixel ratio, color depth, cookie-enabled status, Do Not Track value, online status, platform, touch points, and browser language list.
- Public website analytics may include user agent, source IP, accepted language, approximate country or routing metadata from security providers, device and bot classification, page path, referrer, and UTM fields.
- Public analytics is used for product, reliability, marketing, attribution, abuse detection, and conversion measurement on public pages.
4. Excluded paths
Paybond's public website analytics are intended for public marketing, documentation, and legal pages. They are not intended to record private console workflows, authentication steps, account recovery flows, API requests, or static asset requests.
5. Choices and controls
- You can delete or block cookies and local/session storage through your browser. Blocking session cookies can break login and console workflows.
- You can use browser privacy controls or content blockers to limit public analytics cookies and storage.
- You can contact [email protected] for help with privacy requests tied to a public visitor ID.