IER-0
Home
Legal

Terms

Operational terms for using a governed AI support cockpit, including human approval responsibility, provider dependencies, and acceptable support workflows.

AI role
Assistive

AI prepares outputs but does not own outcomes.

User role
Responsible

Workspace operators approve customer-facing actions.

Providers
External

Connected services have their own terms.

1.0

Use of the product

Tier0 is intended for governed email support operations. Users are responsible for configuring projects, support addresses, domains, policies, knowledge sources, seats, retention, integrations, billing, and approval settings appropriately. The product is not intended for cold email, newsletters, uploaded-contact blasting, or outbound-only campaigns.

  • Project setup
  • Policy configuration
  • Support-only workflows
2.0

Human approval responsibility

AI-generated classifications, summaries, drafts, risk labels, citations, and proposals should be reviewed by authorized operators before customer-facing actions occur unless a project policy explicitly allows a narrow low-risk path. Workspace operators remain responsible for the accuracy, tone, legality, and appropriateness of customer-facing replies.

  • Draft review
  • Approval decisions
  • Operator accountability
3.0

Provider dependencies

The product depends on external services for authentication, email transport, Postgres, object storage, AI model calls, durable workflows, queues, observability, voice, and payments. Vercel, Neon, Resend, Stripe, LiveKit, Google/Gemini, and other configured model providers may each apply their own availability, rate-limit, abuse, security, privacy, and data-processing terms.

  • Email, auth, database, and infrastructure providers
  • Direct AI model providers
  • Billing, voice, and storage providers
4.0

Prohibited use

The product should not be configured to perform autonomous refunds, account cancellations, account upgrades or downgrades, legal advice, medical advice, financial advice, secret access, cross-workspace data access, bulk sending, spam, phishing, harassment, or unreviewed high-risk actions.

  • No autonomous high-risk side effects
  • No bulk or cold email
  • No cross-tenant access
5.0

Customer data responsibilities

Workspace owners are responsible for having appropriate rights, notices, and consents for support content they import, upload, route, or process through the product. Do not upload secrets, payment card data, health records, children's data, or regulated data unless your agreement, plan, provider configuration, and internal policy explicitly permit that use.

  • Use appropriate notices and permissions
  • Do not upload unnecessary sensitive data
  • Configure provider agreements before production traffic
6.0

Credits, limits, and billing

Support credits, voice-minute limits, inbound envelope limits, attachment limits, knowledge-ingestion limits, storage limits, retention limits, and model budgets may apply. When a support-credit or voice-minute cap is reached, the affected AI or voice feature may pause while the inbox remains available. Stripe or another payment processor may handle checkout, invoices, taxes, payment methods, disputes, and customer portal access.

  • No surprise autonomous overage by default
  • AI and voice can pause at cap
  • Payment processor terms apply
7.0

Support and notices

Operational support requests, account questions, abuse reports, privacy requests, and legal notices can be sent to support@driftrail.com. We may require workspace verification before discussing account-specific data or making administrative changes.

  • support@driftrail.com
  • Workspace verification
  • Abuse and privacy requests
8.0

AI Autonomy & Codebase System Disclaimers

YOU ACKNOWLEDGE AND COVENANT THAT THE SOURCE CODE, OPERATIONAL PIPELINES, INTERACTIVE PANELS, AND INFRASTRUCTURE OF THIS PLATFORM IS PARTIALLY OR WHOLLY CONSTRUCTED, GENERATED, MAINTAINED, AND PATCHED BY AUTOMATED ARTIFICIAL INTELLIGENCE AGENTS (E.G., SELF-HEALING AI DEVELOPER SCHEDULERS). YOU EXPRESSLY ASSUME ALL ASSOCIATED RISKS REGARDING AI AUTONOMY AND WAIVE ANY DIRECT REGULATORY OR CONTRACTUAL ACTION CONCERNING MACHINE-ENGINEERED REFACTORINGS.

  • Self-engineered AI runtime logic
  • Complete user assumption of code safety risks
  • Indemnification for autonomous modification outcomes
9.0

Third-Party AI Compliance & Google Gemini Terms

Your configuration, use, and access of this product explicitly constitutes agreement and strict adherence to the respective terms and privacy policies of our subprocessing AI providers. Specifically, you agree to be bound by the [Google Generative AI Service Terms / Google Gemini Terms](https://ai.google.dev/gemini-api/terms) and [Google Privacy Policy](https://policies.google.com/privacy). Any breach of third-party rules results in immediate suspension.

  • Adherence to Google Generative AI Service Terms
  • Agreement to Google Privacy Policy data boundaries
  • Warranty of user compliance with third-party rules
10.0

Verbose Waiver of Liability & Absolute Class Action Disclaimers

UNDER NO LEGAL THEORY, CONTRACT, TORT, OR OTHERWISE, SHALL THE OPERATORS, ASSOCIATED HUMAN INDIVIDUALS, OR AI SYSTEMS BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY INDIRECT, SPECIAL, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES OR LOST PROFITS. YOU AGREE TO INDEMNIFY AND HOLD HARMLESS THE OPERATORS FROM ANY AND ALL CLAIMS ARISING OUT OF YOUR USE. ALL DISPUTES SHALL BE RESOLVED EXCLUSIVELY VIA BINDING INDIVIDUAL ARBITRATION, AND YOU EXPLICITLY WAIVE ANY RIGHT TO CLASS-WIDE LITIGATION.

  • Complete disclaimer of direct and indirect liability
  • Mandatory binding individual arbitration covenant
  • Unconditional class action and jury trial waivers
Operations

What this means in production.

These pages describe the product contract behind the UI, not a decorative brochure. Each surface should connect back to the same governed support loop.

Control boundary

AI is assistive, not the accountable operator.

Operator workflow

Support moves through secure ingest, AI preparation, human approval, outbound execution, and audit evidence.

Configuration impact

Provider setup, project policies, knowledge trust, retention, and billing limits decide how this behaves for a real workspace.

Proof points

Designed for governed support, not hidden autonomy.

AI is assistive, not the accountable operator.
Support workflows must remain support workflows, not outbound marketing.
Contact support@driftrail.com for account, abuse, privacy, or legal requests.
Next

Keep exploring the operating model.