Privacy

Privacy Notice

Jongi handles operational data for service businesses. This notice explains the categories of data we process during the MVP beta and the controls beta salons should expect.

Last updated: June 9, 2026

1. Data we collect

Salon workspace data: organization name, settings, timezone, currency, public booking slug and token, services, staff, schedules, roles, and access settings.

Customer data: names, phone numbers, email addresses, LINE identifiers when connected, notes, visit history, appointments, cancellation and reschedule activity.

Finance data: paid payments, refunds, void corrections, expenses, payment methods, finance summaries, and audit reasons.

Operational data: notification logs, reminder jobs, public booking attempts, rate-limit events, support chat messages, and technical logs needed to run the service.

2. How we use data

We use data to provide booking, calendar, CRM, reminders, finance tracking, support, security, abuse prevention, troubleshooting, and product improvement.

We do not sell customer lists or salon operational records.

3. Public booking and LINE

Public booking is unauthenticated and protected by salon slug, booking token, appointment access tokens, backend availability checks, and rate limits.

LINE-related data is used to support booking identity, confirmations, reminders, postbacks, and customer communication where the integration is configured.

4. Email, reminders, and providers

When email is configured, Jongi can send confirmations and reminders through the configured email provider.

Notification failures are handled as best effort so core booking data can remain committed even when a provider fails.

5. AI support

When AI support is enabled, Jongi may use support messages and limited tenant-safe context to answer operational questions.

The support flow is designed to redact common personal and secret-like values before sending messages to the AI provider, and requests are configured not to store provider-side conversation data where supported.

6. Access and security

Jongi uses authentication, organization-scoped tenant checks, role-based access, public booking tokens, appointment access tokens, webhook signature checks, and operational rate limits.

Salon owners and admins are responsible for inviting the right team members and removing access when people leave.

7. Retention, export, and deletion

During beta, we keep operational data while the workspace is active and as needed for support, security, backups, and legal obligations.

A salon can request export or deletion of workspace data where technically and legally possible. Some backup copies may remain for a limited period until normal backup rotation removes them.

8. International processing

Jongi is built for service businesses in Thailand, but infrastructure and service providers may process data in other countries depending on the configured hosting, database, email, LINE, and AI services.

Beta salons should avoid entering unnecessary sensitive data into free-text notes.

Privacy questions or deletion/export requests: hello@jongi.app.

Read the terms