JOMORA

Privacy

Privacy notice

What we collect, what we refuse to collect, who else touches it, how long we keep it, and how to get it back.

Version 1.0 · 15 October 2026. This notice is issued under the Personal Data Protection Act 2010 (Malaysia).

Two different situations, and they have different answers. When you send us an enquiry through this website, we decide what happens to your details, so the obligations are ours. When a hotel runs JOMORA for its guests, the hotel decides what is collected and why — we hold that data on the hotel's instructions and nothing else. If you are a guest, the hotel's own privacy notice governs your stay, and this page tells you what our part of it does.

Who we are

ONTILUS TECHNOLOGIES SDN. BHD., registration 202601038570 (1700665-W), a company incorporated in Malaysia. JOMORA and JOMORA AI are our product names.

For privacy questions, access requests and complaints: hello@jomora.co. A person reads that mailbox; it is not a ticket queue.

What this website collects

One form, on the briefing request at the bottom of the home page:

All of it is voluntary, and the only consequence of leaving a field out is that we may not be able to answer you. We use it to respond to your enquiry and to follow up on it. We do not add you to a mailing list, we do not sell it, and we do not share it with anyone outside the processors named below.

No cookies, no analytics, no tracking

This website sets no cookies, stores nothing on your device, and runs no analytics of any kind — no Google Analytics, no advertising pixel, no session recording. We genuinely cannot tell you visited.

The one exception worth naming: the page loads its two typefaces from Google Fonts, and your browser's request to Google reveals your IP address to Google in the ordinary way any web request does. Nothing identifying is sent with it by us.

What JOMORA collects inside a hotel

On a hotel's instructions, the product holds:

GuestName, room number, stay dates, the language they chose, the requests and messages they send, the replies they receive, anything a hotel's team notes against the stay, a check-in signature where the hotel uses that flow, and the outstanding balance on the room.
PreferencesWhat a guest tells the hotel they want remembered — a dietary requirement, an allergy, a room preference, a usual order.
Hotel staffName, work email, role, department, and a record of actions taken in the console, including who opened a room.

What we refuse to collect, and why it is more than a promise

JOMORA holds no passport, no identity card or NRIC number, no date of birth, and no card number, expiry or CVV. Identity and payment capture stay with the hotel's own property-management system and its payment gateway, which is where they belong.

That is enforced below the application, not in a policy document: the database carries a check that rejects the creation of any column whose name matches that class of data. A developer cannot add a passport field to this product by accident, and the check is run against the live schema as part of our routine audit.

Allergies and dietary needs are health information. Under the PDPA that is sensitive personal data, and it is only ever recorded because a guest chose to tell the hotel, for the single purpose of getting their request right. It is used to serve them — to flag a kitchen order, or to ask before an order is placed. It is never used to profile anyone, never shared with anyone outside the hotel and the processors below, and a guest can have it removed at any time by asking the hotel or us.

Artificial intelligence, stated plainly

JOMORA answers guests and translates between languages using a third-party AI language model. This is the part of the product most people do not think to ask about, so here it is without hedging.

What is sent out: the text of the conversation, the guest's first name, their room number, and the property's own published facts and menu. What is not sent: contact details, folio or payment information, and the categories listed above as never collected.

A guest's message is sent as written. If a guest types an allergy into the chat, that sentence goes to the AI provider along with the rest of the message, because translating and acting on it is the point. The providers are Anthropic PBC and Google LLC, both in the United States, and which one handles a given deployment depends on how the hotel's instance is configured. We will tell any hotel which one theirs uses.

The model is given the property's facts and instructed to work only from them. It is not given access to the guest database, it cannot look up another guest, and it does not decide anything on its own that a staff member does not see on the board.

Who else processes it

Supabase
Database and application hosting. Guest data for our Malaysian hotels is hosted in Singapore.
Vercel
Hosting for this website and for the application's front end.
Resend
Delivers the email containing your website enquiry to us.
Anthropic PBC and Google LLC
The AI language model described above.
ElevenLabs
Speech, and only where a hotel has switched on the spoken host. Where it is off, no audio leaves the device, because none is captured.

Each is engaged to do a defined job and is not permitted to use the data for its own purposes.

Data leaving Malaysia

Some of the above means your data is processed outside Malaysia — Singapore for storage, the United States for the AI and email providers. We tell you because you are entitled to know, and because a hotel's own privacy notice needs to say the same thing.

How long we keep it

Identity documents and payment identifiers
Not held at all today. If document capture is ever introduced, the commitment is already set: a scan or image is purged on the day the guest checks out, not retained for a review period.
Guest preference profile
Kept between stays, on purpose. Remembering that a guest cannot eat peanuts is the reason the feature exists, and a profile deleted at checkout would have to be collected again every visit. It is kept until the guest or the hotel asks for it to be removed.
Requests, messages and stay records
Kept while the hotel uses JOMORA, as its operating record of what was asked for and what was done. The hotel sets its own period and can have any stay erased.
Room access and staff audit records
Kept for 12 months. These exist to answer "who opened that door", which is a security question, so they outlive the stay.
Website enquiries
Kept for 24 months from your last contact with us, then deleted.

Your rights

Under the PDPA you may ask us to:

Email hello@jomora.co and we will answer within 21 days. If you are a hotel guest, the fastest route is the hotel itself, because the hotel decides; if you come to us, we will act on the hotel's instruction and tell you we have done so. There is no fee.

How it is protected

We do not claim a certification we do not hold. JOMORA is not SOC 2, ISO 27001 or PCI DSS certified, and anyone who tells you otherwise is guessing. We are happy to walk a hotel's IT lead through the architecture instead.

Children

JOMORA is for hotel guests and hotel staff and is not directed at children. Where a child is named on a booking, we hold nothing beyond the number of children on the reservation, which the hotel needs to prepare the room.

Changes

If this notice changes in a way that affects what we collect or who we send it to, we will change the version and date at the top, and tell any hotel using JOMORA directly rather than relying on them to re-read the page.

Complaints

Come to us first at hello@jomora.co. If we do not resolve it, you can complain to the Personal Data Protection Department (JPDP), Ministry of Digital, Malaysia.