Privacy Policy

Last updated: November 12, 2026

Effective date: November 12, 2026

This is the privacy policy of Messaging, the guest messaging application for hotels at messaging.vivifiedtech.com. Messaging is developed and operated by Vivified Tech (“we”, “us”).

This policy explains what personal data we handle when you use Messaging (the “Service”), why we handle it, how we protect it, who we share it with, how long we keep it, and what choices you have. Section 3 covers the data we receive from Google when you sign in with your Google Account.

1. Who this policy covers

The Service is used by two groups of people.

  • Hotel users. People who sign in to the Service for a hotel: owners, managers and staff.
  • Guests. People who write to a hotel on a messaging channel, or who leave a public review, where the hotel has connected that channel to the Service.

For hotel users’ account data, we decide how the data is used, so we are the data controller.

For guest data, the hotel decides why and how the data is used. The hotel is the data controller and we process the data for the hotel as its data processor. If you are a guest and you have a question or a request about your data, contact the hotel first. We help the hotel answer.

2. Data we handle

Hotel users

  • Account data: name, email address and your role in the hotel’s workspace. The Service has no passwords: you sign in with a link sent to your email address or with Google.
  • Sign-in with Google: if you choose it, Google gives us your email address and confirms that it is verified. We use it only to create your account and sign you in. We ask for no other Google data, and we do not share or sell this data.
  • Usage records: sign-in sessions, IP address, browser type, and a record of important actions in a workspace, such as inviting a member or connecting a channel.
  • Billing data: when a paid plan applies, our payment provider handles the payment. We receive the plan, the payment status and invoice details. We do not receive or store card numbers.

Hotels

  • Hotel details: the hotel’s name, address, contact details, rooms, photos, policies and booking link, entered by the hotel or read from the hotel’s own public website when the hotel asks us to.
  • Connection credentials: the keys a hotel gives us to connect its messaging channels and its property management system. We store them encrypted.

Guests

  • Profile data from the channel: the display name, profile picture and account identifier that the channel shares. Some channels also share a phone number.
  • Messages: the text, photos and files a guest and the hotel send to each other, with delivery and read status and reactions.
  • Stay details: dates and number of guests that a guest mentions in a chat.
  • Reviews: public reviews of the hotel on connected review platforms, with the reviewer name and rating as the platform shows them.

We do not ask guests for payment card data in chat, and the Service does not process guest payments.

3. Google user data

Messaging lets you sign in with your Google Account (“Continue with Google”). This section states all the Google user data that Messaging accesses, and how Messaging uses, stores, protects, shares, keeps and deletes it. It applies to every person who signs in with Google.

Data accessed

Our application accesses the following Google user data. When you choose “Continue with Google”, Messaging asks Google for one permission (the userinfo.email scope) and accesses only:

  • the email address of your Google Account;
  • whether Google has verified that email address.

Messaging does not access any other Google user data. It does not access your name, your profile picture, your contacts, or any data in Gmail, Google Calendar, Google Drive or any other Google product.

Data usage

We use your Google user data only to provide the service you asked for, which is signing in to Messaging. Messaging uses the Google user data listed above only to provide the sign-in feature that you see and use:

  • to create your Messaging account the first time you sign in;
  • to recognise you and sign you in on later visits;
  • to check that you are allowed to join a hotel’s workspace, which is by invitation;
  • to send you service email at that address, such as workspace invitations and security notices;
  • to fill in the billing email on the checkout page when a workspace owner starts a paid plan.

We do not sell your Google user data to anyone. Messaging does not use Google user data for advertising, for marketing, for profiling, or to build a database of users. Messaging does not use Google user data to develop, improve or train generalized or non-personalized artificial intelligence or machine learning models. Google user data is never sent to an AI model. Messaging does not use Google user data to decide credit-worthiness or for lending.

Data storage and protection

Security procedures are in place to protect the confidentiality of your Google user data, and we use encryption to protect it.

  • Messaging stores your Google Account email address in its database as your account email. The database is in a data centre in Singapore.
  • Messaging does not store the Google access token after sign-in is complete, and it does not request or store a refresh token.
  • The connection between your browser and Messaging is encrypted with TLS. The database is encrypted at rest and is not reachable from the public internet.
  • Only the staff of Vivified Tech who operate the Service can access the database. No person reads your Google user data unless you ask us for help with your account, it is needed for security (for example, to investigate abuse), or the law requires it.
  • Each hotel’s data is kept separate from every other hotel’s data.

Data sharing, transfer and disclosure

We do not transfer or disclose your Google user data to third parties for purposes other than the ones described in this section. Messaging does not sell Google user data and does not transfer or disclose it to third parties, except in these cases:

  • The members of your hotel’s workspace see your email address in the list of members.
  • Our email delivery provider receives your email address so that it can deliver service email to you. It acts for us under contract and may not use the address for anything else.
  • Our hosting provider stores the database for us under contract.
  • Our payment provider receives your email address only if you start a paid plan, so that it can send the receipt and invoice. It acts for us under contract.
  • A successor, if our business is merged, acquired or sold, and only after we ask for your explicit consent first.
  • Authorities, when the law requires us to disclose it.

Messaging does not transfer Google user data to advertising platforms, data brokers or information resellers, and does not transfer it to anyone for training AI or machine learning models.

Data retention and deletion

  • We retain your Google Account email address only for as long as your Messaging account exists. When you delete your account, or when you ask us to delete your data, we delete it.
  • You can delete your account at any time in Settings. You may also request for your data to be deleted by writing to hello@vivifiedtech.com. When the account is deleted, the email address is deleted from the live database. Backups that contain it expire within 30 days.
  • You can remove Messaging’s access to your Google Account at any time in your Google Account, under “Third-party apps and services”. After that, Messaging can no longer sign you in with Google.

Limited Use

Messaging’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. All people who work for us, and any successor, must follow these rules.

If we want to use Google user data in a new way or for a new purpose, we first update this policy, tell you, and ask for your consent before the new use starts.

4. How we use the data

  • To provide the Service: show conversations to the hotel’s team, send the hotel’s replies, and keep a record of each chat.
  • To answer guests automatically when the hotel turns the assistant on. The assistant chooses from answers the hotel has stored. Automated tools read the guest’s message to choose the right stored answer and to find dates and guest numbers.
  • To draft replies to reviews for the hotel’s team to check and send.
  • To keep accounts secure, prevent abuse, and find and fix faults.
  • To send service email, such as sign-in links, invitations and security notices.
  • To meet legal duties.

We do not sell personal data. We do not use guest messages for advertising. We do not use guest messages to train our own AI models.

Where the law asks for a legal basis, we rely on these:

  • Contract: to provide the Service to the hotel and its users.
  • Legitimate interests: to keep the Service secure and reliable.
  • Legal obligation: where a law requires us to keep or disclose data.
  • Consent: where we ask for it. You can withdraw consent at any time.

The hotel is responsible for its own legal basis for writing to guests.

6. Who we share data with

We share personal data only with:

  • The hotel’s team. Members of a workspace see that hotel’s conversations and guest data. Data of one hotel is never shown to another hotel.
  • Messaging channels and review platforms. When the hotel replies, the message goes to the channel the guest used.
  • Service providers that work for us under contract: cloud hosting and storage, message delivery, email delivery, AI processing, error monitoring and payment handling. They may use the data only to provide their service to us. You can ask us for the current list.
  • Authorities, when the law requires it.
  • A successor, if our business is merged or sold. This policy continues to apply to the data. For Google user data, we ask for your consent first, as Section 3 states.

Section 3 is the full list of who receives Google user data. Google user data is not sent to the AI processing providers.

7. Where data is stored

We store the Service’s database and files in data centres in Singapore. Some service providers process data in other countries. When data moves across borders, we use the safeguards that the applicable law requires.

8. How long we keep data

  • Account data: while the account exists. After you delete your account we delete or anonymise the data, except records we must keep by law.
  • Hotel and guest data: while the hotel uses the Service. When a hotel closes its workspace, or asks us to delete data, we delete it from the live systems. Backups expire within 30 days after that.
  • Security logs: for a limited period, to investigate incidents.

A hotel can remove a message from its record in the Service. This does not delete the message on the guest’s own device or on the channel.

9. Security

We use encryption in transit, encrypted storage of connection credentials, separation of each hotel’s data, access controls for our own staff, and backups. No system is fully secure. If a breach affects your data, we tell the people and authorities that the law requires us to tell.

10. Your rights

Depending on where you live, you may have the right to access, correct, delete or receive a copy of your data, to object to or restrict its use, and to complain to your data protection authority. These rights come from laws such as Thailand’s Personal Data Protection Act and the EU General Data Protection Regulation, where they apply.

  • Hotel users: change your name and email, or delete your account, in Settings. For other requests, write to us.
  • Guests: contact the hotel you wrote to. If you write to us, we pass the request to the hotel and help it respond.

11. Children

The Service is for businesses. It is not directed at children, and we do not knowingly collect account data from anyone under 18.

12. Changes to this policy

We may update this policy. We change the effective date above when we do, and we tell hotel users by email or in the Service when a change is important.

13. Contact

Vivified Tech
Email: hello@vivifiedtech.com

See also our Terms of Service and Cookie Policy.