Terms of service reliance for users with Bridge

Bridge requires a signed terms of service agreement before it will create or verify a customer. By default, the user accepts Bridge’s terms on a Bridge-hosted page. With terms of service reliance, your app presents Bridge’s terms inside its own onboarding flow and records the user’s acceptance. The user never leaves your app, and Privy tells Bridge the agreement was signed.

Reliance does not remove the requirement that users are shown Bridge’s terms of service. It only changes where those terms appear. Your app must display Bridge’s own terms and privacy policy, not a substitute of its own.

Get approved by Bridge

Bridge grants reliance per app, and only after reviewing the onboarding flow. Build the flow to the requirements below, then submit it for review. Until the app is approved, Bridge ignores client_agreement_id and still requires its own acceptance page. Bridge owns these requirements and may change them. Its terms of service reliance documentation is the authoritative reference. Display a checkbox alongside this exact text, with both documents linked:

By clicking “Accept”, you agree to Bridge’s [Terms of Service] and [Privacy Policy].

Link the terms and privacy policy for the region the user is in. Bridge does not permit either document to be embedded inside another link.

Region	Terms of service	Privacy policy
US	Bridge Building Inc	Bridge Building Inc
EEA	Bridge Building sp. z o.o.	Bridge Building sp. z o.o.
Rest of world	Bridge Building Limited	Bridge Building Limited

Store an attestation for each acceptance

Record that the user accepted, under an identifier your app can look up later. Bridge may send a list of identifiers and ask for the matching attestations at any time, so a random or non-durable value is not sufficient.

Submit the flow for review

Share a screenshot of the completed flow with your Bridge contact. Bridge submits it for review and approves reliance for the app.

Signal acceptance to Bridge

Once the app is approved, each user still accepts Bridge’s terms in your app’s own flow. Pass the identifier for that user’s stored attestation as client_agreement_id on the verification request, and Privy signals Bridge on your app’s behalf. client_agreement_id is an optional string between 1 and 1024 characters. It accompanies the verification request rather than a separate call, so there is no reliance-specific endpoint.

Hosted KYC
Headless KYC

Include client_agreement_id when creating the KYC link. Bridge returns a link that goes straight to identity verification, with no terms of service step.

const status = await privy.users().kyc.initiateLinks('did:privy:xxxxx', {
  provider: 'bridge',
  environment: 'sandbox',
  email: '[email protected]',
  client_agreement_id: '<your-attestation-id>'
});

On this path Privy sends Bridge only the fact of acceptance, as developer_accepted_tos. The identifier itself is not forwarded or stored. Omitting it produces a link that includes Bridge’s terms of service step.

Include client_agreement_id when submitting verification data.

const status = await privy.users().kyc.submit('did:privy:xxxxx', {
  provider: 'bridge',
  environment: 'sandbox',
  client_agreement_id: '<your-attestation-id>',
  data: {
    first_name: 'Alex',
    last_name: 'Doe'
    // ...
  }
});

On this path Privy forwards the identifier to Bridge as signed_agreement_id, alongside has_accepted_terms_of_service. Privy stores it, so later submissions for the same user may omit it and Privy replays the stored one.

Verify acceptance took effect

The verification response reports terms of service status under tos.status. When reliance applies, Bridge reports the requirement as satisfied and omits its own acceptance link.

{
  "provider": "bridge",
  "environment": "sandbox",
  "status": "pending",
  "tos": {
    "status": "approved"
  }
}

A tos.status of pending after passing client_agreement_id means Bridge did not treat the terms of service requirement as satisfied, and still expects the user to accept on Bridge’s own page. Confirm with Bridge that the app is approved for reliance.

Bridge’s sandbox accepts any agreement identifier, including identifiers it cannot resolve. Production rejects an unrecognized identifier and leaves the terms of service requirement outstanding, so a flow that works in sandbox can still fail in production. Verify tos.status against production before depending on reliance in a live integration.

KYC and KYB

Users

Organizations

Terms of service reliance

Get approved by Bridge

Store an attestation for each acceptance

Submit the flow for review

Signal acceptance to Bridge

Verify acceptance took effect

Next steps

Hosted KYC

Headless KYC

​Get approved by Bridge

​Show Bridge’s consent language

​Store an attestation for each acceptance

​Submit the flow for review

​Signal acceptance to Bridge

​Verify acceptance took effect

​Next steps

Hosted KYC

Headless KYC

Get approved by Bridge

Show Bridge’s consent language

Store an attestation for each acceptance

Submit the flow for review

Signal acceptance to Bridge

Verify acceptance took effect

Next steps