ezerve

Terms of service

Updated 2026-07-04

These terms are an agreement between Pixlburst, LLC (doing business as ezerve) and you. They cover the ezerve platform: the admin used by businesses, the booking sites used by their customers, and the ezerve API and MCP server. Plain language throughout; the section on payments is the one everyone should actually read.

1. Who these terms cover

Businesses — the organizations that create an ezerve workspace, model their assets, and take reservations. If you accept these terms for a business, you confirm you're authorized to bind it.

Booking customers — people who reserve with a business through ezerve, with or without an ezerve account. Sections 5, 7, and 9–12 apply to you; your reservation itself is a relationship with the business, not with ezerve.

2. Early access

ezerve is in early access. Features arrive and change quickly, quotas and pricing are marked as launch placeholders, and occasional rough edges are part of the deal. We commit to honesty about state — the changelog records what shipped — but early access is offered as-is, and we may modify or discontinue features while the product finds its final shape.

3. Your account and workspace

Keep your credentials secure; you're responsible for activity under your account. Business owners control their staff's roles and access, and are responsible for what their staff do in their workspace. We may suspend accounts that break these terms, after notice where practicable.

4. Payments: whose money is whose

This is the load-bearing section.

Your customers' payments are your money, not ours. When a business connects payments, charges run on the business's own Stripe account under the business's own agreement with Stripe. The business is the merchant of record. ezerve never takes custody of customer funds, never routes them through an ezerve balance, never charges a percentage of them, and never deducts anything from them. Refunds, disputes, and payouts are between the business, its customers, and Stripe.

What ezerve charges businesses appears in exactly one place: the ezerve subscription invoice — a published plan fee plus, where applicable, a flat per-booking meter with a published definition. The meter is platform billing for use of the software; it is not a payment fee and does not touch customer money.

Because ezerve does not hold or transmit customer funds, ezerve is not a payment processor, money transmitter, or escrow service for business-customer transactions.

5. Reservations are the business's promise

A reservation made through ezerve is an agreement between the booking customer and the business — including prices, cancellation deadlines, and no-show policies the business sets. ezerve provides the machinery (and enforces the calendar's integrity), but the service being reserved, and any dispute about it, belongs to the business. Booking customers should direct service questions to the business first.

6. Your data

Businesses own the data they create and their customer relationships. Booking customers own their personal data, handled per the privacy policy. We claim no rights in your data beyond what's needed to operate, secure, and improve the platform. On termination, businesses can export their data during a wind-down window before deletion.

7. API, MCP, and automated agents

API and MCP access uses tokens the business controls; you're responsible for what your tokens do, so scope them narrowly and revoke them when in doubt. Automated agents (including AI assistants booking via MCP) act as agents of whoever operates them — a booking made by your assistant is your booking. Write-capable MCP tools are off by default and require the business's explicit opt-in. Rate limits and field-stability rules published in the help corpus are part of these terms.

8. Acceptable use

No unlawful use, no abuse of other tenants, no attempting to bypass tenant isolation or rate limits, no scraping other businesses' customer data, no interference with the service. We may throttle or suspend abusive workloads to protect everyone else.

9. Disclaimers

The platform is provided "as is" and "as available", without warranties of any kind, express or implied — including merchantability, fitness for a particular purpose, and non-interruption. We work hard on reliability and publish honestly about incidents, but we don't warrant uninterrupted or error-free operation, and during early access, expectations should be sized accordingly.

10. Liability cap

To the maximum extent the law allows: neither party is liable for indirect, incidental, special, consequential, or punitive damages, or lost profits or revenue. ezerve's total aggregate liability arising out of these terms will not exceed the greater of (a) the amounts the business paid ezerve in the twelve months before the event giving rise to the claim, or (b) one hundred US dollars. Nothing here limits liability that can't lawfully be limited.

11. Termination

Businesses can cancel any time; paid periods run to their end. We may terminate for material breach with notice, or immediately for abuse that endangers the platform or other tenants. Sections that by their nature survive (4, 6, 9, 10, 12) survive.

12. Governing law; the rest

These terms are governed by the laws of the state in which Pixlburst, LLC is organized, without regard to conflict-of-law rules, and disputes belong to the courts of that state. If a provision is unenforceable, the rest stands. These terms plus the privacy policy are the whole agreement; updates get a new date, and material changes are announced to account holders before they take effect.

Contact

Pixlburst, LLC · legal@ezerve.com