Paybond Privacy Policy

This Privacy Policy applies to Paybond public websites, self-serve signup, hosted console, APIs, SDKs, product workflows, support, billing, and related services. "Paybond" means the Paybond entity identified in your order form, invoice, or other contracting record.

Paybond is generally the controller for account, website, billing, support, and service operations data. For tenant-submitted workflows, evidence, operator records, identity-provider settings, settlement configuration, and other customer content, Paybond processes that data to provide the service under the customer's instructions and applicable agreement.

• You and your authorized operators when you create accounts, configure workspaces, submit product data, or contact Paybond.
• Your organization, identity provider, SCIM provisioner, trusted agent keys, SDK or API clients, and other tenant-directed systems.
• Payment, settlement, and billing providers such as Stripe and Coinbase CDP Payments, and settlement rail providers you connect directly to your workspace with your own merchant credentials — for example Shopify, Adyen, Flutterwave, or Paystack — when those rails are enabled.
• Plaid, when a bank account is linked for the Stripe ACH settlement rail, for account verification and, where amount and risk policy require it, Identity Match, Balance, and Signal risk evaluations.
• Public website, console, API, browser, network, and infrastructure logs generated when you use Paybond.

• Provide, secure, maintain, and improve Paybond services, including signup, billing, authentication, SSO, SCIM, policy workflows, disputes, settlement lifecycle operations, Signal records, audit exports, and support.
• Enforce tenant isolation, authenticate operators, prevent cross-tenant access, detect abuse, investigate security incidents, and preserve auditability.
• Process subscriptions, invoices, plan changes, usage records, tax and accounting records, and contract-managed exceptions.
• Operate public analytics for product, marketing, reliability, and conversion measurement without exposing one tenant's workflows to another tenant.
• Comply with law, enforce agreements, respond to lawful requests, and protect the rights, safety, and security of Paybond, customers, operators, and third parties.

Where law requires a specific legal basis, Paybond relies on contract performance, legitimate interests in operating and securing the service, compliance with legal obligations, consent where required, and the customer's instructions for customer-controlled product data.

Some workspaces fund ACH settlement by linking a bank account. When you or your authorized operator link a bank account for the Stripe ACH settlement rail, Paybond uses Plaid to verify the account. Plaid does not move money; Stripe remains the money mover and merchant of record for ACH debits.

Account verification uses Plaid Auth to confirm the linked account. For higher-value, agent-funded ACH debits, a server-managed amount and risk policy may additionally require Plaid Identity Match, Balance, and/or Signal evaluations before the debit is authorized; Auth alone is not sufficient above the configured thresholds. These checks support account validation and fraud monitoring for agent-funded settlement, including in a NACHA WEB debit context. Paybond does not present them as legal advice or as a compliance determination for your organization.

Paybond uses first-party cookies and browser storage to run sessions, remember temporary login and SSO state, measure public page requests, and understand public call-to-action activity. Session cookies are protected from browser scripts where they hold access or refresh material. Public analytics uses a first-party visitor cookie named pb_vid and session storage keys for session, landing page, and initial referrer context.

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.

More detail is available in the Cookies & Analytics Notice.

Public pages (marketing, docs, and guides) and the authenticated operator console — but not the internal staff console, the first-run onboarding checklist, or sign-in/sign-up flows — may show a small, dismissible feedback prompt asking a short, randomly-selected question, such as what you would change about the page. The exact question varies by visit rather than by page. Submitting it is entirely optional, and dismissing or ignoring it never blocks or limits your use of the site or console. Once you have seen the prompt on a given page, it will not ask again on that same page; a separate cooldown also limits how often it can appear elsewhere.

If you submit feedback, Paybond collects the text you write, the question you were shown, the page path and URL, and basic technical context (browser user agent, viewport size, language, timezone, and submission time) to help us understand and reproduce what you reported. The email field is optional and used only to reply to you if you ask a question or report a problem that needs follow-up; it is never used for marketing you have not otherwise opted into. Feedback submitted from the authenticated console is not otherwise linked to your operator account or tenant beyond whatever you choose to write.

Feedback submissions are delivered directly to a Paybond product inbox for review and are not displayed publicly, attached to your account, or used to build an advertising profile. Paybond retains feedback messages only as long as needed to review, act on product-improvement input, and respond if you provided an email and asked a question, then deletes or de-identifies them.

Paybond does not sell personal information. Paybond does not use one tenant's private workflows to expose another tenant's workflows, and Paybond does not use customer content to train foundation models unless a separate agreement expressly permits that use.

When an advertising click identifier such as gclid or fbclid is present in a public-page URL, Paybond may retain it in first-party analytics for attribution and conversion measurement. Paybond does not currently disclose those identifiers to advertising platforms or share personal information for cross-context behavioral advertising. Paybond will update this policy and provide any legally required choice before adopting a materially different practice.

• Service providers and subprocessors that host, secure, operate, bill, email, or support Paybond.
• Payment and settlement providers where needed to process subscriptions, invoices, webhook events, settlement states, chargebacks, refunds, or rail-specific operations.
• Bank verification and risk providers, specifically Plaid, to verify a linked bank account and, where amount and risk policy require it, run Identity Match, Balance, or Signal checks; and Stripe to attach the account and fund ACH debits.
• Customer-directed identity providers, SCIM provisioners, observability systems, or integrations configured by your organization.
• Professional advisors, auditors, counterparties in a corporate transaction, or authorities when required by law, legal process, or security response.

The current public list is available at Subprocessors.

Paybond retains personal data for as long as needed to provide the service, satisfy legal and accounting obligations, preserve ledger and audit integrity, resolve disputes, investigate incidents, enforce agreements, and maintain security. Retention periods vary by data type and customer agreement.

Paybond uses technical and organizational safeguards designed for a multi-tenant service: TLS encryption for data in transit, authenticated tenant scope, role-based access, httpOnly console session cookies, short-lived tokens, refresh rotation, encrypted storage for vaulted settlement destination credentials and linked bank-account access tokens, signed audit bundles, structured logging, provider-managed secret storage, and operational controls for elevated support access.

No service can guarantee absolute security. Customers are responsible for safeguarding their own operator credentials, tenant configuration, IdP settings, API keys, trusted agent keys, settlement destinations, and systems that call Paybond APIs.

Paybond may process and store data in the United States and other locations where Paybond, its affiliates, or subprocessors operate. If applicable law requires transfer safeguards, Paybond uses appropriate contractual and operational measures in customer agreements or data processing terms.

Depending on where you live and how you use Paybond, you may have rights to request access, correction, deletion, portability, restriction, objection, or appeal of a privacy decision. Authorized agents may submit requests where law permits. Paybond will verify requests before acting on them.

If you are located in the European Economic Area, United Kingdom, Switzerland, or a U.S. state with a comprehensive consumer privacy law, that law may define these rights — and any related opt-out rights — more specifically than this general summary. Paybond intends to honor verifiable requests under the law that applies to you; contact [email protected] and identify your location so Paybond can apply the correct process.

• Privacy requests: [email protected].
• Contract, DPA, or formal notice requests: [email protected].
• Public analytics choices: delete or block cookies and local/session storage in your browser, use browser privacy controls, or contact Paybond for assistance with analytics data tied to a visitor ID.
• Feedback widget choices: dismiss the prompt at any time, leave the email field blank, or contact [email protected] to request deletion of a feedback submission you provided an email address with.
• Workspace data requests: contact your organization admin first when Paybond processes the data on behalf of your organization.

Paybond is a business service and is not directed to children. Do not use Paybond to knowingly submit personal data about children unless your organization has a lawful basis and the relevant customer agreement permits that use.

Paybond may update this Privacy Policy as the service, subprocessors, analytics, or legal requirements change. Material changes will be reflected by updating the effective or last-updated date and, where appropriate, by providing additional notice through the service, contract record, or email.

Privacy questions should go to [email protected]. Legal notices should go to [email protected] or the notice address stated in your order form or invoice.