Terms and conditions

1. Operator and service role

tableGo is operated by MENYHART SZABOLCS PERSOANA FIZICA AUTORIZATA; contact: tablego.site@gmail.com. tableGo provides a digital interface for restaurant discovery, table requests, communication, menu browsing and on-site ordering at supported restaurants.

tableGo does not prepare or serve food. The selected restaurant provides the restaurant service, distinct from tableGo's own digital service. An external map result does not automatically mean the venue is a tableGo partner or accepts bookings/orders through the system. Digital intermediation does not exclude the operator's statutory responsibility for its own service.

2. Accounts and contact information

Account-based functions require sign-in and, where applicable, email verification. Email/password and Google sign-in flows are available. On-site QR ordering can use a separate table-linked access credential.

Provide accurate details and protect your password, personal request link and session access. A profile phone number is optional, but the current table-request flow also requires a phone number. Do not use another person's account or access link without authorization. The privacy policy describes personal-data processing.

3. Table requests and accepted bookings

Submitting a table request does not automatically create a confirmed booking. The guest selects a restaurant, time and party size; the request reaches the restaurant as pending. It is confirmed in the system when the restaurant accepts it.

Actual availability depends on the restaurant's capacity and response. Check status and messages in the request details. Email and push notifications are supporting channels; their absence or delay does not prove that no status change occurred.

4. Rejection and cancellation

The restaurant may reject a pending request or cancel a booking under the system's rules. Guests can cancel their request or booking using the available cancellation action. Please report changes as early as possible.

If cancellation is no longer available or the status is unclear, contact the restaurant directly. Sending a message does not necessarily change booking status. This document does not introduce automatic cancellation or no-show fees and does not affect mandatory consumer rights.

5. Arrival, no-shows and ending a visit

Arrival and completion of a visit are separate states. Some joining or arrival flows require a location check; ask the restaurant for help if GPS is inaccurate or permission is unavailable.

The partner may report a no-show under the system's conditions. This does not automatically establish the facts in every disputed case: request review of an incorrect report. Ending a visit may stop further orders, but does not mean paying the bill, withdrawing submitted orders or deleting history. The system may request additional confirmation for active orders.

6. Booking-based and QR/WALK_IN orders

Booking-based ordering is linked to your own request and an active visit permitted by the system. QR/WALK_IN ordering is available in a mobile browser through a supported restaurant's table code. Not every restaurant and platform offers the same access route.

Browsing a public menu does not grant ordering access. Before submitting, check the restaurant, table, items, quantities, notes and total in the review step. A cart is not a submitted order; check the submission result and order list. If a network result is uncertain, do not create another order without checking.

7. Order statuses and communication

Order statuses are pending (PENDING), accepted (ACCEPTED), rejected (REJECTED) and served (SERVED). They indicate stages of restaurant processing. Submission is not the same as acceptance, serving or payment.

Discuss changes to or withdrawal of submitted orders, unavailable items and delays with the restaurant. The guest interface does not promise self-service cancellation in every state. The technical role of statuses does not alone determine all legal conditions for formation of the guest–restaurant contract.

8. Menus, prices and product information

Partners manage menus, prices, images, descriptions and availability. Information may change; an earlier screen or cart does not guarantee an unchanged offering. The backend checks items and calculates the total when ordering; order history keeps a snapshot of submitted items and prices.

Discuss price discrepancies, ingredients, allergens or special dietary needs with the restaurant before ordering. A description or image does not replace mandatory product information. tableGo cannot promise food safety or absence of allergens on the restaurant's behalf; this does not release anyone from statutory obligations.

9. Payment and responsibilities

The current system does not provide integrated online payment. Displaying an order total or ending a visit is not proof of payment. Payment, invoicing, food delivery to the table and questions about restaurant performance must be addressed with the restaurant.

Guests provide accurate information and ordering intent; restaurants manage their own offering and performance. tableGo operates its own digital service. This draft contains no blanket exclusion of liability and does not limit mandatory consumer rights.

10. Messages and reviews

Use messages to communicate about the request and reviews to describe genuine experiences. Do not publish unauthorized personal information, threats, unlawful content or misleading reviews.

Reviews are moderated; submission does not mean immediate publication. Approved reviews may be associated with the guest's name. Disputes about content or moderation can be reported to tableGo's contact address; detailed complaint and appeal rules require legal approval.

11. Security and abuse

Do not bypass captcha, authorization or attempt limits, access other people's bookings or disrupt restaurants with false or repeated requests. The system applies automated attempt limits, and administrators can restrict accounts or partner access.

A restriction is not personal-data deletion. Report incorrect restrictions or unauthorized access at the contact address without sending passwords or tokens. Where necessary, also discuss existing requests with the restaurant.

12. Help and complaints

Send questions about tableGo's operation to tablego.site@gmail.com. Include a description, time and, if necessary, the request or order identifier; do not send passwords, access tokens or card details.

For food quality, service, restaurant prices or payment, contact the restaurant too. Reporting an issue to tableGo does not exclude statutory consumer, administrative or judicial remedies. The privacy policy supplies contact and complaint information for data-protection matters.

13. Versions and the separate partner agreement

This is a draft awaiting approval, not retrospectively applicable terms. A final version must receive its own identifier and an approved effective date; the procedure for notifying changes and, where necessary, renewed acceptance must also be approved.

Opening this page does not itself create a version-linked acceptance log. Commercial partner cooperation, fees and data-protection roles belong in a separate Partner Agreement; this guest document does not replace it.

14. Partner cooperation and pricing – not guest fees

New partners provide genuine business and representative details and read and separately accept the displayed, versioned agreement. Main-admin approval is required; registration is not automatic activation. Partners protect their access and ensure the legality of published restaurant details, menus, prices and uploads.

Default partner pricing is 1.00 RON per chargeable booked guest for completed bookings only; QR service has a fixed 50.00 RON fee per active, chargeable month. These are charges between tableGo and the partner, not automatically guest service fees or order commissions. Cancelled, rejected, no-show and active bookings are not chargeable.

The admin may propose individual prices. Partners separately accept them while signed in on WEB; new prices apply only after acceptance and the planned effective date. Previously accepted text/digests and closed settlements remain unchanged. A booking belongs to its scheduled month; late completion becomes a correction in the next open settlement with its original month shown.

After monthly settlement, the operator issues and sends the invoice through an external system. tableGo records the PDF and payment status, rather than providing automated invoicing or payment processing. Partial QR months, VAT status, payment deadlines and legal price-change notice conditions remain open; this draft invents no rules. The separate agreement still requires legal approval.

15. Technical failures, applicable law and remedies

Network, device or provider failures may delay displays and notifications. Check the request/order status and contact the restaurant directly for urgent restaurant matters. Report tableGo problems by email or on +40 755 774 886. This draft promises neither uninterrupted availability nor fixed support hours, and does not exclude the operator's statutory liability.

The service operates in Romania. Mandatory Romanian and applicable EU rules, and mandatory consumer protection that may arise under another country's law, cannot be excluded. This draft imposes no exclusive court and removes no administrative, consumer-protection or judicial remedies. Final choice-of-law and complaints procedures require legal review.

Future changes to approved terms must be introduced accessibly to affected users, with notice required by applicable rules and renewed acceptance where necessary. Replacing page text must not rewrite earlier acceptance evidence or closed financial records.