Sendero’s application logic treats legal clarity as a first-class concern: bookings, escrow, settlement, traveler sessions, and operator workspaces all assume people can read the same canonical legal documents. Use Sendero’s public Terms of Service and Privacy Policy everywhere you surface policy to humans or configure integrations: https://sendero.travel/terms https://sendero.travel/privacy
Express consent means a deliberate action—typically a checkbox or equivalent—before someone is bound to those documents. Product and compliance expectations apply across channels (web app, linked messaging surfaces, buyer-funded trips, and API/MCP callers acting on behalf of a tenant), not only on a single vendor screen.
Whenever you add or operate a Sendero surface—linked messaging, buyer-funded trip invites, API/MCP integrations, or tenant dashboards—the same Terms and Privacy links should appear wherever a person or integration can be bound to policy, and consent should match the channel (inline link, deep link, or recorded acceptance in your tenant flow). Clerk’s “express consent to legal documents” setting below only wires that pattern into browser sign-up and Clerk’s hosted Account Portal; it does not replace aligning other entry points with Sendero’s legal baseline.
For browser-based sign-up and Clerk’s hosted Account Portal, identity and organizations are powered by Clerk. In the Clerk Dashboard → Legal, you can require “express consent to legal documents” so sign-up and the hosted Account Portal collect that acceptance against the same Sendero URLs above. That control exists only on Clerk Core 2; hosted Account Portal must be upgraded to Core 2 before it appears.
Operator reference (Clerk): https://clerk.com/docs/guides/secure/legal-compliance https://clerk.com/docs/guides/development/upgrading/upgrade-guides/core-2 https://clerk.com/docs/guides/development/upgrading/upgrade-guides/core-2/nextjs https://clerk.com/docs/account-portal/overview