Este documento se ofrece en inglés hasta que se publique una traducción. Para el derecho alemán y los procedimientos en Alemania prevalece el texto alemán de las condiciones.

Terms of use

Effective date: 9 September 2026

These terms govern the TravelDataService Hotel Booking Engine booking-engine SaaS provided by TRAVELDATASERVICE. They are standard business terms (AGB) for a B2B contract with hotels and property managers (“you”, “Customer”).

By creating an account, ticking acceptance at signup, or using the service, you conclude a contract with us. The contract is a paid grant of use of software over a network (SaaS). If German law classifies that grant as a lease (Mietvertrag), section 14 still applies, including the exclusion of no-fault liability for initial defects.

Signup includes acceptance of the data-processing agreement in section 15 (Art. 28 GDPR).

1. Provider and scope

TRAVELDATASERVICE Greece specialist travel agency & travel shop Owner: Jean Ioannis Arampatsis (sole proprietorship (Einzelunternehmen)) Müllerstr. 47 80469 Munich Germany Phone: +49 (0) 89 2609410 Email: info@tdsreisen.com VAT identification number: DE455705699

TravelDataService Hotel Booking Engine is a product name. The contracting party is TRAVELDATASERVICE, sole proprietorship (Einzelunternehmen), owner Jean Ioannis Arampatsis.

These terms apply to the dashboard, the paste-in website widgets (button, booking strip, datepicker), the booking engine guests use on your site, and related APIs. They do not apply to TRAVELDATASERVICE’s separate travel-agency / travel-shop activity, if any.

We provide the service only to businesses (Unternehmer, § 14 BGB). You warrant that you act in a commercial capacity. Mandatory consumer law applies only if a consumer nevertheless uses the service.

2. Subject matter — what we provide and what we are not

We provide a billed software service that talks to your Beds24 account: a dashboard, embeddable widgets, and a booking engine.

We are not:

a party to the guest’s accommodation contract (that contract is between the guest and you / the property)
the organiser or retailer of a package travel service for stays booked through this engine (Directive (EU) 2015/2302 / German §§ 651a ff. BGB). You sell your own inventory
the guest’s payment acquirer for lodging (when cards are taken, they are taken in your Beds24 Stripe Checkout)
a replacement for Beds24, your channel manager, PMS, OTAs, or your tax advisor
a sender of booking confirmation email (Beds24 direct-booking templates send those)

Guest complaints about a stay go to the property, not to us as the engine provider.

3. Conclusion of the contract

The contract is formed when we create your organisation account after you submit a valid signup (including acceptance of these terms and the privacy policy).

A trial, if offered on a plan, is part of this contract. A paid subscription is formed when Stripe confirms successful Checkout for that plan. Plan names, intervals, and prices are those shown at checkout and in Billing; they are set by our platform admin and are not hardcoded in these terms.

There is no obligation on us to accept every signup. We may refuse, suspend, or close accounts that are abusive, unlawful, or that jeopardise other customers or Beds24 API limits.

4. Account

You must provide accurate company and login data, keep credentials secret, and ensure only authorised staff use the dashboard. You are responsible for all actions under your organisation, including those of vicarious agents.

Notify us without undue delay if you suspect unauthorised access.

5. Rights of use

We grant you a simple, non-exclusive, non-transferable, non-sublicensable, time-limited right to use TravelDataService Hotel Booking Engine during the term, solely for your own internal operation of the properties you connect (including embedding the widgets on websites you operate for those properties).

You may not: resell or rent the SaaS to third parties as a competing booking product; white-label it for unaffiliated businesses without our written consent; copy the product to build a competing engine except as mandatory law allows (§§ 69d, 69e UrhG remain unaffected); or extract Beds24 tokens.

We and our licensors own the software, design, and TravelDataService Hotel Booking Engine marks. You own your property content.

6. Beds24

You must have a valid Beds24 account and connect with an invite code. We store the refresh token; we never show it again and never send it to the browser.

You are responsible for:

Beds24 settings (prices, restrictions, deposits, questions, emails, Stripe, languages, currency, policies, cut-off, inventory)
API credits and any Beds24 fees
keeping invite / IP whitelist current for our hosting outbound IP
the accuracy of texts and photos you sync or upload
pressing Refresh / Sync after you change texts or settings in Beds24 (Beds24 does not push those edits to us)

Photo import with Beds24 v1 apiKey and propKey is one-shot. We do not store those keys.

If Beds24 is unavailable, rate-limits you, or returns errors, the engine cannot invent inventory.

7. Booking engine rules (product facts)

You acknowledge the product behaves as specified, including:

Live engines need an active or trial subscription with us. The dashboard remains available if billing fails; new guest bookings do not
Guest cards only if Stripe is enabled on that property in Beds24. Other gateways: the guest can still submit; they will not pay inside the engine
Rooms from different properties in one cart only if they share the same Beds24 Stripe account and the same currency
Unpaid Stripe holds last 15 minutes (or cancel immediately if Checkout is closed)
Hidden Beds24 rooms are omitted from the engine
We do not send a second confirmation email
You must set a general policy in Beds24 and paste a privacy policy URL before an engine can go live
Multi-property limitations are always shown in the dashboard; you must not hide them from staff who configure the engine
Deposits, near-term rules, extras, vouchers, and non-payment status follow that property’s Beds24 setup. We do not add an engine-level override
The product does not create a second extras or deposit catalogue. If the painted calendar and a live offer disagree, offers are the sell check

8. Your duties (hotel / property)

You are solely responsible for the accommodation contract and for compliance of your offering with law, including:

room descriptions, photos, occupancy, accessibility, and prices
guest-facing terms, house rules, cancellation, deposits, and that they are shown before checkout (the engine displays your Beds24 general policy and, where present, cancellation policy, plus your privacy URL; you must keep those texts current and complete)
price indication rules (including the German PAngV where it applies), taxes, and local tourist tax as configured in Beds24
Impressum, cookie, and privacy duties on your website
mentioning us and Beds24 in your guest privacy policy (a paste-in paragraph is in the dashboard Help)

You must keep an origin allowlist accurate if you enable one, maintain reasonable security of your site and staff devices, and not use the engine for unlawful listings.

9. Inventory, third parties, overbooking

A quote is a point-in-time check of Beds24 when the guest searches or books. Automated sync does not guarantee that channel managers, OTAs, a PMS, or later manual edits have already reached Beds24.

You are responsible for correct rates and inventory in Beds24. We are not liable for delayed or wrong data caused by Beds24, channel managers, OTAs, other PMS tools, or your own input, nor for overbookings that result from that delay or input.

This section does not exclude liability for a defect in our software (see sections 13 and 14).

10. Fees, Stripe billing, commission

Prices are set by our platform admin and shown at checkout and in Billing. Payment is by Stripe Checkout / Customer Portal on our Stripe account (SaaS only).

Subscriptions renew until cancelled in the Stripe portal or as otherwise agreed
Taxes (e.g. German VAT) are added where applicable. Our VAT ID is DE455705699
Failed payment: Stripe and the dashboard show the status; the live engine stops taking new bookings; you can update the payment method in Billing without delay. If default continues, we may terminate for cause. Bookings already in Beds24 are not altered by us
Prepaid periods are not refunded unless mandatory law or Stripe’s handling of a specific event requires otherwise
Optional commission (if enabled on your plan) is invoiced to you on our Stripe. It is never taken from the guest’s lodging charge. The calculation basis is shown on the plan / invoices. Cancelled stays: unbilled commission is voided; billed commission may be credited on a later invoice as implemented in the product

Where we increase the price of a plan that already applies to you, we will give prior notice (email and/or dashboard) with a reasonable period and the right to terminate before the increase takes effect. If you do not terminate, the new price applies from the stated date. Admin may also create prices for new customers only; those do not change your current subscription until you change plan.

Chargebacks or disputes on guest payments are between the guest, you, Beds24, and your Stripe account. We cannot refund lodging we never received.

11. Your content and photos

You grant us a licence to host and display room photos, property photos, logos, and texts as needed to run the engine and dashboard. You warrant that you have the rights (including guest-appearing photos and trademarks).

Deleting a gallery or the organisation deletes those files from our storage, subject to backups rotating out. You remain responsible for keeping copies of content you need; we do not offer a separate backup-as-a-service.

12. Acceptable use

You must not: probe or overload the service; resell the SaaS without our written consent; use the engine for unlawful listings; attempt to extract Beds24 tokens; submit malware; or scrape other customers’ data.

Public widget APIs are rate-limited.

13. Availability, maintenance and defects

Unless a separate written SLA says otherwise, we do not promise a numerical uptime percentage. We still owe a service that is suitable for the contractual use (a professional booking engine connected to your Beds24 account).

The following are not defects of our service, provided we have not caused them by a fault of our own software: scheduled maintenance, emergency security patches, force majeure (section 17), failures of Beds24, hotel-Stripe, DNS, your website, or your misconfiguration.

We aim to carry out scheduled maintenance in low-traffic hours, typically 02:00–05:00 Europe/Berlin, and to keep it as short as reasonably possible. Emergency patches may occur at other times.

Defects. You must notify us of material defects without undue delay. We will remedy them within a reasonable time. If the live engine is substantially unusable for the contractual purpose for a continuous period that is more than insignificant, you may reduce the SaaS fee for that period (Minderung) and, if the impairment is not remedied within a reasonable further period or is unreasonable to wait for, terminate for cause. Trivial impairments do not entitle you to reduce the fee.

Statutory rights that cannot be waived remain unaffected. Section 14 limits damages.

14. Liability (B2B, German law)

We are liable without limit for intent, gross negligence, and injury to life, body, or health.

No-fault liability for initial defects under § 536a(1) alt. 1 BGB (liability regardless of fault for defects already present when the contract was concluded) is excluded. Liability based on fault remains as set out in this section.

For slight negligence we are liable only for breach of cardinal obligations (duties whose fulfilment makes the contract possible and on which you may regularly rely — including, in particular, providing the booking engine so that, when Beds24 and your configuration allow it, guests can complete a booking). That liability is limited to typical, foreseeable damage. Typical foreseeable damage may include lost direct bookings caused by a defect in our software. It does not include losses caused by Beds24, your Stripe, OTAs, channel managers, or your own data or settings.

In amount, slight-negligence liability for cardinal obligations is limited to the net SaaS subscription fees (excluding VAT) payable for twelve months of the plan applicable when the event occurred. If no paid plan applies (for example a trial), the cap is the higher of (i) the net annual fee of the lowest paid plan then offered with the same feature set and (ii) EUR 1,000.

We are not liable for slight negligence of non-cardinal duties.

We are not liable for: the guest stay; your prices, restrictions, or policy texts; Beds24 or hotel-Stripe failures; guests who abandon Checkout; overbookings from third-party or customer data as in section 9; your failure to fill policies; or tax/tourist-tax calculations that originate in Beds24 — except to the extent a defect in our software caused the harm and this section allows damages.

These limits also apply to Jean Ioannis Arampatsis as proprietor, and to our vicarious agents, to the extent permitted.

Mandatory law remains unaffected (including the Product Liability Act). If a consumer nevertheless uses the service, mandatory consumer rights remain.

15. Data processing agreement (Art. 28 GDPR)

This section is the contract for processing (AVV) of guest personal data. It applies when you use the engine. Owner account and billing data are processed with us as controller under the privacy policy, not under this section.

You are controller of guest booking data. We are processor for data we receive to create the Beds24 booking and to keep the thin bookings log.
Subject matter: operate the booking engine, pass guest answers to Beds24, hold unpaid bookings for up to 15 minutes, receive booking webhooks, compute optional commission on non-identifying log rows.
Duration: for the term of your account, then deletion or return as below.
Nature and purpose: automated transfer and display; no guest CRM; no marketing by us to guests.
Types of data: identification and contact fields Beds24 asks for; custom questions 1–10; stay dates and occupancy; language; payment status. Not PAN/CVC. We do not keep a guest profile. Identity data are sent to Beds24; our log has booking numbers, dates, occupancy, amounts, status — no guest name, email, phone, or card. If you collect ID/passport or similar via custom questions, that content is passed to Beds24 as you configured and is not stored in our log.
Data subjects: your guests and, if present, their travelling party as you configured in Beds24.
Instructions: you instruct us to process only to provide TravelDataService Hotel Booking Engine as documented. We will inform you if we believe an instruction infringes data-protection law; unlawful instructions may be refused.
Confidentiality: persons we authorise are bound to confidentiality.
Security (Art. 32): HTTPS in production; passwords hashed; tenant queries filtered by organisation; secrets not in the client; webhook signature checks; no guest cards on our servers; Beds24 tokens never sent to the browser; v1 photo keys discarded after import; access limited to staff who need it. Further detail is in the privacy policy.
Sub-processors: (a) our hosting provider for the Plesk application and MySQL (location as named in the privacy policy); (b) Stripe, Inc. / Stripe Payments Europe for your SaaS invoices only. Guest card processing is your Beds24 Stripe relationship, not our sub-processing of PAN. Beds24 is your processor, not ours. We will notify you of intended addition or replacement of our hosting or billing sub-processors via this legal page, the dashboard, and/or email, as a rule at least 14 days in advance. You may object on reasonable data-protection grounds within that period. If you object and we cannot reasonably provide the service without the sub-processor, either party may terminate the contract.
International transfers: as in the privacy policy (including Stripe’s SCCs where Stripe processes outside the EEA).
Assistance: we assist with data-subject requests that concern data we hold. Guest access/erasure is primarily in Beds24.
Return or deletion: you may export organisation data in the dashboard (Settings). On end of processing you may choose export (return) before deletion. Organisation delete then removes tokens, cache, photos, and log rows we are not legally required to keep (tax invoices on our Stripe remain). Beds24 stays are not deleted by us.
Audit: on reasonable written notice, no more than once per year unless a competent authority requires more, we provide information needed to demonstrate Art. 28 compliance, avoiding disclosure of other customers’ data or secrets.
Breach: we notify you without undue delay after becoming aware of a personal-data breach affecting your data.

16. Indemnity

You will indemnify us against third-party claims arising from your listings, photos, policies, guest contracts, Beds24 configuration, or your breach of these terms, except to the extent caused by our intent or gross negligence.

17. Confidentiality and force majeure

Each party shall keep confidential the other party’s non-public business information, including access tokens, credentials, and unpublished rates, and use it only to perform this contract. This does not apply to information that is public, independently developed, or that must be disclosed by law.

Force majeure (including natural disasters, war, terrorism, lawful strike, epidemic measures, and outages of electricity or public networks outside our reasonable control) relieves the affected party for the duration of the event. Failures of Beds24 or Stripe count as force majeure for us only insofar as we could not reasonably avoid the effect. Force majeure does not exclude liability for our own software defects under sections 13 and 14.

18. Term, termination and data after the end

The contract starts at signup (including trial). Either party may terminate according to the Stripe subscription (Customer Portal cancel) or by deleting the organisation in Settings. Deleting the organisation ends the SaaS contract.

We may terminate for cause (including continued non-payment after failed collection, abuse, or legal risk) with notice appropriate to the severity.

On end of service: live widgets stop taking bookings; Beds24 stays and historical bookings remain in Beds24.

Export: use Settings → organisation export (JSON) before you delete the organisation. After termination we will, on written request within 30 days, provide a further export of data we still hold if you did not already download it, then delete as in section 15 except legal holds.

19. Changes to these terms

We may change the software (including Beds24 API adaptations) within the contractual purpose.

We may change these terms. For material changes that are adverse to paying customers we will notify you individually (email and/or prominent dashboard notice) at least six weeks before the change takes effect, and we will inform you that you may terminate as of the effective date if you object. If you do not terminate by that date, the new terms apply. Silence after that notice is deemed acceptance of the change. Changes required by law or by a binding court or authority decision may take effect with a shorter period if necessary; we will still inform you.

The current text is always at /terms.

20. Governing law, venue and language

German law applies, excluding CISG and conflict-of-law rules that would refer to another law.

If you are a merchant (Kaufmann), a legal person under public law, or a public-law special fund, the courts of Munich, Germany have exclusive jurisdiction. We may also sue at your seat.

The EU Online Dispute Resolution platform was discontinued on 20 July 2025. We do not participate in consumer arbitration (see Legal notice).

Language. These terms are issued in German and English. For proceedings in Germany, the German text prevails in case of conflict. Other languages (including Greek) are convenience translations.

21. Severability

If a clause is invalid, the rest remains. The invalid clause is replaced by a valid one closest to the commercial intent, within mandatory law.

22. Contact

TRAVELDATASERVICE · Jean Ioannis Arampatsis · Müllerstr. 47, 80469 Munich, Germany info@tdsreisen.com · +49 (0) 89 2609410