Terms of Service

1.Who we are§

Provider

[LEGAL COMPANY NAME] (“i-table”, “we”, “us”)

Legal form and registered seat

[LEGAL FORM], [REGISTERED ADDRESS]

General Commercial Registry (Γ.Ε.ΜΗ.)

[GEMI NUMBER]

VAT number (Α.Φ.Μ.) / tax office

[VAT NUMBER], [TAX OFFICE]

Email

[CONTACT EMAIL]

Website

i-table.gr

↑ Back to contents

2.Acceptance of these terms§

These terms form a binding agreement. They apply when you open an i-table account, sign an order form or proposal that refers to them, use the dashboard, or make or attempt to make a reservation through a booking page powered by i-table.

If you do not accept them, do not use the platform. Where an order form or a signed agreement between i-table and a Restaurant conflicts with these terms, that document prevails to the extent of the conflict.

↑ Back to contents

3.How this document is structured — which parts apply to you§

Part A — Restaurants (sections 5 to 14 and 16 to 29)

Applies to a business that holds an i-table account. This is a business-to-business agreement. Consumer protection legislation does not apply to it.

Part B — Guests (section 15)

Applies to an individual who books a table. Where that individual is a consumer, mandatory Greek and EU consumer protection law applies and nothing in this document limits it.

Common provisions (sections 1 to 4 and 30 to 31)

Apply to everyone.

↑ Back to contents

4.Definitions§

Platform

The i-table software, dashboard, booking pages, embeddable widget, APIs and related services.

Restaurant

A business that has an account and uses the Platform to take bookings. Also “you” in Part A.

Authorised User

An individual the Restaurant permits to access the dashboard under its account.

Guest

An individual who makes or is named in a reservation. Also “you” in Part B.

Reservation

A booking of a table at a Restaurant, made through the Platform.

Deposit

An amount a Restaurant requires a Guest to pay to secure a Reservation. Payable to the Restaurant — see section 14.

Platform Fees

The amounts a Restaurant pays i-table for the Platform — see section 13.

Restaurant Data

All data a Restaurant or its Guests submit through the Platform, including Reservation and guest records.

Data Protection Law

Regulation (EU) 2016/679 (GDPR), Greek Law 4624/2019, Greek Law 3471/2006 and any other applicable data protection legislation.

↑ Back to contents

5.Part A — Eligibility and authority§

To open an account you confirm that you are at least 18 years old, that you are acting in the course of a trade or business, and that where you act for a legal entity you are duly authorised to bind it. If you are not authorised, you must not open the account.

You are responsible for everything done under your account, whether or not you authorised it, other than use resulting from our own breach of these terms.

↑ Back to contents

6.Part A — What the Platform does§

Subject to these terms and to payment of the Platform Fees, i-table grants the Restaurant a non-exclusive, non-transferable, non-sublicensable right to access and use the Platform during the term, for its own internal business purposes. The Platform is provided as a hosted service; no copy of the software is delivered.

The Platform provides, in summary:

• a public booking page and an embeddable widget, with a QR code linking to them;
• configuration of seating areas, tables, service hours, closure dates and optional extras;
• availability calculation and protection against double-booking of the same table;
• a dashboard for viewing and managing reservations, and a guest record per restaurant;
• optional collection of a Deposit through a third-party payment provider; and
• confirmation messages to Guests, where enabled.

↑ Back to contents

7.Part A — Accounts, users and security§

• Account information must be accurate and kept up to date.
• Credentials are personal to each Authorised User and must not be shared. Accounts must not be used by more than one individual.
• The Restaurant is responsible for its Authorised Users' acts and omissions, for granting only the access each needs, and for revoking access promptly when someone leaves.
• The Platform distinguishes an owner role, which can change settings, billing details and team membership, from a staff role, which cannot. The Restaurant is responsible for assigning roles appropriately.
• You must notify us without undue delay at [CONTACT EMAIL] if you suspect any unauthorised access.

↑ Back to contents

8.Part A — Restaurant responsibilities§

The Restaurant is solely responsible for the accuracy of what it publishes and for honouring what it offers. In particular it must:

1. keep its name, address, contact details, description and photographs accurate and not misleading;
2. configure its seating areas, tables, capacities, service hours, closure dates, hold times and extras so that they reflect what it can actually deliver;
3. set and publish accurate Deposit, cancellation, no-show and refund policies, and any minimum spend, in terms that comply with consumer protection law;
4. honour Reservations accepted through the Platform, and deal with Guests fairly where it cannot;
5. handle its own Guest complaints, refunds and disputes;
6. hold every licence, permit and registration its business requires; and
7. comply with all applicable law, including food safety, accessibility, consumer protection, tax and Data Protection Law.

↑ Back to contents

9.Part A — Restaurant Data and lawful use§

As between the parties, Restaurant Data belongs to the Restaurant. The Restaurant grants i-table the right to host, process and transmit it to the extent necessary to provide the Platform, to comply with law, and for the limited purposes for which i-table acts as a controller as described in the Privacy Notice.

The Restaurant warrants that:

1. it has a lawful basis for the personal data it collects and stores through the Platform;
2. it provides its Guests with the transparency information Articles 13 and 14 GDPR require, including who it is and how long it keeps guest records;
3. where it records dietary, allergy, accessibility or other information capable of revealing special categories of personal data, it satisfies a condition under Article 9(2) GDPR — normally the Guest's explicit consent — and records no more than it needs; and
4. it does not use the Platform to build marketing lists without a valid legal basis under Article 11 of Law 3471/2006.

i-table does not use Restaurant Data to market to Guests, does not sell it, and does not share one Restaurant's guest records with another. Guest records are held separately per Restaurant.

↑ Back to contents

10.Acceptable use — applies to everyone§

You must not:

• use the Platform unlawfully, or to store or transmit unlawful, defamatory or infringing material;
• make false, speculative, duplicate or automated Reservations, or Reservations you do not intend to honour;
• attempt to gain unauthorised access to any part of the Platform, another account, or another Restaurant's data;
• probe, scan or test the vulnerability of the Platform, or circumvent any authentication, rate limit or access control;
• scrape, crawl, harvest or systematically extract data from the Platform, or use any robot, spider or automated means to access it, except a search engine indexing public pages in the ordinary way and in accordance with our robots directives;
• interfere with the Platform's operation or place an unreasonable load on it, including by denial-of-service;
• copy, modify, translate, reverse engineer, decompile or disassemble the Platform, or attempt to derive its source code, except to the extent that applicable law expressly permits it notwithstanding this restriction;
• resell, sublicense or make the Platform available to a third party except as expressly permitted; or
• remove or obscure any proprietary notice.

Responsible security research. If you discover a vulnerability, please report it to [SECURITY EMAIL] rather than exploiting it. We will not pursue a good-faith researcher who reports promptly, does not access more data than necessary to demonstrate the issue, does not degrade the service, and gives us a reasonable opportunity to fix it before disclosure.

↑ Back to contents

11.Intellectual property§

The Platform, its software, design, text, graphics and the i-table name and logo are owned by i-table or its licensors and are protected by intellectual property law. Nothing in these terms transfers any ownership. All rights not expressly granted are reserved.

Restaurant content. The Restaurant retains ownership of the content it uploads — its name, descriptions, photographs, policies and marks. It grants i-table a non-exclusive, royalty-free licence to host, reproduce, adapt for formatting purposes and display that content, for as long as needed to operate the Platform and display the Restaurant's booking page. The Restaurant warrants that it holds the rights necessary to grant that licence, in particular for photographs.

Feedback. If you send us suggestions for improving the Platform, we may use them without obligation or payment. This does not give us any right to your confidential information.

↑ Back to contents

12.Third-party services§

The Platform relies on third parties — hosting and database infrastructure, a payment provider, and email and messaging providers. Their own terms and privacy notices govern their services. We choose them with reasonable care and remain responsible for our sub-processors as Article 28(4) GDPR requires, but we do not control their services and cannot guarantee their availability.

Where a Restaurant embeds the booking widget in its own website, it is responsible for its own site, including any consent mechanism its own analytics or other technologies require.

↑ Back to contents

13.Part A — Platform Fees, invoicing and VAT§

Platform Fees are what the Restaurant pays i-table for the software. They are entirely separate from any Deposit a Guest pays the Restaurant — see section 14.

• Fees are those set out in the Restaurant's order form or the published price list in force. The Platform supports a fee calculated per covered guest, at a commission rate configured for each Restaurant.
• All amounts are exclusive of VAT, which is added at the applicable rate. Where the reverse charge applies to a customer established outside Greece and holding a valid VAT identification number, the invoice is issued accordingly.
• Invoices are issued to the billing contact the Restaurant provides and are payable within [PAYMENT TERMS DAYS] days of the invoice date.
• Overdue amounts bear default interest at the statutory rate applicable to commercial transactions under Greek law implementing Directive 2011/7/EU on late payment, accruing from the day after the due date, together with the fixed compensation for recovery costs provided by that legislation.
• The Restaurant is responsible for keeping its billing details current. Fees are non-refundable except where these terms or mandatory law say otherwise.
• We may change the Fees on not less than [FEE CHANGE NOTICE PERIOD] written notice, taking effect at the start of the next billing period. If the Restaurant does not accept the change it may terminate before the change takes effect, without penalty.

↑ Back to contents

14.Deposits and prepayments — who is charging you, and who owes the refund§

This section applies to Restaurants and Guests alike, because it is the point at which the two most often get confused.

• Where a Restaurant requires a Deposit, the payment is made through a third-party payment provider. i-table facilitates the transaction as part of the booking flow; it does not supply the hospitality service and does not receive the Deposit as its own revenue.
• Cancellation, no-show, late-arrival and refund policies are set by the Restaurant and shown before the booking is completed. Read them before you confirm.
• Requests to cancel, amend or refund a Deposit must be directed to the Restaurant. i-table has no authority to grant a refund of a Restaurant's Deposit on its own initiative.
• The Restaurant is responsible for the lawfulness and fairness of its own policies, including their compliance with Law 2251/1994.

↑ Back to contents

15.Part B — Terms for Guests§

This section applies when you book a table through a booking page powered by i-table.

Your contract is with the Restaurant

When you complete a booking, the reservation is between you and the Restaurant. i-table provides the booking software on the Restaurant's behalf. The Restaurant is responsible for the table, the service, the food, its premises, its policies and any Deposit you pay. Complaints about your meal or your booking go to the Restaurant.

Making a booking

• Provide accurate details. A booking confirmation is sent to the contact details you give, so an error in them may mean you do not receive it.
• A booking is only held for a short period while payment or confirmation is completed. If it is not completed in time, the table is released automatically and you will need to book again.
• A booking is confirmed only when the Platform shows it as confirmed, or you receive a confirmation with a booking reference. A request that has not been confirmed is not a reservation.
• The Restaurant may decline, cancel or move a booking in accordance with its own policy — for example on closure days or where a Deposit is not paid.
• Only provide another person's details if they are content for you to do so, and avoid entering health or dietary information about other people unless it is necessary for the booking.

Your right of withdrawal — and why it does not apply here

A consumer entering a distance contract normally has 14 days to withdraw without giving a reason. That right does not apply to a restaurant reservation for a specific date: Article 16(1)(l) of Directive 2011/83/EU, transposed into Greek law by Law 2251/1994, excludes contracts for the provision of catering services or services related to leisure activities where the contract provides for a specific date or period of performance.

In plain terms: booking a table for Friday at 20:30 is not something you can cancel under the 14-day distance selling rules. What you can do is cancel under the Restaurant's own cancellation policy, which is shown to you before you confirm. Nothing here removes any other right you have as a consumer, including in respect of a service that is not supplied as described.

Guest conduct

The acceptable use rules in section 10 apply to you too. Repeated no-shows, abusive content, or bookings made in someone else's name without their agreement may result in bookings being refused.

Your personal data

The Restaurant is the controller of your reservation data and i-table acts as its processor. This is explained fully in the Privacy Notice, which also tells you how to exercise your rights and who to address them to.

↑ Back to contents

16.Availability, maintenance and changes§

We aim to keep the Platform available and to provide it with reasonable skill and care, but we do not warrant that it will be uninterrupted or error-free.

• Planned maintenance. We will give reasonable advance notice where practicable and will try to schedule it outside typical service hours.
• Emergency maintenance. May be carried out without notice where necessary for security or stability.
• Changes to features. We may modify, add or remove features to improve the Platform, address security, or comply with law. We will not materially degrade the core reservation functionality a Restaurant is paying for without giving reasonable notice; if we do, the Restaurant may terminate without penalty.
• Third-party outages. Interruptions caused by hosting, payment or messaging providers, or by the public internet, are outside our control.

↑ Back to contents

17.Part A — Support§

We provide reasonable support to Restaurants by email at [SUPPORT EMAIL] during [SUPPORT HOURS]. Support covers use of the Platform and faults in it. It does not cover the Restaurant's own hardware, network or website, training beyond onboarding, or configuration work we have not agreed to perform.

↑ Back to contents

18.Warranties§

We warrant that we will provide the Platform with reasonable skill and care and in accordance with these terms, and that we have the right to grant the licence in section 6.

To the fullest extent permitted by applicable law, and without prejudice to any mandatory statutory rights of a consumer, all other warranties, conditions and terms implied by statute or common law are excluded. In particular we do not warrant that the Platform will be uninterrupted, that it will meet requirements we have not agreed in writing, or that defects will all be corrected.

↑ Back to contents

19.Liability§

(a) Liability that is never excluded

Nothing in these terms excludes or limits liability for:

1. death or personal injury caused by negligence;
2. wilful misconduct or gross negligence;
3. fraud or fraudulent misrepresentation;
4. any liability that cannot be excluded or limited under mandatory Greek or EU law, including under consumer protection law and Article 82 GDPR.

(b) Limits between i-table and a Restaurant

Subject to paragraph (a), and in this business-to-business relationship only:

1. neither party is liable for loss of profit, loss of revenue, loss of anticipated savings, loss of business or goodwill, or indirect or consequential loss, in each case however arising;
2. i-table's total aggregate liability arising in any period of twelve consecutive months is limited to the total Platform Fees paid or payable by the Restaurant for that period; and
3. i-table is not liable for loss arising from the Restaurant's own configuration of availability, capacity or policies, from data the Restaurant or its Guests supply, or from the Restaurant's failure to honour a Reservation.

(c) Liability towards a Guest

i-table's responsibility to a Guest is limited to the operation of the reservation software. The Restaurant alone is responsible for the hospitality service, the premises, the food and its own policies, and for any Deposit it takes. This allocation reflects who actually supplies what; it does not purport to remove any right a consumer has against either party under mandatory law.

↑ Back to contents

20.Part A — Indemnity§

The Restaurant will indemnify i-table against losses, liabilities and reasonable costs arising from a third-party claim to the extent caused by the Restaurant's breach of section 9 or section 10, by content it uploads infringing a third party's rights, or by its failure to honour a Reservation or to comply with Data Protection Law.

We will notify the Restaurant promptly of any such claim, will not settle it without the Restaurant's consent (not to be unreasonably withheld), and will give reasonable assistance at the Restaurant's cost. This indemnity does not apply to the extent the claim results from our own breach or negligence.

↑ Back to contents

21.Force majeure§

Neither party is liable for failure or delay in performing its obligations, other than an obligation to pay money that has fallen due, caused by an event beyond its reasonable control — including natural disaster, fire, flood, epidemic, war, terrorism, civil unrest, strike, failure of the public internet or of an electricity or telecommunications network, act of government, or a large-scale failure of a third-party infrastructure provider. The affected party will notify the other without undue delay and use reasonable efforts to mitigate. If the event continues for more than [FORCE MAJEURE PERIOD], either party may terminate on written notice.

↑ Back to contents

22.Part A — Confidentiality§

Each party will keep the other's confidential information confidential, use it only to perform these terms, and disclose it only to personnel and advisers who need it and are under equivalent obligations. This does not apply to information that is or becomes public without breach, was already lawfully known, is independently developed, or must be disclosed by law or by a competent authority — in which case the disclosing party will, where lawful, give prior notice.

These obligations continue for [CONFIDENTIALITY SURVIVAL PERIOD] after termination. Obligations relating to personal data continue for as long as Data Protection Law requires.

↑ Back to contents

23.Data protection and the required Data Processing Agreement§

Each party will comply with Data Protection Law. In relation to Reservation and guest data processed through the Platform, the Restaurant is the controller and i-table is the processor within the meaning of Article 4(7) and 4(8) GDPR. i-table also acts as a controller for the limited purposes set out in the Privacy Notice, and does not claim to be a processor for those.

A separate DPA is mandatory, not optional

Article 28(3) GDPR requires processing by a processor to be governed by a written contract that is binding on the processor and sets out prescribed matters. i-table therefore makes a Data Processing Agreement available to every Restaurant, and it must be in place before the Restaurant takes live bookings. It is a separate document, not part of these terms and not part of the Privacy Notice, because it is a distinct contract with its own required content and its own annexes.

What the DPA must contain

1. the subject-matter and duration of the processing, its nature and purpose, the types of personal data and the categories of data subjects — Article 28(3) opening paragraph;
2. an obligation to process only on documented instructions from the Restaurant, including on transfers to third countries, with a duty to inform the Restaurant if i-table believes an instruction infringes Data Protection Law — Article 28(3)(a) and Article 28(3) final paragraph;
3. a duty of confidentiality binding on all personnel authorised to process the data — Article 28(3)(b);
4. the security measures required by Article 32 — Article 28(3)(c);
5. the terms on which sub-processors may be engaged, requiring prior specific or general written authorisation, notice of intended changes, an opportunity to object, and flow-down of the same obligations, with i-table remaining fully liable for its sub-processors — Articles 28(2) and 28(4);
6. an obligation to assist the Restaurant in responding to data subject rights requests under Chapter III — Article 28(3)(e);
7. an obligation to assist with Articles 32 to 36 — security, breach notification to the authority and to data subjects, data protection impact assessments and prior consultation — Article 28(3)(f);
8. the Restaurant's choice, on termination, to have the personal data returned or deleted, and deletion of existing copies unless retention is legally required — Article 28(3)(g);
9. an obligation to make available the information needed to demonstrate compliance and to allow and contribute to audits and inspections — Article 28(3)(h);
10. transfer safeguards under Chapter V — the mechanism relied on, and the Standard Contractual Clauses where applicable, together with a transfer impact assessment;
11. breach notification to the Restaurant without undue delay, with defined content and a target timescale that lets the Restaurant meet its own 72-hour obligation under Article 33(1);
12. an annex listing the approved sub-processors and the processing details, kept current; and
13. the technical and organisational measures as a further annex, at a level of detail sufficient to be meaningful without creating a security risk.

↑ Back to contents

24.Part A — Suspension§

We may suspend access, in whole or in part, where: an amount is overdue and remains unpaid after written notice and a reasonable cure period; we reasonably believe the Platform is being used in breach of section 10; suspension is necessary to protect the security or integrity of the Platform or other customers; or the law requires it.

We will give as much notice as is reasonable in the circumstances, limit the suspension to what is necessary, and restore access promptly once the cause is resolved. Suspension does not relieve the Restaurant of the obligation to pay Fees for the period, unless the suspension was our fault.

↑ Back to contents

25.Part A — Term and termination§

• The agreement runs from account activation until terminated.
• Either party may terminate for convenience on [TERMINATION NOTICE PERIOD] written notice, effective at the end of the then-current billing period.
• Either party may terminate immediately on written notice if the other commits a material breach that is not remedied within 30 days of notice, or becomes insolvent, enters bankruptcy or an equivalent procedure, or ceases to carry on business.
• We may terminate immediately where continuing would breach the law.

↑ Back to contents

26.Part A — What happens on termination§

1. Access to the dashboard and the Restaurant's booking pages ends.
2. Fees accrued up to termination fall due; Fees paid for a period after termination are refunded pro rata, unless we terminated for the Restaurant's material breach.
3. Data export. For [DATA EXPORT WINDOW] after termination, the Restaurant may request an export of its Restaurant Data in a structured, commonly used, machine-readable format. We will not hold data hostage against a payment dispute.
4. Data deletion. After that window, we will delete or return Restaurant Data in accordance with the Restaurant's instruction under the DPA, except where retention is required by law or is necessary for the establishment, exercise or defence of legal claims. Backups are overwritten on their ordinary cycle.
5. Sections on intellectual property, confidentiality, liability, indemnity, data protection and governing law survive.

↑ Back to contents

27.Changes to these terms§

We may amend these terms to reflect changes in the Platform, our business or the law. For Restaurants, we will give at least [TERMS CHANGE NOTICE PERIOD] written notice of a material change; if the Restaurant objects it may terminate before the change takes effect, without penalty, and that is its remedy. Changes that are required by law, or that do not adversely affect the Restaurant, may take effect immediately.

For Guests, the version in force at the time of a booking governs that booking. A change does not affect a Reservation already confirmed.

↑ Back to contents

28.Notices§

Notices to i-table must be sent to [CONTACT EMAIL] and, where the notice concerns termination or a legal claim, also in writing to [REGISTERED ADDRESS]. Notices to a Restaurant are sent to the email address on its account or given in the dashboard. Notices to a Guest are sent to the contact details given when booking. An emailed notice is treated as received on the next business day after sending, unless the sender receives a delivery failure.

↑ Back to contents

29.General§

Assignment

The Restaurant may not assign or transfer these terms without our prior written consent, not to be unreasonably withheld. We may assign to an affiliate or in connection with a merger, reorganisation or sale of the business, provided the assignee assumes our obligations. A Guest may not transfer a Reservation except as the Restaurant permits.

Subcontracting

We may subcontract performance but remain responsible for our subcontractors. Sub-processing of personal data is governed by the DPA.

Entire agreement

These terms, together with any order form, the Privacy Notice and the DPA, are the entire agreement between the parties on their subject matter and supersede earlier discussions. Nothing limits liability for fraudulent misrepresentation.

Severability

If a provision is held invalid or unenforceable, it is severed or modified to the minimum extent necessary and the remainder continues in force.

Waiver

A failure or delay in exercising a right is not a waiver of it, and a single or partial exercise does not prevent further exercise. A waiver is effective only if given in writing.

No partnership

Nothing creates a partnership, joint venture, agency or employment relationship between the parties.

Third parties

Except as expressly stated, a person who is not a party has no right to enforce these terms.

Language

These terms are published in English and Greek. [SPECIFY WHICH LANGUAGE VERSION PREVAILS IN CASE OF DISCREPANCY] — noting that a term in a consumer contract must in any event be plain and intelligible, and that ambiguity is construed in the consumer's favour.

↑ Back to contents

30.Governing law, disputes and jurisdiction§

These terms and any non-contractual obligation arising out of them are governed by Greek law.

(a) Disputes with a Restaurant

The courts of [INSERT APPROPRIATE GREEK COURTS — DETERMINED BY THE REGISTERED SEAT] have exclusive jurisdiction over any dispute arising out of or in connection with these terms.

(b) Disputes with a Guest who is a consumer

The jurisdiction clause above does not apply to a consumer. Under Articles 17 to 19 of Regulation (EU) No 1215/2012, a consumer may bring proceedings in the courts of the Member State where the other party is domiciled or in the courts of the place where the consumer is domiciled, and may only be sued in the courts of the consumer's own domicile. Nothing here deprives a consumer of the protection of mandatory provisions of the law of their country of habitual residence, as Article 6 of Regulation (EC) No 593/2008 (Rome I) provides.

(c) Alternative dispute resolution

A consumer may refer a dispute to a certified alternative dispute resolution body under Directive 2013/11/EU, as transposed in Greece — for example the Consumer Ombudsman (Συνήγορος του Καταναλωτή), an independent authority, or the European Consumer Centre Greece for a cross-border dispute. Use of ADR is voluntary and does not affect the right to go to court.

↑ Back to contents

31.Contact§

General and contractual enquiries

[CONTACT EMAIL]

Support

[SUPPORT EMAIL]

Security reports

[SECURITY EMAIL]

Privacy and data protection

[PRIVACY EMAIL]

Postal

[LEGAL COMPANY NAME], [REGISTERED ADDRESS]

See also our Privacy Notice.

↑ Back to contents