Restaurant Agreement

1Scope and acceptance

This Restaurant Agreement applies when a restaurant, cafe, ghost kitchen, catering business, or other food-service business uses Plaum's restaurant-facing products. Those products currently include restaurant onboarding in the Plaum mobile app, restaurant profiles, menu and dish publishing tools, ordering features, reservation settings, QR dine-in tools, staff access, managed websites, analytics views, support channels, and subscription or billing features inside the Plaum Web App.

By creating, claiming, accessing, or using a restaurant account, or by allowing staff or contractors to use Plaum on the restaurant's behalf, the restaurant accepts this agreement, Plaum's Terms of Service, Privacy Policy, and Refund Policy to the extent they apply.

If the restaurant does not agree, it must not use the restaurant-facing parts of Plaum.

2Authority and restaurant accounts

The person creating or using a restaurant account represents that they have authority to act for the restaurant and to bind the restaurant to this agreement. Plaum may request documents or other proof showing business ownership, operating authority, brand authority, menu authority, or domain authority.

2.1 Authorized use only

Restaurant accounts may be used only by the restaurant, its owners, managers, authorized staff, and authorized service providers acting for the restaurant. Accounts may not be created or used to impersonate a restaurant, take over a listing without permission, interfere with another operator, or publish business information the restaurant is not authorized to control.

2.2 Multiple staff members

A restaurant may invite staff into Plaum and may assign different internal responsibilities, but the restaurant remains responsible for everything done through its accounts, seats, invited users, linked devices, and published tools unless Plaum expressly agrees otherwise in writing.

3Plaum services

Plaum provides software and publishing tools. Plaum does not operate the restaurant, prepare the food, package the order, confirm the allergen accuracy of a meal, supervise the staff on shift, set tax policy for the restaurant, or control how the restaurant fulfills service in the real world.

Plaum's current restaurant-facing services may include some or all of the following: restaurant profile controls, dish and menu management, QR table ordering, order intake and status management, reservation tools, voice or AI-assisted workflows, staff communication tools, analytics surfaces, managed restaurant websites, subscription billing, and support workflows.

Plaum may add, remove, improve, pause, or redesign features over time. Some features may depend on device compatibility, third-party services, internet access, browser support, or region-specific rollout decisions.

4Menu, pricing, and content accuracy

The restaurant is solely responsible for the truthfulness, completeness, and current accuracy of all restaurant-controlled content placed on Plaum. That includes menu item names, prices, modifier prices, quantities, sizes, portion descriptions, taxes, availability, hours, dietary tags, allergen information, reservation policies, deposit amounts, no-show fees, pickup details, contact details, website copy, logos, photos, and any business claims made through Plaum.

4.1 Quantity and pricing clarity

Restaurants must describe items in a way that a reasonable customer can understand. If a posted price is for one taco, one skewer, one side, one scoop, one add-on, or one modifier rather than a full plate, combo, pair, or set, the restaurant must make that clear in the item name or description.

A restaurant may not rely on a customer guessing the serving count, modifier rules, included sides, or final price logic. If pricing is likely to confuse a reasonable diner, the restaurant must clarify it before publishing or must correct it immediately after learning of the issue.

4.2 Availability and current state

Restaurants must keep availability, sold-out status, hours, closures, and seasonal changes reasonably current. If an item, modifier, reservation window, or service mode is no longer available, the restaurant must update the relevant Plaum surfaces promptly.

4.3 Photos, dish cards, and public context

Plaum may show restaurant-controlled content alongside user-generated dish cards, user photos, saved items, creator posts, discovery feed content, or AI summaries. Plaum does not guarantee that every user photo exactly matches the dish's current plating, price, portion size, or service conditions.

The restaurant remains responsible for correcting restaurant-supplied data. If the restaurant believes a Plaum-controlled summary or display creates a materially misleading impression about the restaurant's menu, pricing, availability, or policies, it must notify Plaum promptly so Plaum can review it.

5Orders and fulfillment

Plaum may transmit, display, sync, or organize orders, but the restaurant is responsible for deciding what it offers, preparing the food, packaging the order, honoring service windows, communicating real-world constraints, and fulfilling the transaction properly.

5.1 Operational responsibility

• Accepting or declining orders where the workflow allows it
• Preparing items accurately and safely
• Handling substitutions, stockouts, and special instructions lawfully
• Meeting pickup, dine-in, or service expectations the restaurant offers
• Handling staff-side timing, status changes, and customer handoff

5.2 Plaum software boundaries

Plaum may validate an order against the restaurant's live menu, modifiers, prices, or availability, but that validation does not shift responsibility away from the restaurant. If the restaurant's source data is wrong, stale, or incomplete, the restaurant remains responsible for the consequences.

5.3 Cancellations and service failures

If the restaurant cancels, materially delays, misprices, underfills, refuses, or cannot complete an order after a customer relies on it, Plaum may notify the customer, review a refund request, adjust the restaurant's status on the platform, or take account-level action where repeated or serious failures occur.

6Reservations, deposits, and no-show fees

If the restaurant enables reservation features, it is responsible for the operating rules behind those features. That includes party-size limits, service windows, blackout periods, hold times, cancellation windows, security deposit settings, no-show fees, walk-in treatment, and check-in logic.

6.1 Clear reservation terms

Any deposit, cancellation deadline, late-arrival rule, no-show consequence, or non-refundable condition the restaurant wants enforced must be presented clearly and lawfully through Plaum or through instructions Plaum approves for that workflow.

6.2 Honoring confirmed bookings

A restaurant that activates reservations through Plaum is responsible for honoring valid confirmed bookings unless cancellation is necessary for a legitimate operational or safety reason. If the restaurant fails to honor a valid booking, Plaum may support the diner, review charges, and consider the incident in future platform decisions.

7Managed websites and domains

Plaum may let a restaurant publish a Plaum-hosted website, use a Plaum subdomain, or connect a custom domain. The restaurant is responsible for the legality and accuracy of the public-facing content published through that website, including menu details, hours, reservations, contact details, photos, marketing statements, and ordering information.

7.1 Domain rights

If the restaurant connects a custom domain, it represents that it has the right to use that domain and to point it to Plaum's services. Plaum is not responsible for domain ownership disputes, registrar failures, DNS mistakes made by the restaurant, or third-party outages outside Plaum's control.

7.2 Publication controls

Plaum may provide draft, preview, publish, unpublish, offline, or sync controls. The restaurant is responsible for deciding when its public site should be live and for reviewing content before or after publishing.

8Billing, packages, and payment processing

Plaum may sell restaurant packages or modules through the Plaum Web App. Current package types may include tools such as QR Ordering, Loyalty, and the AI Kitchen Display System, but Plaum may change package names, prices, features, inclusions, or availability over time.

8.1 Subscription timing

Unless Plaum says otherwise in writing, package billing is subscription based. The restaurant is responsible for reviewing package details before activating them and for managing cancellation before the next renewal if it wants future recurring charges to stop.

8.2 End-of-period cancellation

Where Plaum offers cancellation at period end, a cancellation request stops future renewal after the current paid period finishes. It does not usually erase service already provided or undo a renewal that already processed properly.

8.3 Payment processors

Plaum may use third-party processors or billing portals to collect payments, store payment methods, process subscription renewals, and manage invoices. Plaum does not store raw card numbers on Plaum's own servers.

9Refunds, disputes, and cooperation

Plaum may review refund requests, duplicate-charge reports, unauthorized charge reports, reservation disputes, and restaurant billing disputes. Plaum may ask the restaurant for logs, timing, screenshots, staff notes, order history, reservation settings, or other evidence reasonably needed to investigate.

9.1 Restaurant package renewals

A valid restaurant package renewal that already ran is generally not refunded just because the restaurant later stopped using the package, forgot to cancel, changed staff, or left a payment method on file.

9.2 Restaurant-caused customer issues

If a diner refund, reservation dispute, or billing complaint is caused by restaurant-side conduct or restaurant-supplied data, Plaum may take that into account in deciding responsibility, support action, platform action, or future feature eligibility.

10Staff access, security, and acceptable use

The restaurant is responsible for controlling who has access to its Plaum environments, devices, browsers, QR assets, website settings, and subscription settings.

• Keep credentials and device access reasonably secure
• Remove staff access promptly when roles change
• Use Plaum only for lawful restaurant operations
• Do not attempt to disrupt, scrape, reverse engineer, abuse, or overload Plaum
• Do not misuse Plaum AI, voice, messaging, or website tools to harass, defraud, or impersonate

The restaurant is responsible for actions taken through its invited staff, tablets, browsers, or linked business environments unless Plaum confirms a problem was caused by Plaum alone.

11Compliance with law

The restaurant is responsible for complying with all laws, regulations, and industry rules that apply to its business, including rules relating to food safety, allergy and ingredient disclosure, liquor where applicable, tax, employment, accessibility, consumer protection, deceptive marketing, reservation practices, spam laws, and lawful operation of a restaurant in its jurisdiction.

Without limiting the above, the restaurant must not use Plaum to publish materially misleading pricing, false availability, false promotional claims, or reservation or deposit terms that are unlawful or unfair under applicable law.

12Data, privacy, and communications

Plaum handles personal information under Plaum's Privacy Policy. The restaurant is separately responsible for how it uses customer information, staff information, and operational data it accesses through Plaum.

If the restaurant exports, copies, or uses personal information from Plaum, it must do so only for legitimate operational purposes and in compliance with applicable privacy and anti-spam law.

Plaum may send operational emails, billing notices, incident notices, support responses, policy updates, verification requests, and security messages to the restaurant contacts tied to the account.

13Content rights and Plaum's license

The restaurant keeps its ownership rights in content it provides to Plaum, such as menus, logos, names, photos, descriptions, website copy, and other business materials. However, the restaurant gives Plaum a worldwide, non-exclusive, royalty-free license to host, copy, format, adapt, transmit, display, publish, and use that content as needed to operate, improve, promote, secure, support, and provide Plaum's services.

The restaurant promises it has the rights needed to grant that license and that the content does not infringe others' rights or violate applicable law.

14Suspension, termination, and liability

Plaum may suspend, limit, delist, unpublish, or terminate some or all restaurant access if Plaum reasonably believes the restaurant has violated this agreement, created legal risk, misled customers, failed to cooperate with a serious investigation, failed to pay valid charges, misused the platform, or created safety, fraud, trust, or compliance concerns.

14.1 Service is provided as available

Except where the law does not allow it, Plaum provides its restaurant tools on an as-available and as-offered basis. Plaum does not promise uninterrupted service, perfect uptime, or error-free operation across every device, browser, integration, or network condition.

14.2 Restaurant indemnity

The restaurant will defend, indemnify, and hold harmless Plaum and its personnel from claims, losses, damages, liabilities, and reasonable costs arising out of the restaurant's menu inaccuracies, pricing errors, unlawful content, food-service operations, reservation handling, website content, misuse of customer data, staff conduct, or violation of this agreement or applicable law.

14.3 Liability cap

To the fullest extent allowed by law, Plaum's total liability to the restaurant for claims arising out of this agreement will not exceed the amount the restaurant paid to Plaum for the specific affected restaurant services during the three months before the event giving rise to the claim, or CAD $100 if the restaurant paid nothing during that period.

15General terms

• Updates: Plaum may update this agreement as its products, legal obligations, and restaurant workflows change.
• Severability: If one part of this agreement is unenforceable, the rest remains in effect to the extent allowed by law.
• No waiver: If Plaum does not enforce a provision immediately, that does not waive it.
• Assignment: The restaurant may not assign this agreement without Plaum's written consent. Plaum may assign it as part of a merger, financing, sale, or restructuring.
• Governing law: This agreement is governed by the laws of Ontario and the applicable federal laws of Canada.
• Venue: Unless applicable law requires otherwise, disputes will be resolved in the courts located in Ontario, Canada.