Terms posture

Use ControlLayer as an operational review system, not as legal advice.

ControlLayer is for invite-only workspaces with guided setup. Access, billing, optional capabilities, and operational decisions remain subject to named ownership and human review.

Review privacy Review billing

Use stance

No open tenant creation, no hidden provider activation.

Public pages explain how ControlLayer is used after a tenant is manually provisioned. They do not create a self-service tenant, charge a payment provider, or activate external services by themselves.

Access

Invite-only

Users need an issued invitation, authenticated session, and tenant membership before using private workspaces.

Billing

Manual

Public pages do not create Checkout sessions; tenant admins manage fixed subscriptions inside authenticated billing routes.

Advice

None

ControlLayer can organize operational records and review queues, but no legal advice is provided by the product.

Access terms

Tenant access starts with manual provisioning.

ControlLayer public routes may describe the product, pricing posture, privacy posture, and workspace handoffs. They are not an open registration system and do not create tenants from the browser.

A workspace should be created by an implementation owner after commercial, security, access, and service-setup expectations have been reviewed.

Invite-only access

Users enter through issued invitations and tenant membership checks rather than open account creation.

No self-service tenant creation

Public pages and invitation acceptance do not grant a customer the right to create a new tenant without manual provisioning.

Manual provisioning

Tenant setup, module access, owner roles, limits, and support handoffs remain implementation-led.

Product use

Operational summaries require review.

ControlLayer supports contract registers, renewals, suppliers, sites, compliance evidence, imports, tasks, audit activity, and reporting for post-signature operations.

AI and OCR outputs, compliance views, renewal cues, and evidence summaries are operational aids. They require human review and do not provide legal advice, legal conclusions, or replacement counsel.

Human accountability

Operators remain responsible for reviewing extracted fields, source context, recipients, exports, and workflow actions before use.

Provider-backed features only when configured

Storage, OCR, AI, email, notifications, exports, integrations, and billing providers run only when approved for the tenant and environment.

No silent external sends

Supplier outreach, email, exports, and connected-system updates require explicit review before anything leaves the workspace.

Commercial terms

V1 billing is fixed-subscription and conservative.

Pricing pages can describe plans, limits, usage meters, and commercial packaging. V1 uses fixed Stripe subscriptions while metered overage charge posting and automated provider-side usage charges remain disabled.

Fixed subscription billing means subscription records, tenant limits, and plan changes stay explicit while metered overage charge posting remains outside V1 unless a later approved release changes that posture.

Fixed subscription billing

Plan changes, renewals, and exceptions are handled through fixed subscription controls and finance/support review rather than metered overage automation.

Usage gates

The product may enforce usage limits before expensive work starts, but that does not imply provider charges are posted.

Clear availability claims

If a provider is not configured, approved, or release-ready, the relevant product lane should remain unavailable or manual.

Use commitments

What these terms require from V1 use

Review-led operations

Use tenant workspaces responsibly

Keep customer data, supplier records, contract files, source spans, exports, and audit activity inside the tenant boundaries assigned to the user.

Treat outputs as operational aids

AI, OCR, and reporting outputs support review but must not be treated as legal advice or unreviewed authoritative decisions.

Respect manual activation

Do not assume an optional capability, workspace module, or billing automation is available until it is configured and approved.

Boundary note

Public terms do not expand V1 scope.

The product is post-signature operational control. Native drafting, redlining, e-signature, legal advice, and automatic payment-provider charge posting are outside this V1 public posture.

Operational rule

Invite-only access, manual provisioning, fixed subscription billing, and human review stay in force.

Provider-backed features are only available when configured for the tenant and release-approved. Otherwise the correct posture is unavailable, manual, or blocked.

Provision

Implementation owners confirm workspace setup, owner roles, limits, access, support, and connected-service readiness.

Review

Users review operational records, source context, recipients, exports, and decisions before relying on them.

Govern

Workspace owners monitor usage, membership, connected services, billing, and audit records through the product and operating process.

These terms are a V1 product posture summary for ControlLayer public routes. Customer-specific commercial terms, data processing terms, acceptable-use terms, and support instructions may add further obligations.