Door 隐私政策
本政策说明 Door 如何访问、使用、共享、保存和保护与您有关的信息。
使用远程模型或广告功能时,相关第三方也可能依照其政策处理数据。
1. 本地数据
聊天内容、对话历史、角色数据、应用设置、模型配置、远程服务地址和
API 密钥等数据存储在您设备的应用私有目录或本地偏好设置中。
Door 不要求创建应用账户,也不会自动把本地聊天上传到开发者的服务器。
2. 远程模型模式
仅当您主动选择并配置“远程模型”时,Door 才会把生成回复所需的数据
发送到您选择的远程服务。
发送的数据可能包括:
- 您输入的消息;
- 角色设定、系统提示词和为生成回复而选取的对话历史;
- 模型名称和生成参数;
- 用于访问该服务的 API 密钥。
请求由您的设备直接发送到您配置的兼容服务地址,不经过 Door 的中转账户服务。
远程服务提供方会依据其自身的隐私政策和保存规则处理这些数据。
请仅使用您信任的服务、阅读其隐私政策,并优先配置 HTTPS 地址。
3. 广告和同意管理
Door 使用 Google AdMob 展示广告,并使用 Google User Messaging Platform
(UMP)在适用地区收集和管理广告同意选择。Google Mobile Ads SDK
可能自动收集并与 Google 共享以下数据:
- IP 地址(可能用于推断大致位置);
- 用户与产品的互动,例如应用启动、点击、视频观看和广告互动;
- 诊断信息,例如应用启动时间、卡顿或崩溃相关信息;
- 设备或其他标识符,例如广告 ID、应用集 ID 及相关设备标识符。
这些数据用于广告投放与个性化、分析衡量和防止欺诈。Google 表示,
Mobile Ads SDK 会在传输过程中使用 TLS 加密数据。适用地区的用户可以在
Door 的“我的 → 广告隐私”中重新管理同意选择。
4. 保存和删除
本地数据会保留在您的设备上,直至您在应用提供相应入口时删除相关内容、
清除 Door 的应用数据,或卸载 Door。清除应用数据或卸载应用通常会移除
Door 应用私有目录中的聊天、设置、API 密钥和缓存文件;设备备份或操作系统
功能可能另有处理。
Door 无法替您删除 Google 或您所选远程模型服务已经处理的数据。
如需了解或请求删除此类数据,请按照相应服务提供方的隐私政策与其联系。
5. 数据安全
Door 使用 Android 应用沙箱保护本地应用数据;内置外部服务使用平台支持的
HTTPS/TLS 传输。若您配置自定义远程地址,其传输安全取决于该地址和服务提供方,
因此请使用 HTTPS,并妥善保管 API 密钥。任何存储或传输方式都无法保证绝对安全。
6. 第三方政策
7. 儿童隐私
Door 并非专门面向儿童设计。若您认为儿童在未经适当同意的情况下提供了
个人信息,请通过下方联系方式告知开发者。
8. 政策更新
本政策可能因功能、第三方服务或法律要求的变化而更新。
更新后的版本会发布在本页面,并在页面顶部标明新的更新日期。
9. 联系开发者
开发者:songttsong5-lab。对于隐私问题、更正或删除请求,请通过公开的
Door 隐私问题提交入口
联系开发者。提交时请勿公开粘贴 API 密钥、完整聊天记录或其他敏感信息。
Door Privacy Policy
This policy explains how Door accesses, uses, shares, retains, and
protects information related to you. Third parties may also process
data under their own policies when you use advertising or a remote model.
1. Local Data
Chats, conversation history, character data, app settings, model
configuration, remote service URLs, and API keys are stored in your
device's app-private storage or local preferences. Door does not require
an app account and does not automatically upload local chats to the
developer's servers.
2. Remote Model Mode
Door sends data needed to generate a response to a remote service only
when you actively select and configure Remote Model mode.
Data sent may include:
- Messages you enter;
-
Character instructions, system prompts, and conversation history
selected as context for the response;
- The model name and generation parameters; and
- The API key used to access the service.
Requests go directly from your device to the compatible service endpoint
you configure and do not pass through a Door intermediary account
service. The remote provider processes this data under its own privacy
and retention terms. Use only providers you trust, review their privacy
policies, and prefer HTTPS endpoints.
3. Advertising and Consent Management
Door uses Google AdMob to display ads and Google User Messaging Platform
(UMP) to collect and manage advertising consent choices where required.
The Google Mobile Ads SDK may automatically collect and share the
following data with Google:
- IP address, which may be used to estimate general location;
-
User product interactions, such as app launches, taps, video views,
and ad interactions;
-
Diagnostic information, such as app launch time and information
related to hangs or crashes; and
-
Device or other identifiers, such as advertising ID, app set ID, and
related device identifiers.
This data is used for advertising and personalization, analytics and
measurement, and fraud prevention. Google states that the Mobile Ads SDK
encrypts data in transit using TLS. Users in applicable regions can
revisit their choices in Door under “我的 (Profile) → 广告隐私 (Ad Privacy).”
4. Retention and Deletion
Local data remains on your device until you delete the related content
where Door provides that option, clear Door's app data, or uninstall
Door. Clearing app data or uninstalling the app generally removes chats,
settings, API keys, and cached files from Door's app-private storage.
Device backups or operating-system features may handle copies separately.
Door cannot delete data already processed by Google or by a remote model
provider you select. To learn about or request deletion of that data,
contact the relevant provider under its privacy policy.
5. Data Security
Door uses the Android application sandbox to protect local app data.
Built-in external services use platform-supported HTTPS/TLS transport.
If you configure a custom remote endpoint, its transport security depends
on that endpoint and provider; use HTTPS and protect your API key.
No storage or transmission method can guarantee absolute security.
6. Third-party Policies
7. Children's Privacy
Door is not specifically designed for children. If you believe a child
has provided personal information without appropriate consent, notify
the developer through the contact method below.
8. Changes to This Policy
This policy may change when app features, third-party services, or legal
requirements change. The revised policy will be posted on this page with
a new updated date at the top.
9. Contact the Developer
Developer: songttsong5-lab. For privacy questions, correction requests,
or deletion requests, use the public
Door privacy inquiry form
.
Do not publicly post API keys, complete chat logs, or other sensitive
information in an issue.