Legal Center
Thorbis legal & trust
Everything that governs how you use Thorbis, how money moves, how we handle data, and how we communicate, written plainly and kept in one place. Thorbis, Inc., a Delaware corporation.
These documents are provided for transparency and are not legal advice. Your use of Thorbis is governed by the agreement you accept.
- Use of Thorbis
- Terms, acceptable use, accessibility, AI terms, and the rules that govern the service relationship.
- Data and privacy
- Privacy, privacy rights, data processing, subprocessors, cookies, and how customer information is handled.
- Payments and messaging
- Payment terms, SMS disclosures, communication rules, and compliance pages tied to customer workflows.
- Trust and security
- Security context, incident expectations, and links to pages that explain platform reliability and control.
Agreement
Terms of Service
The master agreement governing your use of Thorbis — pricing, billing, acceptable use, warranties, liability limits, and dispute resolution.
ReadAcceptable Use Policy
What you may and may not do on the platform — anti-spam, telephony, content, security-testing, and enforcement rules.
Read
Money & payments
Payments & Money-Movement Terms
How money moves through Thorbis: card payments, payouts, buckets, financing, payroll, and taxes — and the hard line that Thorbis is software, not a bank, lender, processor, accountant, or payroll provider.
ReadAI Disclosure & Acceptable Use
How the Thorbis AI assistant (“Brain”) works, its autonomy limits and guardrails, and your responsibility for reviewing and standing behind AI-assisted actions.
Read
Privacy & data
Privacy Policy
What personal data we collect (yours, your customers', your employees'), why, who we share it with, how long we keep it, and the choices you have.
ReadYour Privacy Rights (GDPR & CCPA/CPRA)
State- and region-specific rights, how to submit a request, authorized agents, non-discrimination, and our commitment that we do not sell personal information.
ReadData Processing Addendum
The controller/processor terms that apply when Thorbis processes personal data on your behalf, including Standard Contractual Clauses and breach notification.
ReadSubprocessors
The third-party service providers that help us run the platform, what each one processes, and how we notify you of changes.
ReadCookie Policy
The cookies and similar technologies we use, what they do, and how to control them.
Read
Review paths
Find documents by the decision you are making
Legal pages should help operators, buyers, and admins review the exact obligation connected to a workflow.
- Buyer review
- Terms, pricing commitments, support expectations, and service boundaries before procurement signs off.
- Data review
- Privacy, DPA, subprocessors, cookies, and how data moves through integrations and vendors.
- Communications review
- SMS, calls, email, consent, opt-out handling, and payment communication rules.
- Trust review
- Security posture, accessibility, incident expectations, and AI disclosure context for administrators.
How to read this
Legal documents should map to product decisions
The index is organized so buyers, owners, and administrators can find the document connected to the feature they are enabling.
- Start with Terms and Privacy when evaluating the core service relationship.
- Review DPA and subprocessors before sending customer or employee data through integrations.
- Use SMS and payment documents when enabling customer communications or in-field payment flows.
Procurement moments
Review the document before the workflow goes live
The right legal page depends on what the business is about to enable, not just the document title.
- Before signing
- Review terms, pricing references, support expectations, entity details, and contract acceptance path.
- Before importing data
- Review privacy, DPA, subprocessors, cookies, and the data categories moving into Thorbis.
- Before messaging customers
- Review SMS, calls, email, consent language, payment links, and opt-out handling.
Contact routing
Send the request to the right owner
Admin checklist
Before enabling a sensitive workflow
Use this as a lightweight route through the legal center when turning on integrations, payments, messaging, or AI-assisted workflows.
- Match each legal document to the feature being enabled.
- Keep a copy of the accepted agreement and effective date with procurement records.
- Review privacy and DPA documents before importing customer, employee, or payment data.
- Use legal@thorbis.com for document questions that need a written trail.
Legal governance
Keep document review connected to operations
- Effective dates
- Treat document dates as part of procurement records when terms, privacy, or data processing obligations are reviewed.
- Workflow links
- Connect each legal page to the product workflow it supports: payments, messaging, AI, security, or privacy.
- Review trail
- Keep questions and exceptions in writing so procurement, legal, and admins share the same record.
Decision matrix
Start with the workflow, then open the policy
The legal center should make it clear which document matters before enabling customer messaging, payments, AI, data import, or procurement review.
Enabling AI
Review AI terms before using assistant-driven actions or generated recommendations.
Read policyImporting customer data
Review privacy, DPA, and subprocessors before moving operational data.
Read policyCollecting payments
Review payment terms before sending links, invoices, and on-site collection flows.
Read policyTexting customers
Review consent, opt-out, and carrier disclosure expectations.
Read policy
Review output
A legal review should produce a clear operating note
- Owner
- Who approves the workflow or exception?
- Record
- Where is the accepted document, date, and question trail stored?
- Action
- What product setup, admin change, or vendor review happens next?
Sensitive workflows
Review the policy before enabling the workflow
AI-assisted actions
Review AI disclosure, approval expectations, and operational boundaries.
Read policyPayments
Review money movement, customer payment, and billing terms before enabling payment flows.
Read policyText messaging
Review consent, carrier disclosures, opt-out handling, and communications terms.
Read policy
Policy routing model
Legal review should start with the workflow being enabled.
- Customer data
- Route the reviewer to the document connected to the product behavior they are about to turn on.
- Payments
- Route the reviewer to the document connected to the product behavior they are about to turn on.
- Messaging
- Route the reviewer to the document connected to the product behavior they are about to turn on.