Skip to main content

Terms of Service (draft outline)

Updated October 10, 2026

Draft — pending legal review; not yet in effect

This document is a working draft prepared for counsel. It may change before launch and is not yet in effect.

Draft for legal review — not in effect.

This page is a structured outline for counsel. It lists the headings the Terms need and the product facts each heading depends on. Text in [COUNSEL: …] must be drafted or decided by counsel. Nothing on this page is a binding term, and it must not be presented to customers as final.

1. Parties and acceptance

  • Provider: [COUNSEL: legal entity name, registered address, company number].
  • Customer: the person or organization that creates a workspace. One user account can belong to several workspaces; each workspace is a separate customer account for billing.
  • Acceptance mechanism: [COUNSEL: click-wrap on sign-up; the sign-up page currently has no terms checkbox — Eng to add once the text exists].
  • Minimum age and capacity: [COUNSEL: minimum age; business-use-only statement].

2. Definitions

Product terms used across the app and help center that the Terms should define consistently:

  • Workspace (organization), member, role, seat.
  • Brand, Brand Brain (a knowledge base built from the customer's website and documents), project, persona (an AI influencer: synthetic character, mascot, faceless persona or consented digital twin of a real person), cohort.
  • Credits: the unit for paid actions. Estimate, reservation, capture, release (see section 6).
  • Output: any text, image, audio or video generated through the service.
  • Integration modes: Mock (simulated, nothing reaches the real service), Sandbox (provider test environment) and Live. Statuses: Available, Beta, Waitlist, Manual export, Coming soon, Deprecated, Disabled.
  • [COUNSEL: "Customer Content", "Customer Data", "Third-Party Services", "Professional Services"].

3. The service

  • Description: brand knowledge, AI persona creation, script/image/video/voice generation through third-party AI providers, editing, quality and compliance review, approvals, social publishing, analytics and recommendations, automation (workflows, Autopilot, Copilot, MCP), public API and webhooks, professional services marketplace, agency and white-label features.
  • Third-party dependency: generation runs on third-party AI providers chosen per task by a router; social publishing runs through social network APIs or an aggregator. The availability of each depends on that third party and is labelled in the app by status and mode. [COUNSEL: no guarantee of any specific provider or model; providers can be replaced or deprecated; model migrations are offered in the app].
  • Beta, Waitlist and Coming-soon features: [COUNSEL: beta terms, no SLA, may change or end].
  • Early access: the public landing page says the service is "in early access". [COUNSEL: early-access disclaimer, if kept at launch].
  • Service levels: [COUNSEL: SLA or none; status page link once it exists].

4. Accounts and security

  • Sign-in methods in the app today: email and password, an emailed one-time sign-in link (only when the operator has email sending configured), and enterprise SSO (OIDC/SAML) with SCIM provisioning (Beta). The authentication backend can also accept Google or Microsoft sign-in when configured, but the sign-in page shows no such buttons today; database tables for passkeys and two-factor authentication exist without a user interface. [Eng: confirm before launch which methods are offered].
  • Workspace security policies (verified domains, enforced SSO, IP allow-list) can restrict how members sign in.
  • Customer responsibilities: keep credentials and API keys secret; API keys are shown once at creation.
  • Workspace owners control membership and roles; access can be suspended.
  • [COUNSEL: responsibility for members' actions, notification of unauthorized use].

5. Customer content, outputs and licences

  • Inputs the customer provides: website URLs (the service reads public pages and respects robots.txt), documents, product pages, images, voice samples, scripts, brand claims and evidence.
  • Outputs are stored in the customer's workspace with provenance (which model, prompt version, cost, sources).
  • [COUNSEL: ownership of inputs and outputs as between the parties; licence to the provider to host, process and display content to operate the service; no training on customer content unless stated — Eng confirms the product does not train models on customer content; third-party provider output terms differ and are recorded per provider in the registry].
  • Provider-specific output terms: each AI provider has its own commercial-use and output terms; the platform blocks Live use of a provider until its terms are reviewed and recorded. [COUNSEL: pass-through of provider output terms, if required].
  • Feedback licence: [COUNSEL].

6. Credits, plans and payment

  • Plans: monthly subscription plans from a plan catalog that the operator edits without a code release; prices shown in the app and on the pricing page. [COUNSEL: price-change notice period].
  • Free trial: a trial offer with a credit allowance may apply; abuse signals (hashed IP and device identifiers) are checked. [COUNSEL: trial terms].
  • Credits: every paid action shows an estimate first; on confirmation the estimate is reserved from the balance; on completion only the actual cost is captured and the remainder is released. If the actual cost would exceed the reservation, the customer is asked to reconfirm. Failed jobs release the reservation.
  • Credit packs, auto-recharge and spending limits are available in Settings → Billing. [COUNSEL: expiry of plan credits and pack credits, refundability, rollover].
  • Seats: paid per seat; inviting beyond the seat count is blocked until a seat is added.
  • Plan changes: upgrades and downgrades in the app with a proration preview; cancellation takes effect at the end of the billing period and can be resumed before then.
  • Payment processing by Stripe (Checkout, Customer Portal, Billing, Tax). [COUNSEL: taxes, currency, invoicing for enterprise accounts (manual invoices exist), late payment and dunning, suspension for non-payment].
  • BYOK (bring your own AI provider key): when a platform operator enables it for a workspace, calls on the customer's key are billed by that provider to the customer, plus a platform fee in credits.

7. Acceptable use

  • Incorporate the Acceptable Use Policy by reference: Acceptable use policy.
  • Product-enforced rules the Terms should reference: AI disclosure, endorsement disclosure, claim review, consent for real people's likeness and voice, no minors' likeness, block on public-figure look-alikes, licensed music and footage. These are hard gates that cannot be overridden in the app.
  • [COUNSEL: suspension and termination for AUP breach].

8. Social networks and third-party services

  • The customer connects their own social accounts through OAuth; tokens are stored encrypted and can be disconnected at any time.
  • Publishing is subject to each network's terms and review status (for example, unaudited TikTok API clients post privately only).
  • Commerce, list-sync and payout integrations (Shopify, WooCommerce, Stripe Payment Links, Klaviyo, Mailchimp, Twilio, Stripe Connect) are labelled Coming soon or Beta and run in Mock only today.
  • [COUNSEL: the customer is responsible for compliance with third-party terms; no liability for third-party outages or policy changes].

9. Automation and AI agents

  • Workflows, Autopilot, Copilot and MCP clients can act on the customer's behalf within an automation policy, budgets, required approvals and kill switches set by the customer.
  • [COUNSEL: the customer remains responsible for content published through automation; human approval settings].

10. Professional services

  • Services ordered in the marketplace (for example a persona creation package) are delivered by platform staff inside the customer's workspace under a time-limited, audited access grant.
  • [COUNSEL: separate service terms or an order form; acceptance and completion; refunds].

11. Agency and white label

  • Agencies can manage client workspaces, white-label reports and use a custom domain. Client re-billing is labelled Coming soon.
  • [COUNSEL: agency is responsible for its clients' compliance; data ownership between agency and client workspaces].

12. Public API, webhooks and MCP

  • API keys with scopes, signed webhooks, SDKs and no-code connectors (Zapier Beta, n8n Beta, Make Coming soon).
  • [COUNSEL: API terms, rate limits, no reverse engineering, changes with notice].

13. Privacy and data protection

14. Confidentiality, warranties, liability, indemnities

  • [COUNSEL: all]. Product facts to consider: outputs are AI-generated and can be inaccurate; recommendations and portfolio decisions are labelled "Recommendation only — requires your acceptance"; analytics show metrics a network does not report as unavailable rather than zero.

15. Term, suspension and termination

  • Product facts: there is currently no self-service account or workspace deletion and no self-service data export in the app (see the privacy outline). [COUNSEL: data return and deletion on termination; Eng must build the tooling before launch].

16. General

  • [COUNSEL: governing law, jurisdiction, dispute resolution, changes to the Terms and notice method, assignment, force majeure, notices, entire agreement, language (EN/ES versions — which prevails)].

More in Legal