Privacy Policy

1. Operator

“Shanhaidiandian POS” (山海點點 POS, the “Service”) is operated by Shanhaidiandian Technology Enterprise (山海點點科技企業社) (Tax ID: 61455610). For any questions about personal-data protection, contact admin@taiwan-cmo.com.

2. Data we collect

2.1 Data you provide

• Trial requests: shop name, phone or LINE, and the system you currently use.
• Account data: used to create and manage your account.
• Support correspondence: the content you send when contacting us.

2.2 Data generated automatically through use

• Login and operation logs, and usage statistics.
• Device and browser information, and approximate region.

2.3 Payment data

Payments are processed by Paddle acting as Merchant of Record. We do not store your full card number or complete payment credentials; we receive only the billing information necessary for our records (such as name, email, country/region, plan, and payment status). Paddle’s processing of the data it collects is governed by the Paddle Privacy Policy.

2.4 Your end customers’ personal data

Personal data belonging to your end customers that you (the merchant) input or generate through the Service (e.g., orders, reservations, contact details, LINE IDs) — for that data, you are the data controller and the Service is the processor, processing it only on your instructions and not for purposes beyond your authorization.

2.5 Categories of data we do not collect

The Service does not collect, solicit, or process any of the following:

• Payment card data: card numbers, expiry dates, security codes, or anything else subject to PCI DSS. Subscription payments are handled entirely by Paddle as Merchant of Record (see 2.3). The POS checkout feature only records which method was used to collect payment (cash, card terminal, mobile payment); it never touches card data.
• Biometric data: fingerprints, facial geometry, voiceprints, or similar.
• Government-issued personal identifiers: national ID numbers, passport numbers, social security numbers, or similar. A merchant’s business tax ID is company information, not a personal identifier.
• Access credentials and authentication secrets: API keys, one-time codes, or passwords. Account passwords are compared as hashes at login only, are never stored in a recoverable form, and are never passed through any API or AI tool parameter.

2.6 Dietary preferences (entered by the guest, may include allergies)

Where a merchant enables online reservations, a guest may enter their own dietary preferences, for example vegetarian, foods they do not eat, or ingredients the guest says they need to avoid (including ones they are allergic to). We handle this as follows:

• The guest chooses: the field is always optional, and leaving it blank does not affect the reservation.
• Strictly necessary: a restaurant needs to know which ingredients a guest must avoid, including ones they are allergic to, in order to serve food safely. The content is the guest’s own description; we do not ask for medical records or diagnoses and do not obtain any data from healthcare providers. Because it may relate to health, we handle it as sensitive data.
• Disclosed at the point of collection: the reservation form states, next to the field itself, that it is provided only to the restaurant (which may view it through its own management tools or AI assistant) and used solely to prepare food and arrange seating, in addition to this policy.
• Limited use: it is made available only to the restaurant the guest booked, used only to prepare food and arrange seating, and never used for any other purpose, for advertising, or for analytics.
• When the merchant uses an AI assistant: if the merchant looks up reservations through the AI assistant connector (ChatGPT, Claude), the reservation notes, including these preferences, are sent to the AI service provider the merchant has chosen, as part of that lookup (see sections 4 and 5).

3. How we use data

• To provide, operate, and improve the Service.
• Billing, subscription, and payment management (in cooperation with Paddle).
• Customer service and technical support.
• System security and anomaly detection.
• Compliance with legal obligations.

4. Third-party services

To provide the Service, we use the following third parties and share data only to the extent necessary:

• Paddle: payments and Merchant of Record (payment, billing, tax, invoicing, refunds).
• Cloud hosting and storage: system operation and data backup.
• ECPay (綠界科技): when a merchant enables reservation deposits or event payments, the guest pays directly on ECPay’s payment page. We receive only the payment status and never handle card numbers or account credentials. ECPay’s processing of the data it collects is governed by ECPay’s privacy policy.
• Email delivery services: sending notifications and billing emails.
• LINE notification services (if you enable the related features): sending reservation-related notifications.
• Google (if you authorize it): writing reservations to your own Google Calendar.
• Website analytics (if enabled): understanding site usage.

In addition, if a merchant connects the Service’s connector inside an AI assistant (see section 5), the data returned by its tools is sent to the AI service provider the merchant has chosen and is governed by that provider’s privacy policy:

• OpenAI (ChatGPT): OpenAI Privacy Policy.
• Anthropic (Claude): Anthropic Privacy Policy.

5. MCP connector (using the Service through Claude, ChatGPT, and other AI assistants)

The Service offers an official MCP (Model Context Protocol) connector that lets you operate your own POS and reservation system conversationally inside AI assistants such as Claude and ChatGPT (view/modify reservations, publish/unpublish menu items, open tables and send orders, view revenue). The connector is provided by us; the AI assistants (e.g., Anthropic’s Claude, OpenAI’s ChatGPT) are independent third-party clients that connect to it. For this connector, our data-handling principles are:

• It receives tool parameters only: the connector receives only the tool parameters you (or the AI assistant on your behalf) explicitly pass in — for example date ranges, item names, or reservation IDs — in order to call the Service’s API.
• It does not read the AI side’s content: the connector does not read, store, or access your conversations with the AI assistant, chat history, memory, conversation summaries, other files, or any data not required to execute the tool.
• Access is scoped to a single merchant: after OAuth 2.1 login, the connector can access only your own merchant (tenant) POS data and cannot access other merchants.
• Minimization and masking: tool-call request parameters are recorded only as a hash (sha256) for auditing, never in plaintext; responses containing customer names/phone numbers are masked by default and revealed only on explicit request.
• Token security: OAuth 2.1 with PKCE, dynamic client registration, and refresh-token rotation; the connector never holds your backend master secret — login only exchanges for an access token that belongs to you.
• No transactions of any kind: the connector has no checkout tool and cannot initiate a payment, apply a reservation deposit, or spend loyalty points — collecting payment is always done in the POS itself. If the merchant requires a deposit for a reservation, the connector declines to confirm that reservation; please confirm it in the POS. The connector sells no goods or services and never handles payment card data. Your subscription to the Service is purchased on our own website and handled by Paddle as Merchant of Record, entirely separately from the connector.
• No credentials collected: the connector has no tool for creating or modifying staff accounts. None of the connector’s tools accepts a password, API key, verification code, or any other credential as a parameter; sign-in happens only on our own login page.
• Returned data goes to the AI assistant you chose: tool results (for example a list of reservations and their notes) are returned to the AI assistant you connected and are processed by that provider under its privacy policy (see section 4). The connector itself does not store the data its tools return.

Retention periods for connector activity logs and sign-in tokens are set out in section 7. All other collection, use, retention, third-party sharing, and your rights are governed by the other sections of this policy. For setup instructions, see Using Shanhaidiandian POS in Claude.

6. International transfers

Some third-party providers (such as Paddle, and OpenAI or Anthropic when a merchant connects them) are located outside Taiwan, so some of your data may be transferred abroad for processing. We require partners to apply appropriate safeguards to the data they process.

7. Retention

• Account data: kept for the life of the account; after termination we delete or anonymize it within a reasonable period (except where law requires retention).
• Merchant operating data such as reservations, orders, and members: this data belongs to the merchant, who keeps and manages it for the life of the account and can edit or delete it at any time. After the service ends, it is deleted according to the merchant’s instructions.
• AI assistant connector activity logs: each time the connector (mcp.taiwan-cmo.com) runs a tool, it records the signed-in account’s email, the tool name, a hash of the parameters (the parameters themselves are not stored), the result status, the duration, and the source IP address, for security auditing. These logs are automatically deleted after 90 days. The connector does not store the data its tools return.
• Connector sign-in tokens: access tokens are valid for 1 hour and refresh tokens for 7 days. The tokens themselves are stored only as hashes; the POS sign-in credential the connector keeps on the merchant’s behalf is stored encrypted. All of this is automatically deleted when it expires. When the AI client revokes access, every token for that connection is deleted immediately; if access is never revoked, it lapses and is deleted when the refresh token expires (7 days).

8. Data security

We apply reasonable technical and organizational measures to protect data, including encryption in transit, access controls, and regular backups. However, no transmission or storage over the internet can be guaranteed absolutely secure.

9. Your rights

Under Taiwan’s Personal Data Protection Act, with respect to the personal data the Service holds about you, you may:

• Inquire about or request to review it.
• Request a copy.
• Request that it be supplemented or corrected.
• Request that we stop collecting, processing, or using it.
• Request deletion.

To exercise these rights, email admin@taiwan-cmo.com. If the data belongs to your end customers, the request should be made by the merchant acting as controller.

10. Cookies and analytics

This website may use cookies and analytics tools to maintain basic functionality and understand usage. You can manage cookies through your browser settings; disabling some cookies may affect site functionality.

11. Minors

The Service is not directed at minors. The reservation flow records only the number and ages of accompanying children, to arrange seating and food, and does not collect children’s names or any other personal data about them.

12. Changes to this policy

If this policy changes, we will post the update on this page and update the “Last updated” date.

13. Contact

For any questions about this policy, email admin@taiwan-cmo.com.