Privacy Policy
Last updated 5 October 2026
This policy explains what personal data GuestFly handles for hotels, their teams and their guests, why, who receives it, how long it is kept, and what rights people have. We have tried to write it plainly.
- Publisher
- ARQEMUS LIMITED
- Legal form
- a limited company registered in Hong Kong
- Contact
- contact@arqemus.com
1. Who we are, and in which role
GuestFly is a web service published by ARQEMUS LIMITED, a limited company registered in Hong Kong ("GuestFly", "we", "us"). It lets independent hotels receive and handle guest requests, sell services, and communicate with their guests.
The law gives different duties depending on the role we play, so this policy separates two situations:
- Hotel accounts, staff, visitors and prospects. We decide why and how this personal data is used. We are the controller (the "data controller").
- Guests of a hotel. The hotel decides why and how its guests' data is used: the hotel is the controller and GuestFly is its processor, acting on the hotel's instructions under the data processing terms in our Terms of Service. A guest who wants to exercise a right should first write to the hotel they stayed at; we help the hotel answer.
Where the law requires us to have a representative in the European Union or the United Kingdom, it is named on this page.
2. The personal data we handle
Hotel owners, managers and staff (we are the controller):
- Identity and access: name, work email, role, hotel membership, password (stored only as a salted hash by our authentication provider), two-factor sign-in status.
- Account and billing: the hotel's name, address and plan; subscription and invoice records. Card details are collected and kept by Stripe, never by GuestFly; we receive the card brand, the last four digits, the billing country and the payment status.
- Use of the product: actions recorded in the audit trail (who changed what, and when), support requests you send us, the progress of the guided tour, and technical logs.
Guests (the hotel is the controller, we are the processor):
- What the hotel or the guest enters: name, email address or phone number when the hotel provides them, language, arrival and departure dates, room or unit.
- What the guest sends through the concierge: messages, requests, answers to booking questions, service orders, ratings and comments.
- What the product derives: the category and urgency of a request, a short summary, and an indication of the guest's mood that helps staff react. These are aids for staff, and no decision with legal or similarly significant effect is taken about a guest by automated means.
- Operational records: payment status (paid, refunded, disputed), emails sent to the guest and whether they were delivered, unsubscribe choices. A blind copy of each email sent to a guest through GuestFly is delivered to a GuestFly mailbox, so that we can monitor delivery, see the replies the hotel gets and support the hotel.
Visitors and prospects: what you write in the contact form (name, email, hotel, message), and a keyed hash of your IP address kept to prevent abuse. If you then create an account, the source that brought you (for example a search engine, a link or a campaign tag) and the first page you saw, kept through two small cookies described in our Cookie Policy, are saved with your hotel so we can measure which sources work. We do not set them when your browser asks not to be tracked. Our servers also record technical data such as IP address, browser type and the pages requested, for security and reliability.
We do not knowingly collect special categories of personal data (health, religion and so on). Hotels must not ask guests to send them through the concierge, and a guest should not.
3. Why we use it, and on what legal basis
- To provide the service we have agreed to provide (account, concierge, requests, sales, emails, billing). Basis: performance of a contract, or steps taken before a contract at your request.
- To understand which sources bring the hotels that use GuestFly and how long it takes a hotel to get value from the product (activation, first guest, first sale). Basis: our legitimate interest in improving and growing the service, using the source labels and the milestones of the account, never guests' messages.
- To secure the service, prevent fraud and abuse, keep audit trails, and fix faults. Basis: our legitimate interest in running a safe and reliable service.
- To answer your messages and give support. Basis: contract or legitimate interest.
- To invoice, collect payment, account for tax and meet legal duties. Basis: legal obligation and contract.
- To send service messages (confirmations, security, billing). Basis: contract. We send marketing about GuestFly to a business contact only where the law allows it or with consent, and every such message can be refused.
- Where we rely on consent, you can withdraw it at any time, without affecting what was done before.
For guest data, the legal basis is decided by the hotel (usually the performance of the guest's stay and the hotel's legitimate interest in serving its guests). We process it only to provide GuestFly to that hotel.
4. Artificial intelligence
The guest concierge uses an AI model to understand a guest's message, to reply, and to prepare a request for staff. Some analytics for hotels also use AI.
- What is sent: the text needed to understand the request, the hotel's own information (opening hours, services, prices), and limited stay context. We do not send payment card details.
- Who processes it: OpenAI, as our processor, under its business API terms, which at the time of writing state that data sent through the API is not used to train its models. We review those terms regularly.
- Guests are told they are talking to an AI concierge. The AI can be wrong, and staff remain responsible for what the hotel promises.
- Guests and hotels can ask for a human: every request can be handled by the hotel's team, and the AI can be switched off for a hotel.
- We use AI usage records (tokens, cost, model) to run and bill the service. We do not use the content of hotel or guest conversations to train our own or third-party models.
6. International transfers
ARQEMUS LIMITED is established in Hong Kong, and some providers are in the United States. Data therefore leaves the European Economic Area, the United Kingdom and other regions with transfer rules.
Where the law requires a safeguard, we use the standard contractual clauses approved by the European Commission (and the UK addendum), or another valid mechanism such as an adequacy decision, and we add technical measures: encryption in transit and at rest, access limited by role and by hotel, and minimal data sent to AI and email providers. You may ask us for a copy of the safeguards in place.
7. How long we keep it
- Hotel and staff account data: while the account exists. After the account is closed we delete or anonymise it within 90 days, except what we must keep.
- Guest data: for as long as the hotel keeps its workspace open, since the hotel decides. The hotel can ask us to delete a guest's data, and we do it within 30 days of a documented request.
- Billing and accounting records: for the period the law requires (seven years under Hong Kong accounting rules).
- Audit trail, security and error logs: up to 24 months.
- Support and contact messages: up to 36 months after the last exchange.
- The blind copies of emails sent to guests, and replies that reach our mailbox: up to 90 days.
- Private guest links expire after 21 days by default, and the link itself is stored only as an irreversible hash.
- Encrypted backups: kept on a rolling schedule of up to 12 months, after which deleted data disappears from them too.
8. How we protect it
- Each hotel's data is isolated at database level: one hotel cannot read another's.
- Connections are encrypted (HTTPS with HSTS). Backups are encrypted before leaving our server and stored away from the database host.
- Staff of GuestFly who can see the back office must use two-factor sign-in, a role that limits what they can do, and every action they take is written to an audit trail that cannot be edited. They see counts and amounts, not guests' names or messages.
- Hotels can require two-factor sign-in for their own team.
- Secrets (service keys, API keys) stay on the server and are never sent to the browser.
If a personal data breach is likely to put people at risk, we notify the affected hotels without undue delay and in any case within 72 hours of becoming aware, and the competent authority where we are the controller.
9. Your rights
Depending on where you live, you may have the right to access your data, correct it, delete it, restrict or object to its use, receive it in a portable format, and withdraw consent. This follows, among others, the GDPR and the UK GDPR, the Hong Kong Personal Data (Privacy) Ordinance, Turkey's Law No. 6698 (KVKK), Morocco's Law 09-08 and Algeria's Law 18-07.
To use a right, write to contact@arqemus.com. We may need to confirm who you are. We answer within one month (30 days), extended where the law allows for complex requests, and we do not charge unless a request is manifestly excessive.
If you are a guest, please start with the hotel you stayed at: it is the controller and can act fastest. If you write to us, we pass your request to the hotel and tell you.
You may complain to your data protection authority (for example the CNIL in France, the ICO in the United Kingdom, or the Office of the Privacy Commissioner for Personal Data in Hong Kong). We would welcome the chance to answer first.
10. Children
GuestFly is a business service for hotels. It is not aimed at children, and we do not knowingly collect their data. A hotel remains responsible for what it asks of its guests, including minors travelling with their family.
12. Changes to this policy
We update this policy when our practices or the law change. The date at the top shows the latest version. If a change is important for you (a new sub-processor, a new purpose), we tell hotels in advance by email or in the product.
13. Contact
Privacy questions and requests: contact@arqemus.com.
Publisher: ARQEMUS LIMITED.