Hallostay Legal Documentation (Global)

This page provides Hallostay’s global legal framework: Privacy, Security, DPA, Sub-processors, SLA, AI Governance, Platform Terms and Master Terms (B2B SaaS).

Company Info Global Privacy Policy DPA (Annex) Sub-Processors Security (TOMs) SLA / Uptime AI Governance Platform Terms Master Terms (B2B)

Last updated: February 2026

Company Information

Company NameZosani Co., Ltd. (operating as “Hallostay”)
Registration Number0105566157610
Registered Address551/1 Moo 10, Nong Prue, Bang Lamung, Chonburi 20150, Thailand
Country of EstablishmentThailand
Business ActivitiesAI Development, Guest Communication Automation, Hospitality SaaS, Web Solutions
Capital4,500,000 THB
Registered Date15 August 2023
StatusActive
Global scope note: Hallostay provides services globally. Customers are responsible for local compliance (privacy, marketing, telecom, consumer rules), while Hallostay provides a security and data-processing framework designed to be broadly compatible with major global privacy regimes.

Global Privacy Policy

Effective Date: February 2026

This Global Privacy Policy explains how Hallostay (Zosani Co., Ltd.) collects, uses, shares, and protects Personal Data. Hallostay is a B2B hospitality SaaS platform. In most guest-related contexts, Hallostay processes Personal Data on behalf of its business customers (e.g., hotels, resorts, serviced apartments, brands, and management companies) as a Processor. In limited cases, Hallostay acts as a Controller, primarily for its own customer administration, billing, security, and website operations.

Key idea: If you are a hotel guest and you message a hotel using Hallostay, the hotel is typically the Controller and decides why/how your data is used. Hallostay supports the hotel as its Processor.
Global compliance: Hallostay is designed to support compliance with PDPA (Thailand) and GDPR principles, and to align with major privacy concepts found in laws such as CCPA/CPRA (California), LGPD (Brazil), POPIA (South Africa), and others, where applicable.

1. Definitions

2. Scope

This Policy applies to:

3. Categories of Data We Process

Hallostay processes different data categories depending on your role (guest vs. hotel staff vs. website visitor) and the modules enabled by the Customer.

Category Examples Primary Purpose Practical Explanation
Account & Admin Data (Controller) Name, work email, role, permission level, login events Account setup, access control, support, security Needed so the Customer can manage staff and maintain secure access.
Guest Communication Data (Processor) Messages, inquiries, attachments, timestamps, channel identifiers Deliver and automate guest conversations Processed under Customer instructions to respond and route service/booking needs.
Booking & Stay Data (Processor) Stay dates, room types, preferences, service requests Booking assistance, in-stay service delivery, upsells Only what the Customer collects or configures to run operations and guest experience.
Integration / OAuth Data Scoped tokens, page IDs, channel configuration, webhook events Connect and operate channels (Meta, LINE, email, web) Allows Hallostay to send/receive messages for the Customer’s authorized channels.
Technical & Security Logs IP address, device details, audit logs, error logs Security monitoring, debugging, fraud prevention Protects the platform and helps diagnose issues quickly.

4. Purposes of Processing

Hallostay processes Personal Data for purposes such as:

5. Legal Bases (Global Summary)

Depending on jurisdiction and context, processing may rely on contract necessity, legitimate interests, legal obligations, or consent. For guest communication processed as Processor, the Customer determines the lawful basis and provides necessary notices.

6. Sharing & Disclosure

Hallostay may share data only as needed to operate the Services:

7. International Transfers

Customer Data may be processed in multiple regions depending on hosting and Sub-processors. Where legally required, Hallostay supports recognized safeguards (e.g., SCCs/IDTA or similar mechanisms) and applies supplementary security measures as appropriate.

8. Data Retention

Data Type Default Retention Explanation
Customer Data (Processor) During contract + post-termination deletion window (typically up to 60 days) Allows export/migration; then delete/anonymize unless legally required.
Security & Audit Logs Up to 24 months Used for security, investigations, and forensic integrity.
Billing/Financial Records Up to 7 years (or as required by law) Required for tax/accounting compliance.

9. Rights of Individuals

Rights vary by jurisdiction (access, correction, deletion, portability, objection). For guest data, requests should generally be directed to the Customer (the Controller). Hallostay will assist the Customer where feasible as Processor.

10. Security

Hallostay implements security measures described in the Security (TOMs) section of this page and maintains processes for incident response.

11. Children’s Data

Hallostay is not intended for children. Customers must not knowingly collect or process children’s data through Hallostay where prohibited by law or without appropriate legal basis and safeguards.

12. Contact

Privacy contact: privacy@hallostay.app
General: hello@hallostay.app

If you are a guest and want to exercise rights related to a hotel’s processing, contact the hotel directly. Hallostay can assist the hotel as Processor.

Data Processing Agreement (DPA) – Annex

Effective Date: February 2026

Summary: This DPA is intended to satisfy GDPR Article 28 requirements and comparable processor obligations under PDPA and other global regimes. It applies when Hallostay processes Personal Data on behalf of a Customer.

1. Roles

2. Processing Details

Item Description Explanation
Subject matter Processing of Personal Data in Customer Data (messages, bookings, requests, metadata). Hallostay runs guest communication and service workflows.
Duration Agreement term + limited deletion/return window after termination. Allows export/migration before deletion.
Nature Hosting, transmitting, analyzing, and displaying data; automation execution; support. Normal SaaS operations + configured AI/automation.
Purpose Provide Services; security; troubleshooting; compliance obligations. Only what is necessary and proportionate.

3. Processor Obligations

Hallostay will:

4. Customer Obligations

Customer will:

5. Sub-Processors

Hallostay may appoint Sub-Processors. Hallostay will ensure Sub-Processors are bound by data protection obligations consistent with this DPA. Notification and objection rights are described in the Sub-Processor section.

6. International Transfers

Where transfers are restricted by law, Hallostay supports recognized safeguards such as SCCs/IDTA or comparable mechanisms, together with supplementary security measures where appropriate.

7. Audits

Upon reasonable request no more than once per year (unless a material incident occurs), Hallostay may provide available compliance evidence and/or permit an audit under confidentiality and non-disruption conditions with 30 days notice.

8. Deletion / Return

On termination, Hallostay will delete or anonymize Personal Data within a commercially reasonable timeframe (typically up to 60 days), unless retention is legally required or permitted (e.g., security logs, dispute defense, accounting).

For enterprise customers, SCCs/IDTA can be attached as a separate annex if required by procurement.

Sub-Processor Framework & List

Effective Date: February 2026

1. Purpose

Hallostay uses carefully selected vendors (“Sub-Processors”) to provide cloud infrastructure, observability, communications connectivity, and AI capabilities. This section explains (a) how Hallostay chooses Sub-Processors, (b) how changes are communicated, and (c) which Sub-Processors may be used.

2. Selection & Governance

3. Change Notifications & Objections

Hallostay will update the list below when introducing new Sub-Processors or materially changing processing. Where feasible, Hallostay will provide email or in-app notice. Customer may object within 30 days on reasonable data protection grounds.

If objection cannot be resolved, Hallostay may offer a reasonable alternative or allow termination of the affected module (if feasible).

4. Sub-Processor List (Template)

Important: Replace the placeholder vendors with your actual stack. Only list vendors you truly use. Keep it factual.
Vendor Category Purpose Data Potentially Processed Primary Processing Location(s)
[Primary Cloud / Hosting Provider] Infrastructure Compute, storage, networking, backups Customer Data, logs, metadata [e.g., Thailand / Singapore / EU / US]
[AI Model Provider] AI / NLP Generate responses, classification, intent extraction Conversation text (as configured), limited metadata [Region(s) per provider]
Meta Platforms Channel provider Facebook/Instagram messaging APIs Message content and metadata under Meta terms Global
LINE Corporation Channel provider LINE OA messaging API Message content and metadata under LINE terms Global
[Email Provider / Relay] Connectivity Email routing, SMTP/IMAP/API connectivity Email content/headers as configured [Region(s)]
[Monitoring / Observability] Security/Monitoring Performance monitoring and alerting Technical logs, metrics [Region(s)]

If you want, we can generate a separate subprocessors.html that mirrors this list and is easy to maintain.

Security (Technical & Organisational Measures – TOMs)

Effective Date: February 2026

Goal: Protect confidentiality, integrity, and availability of the Services and Customer Data. No security is perfect, but Hallostay aims for commercially reasonable controls aligned with global best practice.

1. Access Control

2. Encryption

3. Application Security

4. Logging, Monitoring & Detection

5. Backup & Recovery

6. Vulnerability Management

7. Incident Response

Hallostay maintains procedures for detecting, triaging, and responding to security incidents. For confirmed incidents affecting Customer Data, Hallostay will notify Customer without undue delay and provide reasonably available information.

SLA & Uptime Policy

Effective Date: February 2026

1. Availability Targets

Component Target Monthly Uptime Explanation
Core Web App / Dashboard 99.7% Platform is accessible and usable for core operations during the month (excluding permitted downtime).
API (where enabled) 99.5% API endpoints respond successfully (excluding Customer/third-party causes).
QR Guest Experience (where enabled) 99.7% Guest pages load and submit requests normally.

2. What is Excluded

3. Maintenance Windows

4. Support Response Targets

Severity Definition Initial Response Explanation
P1 Critical Core platform down / major outage 1 hour Immediate triage and continuous remediation work.
P2 High Major feature degraded; significant business impact 4 hours Priority fix with status updates.
P3 Medium Partial impact; workaround exists 24 hours Scheduled fix and clear tracking.
P4 Low Minor issue; cosmetic; requests 3 business days Handled via roadmap/backlog.

5. Service Credits (Optional – Enterprise)

Service credits may be offered in enterprise contracts. If not included in your Order, no credits apply by default.

AI Governance & Ethics Policy

Effective Date: February 2026

Important: AI outputs are probabilistic. Hallostay supports guest communication and workflows, but does not replace human responsibility. Customers must configure escalation rules and review critical outputs.

1. Principles

2. Mandatory Escalation (Human-in-the-loop)

AI must escalate to staff for:

3. Prohibited Uses

4. Monitoring & Quality Controls

Platform Terms (Operational Use Rules)

Effective Date: February 2026

1. Authorized Use

The platform is intended for hospitality businesses (hotels, resorts, serviced apartments, brands, and management groups). Only authorized Customer staff may access and configure the platform. Customer is responsible for staff actions.

2. Supported Channels & Permissions

Hallostay may support channels such as webchat widgets, LINE Official Accounts, Meta (Facebook/Instagram) business messaging, and connected email inboxes. Channel availability depends on third-party approvals and ongoing compliance with provider rules.

Where configured, Hallostay may request permissions and tokens such as: pages_messaging, pages_manage_metadata, pages_manage_engagement, instagram_manage_messages, and related permissions required by providers.

3. Customer Responsibilities

4. Service Changes

Hallostay may adjust integrations to comply with third-party API changes or legal requirements. Hallostay may suspend channels where misuse or policy violations are detected to protect the platform and other customers.

5. Intellectual Property

Hallostay retains all intellectual property in platform code, templates, flows, documentation and designs. Customer receives only a limited subscription right to use the Services during the active term.

6. Indemnity

Customer indemnifies Hallostay against claims, damages, fines, or costs arising from Customer’s unlawful use of the platform, violation of marketing/telecom laws, or breach of third-party channel policies.

Master Terms of Use (Global B2B SaaS)

Effective Date: February 2026

1. Agreement Structure

These Master Terms govern access to and use of Hallostay globally. The following sections are incorporated by reference and form part of the Agreement: Privacy Policy, DPA, Sub-Processor Framework, Security (TOMs), SLA/Uptime Policy, AI Governance, and Platform Terms. If there is a conflict, the Order Form or Statement of Work prevails over these Terms.

2. Subscription Term & Renewal

Unless otherwise agreed, subscriptions run for 12 months and renew automatically for successive 12-month terms. Non-renewal requires written notice in accordance with the Order Form (or, if not stated, no later than 30 days before term end).

3. Fees & Payment

Fees are defined in the Order Form. Fees are typically payable in advance and are non-refundable except where required by law or explicitly stated. Customer is responsible for taxes and withholding obligations where applicable.

4. Warranty Disclaimer

The Services are provided “as is” and “as available”. Hallostay does not guarantee uninterrupted operation or error-free service, and AI outputs may be inaccurate or incomplete. Customer remains responsible for verifying critical outcomes.

5. Limitation of Liability

To the maximum extent permitted by law, Hallostay is not liable for indirect or consequential damages. Hallostay’s total liability is capped at fees paid in the 12 months preceding the event giving rise to the claim.

6. Governing Law

Default: Thailand law and courts (replace with Singapore arbitration if you prefer global enterprise default).

7. Contact

General: hello@hallostay.app  |  Legal: legal@hallostay.app