Terms
Public terms boundary for payroll-sensitive operations.
Buyer-safe ClaraOps service terms boundaries covering account responsibility, third-party integrations, source-data accuracy, payroll provider, accountant, legal, tax, HR, and owner-review boundaries, limitation of liability, termination/export requests, support boundaries, and acceptable use.
Agreement first
Formal customer agreements should be reviewed before operational onboarding. This public page explains responsibility boundaries for evaluation; it is not a signed customer agreement, DPA, BAA, SLA, indemnity, or substitute for legal review.
Account responsibility
Customers remain responsible for accurate account information, authorized admins/operators, permission review, credential protection, and reviewing generated outputs before relying on them operationally.
Third-party integrations
ClaraOps may organize authorized SimplePractice exports, Google Workspace context, hosted app/database/storage workflows, and approved export or email-provider workflows when configured, without claiming official SimplePractice or Google partnership or certification.
Source-data accuracy
Customers are responsible for the accuracy, completeness, timeliness, and authorization of source records. ClaraOps can flag stale source material, missing evidence, unusual pay, adjustment questions, and review blockers, but it cannot make incomplete source data correct without customer review.
What ClaraOps does not replace
ClaraOps supports payroll-readiness review, exception handling, evidence organization, export preparation, and audit-friendly operating records. It does not run payroll, file payroll, submit payroll taxes, provide legal/tax/HR advice, guarantee compliance, or replace the payroll provider, accountant, attorney, HR advisor, or final owner review.
Limitation of liability
Public materials should not promise error-free payroll, guaranteed compliance, guaranteed payroll precision, uninterrupted availability, guaranteed savings, or certification status that has not been formally approved and documented. Any liability, warranty, indemnity, SLA, breach-notice, or damages language belongs in a reviewed customer agreement.
Termination and data requests
Account termination, export, retention, and deletion requests are reviewed request paths. ClaraOps should not promise immediate deletion, immediate backup-byte purge, or unreviewed self-service purge from public pages.
Support boundaries and acceptable use
Support boundaries and acceptable use should require consent or reviewed break-glass approval where sensitive customer data is involved. Acceptable use should prohibit credential sharing, unauthorized access, source-system bypass attempts, sensitive uploads through public demo paths, and requests for ClaraOps to make decisions outside approved service boundaries.
No instant onboarding
This page does not create a customer account, checkout session, payment-provider action, public upload path, account provisioning, or production workflow.
Last updated
May 27, 2026
This is not a signed agreement, DPA, BAA, SLA, indemnity, certification claim, checkout, instant onboarding, hosted mutation, or payroll-provider action.
Beta scope
Current paid-beta terms scope
This page summarizes buyer-facing responsibility boundaries for evaluation and paid-beta onboarding. Formal customer agreements, DPA/BAA terms, SLAs, indemnity, warranties, payment-provider actions, and custom commercial commitments require separate reviewed approval.
Contact
Agreement or account questions
Email support@claracaps.com without PHI, payroll files, employee SSNs, credentials, raw payroll rows, exploit payloads, or sensitive customer data.
Runtime smoke boundary
What was checked for paid-beta readiness
Source-backed runtime smoke checks confirm the public legal routes are crawlable policy pages while app, payroll, exports, support-console, and account data routes stay private/no-store/auth bounded.