Legal and trust
Product-accurate public boundaries for the current prototype. Final production policies and contracts still require jurisdiction-aware legal review.
Trust center
These summaries explain the current direction without inventing production compliance, live providers, or finalized contractual promises.
Account, acceptable-use, service, customer-content, and prototype-availability boundaries.
Read overviewHow restaurant, Partner, customer, support, and provider data are conceptually separated.
Read overviewNecessary session state, preferences, and the boundary before optional analytics are enabled.
Read overviewWorkspace scope, connection capabilities, protected routes, and remaining production hardening.
Read overviewWorking prices, provider charges, subscription evidence, cancellation, and contracting status.
Read overviewThe categories of hosting, identity, app-store, database, payment, AI, and communication providers Plenty may use.
Read overviewPlenty may provide website review, setup, a Branded Restaurant App, customer web ordering, Plenty Partner workspaces, connected website surfaces, and related services according to the agreed plan and implementation state. Restaurants remain responsible for authorized access, accurate prices, menu claims, allergens, legal pages, fulfillment, and their use of customer data. Prototype or preview behavior must not be treated as a production guarantee.
Ask a questionPlenty separates restaurant Partner access from restaurant-facing customer accounts and orders. The platform may process restaurant profile and workspace data, customer account and order data, support messages, consent records, technical events, and provider references where those features are enabled. Final privacy notices, lawful bases, retention schedules, and data-subject workflows require production-specific legal review.
Ask a questionNecessary cookies or browser storage may support authentication, customer sessions, cart continuity, security, and saved preferences. Optional analytics, marketing, or third-party tracking should not be assumed enabled and must be documented and consented to where required before production use.
Ask a questionThe prototype uses workspace-scoped access, protected APIs, scoped Site and Integration Connections, capability-bound customer status, and server-side provider boundaries in implemented areas. Production still requires deliberate hardening, credential rotation, rate limits, monitoring, incident procedures, and reviewed deployment configuration.
Ask a questionPublished prices on this prototype are working launch recommendations, exclude VAT, and are not a binding quote. Stripe sandbox evidence is not live billing. Final renewal, cancellation, refund, service-delivery, provider-cost, and fair-use terms must be agreed before a production subscription or project begins.
Ask a questionDepending on the commissioned setup, Plenty may rely on identity, hosting, Apple or Google app-store services, database, payment, email, messaging, mapping, AI, image, and connected-site providers. Store publication remains subject to third-party review. Exact processors, regions, transfer terms, retention, and enabled services must be documented against the production configuration rather than inferred from prototype code.
Ask a question