Privacy policy

Last updated 13/10/2026

Liwan is a system hotels and residential buildings use to run their reservations — the rooms, the guests, the cleaning and the money. This page says what the Liwan app on a phone collects, who can see it, and why.

Each property runs Liwan on its own server. The information in it belongs to that property and stays there. The app asks which server it belongs to the first time it is opened, and talks to that one only — it does not send anything to us, and we hold no copy of any property's guests, bookings or payments.

Who the app is for

Staff, not guests. Everyone using it has an account their employer created for them, and signs in with it. There is no way to register, and nothing in the app is open to the public.

What is held about the person using the app

Their account — the username and name their employer gave them, their telephone number if it was entered, and what the system allows them to do.
A notification address for the phone, issued by Google so that messages can reach it. It identifies the phone, not the person, and is replaced whenever the app is reinstalled.
A record of what they did — which booking they changed, what money they took, when they signed in. A hotel has to be able to answer “who did this”, and this is the answer.
A sign-in cookie, so that signing in lasts.

What is held about guests

This is the property's own record of its guests, entered by its staff: name, nationality, identity or passport number, telephone, email, address, date of birth, the stays they booked, what they paid, and any photographs attached to a booking or a repair. It is kept so the property can run the stay, issue the bill, and meet whatever its own country requires of it.

The property decides what is collected, how long it is kept, and who may see it. A guest with a question about their own information should ask the property they stayed at.

What the app asks the phone for

Notifications, so a request or a repair reaches somebody who is not looking at the screen. Refusing is allowed; the rest still works.
The camera or the gallery, only at the moment somebody chooses to attach a photograph. The app holds no camera permission of its own: the phone's own picker opens, and only the picture that is chosen is sent.

It asks for nothing else. No location, no contacts, no microphone, no files beyond the one attached.

What the app does not do

No advertising, and nothing is sold or passed to anybody for marketing.
No analytics, no tracking, and no third-party measurement of any kind.
No profile built from behaviour, and no automated decision made about anybody.

The one outside service

Notifications are delivered through Google's Firebase Cloud Messaging, because a phone with the app closed can only be reached that way. Google therefore handles the phone's notification address and the text of the notification itself, which says what happened and never carries a guest's identity document or payment details.

How it is protected

Everything travels over an encrypted connection. The app refuses to open anything that is not.
Passwords are stored as one-way hashes. Nobody, including us, can read one.
Each property's data is in a database of its own, reachable only by that property's system.
What a person can see is decided by the role their employer gave them.

Removing it

Uninstalling the app ends the notifications and removes everything it kept on the phone. The property's own records stay with the property, which is the only party that can change or delete them.

Asking about this

About your own information: ask the property you stayed at or work for — they hold it and they decide about it.

About the software itself: hanyfaris76@gmail.com