Back to ToastTi

Legal document · Private Pilot

Terms and EULA for the beta product.

Draft/current beta terms for ToastTi access, acceptable use, marketplace responsibility, automation boundaries, billing and usage-fee estimates, and software license basics.

These Terms & EULA are draft/current beta terms for product clarity. Final customer terms should be reviewed by qualified counsel before broad rollout.

01

Beta and private access

ToastTi access may be limited to invited organizations, Private Pilot participants, and supported marketplace workflows. Public self-serve availability is not guaranteed by these draft terms.

02

EULA-style license basics

ToastTi grants authorized users a limited, revocable, non-transferable right to use the software for their organization operations while access remains active and permitted.

03

Acceptable use

Users may not attempt unauthorized access, scrape or attack the service, upload unlawful content, misuse data, evade security controls, or use ToastTi to violate marketplace or payment-provider rules.

04

Marketplace provider responsibility

Users remain responsible for their marketplace accounts, product data, seller obligations, provider terms, account permissions, pricing choices, listing accuracy, and fulfillment decisions.

05

Supported and unsupported providers

Current Controlled Production Pilot support focuses on Shopify, StockX, and GOAT/Alias. eBay and TikTok are not active customer setup paths today and should not be treated as current support.

06

No unsupported write abuse

Provider writes must stay inside supported actions, exact targets, verification checks, idempotency controls, readback/rollback requirements, and enabled organization permissions.

07

Automation disclaimers

ToastTi automation is verified before update. It should not be treated as a guarantee of uninterrupted provider availability, error-free marketplace state, or absolute oversell prevention.

08

Billing and usage-fee disclaimers

Usage fees, location add-ons, plan changes, invoices, and payment collection depend on the applicable plan, contract, tracked sales, exemptions, and configured billing system. Public pages may show estimates rather than final charges.

09

Customer data and permissions

Organizations are responsible for granting appropriate user roles and for ensuring team members access only the inventory, orders, reports, and marketplace workflows they are allowed to operate.

10

Limitations and remedies

Final limitation, warranty, indemnity, termination, dispute, and remedy language should be drafted or reviewed by qualified counsel before broad customer launch.