Baca dalam Bahasa Malaysia

Privacy Policy

Last updated: 1 November 2026

1. Who we are

Inchat ("Inchat", "we", "us") is an omnichannel conversational AI platform that helps merchants manage and reply to customer conversations across WhatsApp, Facebook Messenger, Instagram, Telegram, and their own website chat widget. This policy explains what personal data we process, why, and the choices available to you.

It applies to merchants who create an Inchat workspace ("Merchants") and to their customers whose messages flow through the platform ("End Customers"). We process End Customer data on behalf of the Merchant who owns the connected channel.

2. Data we collect

We collect only what is needed to run the service:

  • Account data — Merchant name, email address or phone number, and workspace settings when you sign up.
  • Messaging data — message content (text, images, voice notes, files), timestamps, delivery/read status, and platform-scoped sender identifiers (e.g. WhatsApp phone number or username ID and profile name, Messenger PSID, Instagram-scoped ID) received from the channels the Merchant has connected.
  • Attribution data — ad and referral identifiers a platform attaches to a conversation (e.g. ad ID, click ID) so Merchants can attribute conversations to campaigns.
  • Knowledge base content — documents a Merchant uploads to ground AI replies.
  • Billing data — subscription status and usage counts. Card details are handled by Stripe and never touch our servers.
  • Technical data — logs necessary for security and reliability (e.g. webhook delivery records, IP address at sign-in for bot protection).
  • Product usage — in the signed-in app only, we use PostHog to see whether a Merchant's workspace signs up, starts a trial, becomes a paid plan, and has had an AI reply sent. The public website, the chat widget, public forms and booking pages do not load it. We send the account's user id, the workspace id and plan, and the kind of channel an AI reply went out on (for example WhatsApp). We do not send the account email, the workspace name, any person's name, message content, or the page address, and never an End Customer's phone number. Session recording is off and typed input is masked. Nothing is sent when PostHog is not configured.
  • Website visit data — on our public website (the marketing, help and blog pages; not the app you sign in to) we measure visits with two tools. Vercel Web Analytics counts page views without a cookie: the page address, the referring site, and the country, device and browser type of the visit. Google Analytics measures the same pages and sets first-party cookies (named _ga and _ga_RMMDBP6SYZ, kept for up to two years) so it can tell a returning visitor from a new one. It records the page address, the referring site, approximate location, device and browser, and how the visitor moved through the site: pages viewed, scrolling, embedded videos played, and the address of links clicked to other sites and of files downloaded. Of the page address, and of a referring page on our own website, only the path and campaign tags (utm_) are sent; a referring page anywhere else is reduced to its site name. When a browser that carries these cookies creates its first workspace, our server tells Google Analytics that a sign-up happened, with the visitor and visit IDs from those cookies and nothing else — no name, e-mail address or phone number — so we can see which sources bring sign-ups. Google deletes visit-level data after two months, and data tied to a visitor's cookie 14 months after their last visit; aggregated reports are kept. Google signals are turned off, and the Google Analytics tag does not run in the app. For visitors in the European Economic Area, the United Kingdom and Switzerland, it runs without cookies. You can block or delete these cookies in your browser, or install Google's opt-out add-on (tools.google.com/dlpage/gaoptout).
  • Advertising data — to measure and improve our own advertising, our public website also uses the Meta Pixel and, once we enable them, the OpenAI (ChatGPT Ads) pixel and the Google Ads tag. They set advertising cookies (Meta: _fbp and _fbc, kept for up to 90 days; OpenAI: __oppref for 30 days and __obref for up to a year; Google Ads: _gcl_au for 90 days) and send Meta, OpenAI and Google the address of the page, the referring page, device and browser information, and the identifier of the ad that was clicked. These browser tags run only on pages whose address carries nothing but campaign tags and ad-click identifiers, never in the app, and not at all for visitors in the European Economic Area, the United Kingdom and Switzerland. The OpenAI pixel may read contact details typed into forms on those pages and send them hashed. When someone who visited our public website from outside those regions creates their first workspace, our server tells Meta and, once enabled, OpenAI that a sign-up happened, together with those cookie identifiers, the IP address and browser type of the request, and the account's e-mail address and phone number hashed with SHA-256 — never in readable form — so they can match it to an ad they showed. You can block or delete these cookies in your browser and manage your ad preferences in your Meta, Google and OpenAI accounts.

3. How we use data

We use the data above solely to provide the service:

  • Displaying conversations in the Merchant's inbox and tracking response states.
  • Generating AI-assisted replies, reading images customers send (for example payment slips), and transcribing voice notes. How each of these reaches an AI provider is set out in section 6. Customer conversations are not used to train AI models.
  • Reporting conversation analytics (volumes, response times, AI deflection) to the Merchant who owns the data.
  • Sending conversion signals to Meta's Conversions API only where the Merchant has enabled ad attribution for their own ad account.
  • Billing, fraud prevention, and service integrity.
  • Measuring and improving Inchat's own advertising on Meta, ChatGPT and Google, using data about visits to our public website and the hashed contact details of people who sign up (see section 2) — never End Customer data.
  • Measuring how Merchants move from sign-up to a paid plan, as described in section 2. This sends the account user id and the workspace id, plus the plan and the channel type of an AI reply — never an email address, a name, a page address, End Customer message content, or a phone number.
  • We do not sell personal data, and we do not use End Customer data for advertising of our own.

4. Data from Meta platforms

Data received through Meta's APIs (Messenger, Instagram, WhatsApp Cloud API) is used only to provide messaging functionality to the workspace that owns the connected Page, Instagram account, or WhatsApp Business Account, in accordance with Meta's Platform Terms and Developer Policies. Access tokens are stored as encrypted references, never in plain text. We request only the permissions required for the features a Merchant enables.

5. Data from Google APIs (Limited Use)

Google Calendar is an optional appointment-booking integration that is not yet generally available. When a Merchant connects it, Inchat accesses only free/busy time ranges — so the Merchant's booking page never offers a slot that clashes with an existing commitment — and creates or updates calendar events that mirror appointments booked through the Merchant's Inchat booking page. We never read event titles, descriptions, attendees, or any other calendar content.

Google Sheets is an optional workflow integration. When a Merchant connects a Google account, Inchat reads that account's e-mail address to show which account is connected. When the Merchant pastes a spreadsheet link into an "Add Google Sheets Row" workflow step, Inchat reads that spreadsheet's title, its tab names and the first (header) row of the chosen tab, so the Merchant can map columns; when the workflow runs, Inchat appends one new row containing the values the Merchant mapped. If the Merchant chooses to update a contact's existing row instead — in the workflow step, or in the AI Agent's "Sync to Google Sheets / Notion" action — Inchat also reads the one column the Merchant picked to find that row (for example the phone number column), and writes the mapped values into that row's cells. For these row-writing actions, Inchat does not read any other cells, does not list or open other files in the Merchant's Google account, and never deletes rows. Only spreadsheets the Merchant names in a workflow step or an AI Agent action are touched.

When a Merchant selects Google Sheets as the source for customer purchase records, Inchat reads the named worksheet on demand, using only the mapped columns to find purchases by the contact’s phone or an operator-confirmed buying phone or order link. Matching purchase records may be shown to authorised team members and sent to the Merchant’s configured AI inference providers to answer customer questions; these records are reference data, not instructions or proof of payment. This purchase lookup does not write to the spreadsheet or change the customer’s messaging identity. Disabling the purchase source or disconnecting Google Sheets stops future purchase lookups.

Inchat's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Google user data is used only to provide the Google Calendar and Google Sheets features described above. It is never sold, never used for advertising, never used to train AI models (including generalised AI or machine-learning models), and never transferred to third parties except as necessary to provide the feature, for security purposes, or to comply with law. Disconnecting Google Calendar revokes Inchat's access and stops all synchronisation. Disconnecting Google Sheets in Settings deletes the stored credential and stops every workflow step that writes rows; a Merchant can also remove Inchat's access at any time from their Google Account permissions page (myaccount.google.com/permissions).

6. Service providers (sub-processors)

We rely on the providers below to run Inchat. Some are located outside Malaysia, so personal data may be transferred to and processed in other countries, including Singapore and the United States. We choose providers that contractually protect the data and use it only to provide their service to us.

WhatsApp calls answered by the AI voice agent, for Merchants who have it switched on, are handled differently from the other AI requests listed below. Our own voice runtime, one per workspace and run outside Vercel, streams the call audio and the agent's instructions directly to the speech model it is set up with: Google (Gemini Live), or OpenAI (GPT-Live), which can also hand a harder question to an OpenAI text model. These requests do not go through the Vercel AI Gateway and are not covered by its zero data retention requirement; the provider's own retention terms apply.

  • Supabase — database, file storage and authentication (hosted in AWS ap-southeast-1, Singapore).
  • Vercel — application hosting, the Vercel AI Gateway, which routes the GLM, Claude, Gemini and Whisper requests below, and the cookie-less page-view counts on our public website (Vercel Web Analytics).
  • Google (Google Analytics) — measuring visits to our public website, and counting the sign-ups those visits lead to, as described in section 2. It receives no conversation data.
  • Meta Platforms (advertising) — measuring our own ads with the Meta Pixel on our public website and the Conversions API at sign-up, as described in section 2.
  • OpenAI (ChatGPT Ads) — measuring our own ads in ChatGPT with its pixel and conversions API, once enabled, as described in section 2.
  • Google (Google Ads) — measuring our own Google ads, once enabled, as described in section 2.
  • Z.ai (GLM models) — AI reply generation, message classification, conversation summaries, customer memory, handoff summaries and learning from the Merchant's team's replies. Requests go through the Vercel AI Gateway with zero data retention required and are served only by Baseten or Fireworks AI. The prompt is not stored by the provider.
  • Anthropic (Claude) — the Agent Studio co-builder, the workflow builder and the agent Copilot, through the Vercel AI Gateway with zero data retention required. It receives the Merchant's own configuration and what the Merchant's team types into these tools, not customer conversations.
  • Google (Gemini) — reading images customers send, such as payment slips, through the Vercel AI Gateway with zero data retention required.
  • OpenAI (Whisper) — transcribing voice notes customers send, through the Vercel AI Gateway. No zero-retention provider currently offers transcription in Malay, English and Chinese together, so audio sent for transcription is subject to the provider's standard retention policy. It is not used to train models.
  • Voyage AI — text embeddings for knowledge-base retrieval. Called directly, not through the AI Gateway; it receives the Merchant's knowledge-base text and the customer message being answered.
  • Inchat voice runtime — answers WhatsApp calls for the AI voice agent, only for Merchants who switch it on. It is our own voice runtime, operated by Inchat rather than a third party, and passes the call audio and the agent's instructions directly to one of the two speech models below.
  • Google (Gemini Live) — the speech model for AI-answered WhatsApp calls when the voice runtime is set up with Gemini. It receives the call audio and the agent's instructions directly from the voice runtime, not through the Vercel AI Gateway.
  • OpenAI (GPT-Live) — the speech model for AI-answered WhatsApp calls when the voice runtime is set up with GPT-Live. It receives the call audio and the agent's instructions directly from the voice runtime, not through the Vercel AI Gateway, and can hand a harder question to an OpenAI text model.
  • Stripe — subscription billing and card payments.
  • Shopify — store orders and customer records, only for Merchants who connect a Shopify store.
  • Inseller — order and customer context exchanged with Inseller, only for Merchants who enable the Inseller integration.
  • Twilio — SMS verification codes for phone sign-in.
  • Resend — account emails (sign-up confirmation, password reset, invitations).
  • Cloudflare Turnstile — bot protection on the sign-in page.
  • Expo — push notifications to the Inchat mobile app.
  • Meta Platforms, Telegram, and TikTok Shop — delivering messages on the channels a Merchant chooses to connect.
  • Google — calendar free/busy checks and event creation, only for Merchants who connect Google Calendar once it is available; and reading configured purchase records or adding or updating rows in spreadsheets from workflows and AI Agents, only for Merchants who connect Google Sheets.
  • Notion — adding or updating records in a Merchant's Notion database from workflows and AI Agents, only for Merchants who connect Notion. Inchat reads the shared database's title and property names and types, and adds one page with the values the Merchant mapped. When the Merchant chooses to update a contact's existing record, Inchat asks Notion for the page whose chosen property (for example the phone number) matches, and updates that page's mapped properties. It does not read page content, and never touches a page the Merchant did not share.
  • Sentry — error monitoring (technical logs, with e-mail addresses, phone numbers and similar identifiers redacted before they are sent).
  • PostHog — product analytics for the signed-in app, as described in section 2. It receives the account user id, the workspace id and plan, and the channel type of an AI reply. It does not receive email addresses, names, message content, or phone numbers, and session recording is disabled.

7. Retention and deletion

We keep personal data while the Merchant's workspace is active or as required to provide the service. Disconnecting a channel revokes its credentials and stops future access and synchronisation. Existing conversation history remains in the workspace so the Merchant does not lose its customer-service record.

Merchants who are workspace owners can permanently delete their workspace and all personal data stored in it from Settings → General → Danger zone (type the confirmation phrase shown there). That path removes contacts, messages, identities, and channel credentials for that workspace only.

End Customers (and anyone who cannot use the in-product path) may request deletion by emailing hello@inseller.my with the channel and identifier involved. We honour verified requests within 30 days.

When a Merchant erases one End Customer in Inchat, or Meta asks Inchat to delete a person's data, Inchat keeps a one-way code made from that customer's phone number and email address, for that workspace only, so that the Merchant's imports and integrations (an Inseller contact import, a CSV file, the Merchant's API or apps, a WhatsApp chat-history sync) do not add them back, and the Merchant's workflows and integrations do not start a WhatsApp chat with them unless the customer contacts the Merchant again or the Merchant adds them back. If the customer writes to the Merchant again, they are added as a new contact. The code is made with a secret key that Inchat keeps encrypted in its key store. It does not contain the number, the address, a name or any message, and it is deleted with the workspace.

Meta Facebook Login deauthorize and user data-deletion callbacks are handled at /api/meta/deauthorize and /api/meta/data-deletion (signed_request verified with the app secret). Status checks for Meta data-deletion confirmations are served at /api/meta/data-deletion/status.

8. Your rights (PDPA)

Inchat complies with the Personal Data Protection Act 2010 (Malaysia). You have the right to access, correct, and request deletion of your personal data, to withdraw consent to processing, and to limit processing for direct marketing. To exercise any of these rights, contact us at the email below. If you are an End Customer, we may direct your request to the Merchant who controls the conversation data, and will assist them in fulfilling it.

9. Security

All traffic is encrypted in transit (TLS). Webhook payloads are authenticated with platform signatures before processing. Database access is isolated per workspace with row-level security, and platform credentials are stored as encrypted references. We practise data minimisation: we do not collect data the service does not need.

10. Changes to this policy

We may update this policy as the service evolves. Material changes will be announced to Merchants by email or in-product notice, and the "Last updated" date above will change. Continued use of Inchat after a change constitutes acceptance of the updated policy.

11. Contact

Data protection enquiries and requests: hello@inseller.my