隐私政策

家脉如何使用 Google 权限与客户数据

生效日期:2026 年 6 月 1 日。本文重点说明为什么需要 Gmail 发信、为什么使用 Google Form,以及为什么客户数据默认保存在用户本机而不是家脉云端。

Privacy Policy

How KinlinkCRM uses Google permissions and customer data

Effective date: June 1, 2026. This policy explains why KinlinkCRM uses Gmail sending and Google Forms, and why customer data is stored locally on the user's device instead of in KinlinkCRM cloud databases.

1. 我们是谁

家脉 KinlinkCRM 是一款面向华人经纪的桌面 CRM。我们的核心原则是:客户资料优先本地存储,由用户自己掌控。家脉提供 Google 连接能力,是为了帮助用户把自己已有的获客和沟通流程接入到桌面 CRM,而不是把用户的客户数据集中上传到我们的云端。

2. 为什么需要 Google 登录

用户连接 Google 账户后,家脉主要只做两件事:

  • 代表用户使用其 Gmail 账户发送客户沟通邮件,例如群发通知、节日问候或手动选择的邮件模板。
  • 连接用户自己的 Google Form 与表单回应,用于把潜在客户线索同步到用户本机的 CRM 中。

如果用户不需要 Gmail 发信或 Google Form 同步,可以不连接 Google,仍然可以使用家脉的大部分本地客户管理功能。

3. 为什么要用 Gmail 发邮件

家脉使用 Gmail 发送邮件,是因为很多经纪已经在用自己的 Gmail 或 Google Workspace 邮箱与客户沟通。通过 Google 授权后,邮件会直接从用户自己的邮箱身份发出,用户可以继续使用自己现有的发件地址、已建立的客户信任关系和 Google 邮箱发件记录。

家脉不会替用户创建新的公共群发邮箱,也不会把客户联系人导出到第三方邮件营销平台。我们的目标只是让用户在自己的 Gmail 账户内更高效地完成客户沟通。

4. 为什么要用 Google Form

很多经纪已经在微信、小红书、朋友圈或广告落地页中使用 Google Form 收集客户登记信息。家脉接入 Google Form 的目的,是让这些已有流程继续保留,同时把表单回应自动同步到桌面 CRM,减少手动录入。

Google Form 回应首先保存在用户自己的 Google 账户中。家脉读取这些回应后,会把相关线索导入到用户自己的本地数据库,方便后续跟进、分配渠道和修改资料。

5. 客户数据存储在哪里

客户档案、跟进记录、标签、备注、导入后的线索等 CRM 数据默认保存在用户自己的电脑上。 家脉的设计目标是本地优先,而不是 SaaS 式集中托管客户数据。

我们不会把用户的客户名单、客户联系方式、跟进记录或 Google Form 回应全文同步到家脉自有的云端客户数据库用于运营、广告投放或数据出售。

6. 哪些数据可能经过云端

为支持账号登录、订阅状态和基础产品运维,家脉可能处理少量账户级信息,例如登录标识、订阅状态、应用版本、平台信息或必要的技术日志。这些信息用于让软件可登录、可订阅、可排查故障,不用于建立客户画像。

我们在设计上尽量把业务客户数据与账户级技术数据分开处理。

7. 我们如何使用 Google 数据

  • 仅在用户明确授权并主动启用相关功能后,访问与 Gmail 发信和 Google Form 同步相关的数据。
  • Google 数据只用于用户在家脉中发起的核心功能,不用于广告、出售数据或向无关第三方共享。
  • 我们不会使用这些 Google 数据来训练通用广告模型或建立跨客户的营销画像。

8. 数据控制与撤销

用户可以随时停止在家脉中使用 Gmail 发信或 Google Form 同步,也可以直接在自己的 Google 账户权限设置中撤销家脉的授权。撤销后,家脉将无法继续访问相关 Google 功能。

用户本机里已经保存的客户资料,仍由用户自行决定是否保留、导出或删除。

9. 联系我们

如果你对这份隐私政策或 Google 数据使用方式有疑问,请联系:support@kinlinkcrm.com

1. Who we are

KinlinkCRM is a desktop CRM built for Chinese-speaking real estate agents. Our core principle is that customer records should remain under the user's control and be stored locally first. We provide Google connectivity so users can connect their existing lead capture and communication workflows to the desktop CRM, not to centralize customer data in KinlinkCRM cloud databases.

2. Why Google Sign-In is needed

After a user connects a Google account, KinlinkCRM mainly uses the connection for two purposes:

  • To send customer emails from the user's own Gmail account, such as selected templates, bulk outreach, or follow-up messages initiated by the user.
  • To connect the user's own Google Forms and form responses so incoming leads can be synced into the user's local CRM database.

If a user does not need Gmail sending or Google Forms sync, most local CRM features can still be used without connecting Google.

3. Why KinlinkCRM uses Gmail to send email

Many agents already communicate with clients through their personal Gmail or Google Workspace address. With Google authorization, messages are sent from the user's own mailbox identity, allowing the user to keep the same sender address, client trust, and mail history they already use in their business.

KinlinkCRM does not create a replacement bulk-mail platform and does not export customer contacts into unrelated third-party email marketing systems. The purpose is simply to help the user send business emails more efficiently from the Google account they already own.

4. Why KinlinkCRM uses Google Forms

Many agents already collect leads through Google Forms shared on WeChat, Xiaohongshu, referrals, or ad landing pages. KinlinkCRM integrates with Google Forms so those existing workflows can remain in place while form responses are automatically synced into the desktop CRM, reducing manual entry.

Google Form responses are first stored in the user's own Google account. KinlinkCRM reads those responses and imports the relevant leads into the user's local CRM database for follow-up, channel attribution, and later edits by the user.

5. Where customer data is stored

Customer profiles, follow-up records, tags, notes, and imported lead data are stored locally on the user's device by default. KinlinkCRM is designed to be local-first rather than a cloud-hosted system for centralized customer records.

We do not upload or maintain the user's customer lists, customer contact details, follow-up histories, or full Google Form response content in a KinlinkCRM-owned cloud customer database for advertising, resale, or behavioral profiling.

6. What data may still pass through cloud systems

To support sign-in, subscription status, and basic product operations, KinlinkCRM may process limited account-level information such as login identifiers, subscription state, app version, platform details, or necessary technical logs. This data is used to keep the product operational and secure, not to build customer profiles.

We intentionally separate account-level technical data from business customer data wherever possible.

7. How we use Google data

  • We access Google data only after the user explicitly authorizes and enables the related feature.
  • Google data is used only for the user-facing core functions requested inside KinlinkCRM, not for advertising, resale, or unrelated third-party sharing.
  • We do not use Google data to train advertising systems or create cross-customer marketing profiles.

8. User control and revocation

Users can stop using Gmail sending or Google Forms sync inside KinlinkCRM at any time, and they can revoke KinlinkCRM access directly from their Google account permissions settings. Once revoked, KinlinkCRM can no longer access the related Google features.

Customer data already stored locally on the user's device remains under the user's control for export, retention, or deletion.

9. Contact

If you have questions about this Privacy Policy or how KinlinkCRM uses Google data, contact: support@kinlinkcrm.com