Spoor Privacy Policy

# Spoor — Privacy Policy > The English text is the governing version. The Chinese translation is provided for convenience; if the two versions differ, the English version controls. **Version:** 1.0.0 **Last updated:** 19 August 2026 **灰阶法典（佛山）科技有限公司** (operating as **Spoor**, "we", "us", or "our") respects your privacy. This Privacy Policy explains what personal data we collect, use, store, and share when you use the Spoor spatial notes canvas and AI personas service (the "**Service**"), and the rights you can exercise. **Spoor is local-first by default**: most of your canvas content lives on your device, not on our servers. The amount of personal data we handle is therefore much smaller than for typical SaaS products, but please read this policy to understand exactly what does and does not leave your device. We may update this policy from time to time. Material changes will be communicated in advance via an in-product banner and/or email to your account address. --- ## 1. Data Controller The data controller for the Service is: - **Legal entity:** 灰阶法典（佛山）科技有限公司 - **Registered address:** 广东省佛山市禅城区 (Chancheng District, Foshan, Guangdong, China) - **Privacy contact:** [w978109720@gmail.com](mailto:w978109720@gmail.com) - **Data Protection Officer (DPO):** Not appointed — for questions, contact [w978109720@gmail.com](mailto:w978109720@gmail.com) Spoor's Service has multiple processing paths. When you enable **Supabase-based cloud sync** (optional, configurable under Settings), synced canvas data is stored in **your own Supabase project** under your own control. In that case, you (or your organisation) act as an additional data controller for that data; Spoor's role is limited to providing the open-source sync code published under [PolyForm Noncommercial 1.0.0](https://polyformproject.org/licenses/noncommercial/1.0.0/). See §11.1 for details. --- ## 2. What Personal Information We Collect Spoor operates in **two processing modes** for AI calls. The data we handle depends on which features you use. ### 2.1 Common to all modes These data points are collected regardless of which mode you operate in: - **Account credentials** *(only if you sign in to enable cloud sync or hosted AI credits)*: email address, password (one-way hash), session token. - **Billing data** *(only on paid plans)*: subscription tier, billing cycle, transaction status and ID. We do **not** store full card numbers — see §5. - **Support communications**: emails, support tickets, or feedback you send to us. - **Operational metadata from API proxies**: when you use the web app or the bundled desktop build over the network, our Netlify-hosted edge functions log request metadata (timestamp, route, response code, error class) for security, abuse prevention, and capacity planning. **API-key material is not logged**, and request **bodies are not retained** beyond the in-flight call. ### 2.2 What we DO NOT collect by default - **Canvas content** (notes, screenshots, documents, persona responses, agent dialogues): stored locally in your browser's IndexedDB (web) or under `%LOCALAPPDATA%\com.spoor.app\` on Windows (desktop build). Spoor's servers do **not** receive this content unless you enable cloud sync (§11.1). ### 2.3 Hosted AI mode When you operate the Service using Spoor's bundled or hosted AI credentials — i.e. on plans that include hosted AI credits (Pro, Studio) or when you use the hosted web demo's built-in provider — your AI **Inputs and Outputs pass through our Netlify-hosted API proxy** en route to the underlying AI provider (Google Gemini, Volcengine Doubao, Xiaomi MiMo, DeepSeek, Metaso, 302.AI, etc.). Spoor processes these Inputs and Outputs solely to deliver the Service. ### 2.4 BYO Key mode When you paste your own AI provider API key into Settings: - **Desktop build**: where connectivity permits, the call may be made directly from your device to the chosen provider, **without transiting Spoor's proxy**. In that path Spoor sees neither the request nor the response. - **Web build**: the call still flows through our Netlify proxy because of CORS and API-key safety; Spoor's proxy sees the request body to forward it. The in-app Settings panel indicates the active provider and the request route. Choosing to use your own key means the AI provider becomes your direct counterparty under its own privacy policy; Spoor is not a party to that relationship. --- ## 3. How We Use Personal Information | Purpose | Legal basis (GDPR Art. 6) | |---|---| | Provide and operate the Service | Contract performance | | Process subscription billing | Contract performance | | Customer support | Contract performance / legitimate interest | | Operational notices (billing, security, policy updates) | Legitimate interest | | Fraud prevention and abuse mitigation | Legitimate interest | | Service improvement and analytics | Legitimate interest | | Legal and tax compliance | Legal obligation | | Marketing communications *(not currently sent)* | Consent (opt-in) | > Spoor does not currently run third-party analytics, advertising pixels, or marketing trackers. If this changes, the type, vendor name, and a link to that vendor's own privacy policy will be listed in §4 and announced in advance through the same channel used for policy updates. --- ## 4. Cookies and Tracking Technologies Spoor uses **no third-party tracking cookies today**. The Service stores only the minimum data needed to function: | Type | Purpose | Can be disabled | |---|---|---| | Strictly necessary | Session token, authentication state, language preference, CSRF token | No | | Functional | Last-opened canvas pointer, theme preference, ambience toggles | Yes (signing out clears them) | | Analytics | None deployed | N/A | | Marketing | None deployed | N/A | You can clear functional data at any time via Settings → Clear local data, or by signing out and clearing browser storage. The desktop build does not use browser cookies; local preferences are stored in the platform-appropriate user data folder. --- ## 5. Sharing and Disclosure We do **not** sell your personal information, including under the meaning of "sale" in the California Consumer Privacy Act (CCPA) or analogous laws. We share your information only as follows: - **AI providers.** To fulfil persona requests, we transmit your Inputs to the provider you have selected (Google Gemini, Volcengine Doubao, Xiaomi MiMo, DeepSeek, Metaso, 302.AI, or any other provider supported by the Service). Each is a separate data controller with its own privacy policy. When your API key is on file (BYO Key), the request is made in your name; when hosted credits are on file, the request is made in our name on your behalf. - **Payment processor.** Paid-plan card data is processed exclusively by our PCI-DSS-compliant payment processor, **Waffo Pancake**. Spoor never stores raw card data on its own servers. - **Cloud infrastructure.** - **Web build**: Netlify (edge functions, static hosting, redirects). - **Optional cloud sync** (only if you enable it): Supabase, configured under **your own account**, using your own project — Spoor's role is limited to the open-source sync code. - **Desktop build updates**: GitHub Releases channel used for version checks and installer delivery. - **Legal and regulatory.** Where required by valid law, court order, or competent authority. - **Business transfers.** In the event of a merger, acquisition, or asset sale, with prior notice to you and continued protection obligations. - **With your consent.** For any other purpose for which you provide explicit prior consent. The Spoor codebase is open source under the [PolyForm Noncommercial 1.0.0 License](https://polyformproject.org/licenses/noncommercial/1.0.0/) and publicly auditable at [https://github.com/iimorning/spoor](https://github.com/iimorning/spoor). No personal data is hard-coded or hard-shipped through the source. --- ## 6. Security Measures - **Transport encryption**: TLS / HTTPS for all client-server traffic. - **Local-first storage**: canvas content lives on your device by default; compromising Spoor's servers does not expose your canvas data. - **Authentication**: passwords stored using a one-way hash; session tokens are short-lived; cookies are flagged `HttpOnly` and `SameSite=Lax` where applicable. - **Access control**: principle of least privilege; maintainer-side administrative access is logged and reviewed. - **Open-source review**: the codebase is publicly auditable at [https://github.com/iimorning/spoor](https://github.com/iimorning/spoor). In the event of a personal-data breach affecting your rights, we will notify you and the relevant supervisory authority within 72 hours of discovery. --- ## 7. Data Retention | Data type | Retention | After expiry | |---|---|---| | Account credentials | While account is active | Deleted on account closure | | Subscription billing records | 7 years (to meet tax / accounting obligations) | Archived encrypted, then deleted | | Support correspondence | 2 years | Securely deleted | | API-proxy operational logs (metadata only, not Inputs) | 90 days | Auto-purged | | Canvas content (local) | Stored on your device until you delete or uninstall the app | Your control, not ours | | Cloud-synced canvas content (Supabase) | While sync is enabled; 30 days after sync disabled | Deleted automatically | --- ## 8. Your Data Rights To exercise any of the rights below, contact [w978109720@gmail.com](mailto:w978109720@gmail.com). We will respond within 30 calendar days. | Right | Description | |---|---| | Right to be informed | Understand what we collect and use, as set out above | | Right of access | Obtain a copy of your personal information | | Right to rectification | Correct inaccurate or incomplete data | | Right to erasure ("right to be forgotten") | Request deletion under applicable conditions | | Right to restrict processing | Pause data processing in defined circumstances | | Right to data portability | Receive your data in a machine-readable format | | Right to object | Object to processing based on legitimate interest or for marketing | | Right to withdraw consent | Withdraw any consent-based processing | You also have the right to lodge a complaint with your local data protection authority (for example, the CAC in China, the CNIL in France, the ICO in the UK, or the California AG). > **Self-service paths.** Because most of your canvas content is local-first, you can exercise the strongest forms of these rights directly in-app: > - **Export**: Settings → Export canvas (JSON / Markdown / PDF bundle). > - **Delete**: Settings → Clear local data, or uninstall the desktop build. > - **Rectify**: edit any note on the canvas. > Cloud-synced content follows the same controls in **your own Supabase project**. --- ## 9. Marketing Communications and Opt-Out Spoor does not currently send marketing email. Should this change in the future: By your consent, we may send product news, feature updates, and usage tips via email. You can opt out at any time: - Click "unsubscribe" in any marketing email. - Disable marketing notifications in Settings (when available). - Contact [w978109720@gmail.com](mailto:w978109720@gmail.com). Opting out does not affect service-essential notices (billing, security, policy updates). --- ## 10. International Data Transfers Spoor uses infrastructure and providers located in multiple jurisdictions, including the United States, Singapore, the European Union, and China (for example: Netlify and GitHub in the United States; AI providers that may process data in the United States, Singapore, the EU, or China depending on the provider you select; Waffo Pancake for payments). When data is transferred across borders, we safeguard it through: - Selection of providers with documented equivalent protection levels where possible. - Standard Contractual Clauses (SCC) or comparable safeguards with processors where applicable. - **Minimisation**: most user-generated canvas content never leaves your device; only authentication, billing, and operational telemetry cross borders, and only when those features are used. Data-subject rights enumerated in §8 apply regardless of where the data is processed. --- ## 11. Children's Privacy The Service is intended for users aged 16 and over. We do not knowingly collect personal information from anyone below that age. If you believe a child has provided information to us, please contact [w978109720@gmail.com](mailto:w978109720@gmail.com) and we will delete it promptly. Users below 16 must have verifiable parental or guardian consent before using the Service; please do not allow them to use the Service without it. Paid plans and account registration under the Terms of Service additionally require that you are at least 18 years of age. ### 11.1 Self-managed Supabase sync (additional note) When you configure cloud sync under Settings, you provide your own Supabase project URL and an API key. At that point: - You create an account directly with Supabase; [Supabase's own privacy policy](https://supabase.com/privacy) governs what it collects about your Supabase account. - The sync code (open source at [https://github.com/iimorning/spoor](https://github.com/iimorning/spoor)) writes canvas snapshots to your own project's storage using row-level security rules. - Spoor does not store a copy of your synced content on its own servers and has no way to read it. - Deleting your Supabase data is your responsibility — see our [Supabase setup guide](./SUPABASE.md) and [Supabase documentation](https://supabase.com/docs). --- ## 12. Third-Party Links and Services The Service may contain links to third-party sites and references to third-party services — for example, the project's GitHub repository at [https://github.com/iimorning/spoor](https://github.com/iimorning/spoor), the AI providers listed in §5, and the Supabase project you configure for sync. This policy applies only to data Spoor directly processes. For third-party sites, please review their own privacy policies, especially the AI providers' model-training and data-retention practices. --- ## 13. Changes to This Policy For material changes, we will notify you at least 14 days in advance via an in-product banner and/or email at your account address. The "Last updated" date at the top of this document will be revised accordingly. Continued use after the effective date constitutes acceptance of the revised policy. A public version history is maintained on the Privacy Policy page at [https://spoor.ink/privacy](https://spoor.ink/privacy) so that the version in force at any past date can be reproduced. --- ## 14. Contact For privacy, support, billing, or security questions, email [w978109720@gmail.com](mailto:w978109720@gmail.com). - **Legal entity:** 灰阶法典（佛山）科技有限公司 - **Postal address:** 广东省佛山市禅城区 - **Hours:** Monday–Friday 10:00–18:00 (China Standard Time, UTC+8) - **Website:** [https://spoor.ink](https://spoor.ink)

# Spoor — 隐私政策 > 中文译本仅供参考。如与英文版不一致，以英文版为准。 **版本：** 1.0.0 **最后更新：** 2026 年 8 月 19 日 **灰阶法典（佛山）科技有限公司**（以 **Spoor** 名义经营；下称"我们"、"我方"）尊重您的隐私。本隐私政策说明您使用 Spoor 空间便签画布与 AI 角色服务（"**服务**"）时，我们如何收集、使用、储存与共享您的个人信息，以及您可依法行使的权利。 **Spoor 默认采取本地优先策略：** 您绝大部分的画布内容位于您的设备之上，而非我们的服务器。这显著小于典型 SaaS 产品对个人数据的处理范围，但仍请您仔细阅读本政策，以准确理解哪些数据会离开您的设备。 我们可能不时更新本政策。重大变更会通过应用内提示和/或您的账户邮箱提前通知。 --- ## 1. 数据控制者 本服务的数据控制者为： - **法律主体：** 灰阶法典（佛山）科技有限公司 - **注册地址：** 广东省佛山市禅城区 - **隐私联系邮箱：** [w978109720@gmail.com](mailto:w978109720@gmail.com) - **数据保护负责人（DPO）：** 暂未设立 —— 如有疑问请联系 [w978109720@gmail.com](mailto:w978109720@gmail.com) 当您启用**基于 Supabase 的云端同步**（可选，于设置中配置）时，被同步的画布数据存储于**您自己的 Supabase 项目**，由您自行掌控。此时，您（或您所属的机构）成为该数据的额外控制者；Spoor 仅提供受 [PolyForm Noncommercial 1.0.0](https://polyformproject.org/licenses/noncommercial/1.0.0/) 协议授权的同步代码。详见 §11.1。 --- ## 2. 我们收集哪些个人信息 Spoor 在 AI 调用上有**两种处理通路**。我们处理的数据取决于您使用的是哪一项。 ### 2.1 通用（任何模式下都适用） - **账户凭据**（仅当您登录以启用云端同步或托管 AI 额度时）：电子邮箱地址、单向哈希后的密码、会话令牌。 - **账单数据**（仅限付费套餐）：订阅套餐、计费周期、交易状态与交易 ID。我们**不会**保存完整卡号——见 §5。 - **客户支持沟通记录**：您发送给我们的邮件、工单和反馈。 - **API 代理的运维元数据**：当您使用网页版或联网的桌面版时，我们部署在 Netlify 上的边缘函数会记录请求元数据（时间戳、路径、响应状态码、错误类别），用于安全、反滥用与容量规划。**API Key 本身不会被记录**，**请求体也不会**在内存外留存。 ### 2.2 默认情况下我们**不收集**的信息 - **画布内容**（便签、截图、文档、角色回复、代理对话）：存储于您浏览器的 IndexedDB（网页版）或 Windows 上 `%LOCALAPPDATA%\com.spoor.app\` 下的本地文件（桌面版）。Spoor 的服务器**不会**接收到这些内容，除非您启用了云端同步（§11.1）。 ### 2.3 托管 AI 模式 当您使用 Spoor 的内置或托管 AI 凭据——例如在使用包含托管 AI 额度的套餐（Pro、Studio）时，或在官方网页演示上使用内置提供方时——您的 AI **输入内容与输出内容会经过我们在 Netlify 上的 API 代理**，再抵达底层的 AI 提供方（Google Gemini、Volcengine 豆包、Xiaomi MiMo、DeepSeek、Metaso、302.AI 等）。Spoor 为交付服务所必需，仅就这些输入与输出进行最小限度的处理。 ### 2.4 BYO Key 模式 当您在设置中粘贴自己的 AI 提供方 API Key 时： - **桌面版：** 在具备网络条件的情况下，调用可直接从您的设备发往所选提供方，**不再经过 Spoor 的代理**；在此通路上 Spoor 既不看到请求也不看到响应。 - **网页版：** 调用仍需经我们的 Netlify 代理（出于 CORS 与 API Key 安全考虑），Spoor 的代理会看到请求体以完成转发。 应用内"设置"面板会指示当前激活的提供方与请求通路。决定使用您自己的 Key，即意味着与该 AI 提供方按其自身的隐私政策成立直接合同关系；Spoor 不是这一关系的当事方。 --- ## 3. 我们如何使用您的个人信息 | 用途 | 法律依据（GDPR 第 6 条） | |---|---| | 提供与运营本服务 | 合同履行 | | 处理订阅计费 | 合同履行 | | 客户支持 | 合同履行 / 合法利益 | | 运维通知（账单、安全、政策更新） | 合法利益 | | 反欺诈与反滥用 | 合法利益 | | 服务改进与分析 | 合法利益 | | 法律与税务合规 | 法律义务 | | 营销通讯（*当前未开展*） | 同意（opt-in） | > Spoor 当前不运行第三方分析、广告像素或营销追踪器。如未来引入，将在本节明确披露其类型、提供方与该提供方自身隐私政策的链接，并通过与本政策更新相同的渠道提前告知。 --- ## 4. Cookie 与追踪技术 Spoor 当前**不使用任何第三方追踪 Cookie**。本服务仅储存最小必要的数据： | 类型 | 用途 | 是否可关闭 | |---|---|---| | 严格必要 | 会话令牌、认证状态、语言偏好、CSRF 令牌 | 否 | | 功能性 | 上次打开的画布指针、主题偏好、氛围开关 | 是（注销时一并清除） | | 分析型 | 当前未部署 | — | | 营销型 | 当前未部署 | — | 您可随时通过"设置 → 清除本地数据"清理功能性数据，或通过注销并清除浏览器存储来达到同样效果。桌面版不使用浏览器 Cookie；本地偏好存放在操作系统对应的用户数据目录下。 --- ## 5. 个人信息的共享与披露 我们**不出售**您的个人信息，包括《加州消费者隐私法》（CCPA）或类似法律下所定义的"出售"行为。我们仅在以下情形共享您的信息： - **AI 提供方。** 为完成角色请求，我们将您的输入内容传输至您所选的提供方（Google Gemini、Volcengine 豆包、Xiaomi MiMo、DeepSeek、Metaso、302.AI，或本服务所支持的任何其他提供方）。各家均为独立的数据控制者，依其各自的隐私政策行事。当您的 API Key 在案（BYO Key）时，请求以您的名义发出；当托管额度在案时，请求以我们的名义代您发出。 - **支付处理方。** 付费套餐的卡数据**仅**由我们符合 PCI-DSS 标准的支付处理方（**Waffo Pancake**）处理。Spoor 不在自己的服务器上存储原始卡数据。 - **云基础设施：** - **网页版：** Netlify（边缘函数、静态托管、重定向）。 - **可选云端同步**（仅当您启用时）：Supabase。您在自己的账户下，用自己的项目进行配置——Spoor 仅提供开源同步代码。 - **桌面版更新：** 使用 GitHub Releases 通道进行版本检查与安装包分发。 - **法律与监管要求。** 按有效法律、法院命令或主管机关的合法请求。 - **企业交易。** 在合并、收购或资产转让的情形下，事先通知您，并继续承担保护义务。 - **经您同意。** 在您事先明确同意的任何其他用途中。 Spoor 代码以 [PolyForm Noncommercial 1.0.0 License](https://polyformproject.org/licenses/noncommercial/1.0.0/) 开源，可在 [https://github.com/iimorning/spoor](https://github.com/iimorning/spoor) 公开审查。代码中不嵌入也不携出任何个人数据。 --- ## 6. 安全措施 - **传输加密：** 所有客户端—服务器通信均采用 TLS / HTTPS。 - **本地优先存储：** 画布内容默认留在您的设备上；即使 Spoor 的服务器出现意外，也无法接触到您的画布数据。 - **认证：** 密码采用单向哈希存储；会话令牌生命周期较短；Cookie 在可能的情况下标记 `HttpOnly` 与 `SameSite=Lax`。 - **访问控制：** 最小权限原则；维护者侧的管理访问会被记录并接受复核。 - **开源审查：** 代码可在 [https://github.com/iimorning/spoor](https://github.com/iimorning/spoor) 公开审计。 若发生影响您权益的个人数据安全事件，我们将在发现后 72 小时内通知您及相关监管机构。 --- ## 7. 数据保留期 | 数据类型 | 保留期 | 到期处理 | |---|---|---| | 账户凭据 | 账户有效期内 | 账户关闭后删除 | | 订阅账单记录 | 7 年（满足税务 / 会计义务） | 加密存档后删除 | | 客户支持通信记录 | 2 年 | 安全删除 | | API 代理运维日志（仅元数据，不含请求体） | 90 天 | 自动清除 | | 画布内容（本地） | 存放在您的设备上，直至您卸载应用 | 由您掌控，与我方无关 | | 云同步画布内容（Supabase） | 同步开启期间；同步关闭后 30 天 | 自动清除 | --- ## 8. 您的数据权利 如需行使以下任一权利，请联系 [w978109720@gmail.com](mailto:w978109720@gmail.com)。我们将在 30 个日历日内回复。 | 权利 | 说明 | |---|---| | 知情权 | 了解我们收集和使用哪些数据（详见上文） | | 访问权 | 获取一份您的个人信息副本 | | 更正权 | 更正不准确或不完整的信息 | | 删除权（"被遗忘权"） | 在符合条件的情况下请求删除 | | 限制处理权 | 在特定情形下暂停您的数据处理 | | 数据可携权 | 以机器可读格式取得您的数据 | | 反对权 | 反对基于合法利益或为营销目的而进行的处理 | | 撤回同意权 | 撤回以同意为依据的任何处理 | 您也有权向您所在地的数据保护机关提出投诉（如中国网信办、法国 CNIL、英国 ICO、美国加州司法部长等）。 > **自助路径。** 由于您绝大部分的画布内容是本地优先的，您可以直接在应用内以最强形式行使这些权利： > - **导出：** 设置 → 导出画布（JSON / Markdown / PDF 整包）。 > - **删除：** 设置 → 清除本地数据，或卸载桌面版。 > - **更正：** 在画布上直接编辑对应便签。 > 云同步的内容遵循您在**自己的 Supabase 项目**内同样的控制手段。 --- ## 9. 营销通讯与退订 Spoor 当前不发营销邮件。若未来开展此类通讯，将遵守以下规则： 经您同意后，我们可能通过邮件发送产品动态、功能更新与使用提示。您可随时退订： - 点击任一营销邮件中的"取消订阅"链接； - 在设置中关闭营销通知（如已上线）； - 或直接联系 [w978109720@gmail.com](mailto:w978109720@gmail.com)。 退订营销通讯不影响涉及账单、安全、政策更新的服务必要通知。 --- ## 10. 跨境数据传输 Spoor 使用的设施与服务方位于多个司法辖区，包括美国、新加坡、欧盟与中国（例如：Netlify 与 GitHub 位于美国；AI 提供方可能在美国、新加坡、欧盟或中国处理数据，视您所选提供方而定；支付由 Waffo Pancake 处理）。当数据跨境传输时，我们通过以下方式加以保障： - 在可能的情况下选择有公开同等保护水平的提供方； - 在适用情况下与处理方签订标准合同条款（SCC）或同类保障机制； - **最小化：** 绝大部分用户生成的画布内容从不离开您的设备；只有认证、计费和运维遥测会在使用相应功能时跨境。 第 8 条所列数据主体的权利在任何处理地均适用。 --- ## 11. 未成年人保护 本服务面向年满 16 周岁及以上的用户。我们不会故意收集低于该年龄的未成年人的个人信息。 如您认为未成年人向我们提供了信息，请联系 [w978109720@gmail.com](mailto:w978109720@gmail.com)，我们将在知悉后尽快删除。未达 16 周岁的用户须有可核实的家长或监护人同意方可使用本服务；在此同意取得前，请勿允许其使用。 根据《服务条款》，付费套餐与账户注册还要求您年满 18 周岁。 ### 11.1 自管 Supabase 同步（补充说明） 当您在设置中配置云端同步时，您提供的是您自己的 Supabase 项目 URL 与 API Key。此时： - 您直接与 Supabase 注册账户；[Supabase 自己的隐私政策](https://supabase.com/privacy)约束其收集到的您账户相关信息。 - 同步代码（开源地址：[https://github.com/iimorning/spoor](https://github.com/iimorning/spoor)）使用行级安全规则将画布快照写入您自己的项目。 - Spoor 不在自家服务器上留存您同步内容的副本，也无法读取它。 - 删除您在 Supabase 中的数据由您自行负责——详见 [Supabase 设置指南](./SUPABASE.md) 与 [Supabase 文档](https://supabase.com/docs)。 --- ## 12. 第三方链接与服务 本服务可能包含指向第三方站点的链接或对第三方服务的引用，例如项目本身的 GitHub 仓库（[https://github.com/iimorning/spoor](https://github.com/iimorning/spoor)）、第 5 条列出的 AI 提供方，以及您为云端同步而配置的 Supabase 项目。本政策仅约束 Spoor 直接处理的数据。对于第三方站点，请审阅它们各自的隐私政策——尤其是 AI 提供方的"模型训练"与"数据保留"实践。 --- ## 13. 本政策的变更 重大变更将在生效日前至少 14 天通过应用内提示和/或您账户邮箱发出通知。本文件顶部的"最后更新"日期也将随之更新。生效日后您继续使用，即视为接受修订后的政策。 我们将在隐私政策页面维护公开版本记录：[https://spoor.ink/privacy](https://spoor.ink/privacy)，以便在必要时证明过去某一时间点生效的版本。 --- ## 14. 联系我们 隐私、客服、账单或安全相关问题，请发送邮件至 [w978109720@gmail.com](mailto:w978109720@gmail.com)。 - **法律主体：** 灰阶法典（佛山）科技有限公司 - **通讯地址：** 广东省佛山市禅城区 - **服务时间：** 周一至周五 10:00–18:00（中国标准时间，UTC+8） - **网站：** [https://spoor.ink](https://spoor.ink)