Features
Room chargesPay with the room key at the tillReception viewEvery charge, live at the deskRooms and keysCharging on or off per roomRetriesA slow PMS is tried again for youIntegrationsConnect your PMS and POS
Hardware
NFC reader€49 once per tillScan pageOpens on the till screenAPI keysOne key per till system
Step by stepFrom sign-up to the first chargeFor the front deskA live list with reasons attachedFor restaurant and barOne button on the till you haveFor financeEvery charge matched to a folio
SupportAnswers and contactSetup guideConnect Mews in minutesIntegrationsWhat works todayPricing€2 per room per monthSecurityEU hosting, hashed keysTermsThe service agreementSign inFor hotel teamsContactTalk to the DGME team
Integrations
Pricing
Talk to usGet startedSign up
Room chargesReception viewRooms and keysIntegrationsNFC reader
Step by stepFor the front deskFor restaurant and barFor finance
SupportSetup guideTermsSign in
Integrations
Pricing
Get startedSign upTalk to us

Legal

Terms of servicePrivacy policyData processing agreementSub-processors

Draft, pending legal review.

Privacy Policy

Effective date: [pending]

1. Who we are

DGME HotelPay is a service of DGME (“DGME”, “we”, “us”). This policy explains what personal data we collect when you visit our website, contact us or use the HotelPay dashboard, why we use it, and what rights you have.

DGME, Karel van Egmondstraat 133, 5913 CM Venlo, the Netherlands.

For anything about this policy or your personal data, email support@dgme-hotelpay.com.

2. What we collect

Website visitors

Our servers log technical details of each request, such as your IP address, browser type, the page you asked for and the time. Our forms use Cloudflare Turnstile to check that a person, not a bot, is sending them.

Leads and contact requests

When you fill in our contact form, we receive your first and last name, work email, hotel name, number of rooms, the PMS and till system you use, your message, and your consent to be contacted.

Hotel staff accounts

When your hotel gives you an account, we hold your name, email address and role, your sign-in sessions, and an audit log of sign-ins and important actions in the dashboard.

Billing contacts

Once billing is live, we will hold the name, email address and billing details of the person who manages the hotel’s subscription. Payments will be handled by Stripe.

3. Why we use it, and on what legal basis

  • Running and protecting the website and its forms: our legitimate interest in keeping the service available and free of abuse.
  • Answering your contact request: your consent, which you give on the form. You can withdraw it at any time.
  • Giving hotel staff access to the dashboard: the contract with your hotel, and our legitimate interest in keeping accounts secure.
  • Billing hotels: the contract with your hotel. We also keep invoices because the law requires it.

4. Guest data

When a hotel uses HotelPay, we process data about its guests, such as the name held in the PMS, the room number, stay dates and room-key identifiers. For that data the hotel is the controller and DGME is its processor. The same applies to the staff data the dashboard handles for the hotel.

How we process that data for hotels is set out in our data processing agreement. If you are a guest, please contact the hotel you stayed at.

5. How long we keep it

  • Server logs: [retention period pending].
  • Contact requests: [retention period pending].
  • Staff accounts and audit logs: [retention period pending], and never longer than our terms allow after a hotel’s agreement ends.
  • Billing records: [retention period pending], as tax law requires.

6. Who we share it with

We use a small number of service providers to host and run HotelPay: hosting, network protection, error monitoring, email delivery and, once billing is live, payments. The current list is on our sub-processors page.

We do not sell personal data, and we do not share it for advertising.

7. Transfers outside the EU

HotelPay is hosted in the EU, in Frankfurt, Germany. Some providers may process data outside the European Economic Area: Cloudflare runs a global network, and Stripe will be used for billing. Where that happens, we rely on appropriate safeguards such as the EU Standard Contractual Clauses.

Where our email provider, Resend, stores data is [pending confirmation].

8. Your rights

You have the right to:

  • see the personal data we hold about you;
  • have it corrected or deleted;
  • limit or object to how we use it;
  • get a copy in a format you can take elsewhere;
  • withdraw your consent at any time, where we rely on it.

To use any of these rights, email support@dgme-hotelpay.com. We answer within one month.

You can also complain to the Dutch data protection authority, the Autoriteit Persoonsgegevens.

9. Cookies

The hotel dashboard uses one cookie to keep you signed in. It is needed for the dashboard to work.

Our forms use Cloudflare Turnstile to tell people and bots apart. We do not use analytics or advertising cookies, so there is no cookie banner.

10. Changes to this policy

We may update this policy. When we do, we change the effective date at the top of this page. If a change matters to hotels using HotelPay, we also tell them by email.

11. Contact

  • Privacy questions and requests: support@dgme-hotelpay.com
  • Sales and pricing: sales@dgme-hotelpay.com
  • Technical questions: tech@dgme-hotelpay.com

DGME, Karel van Egmondstraat 133, 5913 CM Venlo, the Netherlands

© 2026 DGME
Product
Room chargesReception viewRooms and keysIntegrationsNFC readerPricingSecurityHotel dashboard
Teams
Front deskRestaurant and barRoom serviceFinanceManagement
Resources
SupportSetup guideHow it worksMewsVan Eijsink DishFAQ on pricingRequest a system
Company
ContactBook a demoSupportTermsPrivacySub-processorsSign in

Product news, once a month.

DGME, Karel van Egmondstraat 133, 5913 CM Venlo, the Netherlands

HotelPay