Partner terms (B2B)

Beezbites is operated by:

Justin Milaszewski
trading as Beezbites
Sole proprietorship (Einzelunternehmen)
Krümmeweg 46
38518 Gifhorn
Germany

Email: [email protected]

Commercial register: Not registered (sole proprietorship).
VAT identification number (Germany, Section 27a UStG): DE457116420.

(hereinafter "platform operator")

(1) These partner terms ("Partner Terms") govern cooperation between the platform operator and the restaurant partner (entrepreneur within the meaning of Section 14 of the German Civil Code, BGB).

(2) The platform operator provides a digital intermediary platform. This includes discovery and recommendations, restaurant and user profiles, social interactions, posts and media, and the technical mediation of orders and related services.

(3) The restaurant partner offers food, beverages and other services to end customers via the platform and maintains its trader identity and a complete, current legal notice (imprint).

(1) Contracts for goods and services are concluded exclusively between the restaurant partner and end customers.

(2) The platform operator provides the technical platform for menus, orders and — where processed via the platform — online payment integration. It is neither seller nor contracting party under the end-customer contract for food, beverages or other services and does not act in the name of end customers.

(3) The restaurant partner is the seller and provider of goods/services to end customers and is solely responsible for its offer, pricing, taxes, quality, statutory labelling (including allergens), performance, delivery or pickup, and customer service towards end customers.

(4) The restaurant partner authorises the platform operator to accept orders placed via the platform solely in the name and for the account of the restaurant partner, according to prices, availability and acceptance criteria preset by the restaurant partner. The platform operator has no independent discretion regarding price, scope of services or other material contract terms and does not act in the name of end customers.

(5) The channel-specific information shown immediately before the order button governs the time and manner of contract formation. By clicking the button, a binding contract between the end customer and the restaurant partner is generally formed immediately, where the interface states this (e.g. "Place order with obligation to pay" or "Submit order with obligation to pay"). The platform operator accepts the order on behalf of the restaurant partner within the meaning of paragraph 4.

(6) For online card payments via the platform, Stripe processes the payment technically. The platform operator creates the payment request in the name and for the account of the restaurant partner and transmits the required transaction data to Stripe; it acts towards Stripe solely as a technical platform integrator. The restaurant partner is the settlement merchant and payment recipient for each card payment. The platform operator is not a party to the purchase contract. Payment initiation, authorisation, success or failure does not by itself determine formation or continuation of the end-customer contract; paragraph 5 and the restaurant partner's acceptance, rejection and related communication remain decisive.

(1) The restaurant partner shall provide complete and accurate trader, representative, contact, tax and payment data and cooperate with legally required trader verification.

(2) All information must be kept up to date without undue delay.

(3) Partner account credentials must be kept confidential and must not be shared with unauthorised third parties.

(4) The restaurant partner keeps its complete and current legal notice (trader identity, address, contact) up to date in the partner account and ensures it is accessible to end customers in checkout via the platform. Consumer information (GTC, privacy, withdrawal) is provided centrally by the platform operator for use of the platform; the restaurant partner is not required to maintain its own consumer website or separate privacy policy URL. It may additionally provide its own consumer information.

(1) The platform operator receives a commission for orders successfully intermediated via the platform.

(2) Unless otherwise agreed in text form, the commission depends on the order channel and is calculated on the order value recorded in the system (after discounts, including any delivery and service costs recorded through the platform, excluding tips, after cancellations and refunds; the amounts shown to end customers apply, typically including VAT):

• On-site / table: 2.49 % plus a fixed fee of EUR 0.15 per completed payment;
• Delivery and pickup: 6.99 % plus a fixed fee of EUR 0.25 per completed payment.

(3) The fixed fee under paragraph 2 is additive to the percentage (not per individual order when settled together). A payment includes in particular an online checkout and cash payment at the counter for in-app orders; for table settlement (e.g. add-on orders billed together), the fixed fee is charged only once.

(4) The order data recorded in the platform operator's system is decisive.

(5) The commission amounts stated in paragraphs 2 and 3 include any statutory VAT that may be due. The VAT portion is shown separately in the statement. The percentage component is rounded up to the next full cent for each payment. Stripe card fees are borne by the restaurant partner in addition (Section 6(4)).

(1) Payments may be made directly between end customers and the restaurant partner or via payment service providers (e.g. Stripe).

(2) Where payment processing is handled via the platform, payments are processed via Stripe Connect (direct charges): the Checkout Session, Payment Intent and Charge are created exclusively on the restaurant partner's connected Stripe account. The restaurant partner is the payment recipient and settlement merchant; customer funds do not pass through the platform operator's Stripe account. The restaurant partner owns the payment claim.

(3) The restaurant partner enters into and maintains its own payment services agreement with Stripe. The platform operator is not a party to that agreement and receives only its own agreed remuneration as a Stripe application fee.

(4) Card-payment fees charged by the payment service provider (Stripe) are borne by the restaurant partner; they generally arise on the restaurant partner's connected Stripe account. This applies to successful online payments and to fees actually incurred and not refunded by Stripe following a cancellation, refund, reversal or chargeback (Section 8). The amounts charged by Stripe are decisive; a typical guide for DE/EEA card payments is about 1.5% + EUR 0.25 per payment. Where fees create the platform operator's own due claim, they are billed separately and collected only under Section 7(4).

(5) The platform operator has no disposal, blocking, withholding or payout rights over restaurant funds. Stripe handles payments, balances and payouts under its own agreement with the restaurant partner. The platform operator may only restrict its own platform functions for future transactions under these Partner Terms.

(6) The restaurant partner remains responsible for its tax obligations, proper invoicing to end customers and other statutory duties.

(1) For successful online card payments, the platform commission is settled as an application fee. Other claims are billed separately and are not set off against restaurant funds.

(2) Billing documents are provided to the restaurant partner digitally (e.g. in the partner account or by email). For ancillary charges, they state at least the settlement period, type of claim, underlying order or payment reference and amount. If automatic collection fails, the claim may be shown in the partner statement and pursued by invoice or another agreed payment method.

(3) For online card payments, payouts to the restaurant partner are made directly by the payment service provider (Stripe) to the restaurant partner's connected Stripe account. Payout to the restaurant partner's bank account follows the payout schedule and bank details configured in the restaurant partner's Stripe dashboard; the platform commission is already retained in the payment flow (application fee). The platform operator does not influence the payout cycle.

(4) A Stripe Connect account debit requires separate consent and may be used only for the platform operator's own due claims. As a rule, the restaurant receives a statement before collection, and collection occurs no earlier than one business day after receipt. An exceptional immediate ancillary charge requires the separate agreement and gives an immediate objection and reimbursement right. Without separate consent no account debit occurs; the claim is pursued by invoice or another agreed payment method.

(5) Objections may be sent in particular to [email protected]. Statutory rights remain unaffected. Amounts collected without entitlement are reimbursed without undue delay.

(1) Cancellations and partial cancellations result in corresponding commission adjustments.

(2) The restaurant partner decides on and bears economic responsibility for refunds to end customers. The platform operator may technically initiate a refund on the connected Stripe account only on a documented, express instruction by the restaurant partner for that individual transaction. This is not a general advance authority, reverse transfer or independent disposal of restaurant funds.

(2a) Stripe transaction fees from the original card payment and any additional refund or reversal fees are economically borne by the restaurant partner only to the extent actually incurred and not refunded by Stripe. They are passed on without a surcharge, evidenced in the statement and may be collected using Stripe Connect account debit only under Section 7(4).

(3) In the direct-charge model, chargebacks and reversals are handled on the connected Stripe account under the restaurant partner's own Stripe agreement. Internally, the restaurant partner bears amounts and actually incurred fees attributable to its orders unless caused by the platform operator.

(4) The platform operator's own due claims arising from chargebacks or refunds may be invoiced separately and collected by account debit only under Section 7(4).

(5) In case of suspected fraud, increased chargeback risk or breach of these Partner Terms, the platform operator may temporarily disable future online payments through the platform. It cannot block or withhold existing Stripe payments, balances or restaurant payouts.

(1) The restaurant partner must comply with all laws applicable to its business (food safety, youth protection, pricing, etc.).

(2) Allergens and other mandatory information must be complete and accurate.

(3) Promised delivery/pickup times and availability must be honoured.

(4) Manipulation of the platform, circumvention of commission (e.g. systematic off-platform arrangements to bypass the platform) or other abuse is prohibited.

(5) For restaurant profiles, menus, posts, images, videos and other discovery content, the restaurant partner shall provide complete, current and lawful information, label advertising and commercial communications and hold all required copyright, trade mark, personality and consent rights.

(1) Restaurant partners are currently shown alphabetically in directories as a rule. Curated areas such as "Popular", "Fast" or "New" may additionally use the following main parameters:

• externally sourced rating scores and number of ratings,
• current opening or availability,
• recency of the offer,
• technical data quality.

(2) Future changes, including dynamic ranking, will be reflected in this provision. Weighting may change; no specific organic placement is guaranteed.

(1) The platform operator may offer paid advertising and placement options (e.g. highlighted listings, preferred search placement, banners or other marketing).

(2) Content labelled as "Sponsored Listing" or similar constitutes paid placement and is identifiable as advertising.

(3) Bookings are made under separate agreements or via tools in the partner account.

(4) The platform operator sets parameters for sponsored listings, which may include bids, relevance, user behaviour or performance criteria.

(5) Sponsored listings may affect visibility and may differ from organic ranking under § 10.

(6) The platform operator ensures paid placements meet statutory transparency requirements, in particular under competition and consumer protection law.

(7) The restaurant partner is responsible for the lawfulness of its advertising content and shall indemnify the platform operator against third-party claims arising from unlawful content.

(8) There is no entitlement to specific placements, reach or commercial outcomes unless expressly agreed in writing.

(1) The restaurant partner grants the platform operator the rights necessary to operate the platform for texts, images, trade marks and other materials provided.

(2) The restaurant partner warrants it holds the rights required to use and publish such content.

(3) The restaurant partner shall indemnify the platform operator against third-party claims arising from infringement of third-party rights by content provided by the restaurant partner.

(4) Where the platform enables end-customer ratings, the terms of use / general terms for consumers and the platform's moderation and notice procedures apply in addition; the restaurant partner's obligations regarding the lawfulness of its own content under paragraphs (1–3) remain unaffected.

(1) The restaurant partner receives access to order-related data required to fulfil orders and to its own master, offer, billing and content data. Where provided, it may view aggregated performance data for its profile and discovery content.

(1a) It has no access to personal data of other restaurant partners, end-customer profile data not required for orders, or internal ranking, security and moderation data. Data required by law or for legal defence may remain after termination; exportable own data is made accessible through the functions provided.

(2) The platform operator may analyse aggregated or anonymised data to improve the platform, for statistics and compliance, subject to applicable data protection law. Operationally necessary analysis (e.g. table menu activity) is processed as first-party data on the platform; no optional third-party marketing or profiling trackers are used in the browser (e.g. Google Analytics or PostHog). Operationally necessary, cookieless reach and performance measurement via Vercel as part of hosting is separate (see our privacy policy).

(3) Information on personal data processing by the platform operator (including end-customer data in connection with use of the platform) is provided in our privacy policy.

(4) The following technical service providers may be used in particular to operate the platform:

• Supabase (database / authentication),
• Render (backend hosting),
• Vercel (frontend / hosting),
• Upstash Redis (rate limiting / abuse prevention),
• Stripe (payment processing),
• Google Workspace (email delivery),
• OpenRouter (AI features in the partner dashboard).

(5) A fuller overview of service providers is provided in our privacy policy. For intermediation and performance of orders, the platform operator and restaurant partner generally process personal data as separate controllers for their respective own purposes. Processing under Article 28 GDPR applies only to specifically identified modules in which the platform operator processes data on documented instructions from the restaurant partner; where required, it is subject to a separate data processing agreement.

(6) Where the restaurant partner processes personal data of end customers received via the platform (especially in connection with orders), it shall use such data only for order fulfilment, customer service, compliance with legal obligations and other lawful purposes within its own area of responsibility. It shall not disclose data to third parties without a legal basis, shall observe statutory retention periods and shall delete or anonymise data when no longer required for those purposes and no retention obligation applies. It shall respond to data subject requests via the contact details in its legal notice and shall cooperate with requests addressed to the platform operator that concern the restaurant partner.

(1) Uninterrupted availability is not guaranteed.

(2) Maintenance, updates and technical faults may cause temporary restrictions.

(1) Complaints within the meaning of Regulation (EU) 2019/1150 may be sent to: [email protected].

(2) For additional out-of-court resolution of disputes between the platform and restaurants, suitable mediation or conciliation bodies may be used where legally relevant. We will identify appropriate contact points upon request.

(1) The platform operator has unlimited liability for injury to life, body or health and for intent and gross negligence.

(2) In case of ordinary negligence, the platform operator is liable only for breach of material contractual obligations and limited to typically foreseeable damage.

(3) The restaurant partner is liable to end customers under applicable law and the contract concluded with the end customer.

(4) The restaurant partner shall indemnify the platform operator against third-party claims arising from breaches of duties towards end customers or unlawful content by the restaurant partner, unless the platform operator is solely responsible under general law.

(1) The platform agreement is concluded for an indefinite term unless expressly agreed otherwise.

(2) Either party may terminate with 30 days' notice to the end of a calendar month.

(3) The right to extraordinary termination for good cause remains unaffected.

(1) The platform operator may suspend access temporarily in case of breaches of these Partner Terms or applicable law.

(2) Serious or repeated breaches may justify immediate suspension or extraordinary termination.

(3) If services are restricted or suspended, the restaurant partner receives reasons on a durable medium no later than when the measure takes effect. For complete termination, reasons are provided at least 30 days in advance unless a statutory exception applies, including a legal obligation or repeated breach (Article 4 of Regulation (EU) 2019/1150).

Neither party is liable for failure to perform obligations caused by events beyond its reasonable control (force majeure), including natural events, governmental action, failures of third parties outside its control or general internet disruptions.

The parties act as independent businesses. No employment relationship, civil-law partnership or permanent agency is established.

The platform operator may amend these Partner Terms. Amendments will be communicated to the restaurant partner in text form in good time (e.g. by email or notice in the partner account). If the restaurant partner objects to the amendment in writing or in text form within six weeks of receipt, the amended version shall not be deemed agreed; the last version accepted by or otherwise continuing to apply for the restaurant partner shall remain in force — without triggering automatic termination unless otherwise required by law. If no declaration is received within the objection period and the platform operator has duly informed the restaurant partner about the legal consequences and objection period, the new version may become effective where permissible under statutory requirements for amendments to B2B general terms.

(1) The laws of Germany apply, excluding the UN Sales Convention (CISG).

(2) If the restaurant partner is a merchant within the meaning of the German Commercial Code, a legal entity under public law or a special fund under public law, the exclusive place of jurisdiction for all disputes arising from or in connection with these Partner Terms is Gifhorn, Germany.

(3) Should individual provisions be or become invalid, the validity of the remaining provisions remains unaffected. Invalid provisions shall be replaced by a legally permissible provision closest in economic purpose.