Allure Connect
Legal posture

Commercial clarity and tenant safety are part of the product, not separate from it.

Connect legal posture should make the service boundary, billing boundary, and data handling posture legible for buyers, operators, and procurement.

Operational stance

Connect avoids pretending uncertain states are final states.

Provisioning waits for Stripe confirmation, access is tenant-aware, and customer operations live behind explicit product routes.

Checkout does not imply activation until billing confirmation lands.
Workspace access is resolved through signed-in identity and tenant membership.
Operational controls like credentials, dispatch, and reporting sit in product routes, not hidden side tools.

Published documents

Terms of ServicePrivacy PolicyFair Use Policy

Service terms

How customers can use Connect, what the service boundaries are, and how commercial use is governed.

  • Service access and account use
  • Commercial usage boundaries
  • Termination and change management

Privacy and data posture

Connect handles tenant isolation, learner-session state, and customer operations data as product-critical responsibilities.

  • Tenant-scoped access
  • Learner session persistence
  • Operational audit posture

Billing and procurement

Self-serve plans stay checkout-driven, while enterprise keeps a contact-sales boundary for procurement and implementation review.

  • Stripe-confirmed activation
  • Enterprise outside generic checkout
  • Workspace plan and quota ownership

Questions

Need legal or procurement clarification?

Enterprise buyers and procurement reviewers should not have to infer the commercial path from a generic checkout.

Contact the team

Use email for procurement, legal, or enterprise rollout questions that need a human answer.

Revisit pricing and plan boundaries

Self-serve and enterprise paths are separated on purpose so the commercial story stays honest.