隐私政策 Privacy Policy
CT5 · 更新日期 / Updated: 2026-10-30
本页适用于 CT5 公司内部受控测试通路及本说明网站。其他版本的数据处理方式，以对应版本的说明为准。
1. 文件与恢复权限
受信任客户端先加密文件，再通过 CT5 受控服务将加密包传输至公司批准的 Google Drive。恢复在获授权的受信任客户端完成。当前公网测试仅接受指定公开样本，尚未开放真实公司资料上传。
组织授权管理员具有相应的资料恢复权限。员工使用权限由所属组织管理，不因此获得其他员工资料的访问权。
2. 处理哪些信息
CT5 受控服务处理必要的组织账号、安全验证信息、设备标识、Google 授权账号标识与邮箱，以及备份包标识、大小、时间、校验结果和运行状态。
服务端保存受保护的 Google 访问令牌与刷新令牌，用于维持已授权的云盘连接。这些信息用于访问控制、密文传输和核对操作结果。Google 账号登录由 Google 处理，CT5 不要求提供 Google 账号密码。
3. Google 权限
| 权限 | 用途 |
|---|---|
drive.file | 管理本应用创建或被明确授权访问的 Drive 文件，不申请整个云盘的完整访问权限。该范围允许创建、读取、更新及删除相应文件；实际操作受已开放功能与组织审批约束。 |
openid | 确认已授权 Google 账号的身份。 |
email | 核对并显示组织批准的授权邮箱。 |
这些权限不用于读取 Gmail 邮件、联系人或日历。参阅 Google Drive 权限说明。
CT5 对通过 Google API 取得的信息的使用和转移，遵守 Google API Services User Data Policy，包括 Limited Use 要求。我们不出售这些数据，也不将其用于广告或训练通用人工智能模型。
4. 云服务与支持
Google Drive 保存加密备份包。CT5 服务及必要的托管基础设施处理所需授权信息、元数据和密文；组织授权管理员可按权限恢复资料。
网站托管平台可能为页面交付和安全处理网络地址、浏览器信息及访问时间。支持沟通中由你主动提供的信息，仅用于处理相关请求。
5. 保留、撤销与删除
备份计划、保留期限、恢复及删除范围，由组织按照已启用版本和审批规则管理。
删除源文件、退出登录、撤销授权或卸载程序，不会自动删除已有云端副本。删除云端副本也不会自动删除设备原文件；备份计划未调整时，原文件仍可能再次备份。
Google 账号持有人可在 Google 第三方应用连接 中撤销 CT5 访问权限。撤销会影响后续访问，但不等同删除已有资料。
如需访问、更正、恢复或删除资料，请联系组织管理员。服务端账号及授权信息的移除，可向管理员或下方支持渠道提出请求。Google 回收站、平台保留规则及其他副本，可能影响最终删除时间。
6. 联系与变更
数据处理方式发生实质变化时，我们会更新本页，并按需要重新取得授权。支持邮箱：ziyanyusrilfirmansyah57@gmail.com。请勿在支持邮件中发送密码、验证码或完整授权凭据。
English
Scope and testing. This policy covers the CT5 company-controlled test connection and this information website. Other versions may use different data flows and require their corresponding documentation. The current public test connection accepts designated public samples only.
Files and recovery. Trusted clients encrypt files before CT5 controlled services relay encrypted packages to an organization-approved Google Drive. Recovery takes place on authorized trusted clients. Organization-authorized administrators have recovery rights within their assigned scope. Employee access does not grant access to other employees’ data.
Service information. CT5 processes necessary organization accounts, security verification information, device identifiers, approved Google account identifiers and email addresses, package identifiers, sizes, timestamps, integrity results and operation status. Protected Google access and refresh tokens are stored on the service to maintain authorized Drive connections. Google handles Google account authentication; CT5 does not request the Google account password.
Google permissions. CT5 uses drive.file for files created by or explicitly made available to the application, rather than full-Drive access. This scope permits creating, reading, updating and deleting those files; actual actions depend on enabled functionality and organizational approvals. openid and email identify and verify the approved Google account. These permissions are not used to read Gmail, contacts or calendars.
CT5 follows the Google API Services User Data Policy, including Limited Use. Google API data is not sold, used for advertising or used to train general-purpose AI models.
Storage and sharing. Google Drive stores encrypted packages. CT5 services and necessary hosting infrastructure process the authorization information, metadata and ciphertext needed to provide the service. Website hosting providers may process ordinary delivery and security information. Information voluntarily provided for support is used to handle the request.
Retention and choices. The organization controls retention, recovery and deletion under its policies and approvals. Deleting source files, uninstalling CT5 or revoking Google access does not automatically delete existing cloud copies. Deleting a cloud copy does not delete the original device file or prevent a later backup under an unchanged schedule. Google account holders can revoke access through Google third-party connections. Contact your administrator for data requests, or the support address below for assistance. Provider retention, trash and other copies may affect final deletion.
Material changes will be reflected in this policy, with renewed authorization where necessary. Contact: ziyanyusrilfirmansyah57@gmail.com. Do not send passwords, verification codes or complete authorization credentials.