metabiz mCRM connector privacy policy

This policy covers the metabiz mCRM MCP connector/plugin, including connections through ChatGPT, Claude, and Gemini CLI. metabiz mCRM is developed and provided by 用益網路科技股份有限公司 (metabiz Co., Ltd.); metabiz.ai is its official product website. Updated: October 24, 2026.

Merchants determine why they collect member data and who may access it. metabiz provides connection and processing services under merchant service arrangements and user instructions. AI platforms and messaging channels process data under their respective agreements with users and merchants.

We process the merchant code, selected environment, operator identity, account permissions, OAuth client and callback information, authorization state, access/refresh tokens, and upstream sessions to authenticate users, maintain authorization, isolate merchants, and enforce permissions. Passwords are supplied to mCRM during merchant sign-in. Complete authentication in the sign-in page and keep credentials within the private authorization flow.

Tools receive user-requested filters such as member identifiers or phone numbers, tags and dimensions, dates, stores, orders, segments, conversation identifiers, and pagination. Available tools and account permissions determine the results, which may include member names and contact details, tags and dimensions, purchases and orders, points, stores, RFM and statistics, segments, retained customer or LINE group conversations, and channel identifiers.

The purpose is to perform the requested CRM lookup, analysis, or customer service task. Results are returned to the AI platform selected by the user for its response. Merchant permissions, integrations, source retention, and pagination determine coverage. Users can narrow their queries and returned scope.

Preparing tag changes, segments, templates, LINE/SMS messages, or App push notifications involves target identifiers, recipients or segment criteria, message text, LINE Flex JSON, image URLs, templates, push titles and navigation parameters, merchant and operator identity, payload verification values, proposal identifiers, approval times, execution status, and provider responses.

The connector stores a specific proposal for the same operator to review, approve, and reconcile with execution results. A separate execution step triggers the write or send. Review the target, content, and channel before approval. Image URLs and their resources may be loaded by the selected platform, channel, or recipient device.

Selected AI platform: ChatGPT/OpenAI, Claude/Anthropic, or Gemini/Google receives the tool inputs and outputs for that connection and processes them under its own terms, privacy policy, and account settings. Manage conversations and data settings in that platform.

Merchant metabiz Hub/mCRM: supplies authorized source data, executes approved operations, and retains business or channel records. Authorized metabiz support personnel handle support requests; provide only necessary, appropriately redacted material.

Selected messaging channels: LINE processes recipient/group identifiers and message, Flex, and image data; the merchant-configured SMS provider processes phone numbers and SMS content; Google Firebase Cloud Messaging processes App device tokens, notification content, and navigation data, with Apple APNs delivering iOS notifications. Each channel receives the data required when its corresponding send feature is used.

Hosting and technical service providers process connection, security, and storage data needed to operate the service. AI platforms and channels may process data across borders under their service arrangements. Merchants should choose features according to their data sources and authority.

The connector currently issues access tokens valid for one hour and refresh tokens valid for seven days, rotating refresh tokens on use. Active use extends a connection record by seven days. Authorization-flow records last ten minutes; authorization codes and final-consent records last two minutes. OAuth client registrations last 365 days. Upstream mCRM sessions follow their own validity and revocation state.

These periods describe valid connector access. A later store write triggers cleanup of expired records. Physical storage and backups follow the retention explanation below.

Write/send proposal approval is valid for 15 minutes, and proposal-record access lasts 24 hours from creation. Access checks reject expired proposals. Physical records are cleaned on a subsequent store write, so physical cleanup timing depends on later write activity.

Members, orders, retained conversations, templates, segments, sent messages, and channel execution records are merchant business data. They remain stored until the relevant deletion or retention processing is completed under merchant service arrangements, data administration, and applicable retention obligations. Copies held by AI platforms and channels follow those providers’ policies.

Fixed retention periods for technical/security logs and backups are still being determined. The confirmed proposal validity and cleanup mechanism are described above. Log/backup retention and deletion scope require review of the affected systems; request details through the data-request contact. We will update this page when fixed periods are established.

You can choose a merchant, adjust account permissions and query scope, decide whether to approve each proposal, and remove the connection in the AI platform or request revocation through support. On receiving a valid revocation, the connector stops access through that connection and attempts to revoke the upstream session.

Request access or a copy, correction, deletion, cessation of processing, or connection revocation at [email protected]. Include the merchant code, request type, data scope, and relevant operation time. Protect passwords, tokens, and channel private keys. We verify identity, merchant authority, affected systems, and retention obligations, then communicate scope, constraints, and progress. Completion timing is confirmed following the individual review.

Removing an AI-platform connection ends use of that connection. Merchant source data, sent messages, AI-platform conversations, and backups are handled through their respective data administration or deletion processes.

The service uses HTTPS and merchant/operator permissions to restrict data scope. Supported write/send flows check proposal content, approver identity, and state. Supply data needed for the task and redact unnecessary personal information from support screenshots or conversations.

We update this policy as features and data practices change, publishing the latest date and text here. Service provider and privacy contact: 用益網路科技股份有限公司 / metabiz Co., Ltd., [email protected]. Product and support links appear in the navigation.