All legal documents
Draft: pending professional Philippine legal review. This describes how DinkingBuds actually works today but has not yet been reviewed by a lawyer, and is not a final, binding agreement. Sections marked ⚖ specifically await legal judgment.

DinkingBuds Venue Partner Agreement (DRAFT: not yet reviewed by counsel)

Effective date: [DATE].

**This is a draft prepared for legal review. It is not currently in

effect and must not be signed by any real venue until a Philippine

lawyer has reviewed it.**

This Agreement is between [LEGAL ENTITY NAME] ("DinkingBuds") and

[VENUE LEGAL NAME] ("the Venue Partner") governing the Venue Partner's

use of the DinkingBuds owner console to manage court bookings, pricing,

staff, and payment verification.

1. What DinkingBuds provides

  • A booking and scheduling system for the Venue Partner's courts,

including double-booking prevention, availability management, and

scheduled maintenance blocks.

  • A pricing engine the Venue Partner controls (standard/peak rates,

date-specific rules, member discounts, promo codes).

  • A payment-verification workflow (see the Marketplace Disclaimer,

04-marketplace-disclaimer.md). **DinkingBuds does not process,

hold, or move the Venue Partner's revenue.** All player payments go

directly to the Venue Partner's own GCash/Maya/bank account; the

Venue Partner's staff verify them in-app.

  • A staff console with role-based access (front desk, manager, owner)

scoped to the Venue Partner's own venue(s) only.

  • Reporting (revenue, utilization, channel mix, no-shows) computed from

the Venue Partner's own booking data.

  • Optional additional modules if enabled: coaching/clinics, tournaments,

leagues, memberships, marketing (promo codes, campaigns, referrals),

multi-branch management.

2. What DinkingBuds does not provide

  • Payment processing or fund holding. There is no automated payout,

and no "settlement" in the traditional marketplace-platform sense:

the Venue Partner already has the money the moment a player pays them

directly.

  • Insurance, liability coverage, or safety certification for the Venue

Partner's facility.

  • Staffing, coaching, or event operation: the Venue Partner runs their

own business; DinkingBuds provides the software.

3. Fees

DinkingBuds does not currently charge Venue Partners a platform fee.

[If/when a fee model is introduced, this section (and the BIR item in

the legal-review checklist §2) must be revisited before any fee is

charged.]

4. Venue Partner's responsibilities

  • Verify player payments promptly and honestly against the Venue

Partner's own account records, not on trust of a screenshot alone.

  • Pay refunds owed (per 03-cancellation-refund-terms.md) to players

directly and mark them complete in the app.

  • Keep court availability, pricing, and hours accurate and up to date.
  • Ensure staff given console access understand their role's data-access

scope (e.g. front desk cannot see other branches' financial data).

  • Handle customer PII visible in the console (booking history, contact

info, payment references) responsibly. Do not export or share it

outside the ordinary course of running the venue's booking operations.

  • Comply with the Venue Partner's own tax, safety, and permit

obligations. DinkingBuds is not responsible for the Venue Partner's

regulatory compliance as a business.

5. Data handling

The Venue Partner can see customer data (bookings, contact info,

payment references, CRM notes/tags) only for their own venue(s).

This is enforced by the platform, not just policy. If the Venue Partner

operates multiple branches, branch-level staff access can be scoped

further (a front-desk login can be pinned to one branch).

6. Term and termination

[⚖ Standard term/termination clauses to be drafted by counsel,

including notice period, and see §7 for what happens to data on exit.]

7. Offboarding

If this Agreement ends: [define what happens to the Venue Partner's

booking/customer data: retained for a defined period per the retention

policy once set (see Privacy Policy §6), or exported to the Venue

Partner and then handled per the deletion process. No automated

offboarding data-export exists today; this would currently be a manual

platform-admin action.]

8. Disputes between the Venue Partner and DinkingBuds

[⚖ Standard dispute-resolution clause: governing law (Republic of the

Philippines), venue for disputes, to be set by counsel.]

9. Liability

[⚖ To be drafted by counsel. Must not disclaim DinkingBuds' actual

technical guarantees (e.g. the no-double-booking constraint) while

appropriately limiting liability for matters genuinely outside

DinkingBuds' control (e.g. the Venue Partner failing to verify or pay a

refund).]