Privacy Policy 隐私政策

1. 产品与政策范围

Fan's Happy Work（简称“FanWork”）是面向授权用户的网页设计工作流辅助扩展，用于指定网页设计平台中的页面辅助、预览、工作流工具、授权功能和生产力增强。本政策说明扩展及其授权服务为实现这些单一用途而处理的信息。

2. 我们处理的信息

依据所使用的功能，FanWork 可能处理：

• 用户或员工标识信息：例如经授权服务返回的账号别名、员工标识或与权限配置相关的资料字段。
• 认证与授权信息：例如激活码、会话令牌、授权状态、功能权限以及会话到期或年度重新激活时间。
• 会话与设备授权元数据：例如扩展生成的设备标识符、幂等请求标识、认证状态和安全事件所需的技术元数据。
• 有限的工作页面 URL 数据：扩展会在本地检查当前标签页 URL，以判断功能是否适用。仅在用户主动请求生成 FAN2 激活信息且页面符合指定预览域名与运行条件时，当前预览页面 URL 和项目标识会发送至 FanWork 授权服务，用于授权、安全审计和激活记录。该 URL 是当时页面提供的必要预览地址，可能包含其路径和查询参数；FanWork 不会持续上传一般浏览历史。
• FanCode / FAN2 激活审计元数据：例如项目标识、预览 URL、激活标识、激活指纹、版本、结果、时间及防重复请求信息。
• 扩展偏好和本地配置：例如主题颜色、界面效果、一次性提示状态和其他功能设置。

3. 网页内容与本地处理

为提供页面辅助、订单视图、预览检查和复制等功能，FanWork 可在用户正在使用的指定工作页面上读取并处理必要的页面内容，例如页面结构、订单字段、用户选择的文本和运行状态。这些内容在浏览器本地用于执行用户请求的功能。

经当前版本源码复核，FanWork 不会把客户网页正文、图片、完整 HTML、用户选择的文本或页面交互作为通用后台采集数据上传至 FanWork 服务器。指定工作平台自身的接口通信仍由该平台提供；如上所述，FAN2 激活请求会向 FanWork 授权服务发送必要的项目标识和当前预览 URL。

4. 认证与使用目的

认证和授权信息仅用于验证身份、管理会话、确认功能权限、防止未授权访问、提供请求的功能，以及维护必要的安全和激活审计记录。FanWork 不进行通用浏览历史监控，也不将信息用于与上述 FanWork 单一用途无关的目的。

5. 我们不收集的信息

FanWork 不以其产品用途为目的收集健康信息、金融或支付信息、私人通信内容、精确位置或广告画像数据。FanWork 也不收集或上传用于分析用户行为的点击、按键或浏览活动遥测。用户主动调用的本地快捷键和复制操作只在本机完成。

6. 数据共享

我们不出售用户数据，不将其用于广告或信用评估，也不向无关第三方出售或转移数据。仅在提供和保护 FanWork 所必需、遵守法律义务或维护合法权利时，才会由受约束的基础设施服务商处理必要信息或依法披露信息。

7. 安全

FanWork 采用服务端授权、适用情况下的哈希或受保护凭据、受限会话存储和合理的技术与组织安全措施。敏感签名私钥不会分发到客户端。任何传输或存储系统都无法保证绝对安全，但我们会采取与信息性质相称的保护措施。

8. 保留与删除

我们仅在提供服务、履行业务和法律义务、维护安全以及完成必要审计所需期间保留必要数据。已撤销或已过期会话可依据系统策略清理；安全和激活审计记录可在合理必要期间保留。用户可以停止使用或卸载扩展，并可通过浏览器清除扩展的本地数据。若需了解、访问或请求删除与授权服务相关的信息，请通过下方网站联系我们；请求将依据身份验证要求及适用的法律、安全和审计保留义务处理。

9. 本政策的变更

如 FanWork 的功能或数据处理方式发生实质变化，我们会更新本政策和生效日期。新版本以本页面公布的内容为准。

10. 联系我们

如对本政策有疑问，请访问 fandesign.art。

1. Product and scope

Fan's Happy Work (“FanWork”) is a web-design workflow extension for authorized users. It provides page assistance, preview and workflow tools, authorization features, and productivity enhancements on designated web-design platforms. This policy explains the information processed by the extension and its authorization service for those single-purpose functions.

2. Information we process

Depending on the feature used, FanWork may process:

• User or employee identifiers: such as an account alias, employee identifier, or profile fields related to permissions returned by the authorization service.
• Authentication and authorization information: such as activation codes, session tokens, authorization state, feature entitlements, and session-expiry or annual-reactivation dates.
• Session and device authorization metadata: such as an extension-generated device identifier, request idempotency identifier, authentication status, and technical metadata needed for security events.
• Limited work-page URL data: the extension checks the current tab URL locally to decide whether a feature applies. Only when a user requests FAN2 activation and the page meets the designated preview-domain and runtime conditions are the current preview URL and project identifier sent to the FanWork authorization service for authorization, security auditing, and activation records. The URL is the necessary preview address supplied by the page at that time and may include its path and query parameters. FanWork does not continuously upload general browsing history.
• FanCode / FAN2 activation audit metadata: such as project identifier, preview URL, activation identifier, activation fingerprint, version, outcome, time, and replay-prevention information.
• Extension preferences and local configuration: such as theme color, interface effect, one-time notice state, and other feature settings.

3. Website content and local processing

To provide page assistance, order views, preview checks, and copying tools, FanWork may read and process necessary content on a designated work page that the user is actively using, including page structure, order fields, user-selected text, and runtime state. This content is processed locally in the browser to perform the function requested by the user.

A source review of the current version found that FanWork does not upload customer webpage body text, images, complete HTML, user-selected text, or page interactions to FanWork servers as general backend collection. Communications with a designated work platform's own APIs remain services of that platform. As described above, a FAN2 activation request sends the necessary project identifier and current preview URL to the FanWork authorization service.

4. Authentication and purposes

Authentication and authorization information is used only to verify identity, manage sessions, confirm feature access, prevent unauthorized access, provide requested functionality, and maintain necessary security and activation audit records. FanWork does not monitor general browsing history or use information for purposes unrelated to FanWork's stated single purpose.

5. Information we do not collect

FanWork does not collect health information, financial or payment information, private communications, precise location, or advertising-profile data for its product purpose. It also does not collect or upload click, keystroke, or browsing-activity telemetry for behavioral analytics. User-invoked local shortcuts and copy actions remain on the device.

6. Data sharing

We do not sell user data, use it for advertising or credit assessment, or sell or transfer it to unrelated third parties. Necessary information may be processed by service providers bound to support and protect FanWork, or disclosed when required by law or necessary to protect legitimate rights.

7. Security

FanWork uses server-side authorization, hashed or otherwise protected credentials where applicable, restricted session storage, and reasonable technical and organizational safeguards. Sensitive signing private keys are not distributed in the client. No transmission or storage system can be guaranteed completely secure, but safeguards are applied in proportion to the nature of the information.

8. Retention and deletion

Necessary data is retained only as long as required to provide the service, meet business and legal obligations, maintain security, and perform necessary audits. Revoked or expired sessions may be cleared under system policy; security and activation audit records may be retained for a reasonably necessary period. Users can stop using or uninstall the extension and can clear its local data through the browser. To ask about, access, or request deletion of information associated with the authorization service, contact us through the website below. Requests are handled subject to identity verification and applicable legal, security, and audit-retention obligations.

9. Changes to this policy

If FanWork's features or data practices materially change, we will update this policy and its effective date. The version published on this page is the current version.

10. Contact

For questions about this policy, visit fandesign.art.