Xenia Cloud Terms

These Terms govern use of the Xenia platform and become binding only when incorporated by an executed Cover Page or Order Form.

1. The Agreement.

The Xenia by Yo-Do Software Corp. Cloud Service Terms govern Merchant's use of the Xenia cloud-based platform (the “Cloud Service”). Customer and Provider agree to these terms by executing a Cover Page that specifies Key Terms, Attachments, and any Additional Terms. Collectively, these terms, the Cover Page, and any Orders form the parties' agreement (“Agreement”). In case of conflicts, Section 20(e) (Order of Precedence) governs. Capitalized terms are defined in context or in Section 21 (Definitions).

2. Cloud Service.

Subject to this Agreement, Merchant may use the Cloud Service for its own business purposes during each Subscription Term (“Permitted Use”). The Cloud Service enables Merchant to be discovered by visitors and residents, accept reservations and payments, sell gift cards, and manage transactions through a single integrated platform. Provider reserves the right to update or enhance the Cloud Service from time to time, provided that no modification will materially decrease overall functionality during a Subscription Term without thirty (30) days prior written notice to Merchant.

3. Fees and Revenue Model.

a. Launch Partner Terms. Merchants designated as Launch Partners on the applicable Cover Page will not be charged any platform, subscription, or transaction fees during the term of this Agreement. This no-cost structure is a launch-specific benefit applicable to merchants identified as Launch Partners on the Cover Page.

b. Customer-Side Platform Fees. Customers using the Cloud Service will pay a 5% platform fee on Transactions. This fee is charged to and paid by the customer and is not deducted from amounts owed to Merchant.

c. Gift Card Program. When a customer purchases a gift card through the Cloud Service, the customer pays a fee of 5% plus $1.00. When a gift card is redeemed at Merchant's business, Merchant receives the full-face value with no processing fee deducted. Gift card redemptions are settled in the same manner as other Transactions under Section 5.

d. Future Features. Provider may develop additional platform features beyond those described in this Agreement, including but not limited to active waitlists, in-application advertising tools, and advanced AI-powered features (collectively, “Additional Features”). Additional Features will be offered to Merchant under a separate addendum to this Agreement, which will specify the applicable terms, pricing, and any modifications to the fee structure set forth herein. Merchant's use of any Additional Feature is conditioned on execution of the applicable addendum. Nothing in this Agreement obligates Provider to develop any Additional Feature or obligates Merchant to adopt one.

e. Standard and Future Fee Structures. Provider reserves the right to introduce or modify fee structures applicable to Merchants not operating under Launch Partner Terms, as set forth on the Cover Page or upon thirty (30) days prior written notice to Merchant.

f. Payment. Where fees are payable by Merchant under this Agreement or any addendum hereto, Merchant authorizes Provider to bill and charge Merchant's payment method on file for immediate payment. Late payments are subject to a charge of 1.5% per month or the maximum amount allowed by Law, whichever is less. All fees are non-refundable except as expressly set out in this Agreement.

g. Taxes. Merchant is responsible for any sales, use, GST, value-added, withholding, or similar taxes or levies that apply to its Orders, whether domestic or foreign (“Taxes”), other than Provider's income tax. Fees are exclusive of Taxes.

h. Payment Disputes. If Merchant disputes an invoice in good faith, it will notify Provider within fifteen (15) business days, and the parties will seek to resolve the dispute over a fifteen (15)-day discussion period. Merchant is not required to pay disputed amounts during the discussion period but will timely pay all undisputed amounts. After the discussion period, either party may pursue available remedies.

4. Term and Renewal.

a. Initial Subscription Term. Each Subscription Term will last for an initial twelve (12)-month period unless the Cover Page states otherwise.

b. Renewal. Following the Initial Subscription Term, this Agreement will automatically renew on a month-to-month basis unless either party provides written notice of non-renewal at least thirty (30) days prior to the end of the then-current term.

c. Term of Agreement. This Agreement starts on the Effective Date and continues until the end of all Subscription Terms, unless sooner terminated in accordance with its terms.

5. Transaction Settlement.

a. Payment Processing. Payment acceptance and settlement of Normal Transactions are provided through Stripe, Inc. (“Stripe”) using Stripe Connect. To receive settlement of Normal Transactions, Merchant must create or connect a Stripe account and enter into and remain in good standing under Stripe's Connected Account Agreement and other applicable Stripe terms (collectively, the “Stripe Terms”). Merchant's use of Stripe is governed by the Stripe Terms, which are between Merchant and Stripe and not part of this Agreement. Merchant is responsible for complying with the Stripe Terms, including Stripe's identity verification, prohibited-business, and risk requirements. Settlement timing, holds, reserves, and account actions for Normal Transactions are controlled by Stripe and are subject to the Stripe Terms; any such timing, hold, reserve, or action imposed by Stripe is outside Provider's control and does not constitute a breach of Provider's settlement obligations under this Agreement. Provider is not liable for the acts, omissions, availability, or account decisions of Stripe.

b. Normal Transactions. Provider will settle amounts owed to Merchant from normal Transactions (excluding gift card redemptions) through Stripe or another payment processor on a schedule consistent with standard industry practices (typically daily or next-business-day settlement, subject to the payment processor's terms and any applicable holds or reserves).

c. Gift Card Redemptions. Gift card redemptions will be settled separately with Merchant via ACH on the following schedule:

i. Every Tuesday: for Transactions occurring from 12:00 AM Friday through 11:59 PM Monday; and

ii. Every Friday: for Transactions occurring from 12:00 AM Tuesday through 11:59 PM Thursday.

d. Transaction Summary. Provider will provide Merchant with a weekly transaction summary itemizing all Transactions settled during the applicable period.

e. Settlement Disputes. Merchant must notify Provider in writing within fifteen (15) business days of receipt of a transaction summary if Merchant believes a settlement amount is incorrect. Provider will investigate and respond within five (5) business days of receiving a dispute notice. Settlement amounts not disputed within fifteen (15) business days shall be deemed accepted.

6. Chargebacks and Fraud.

a. Merchant Liability. Merchant bears full liability for all chargebacks, reversals, and customer disputes with respect to Transactions processed through the Cloud Service on Merchant's behalf. If a chargeback is assessed, Provider may deduct the chargeback amount plus any associated network processing fees from Merchant's next scheduled settlement.

b. Chargeback Notice. Provider will notify Merchant of any chargeback within three (3) business days of Provider's receipt of notice from the applicable payment processor. Merchant will cooperate fully with Provider in any chargeback dispute process, including providing documentation of the underlying Transaction.

c. Fraud Prevention. Merchant agrees to implement reasonable measures to prevent fraudulent Transactions. Provider reserves the right to suspend processing for Merchant's account if Provider reasonably determines that Merchant's account presents an elevated fraud or chargeback risk, pending investigation and resolution.

7. Support and SLA.

a. Support. Provider will provide support for the Cloud Service on a twenty-four (24) hour, seven (7) day per week basis. Provider will respond to critical support requests (platform unavailability or transaction processing failures) within two (2) hours, and to general support requests within one (1) business day.

b. SLA. Provider will use commercially reasonable efforts to make the Cloud Service available 99% of the time in each calendar month, excluding scheduled maintenance and downtime caused by Force Majeure Events or circumstances outside Provider's reasonable control.

c. Scheduled Maintenance. Provider will provide at least forty-eight (48) hours advance notice of scheduled maintenance reasonably expected to result in Cloud Service unavailability and will use commercially reasonable efforts to schedule maintenance during off-peak hours.

8. Warranties.

a. Mutual Warranties. Each party represents and warrants that:

i. it has the legal power and authority to enter into this Agreement; and

ii. it will use industry-standard measures to avoid introducing Viruses into the Cloud Service.

b. Additional Provider Warranties. Provider warrants that:

i. the Cloud Service will perform materially as described in the Documentation and Provider will not materially decrease the overall functionality of the Cloud Service during a Subscription Term (the “Performance Warranty”); and

ii. any Professional Services will be provided in a professional and workmanlike manner (the “Professional Services Warranty”).

c. Warranty Remedy. Provider will use reasonable efforts to correct a verified breach of the Performance Warranty or Professional Services Warranty reported by Merchant. If Provider fails to do so within thirty (30) days after Merchant's warranty report (“Fix Period”), either party may terminate the affected Order, and Provider will refund any pre-paid, unused fees for the terminated portion of the Subscription Term. Merchant must report a breach within thirty (30) days of discovering the issue (“Claim Period”). These procedures are Merchant's exclusive remedies and Provider's sole liability for breach of either warranty.

d. Disclaimers. Except as expressly set out in this Agreement, each party disclaims all warranties, whether express, implied, statutory or otherwise, including warranties of merchantability, fitness for a particular purpose, title and noninfringement. These disclaimers apply to the full extent permitted by Law.

9. Merchant Obligations and Usage Rules.

a. Compliance. Merchant will (i) comply with all applicable federal, state, and local laws and regulations; (ii) provide accurate, complete, and current business information, descriptions, photos, and pricing for listing on the Cloud Service, and promptly update such information as needed; and (iii) honor all reservations, purchases, and gift cards made through the Cloud Service.

b. High Risk Activities and Sensitive Data. Merchant:

i. will not use the Cloud Service for High Risk Activities;

ii. will not submit Sensitive Data to the Cloud Service; and

iii. acknowledges that the Cloud Service is not designed for use prohibited in this Section 9(b).

c. Restrictions. Merchant will not and will not permit anyone else to: (i) sell, sublicense, distribute or rent the Cloud Service (in whole or part) or use the Cloud Service to provide a hosted or managed service to others; (ii) reverse engineer, decompile or seek to access the source code of the Cloud Service; (iii) copy, modify, create derivative works of or remove proprietary notices from the Cloud Service; (iv) conduct security or vulnerability tests of the Cloud Service, interfere with its operation or circumvent its access restrictions; or (v) use the Cloud Service to develop a competing product.

d. Notification of Security Incidents. Merchant will promptly notify Provider of any suspected unauthorized access to Merchant's Cloud Service account or any known security incident affecting Transactions.

10. Data.

a. Use of Merchant Data. Provider will access and use Merchant's business data and transaction data solely to provide, maintain, and improve the Cloud Service under this Agreement. Provider will not otherwise disclose Merchant data to third parties except as permitted in this Agreement.

b. Security. Provider will use commercially reasonable administrative, technical, and physical safeguards designed to protect Merchant data against unauthorized access, use, or disclosure.

c. Usage Data. Provider may collect Usage Data and use it to operate, improve, and support the Cloud Service and for other lawful business purposes, including benchmarking and reporting. Provider will not disclose Usage Data externally unless it is (i) deidentified so that it does not identify Merchant, its customers, or any other person and (ii) aggregated with data across other merchants.

d. Data Ownership. Merchant retains ownership of its business information and customer transaction data. Provider retains ownership of all Cloud Service technology, systems, and aggregated anonymized Usage Data.

e. Data Export and Deletion. Upon termination or expiration of this Agreement, Provider will provide Merchant with an export of its transaction data within thirty (30) days of Merchant's written request. Within sixty (60) days of termination, Provider will delete Merchant data except as required by its standard backup or record retention policies or by Law.

11. Suspension.

a. Suspension. Provider may suspend Merchant's access to the Cloud Service and related services due to a Suspension Event, but where practicable will give Merchant prior notice so that Merchant may seek to resolve the issue and avoid suspension. Provider is not required to give prior notice in exigent circumstances or for a suspension made to avoid material harm or violation of Law. Once the Suspension Event is resolved, Provider will promptly restore Merchant's access.

b. Suspension Event. “Suspension Event” means

i. Merchant's account is thirty (30) or more days overdue.

ii. Merchant is in breach of Section 9 (Merchant Obligations and Usage Rules).

iii. Merchant's chargeback rate exceeds levels deemed acceptable by Provider's payment processor, or

iv. Merchant's use of the Cloud Service risks material harm to the Cloud Service or others.

12. Term and Termination.

a. Termination for Convenience. Either party may terminate this Agreement at the end of the Initial Subscription Term or any renewal period by providing at least thirty (30) days prior written notice.

b. Termination for Cause. Either party may terminate this Agreement (including all Subscription Terms) if the other party (i) fails to cure a material breach within thirty (30) days after written notice, (ii) ceases operation without a successor, or (iii) seeks protection under bankruptcy, receivership, or comparable proceeding, or such a proceeding is instituted against that party and not dismissed within sixty (60) days. Provider may terminate immediately upon written notice if Merchant engages in fraudulent activity, submits false information, or materially misuses the Cloud Service.

c. Effect of Termination. Upon termination or expiration, Provider will settle any outstanding Transactions within the next applicable settlement cycle and provide a final transaction summary. Merchant's right to use the Cloud Service will cease. Sections 6, 10(c), 10(e), 13, 14, 15, 16, 17, 18, and 22 survive termination or expiration.

13. Intellectual Property.

a. Reserved Rights. Neither party grants the other any rights or licenses not expressly set out in this Agreement. Except for Provider's express rights in this Agreement, Merchant retains all intellectual property and other rights in its trademarks, content, and customer data. Except for Merchant's express rights in this Agreement, Provider and its licensors retain all intellectual property and other rights in the Cloud Service and related technology.

b. License to Merchant Content. Merchant grants Provider a non-exclusive, royalty-free license to display, reproduce, and distribute its content on the Cloud Service solely during the term of this Agreement and solely for the purpose of operating the Cloud Service.

c. Feedback. If Merchant gives Provider feedback regarding improvement or operation of the Cloud Service, Provider may use the feedback without restriction or obligation. All feedback is provided “AS IS” and Provider will not publicly identify Merchant as the source without Merchant's permission.

14. Third-Party Platforms.

Merchant may choose to enable integrations or exchange data with Third-Party Platforms. Merchant's use of a Third-Party Platform is governed by its agreement with the relevant provider, not this Agreement, and Provider is not responsible for Third-Party Platforms or how their providers use Merchant data.

15. Confidentiality.

a. Obligations. Each party agrees to keep confidential any Confidential Information disclosed by the other party in connection with this Agreement and to use such Confidential Information only for purposes of performing under this Agreement. Each party will protect the other's Confidential Information with at least the same degree of care it uses to protect its own confidential information, but in no event less than reasonable care.

b. Exceptions. Confidential Information does not include information that: (i) is or becomes publicly known through no fault of the receiving party; (ii) was rightfully known to the receiving party prior to disclosure; or (iii) is independently developed by the receiving party without use of the disclosing party's Confidential Information.

c. Required Disclosures. If legally required to disclose Confidential Information, the receiving party will (where permitted by Law) promptly notify the disclosing party to allow it to seek a protective order and will cooperate reasonably with such efforts.

d. Survival. Confidentiality obligations survive termination of this Agreement for two (2) years.

16. Limitations of Liability.

a. General Cap. Each party's entire liability arising out of or related to this Agreement will not exceed the General Cap.

b. Consequential Damages Waiver. Neither party will have any liability arising out of or related to this Agreement for indirect, special, incidental, reliance or consequential damages or damages for loss of use, lost profits or interruption of business, even if informed of their possibility in advance.

c. Exceptions and Enhanced Cap. Sections 16(a) and 16(b) will not apply to Enhanced Claims or Uncapped Claims. For all Enhanced Claims, each party's entire liability will not exceed the Enhanced Cap.

d. Nature of Claims. The waivers and limitations in this Section 16 apply regardless of the form of action, whether in contract, tort (including negligence), strict liability or otherwise and will survive and apply even if any limited remedy fails of its essential purpose.

e. Liability Definitions. The following definitions apply unless modified on the Cover Page.

“Enhanced Cap” means three times (3x) the General Cap.

“Enhanced Claims” means Provider's breach of Section 10(b) (Security) or either party's breach of Section 15 (Confidentiality), excluding breaches related to Merchant Data.

“General Cap” means the greater of: (i) $10,000; or (ii) amounts paid or payable by Merchant to Provider under this Agreement in the twelve (12) months immediately preceding the first incident giving rise to liability. For Launch Partner merchants with no fees during the applicable period, the General Cap is $10,000.

“Uncapped Claims” means (i) the indemnifying party's obligations under Section 17 (Indemnification), (ii) either party's infringement or misappropriation of the other party's intellectual property rights, (iii) Merchant's chargeback liability under Section 6, (iv) any breach of Section 15 (Confidentiality) other than breaches related to Merchant Data, and (v) liabilities that cannot be limited by Law.

17. Indemnification.

a. Indemnification by Provider. Provider, at its own cost, will defend Merchant from and against any Provider-Covered Claims and will indemnify and hold harmless Merchant from and against any damages or costs awarded against Merchant (including reasonable attorneys' fees) or agreed in settlement by Provider resulting from Provider-Covered Claims.

b. Indemnification by Merchant. Merchant, at its own cost, will defend Provider from and against any Merchant-Covered Claims and will indemnify and hold harmless Provider from and against any damages or costs awarded against Provider (including reasonable attorneys' fees) or agreed in settlement by Merchant resulting from Merchant-Covered Claims.

c. Indemnification Definitions.

“Merchant-Covered Claim” means a third-party claim arising from Merchant's breach or alleged breach of Section 9(a) (Compliance) or Section 9(b) (High Risk Activities and Sensitive Data).

“Provider-Covered Claim” means a third-party claim that the Cloud Service, when used by Merchant as authorized in this Agreement, infringes or misappropriates a third party's intellectual property rights.

d. Procedures. The indemnifying party's obligations are subject to receiving from the indemnified party: (i) prompt notice of the claim, (ii) the exclusive right to control the claim's investigation, defense and settlement, and (iii) reasonable cooperation at the indemnifying party's expense. The indemnifying party may not settle a claim requiring the indemnified party to admit fault without the indemnified party's prior approval. The indemnified party may participate with its own counsel at its own expense.

e. Mitigation. In response to an infringement or misappropriation claim, Provider may: (i) procure rights for Merchant's continued use of the Cloud Service, (ii) replace or modify the allegedly infringing portion without reducing overall functionality, or (iii) terminate the affected Order and refund any pre-paid, unused fees for the terminated portion of the Subscription Term.

18. Dispute Resolution.

a. Informal Resolution. Before initiating formal proceedings, the parties agree to attempt to resolve any dispute through good-faith negotiation for thirty (30) days following written notice from either party describing the dispute.

b. Governing Law and Venue. This Agreement is governed by the laws of the State of New York, without regard to its conflict of law principles. Any dispute not resolved informally shall be submitted to a court of competent jurisdiction in New York County, New York, and each party consents to such jurisdiction.

19. Force Majeure.

Neither party is liable for a delay or failure to perform this Agreement due to a Force Majeure Event. If a Force Majeure Event materially adversely affects the Cloud Service for fifteen (15) or more consecutive days, either party may terminate the affected Order upon notice and Provider will refund any pre-paid, unused fees for the terminated portion of the Subscription Term. This Section does not limit Merchant's obligation to pay fees already owed.

20. General Terms.

a. Entire Agreement. This Agreement, together with all applicable Cover Pages and Orders, constitutes the entire agreement between the parties with respect to its subject matter and supersedes all prior agreements, representations, and understandings.

b. Amendments — Material Changes. Any amendment to these terms that materially affects Merchant's rights or obligations requires a written instrument signed by both parties or a new Cover Page.

c. Amendments — Operational Changes. With notice to Merchant, Provider may modify support policies, SLA, or security measures to reflect new features or changing practices, but modifications may not be retroactive or materially decrease Provider's overall obligations during a Subscription Term.

d. Updates to these Terms. Provider may update these Terms from time to time. The current version will always be available at the designated Provider URL, identified by version number and “last updated” date. Material changes to these Terms are governed by Section 20(a) and require a written instrument signed by both parties or a new Cover Page; for material changes affecting an active Subscription Term, Provider will provide thirty (30) days prior notice to Merchant consistent with Section 20(b). Non-material updates take effect upon posting, and Merchant's continued use of the Cloud Service after such non-material update takes effect constitutes acceptance of the updated Terms. The version in effect for a given Merchant is the version incorporated by that Merchant's executed Cover Page, as amended in accordance with these Terms. For merchants enrolling after an update, the version posted at the time of enrollment governs.

e. Order of Precedence. In the event of a conflict between these Master Terms and a Cover Page or Order, the Cover Page or Order controls with respect to that specific engagement. An Order does not modify any other part of the Agreement unless it specifically identifies the provisions it supersedes.

f. Waivers and Severability. Waivers must be signed by the waiving party's authorized representative and cannot be implied from conduct. If any provision is held invalid, illegal, or unenforceable, it will be limited to the minimum extent necessary so the rest of the Agreement remains in effect.

g. Assignment. Neither party may assign this Agreement without the prior written consent of the other, except that Provider may assign this Agreement in connection with a merger, acquisition, or sale of all or substantially all of its assets upon written notice to Merchant.

h. Subcontractors. Provider may use subcontractors and permit them to exercise its rights and fulfill its obligations, but Provider remains responsible for their compliance with this Agreement and for its overall performance.

i. Independent Contractors. The parties are independent contractors, not agents, partners, or joint venturers.

j. No Third-Party Beneficiaries. There are no third-party beneficiaries to this Agreement.

k. Notices. All notices must be in writing and delivered by email with confirmation of receipt, overnight courier, or certified mail to the addresses set forth on the Cover Page.

l. Counterparts. This Agreement may be executed in counterparts, each deemed an original. Electronic signatures are valid and binding.

m. Export. Each party will comply with all export and import Laws in performing this Agreement and represents that it is not listed on any U.S. government list of prohibited parties or located in a country subject to a U.S. government embargo.

21. Definitions.

“Agreement” has the meaning given in Section 1 (The Agreement).

“Cloud Service” means Provider's proprietary Xenia cloud-based platform, as identified in the relevant Order and as modified from time to time. The Cloud Service includes the Provider Software and Documentation but not Professional Services deliverables or Third-Party Platforms.

“Confidential Information” means information disclosed by or on behalf of one party (as discloser) to the other party (as recipient) under this Agreement, in any form, which (a) the discloser identifies as “confidential” or “proprietary” or (b) should be reasonably understood as confidential or proprietary due to its nature and the circumstances of its disclosure. Provider's Confidential Information includes technical or performance information about the Cloud Service, and Merchant's Confidential Information includes Merchant Data.

“Cover Page” means a Xenia by Yo-Do Software Corp. cover page or Order Form that (a) incorporates these Cloud Service Terms by reference, (b) specifies Key Terms and any Additional Terms, and (c) is signed by Merchant and Provider.

“Documentation” means Provider's standard usage documentation for the Cloud Service.

“Enhanced Cap” is defined in Section 16(e).

“Enhanced Claims” is defined in Section 16(e).

“Force Majeure Event” means an unforeseen event beyond a party's reasonable control, such as a strike, blockade, war, pandemic, act of terrorism, riot, third-party internet or utility failure, refusal of government license, or natural disaster, where the affected party takes reasonable and customary measures to avoid or mitigate such event's effects.

“General Cap” is defined in Section 16(e).

“High Risk Activities” means activities where use or failure of the Cloud Service could lead to death, personal injury, or environmental damage, including life support systems, emergency services, nuclear facilities, autonomous vehicles, or air traffic control.

“Key Terms” means Effective Date, Governing Law, Subscription Term, fee structure, and other terms specified by the parties as “Key Terms” on the Cover Page.

“Launch Partner Terms” is defined in Section 3(a).

“Laws” means all laws, regulations, rules, court orders, or other binding requirements of a government authority that apply to a party.

“Merchant” means the party identified as “Merchant” on the Cover Page.

“Merchant-Covered Claim” is defined in Section 17(c).

“Order” means an order for Merchant's access to the Cloud Service or related services that is executed by the parties and references this Agreement.

“Professional Services” means training, migration, or other professional services that Provider furnishes to Merchant related to the Cloud Service.

“Provider” means Yo-Do Software Corp., a corporation organized under the laws of the State of New York.

“Provider-Covered Claim” is defined in Section 17(c).

“Sensitive Data” means (a) patient, medical or other protected health information regulated by HIPAA, (b) credit, debit, bank account or other financial account numbers, (c) social security numbers, driver's license numbers or other government ID numbers, and (d) special categories of data enumerated in EU Regulation 2016/679, Article 9(1) or any successor legislation.

“Subscription Term” means the term for Merchant's use of the Cloud Service as identified on the Cover Page or in an Order.

“Suspension Event” is defined in Section 11.

“Third-Party Platform” means any product, add-on or platform not provided by Provider that Merchant uses with the Cloud Service.

“Transaction” means any sale, reservation, payment, or gift card purchase or redemption processed through the Cloud Service on behalf of Merchant.

“Uncapped Claims” is defined in Section 16(e).

“Usage Data” means Provider's technical logs, data and learnings about Merchant's use of the Cloud Service, excluding Merchant Data.

“Virus” means viruses, malicious code, or similar harmful materials.