English
1. Scope and operator
This policy applies to the overseas Android version of Bluff King, package com.luming.bluffking, and its companion player-card page hosted on GitHub Pages. The project is maintained by the Bluff King developer (“we”).
2. Data used by the app
| Data | Where it is processed | Purpose |
| Player names entered for a round | On the host device and inside that round’s QR fragment | Assign seats and show each player’s role |
| Local nickname | Private app storage | Display the local Mine profile |
| Round total and recent round details: time, card word, language, player count and outcome | Private app storage; up to 100 detailed records | Show local history and unlock played cards |
| Unlocked card identifiers and locally generated card sets | Private app storage; up to 40 generated sets | Show definitions, reuse cards offline and start a round from a selected set |
| Create chat messages, recent chat context, selected language and confirmed theme | Sent to the DeepSeek API only after you tap Send or Generate | Discuss a theme and generate a card set |
No account is required. The app does not request location, contacts, photos, files, microphone, camera, advertising ID or payment data. It requests Internet and network-state access solely for the optional Create feature.
3. Default offline gameplay
Setup, card selection from bundled/local cards, role assignment, QR creation, accusation and settlement run on the host device. These operations do not contact the WeChat backend or a Bluff King game server.
4. Optional DeepSeek processing
DeepSeek is used only in Create. Tapping Send transmits the Create conversation context and language instructions; tapping Generate transmits the confirmed theme, language and card-generation instructions. We do not intentionally include your nickname, round history, player list or unlocked-card history in those requests. Avoid entering personal, confidential or sensitive information in Create.
Requests are sent over HTTPS directly to DeepSeek. DeepSeek may process technical information such as IP address under its own terms. Review the DeepSeek Privacy Policy.
5. Shared QR and GitHub Pages
One shared QR contains the entire round, including player names, roles, the card word, hints and the Honest player’s definition. It is an honor-system design: anyone with the QR can deliberately inspect another seat or decode the payload. Share it only with participants.
The payload is stored after # in the URL fragment. Browsers do not send that fragment to GitHub in the HTTP request, and the player page decodes it locally without calling a business API. GitHub Pages may still receive ordinary hosting data such as IP address, browser details and request time under GitHub’s own policy. Screenshots, browser history or forwarded URLs may retain the fragment.
6. Sharing, sale and tracking
We do not sell personal data. The app contains no advertising or analytics SDK. Data is disclosed only as described above: to DeepSeek when you explicitly use Create, to participants through the QR you display, and to infrastructure providers for ordinary HTTPS/static-page delivery.
7. Retention, deletion and backup
Local data remains until you clear the app’s storage or uninstall it. Android backup may copy or restore app data depending on your device and Google account settings. You can delete local data through Android Settings → Apps → Bluff King → Storage → Clear storage, or by uninstalling the app. DeepSeek and GitHub retain service data according to their own policies.
8. Security and children
Local records use Android private app storage and network requests use HTTPS, but no system is completely secure. This party game is not designed to knowingly collect children’s personal information. Children should not submit personal or sensitive information through Create and should use the app with appropriate adult guidance.
9. Changes and contact
We may update this policy when the app or legal requirements change. The effective date above will be updated. For privacy questions or requests, open an issue in the public Bluff King GitHub repository. Do not include sensitive information in a public issue.
Back to top ↑
中文
1. 适用范围与运营者
本政策适用于 胡扯王 / Bluff King 海外 Android 版(包名 com.luming.bluffking)及其托管在 GitHub Pages 的玩家卡静态页。本项目由胡扯王开发者(下称“我们”)维护。
2. 应用使用的数据
| 数据 | 处理位置 | 用途 |
| 每局输入的玩家姓名 | 主持人设备及该局二维码的 URL fragment | 分配座位并向玩家展示角色 |
| 本地昵称 | 应用私有存储 | 展示“我的”本地资料 |
| 累计对局数及近期明细:时间、词语、语言、玩家人数和胜负结果 | 应用私有存储;最多保存 100 条对局明细 | 展示本地历史并解锁玩过的词卡 |
| 已解锁词卡标识和本地生成词卡组 | 应用私有存储;最多保存 40 个生成词卡组 | 展示释义、离线复用词卡及用指定词卡组开局 |
| “胡说”聊天消息、近期聊天上下文、所选语言和确认的主题 | 仅在您点击“发送”或“生成”后发送给 DeepSeek API | 讨论主题并生成词卡组 |
应用无需注册账号,不申请位置、联系人、照片、文件、麦克风、相机、广告标识符或支付数据。应用仅为可选的“胡说 / Create”功能申请网络与网络状态权限。
3. 默认离线玩法
玩家设置、从预装或本地词库抽卡、角色分配、生成二维码、指认和结算均在主持人设备本地完成,不访问微信后台或胡扯王游戏服务器。
4. 可选的 DeepSeek 处理
DeepSeek 仅用于“胡说 / Create”。点击“发送”时会传输该页面的聊天上下文和语言指令;点击“生成”时会传输已确认主题、语言和词卡生成指令。我们不会有意在请求中加入您的本地昵称、对局历史、玩家名单或解锁历史。请勿在聊天中输入个人、机密或敏感信息。
请求通过 HTTPS 从应用直接发送给 DeepSeek。DeepSeek 可能依据其政策处理 IP 地址等技术信息,请阅读 DeepSeek 隐私政策。
5. 共享二维码与 GitHub Pages
一个共享二维码包含整局数据,包括玩家姓名、角色、词语、提示以及老实人的真实释义。本玩法基于线下自觉:持码者可以故意选择他人座位或自行解码。请仅向本局参与者展示。
动态数据位于网址 # 后的 URL fragment 中,浏览器发起 HTTP 请求时不会把 fragment 发送给 GitHub;玩家页只在本地解码,不调用业务 API。GitHub Pages 仍可能依据其政策接收 IP 地址、浏览器信息和请求时间等普通托管日志。截图、浏览器历史或转发的完整网址可能保留 fragment。
6. 共享、出售与跟踪
我们不出售个人数据,应用不包含广告或分析 SDK。数据只会按上述方式披露:您主动使用“胡说”时发送给 DeepSeek、您展示二维码时提供给同局参与者,以及 HTTPS/静态页服务商为提供服务而进行的常规处理。
7. 保存、删除与备份
本地数据会保留到您清除应用存储或卸载应用。Android 可能根据设备和 Google 账号备份设置备份或恢复应用数据。您可前往 Android 设置 → 应用 → 胡扯王 → 存储 → 清除存储,或卸载应用,以删除本地数据。DeepSeek 与 GitHub 按各自政策保存其服务数据。
8. 安全与儿童隐私
本地记录保存在 Android 应用私有存储中,网络请求使用 HTTPS,但任何系统都无法保证绝对安全。本聚会游戏并非为故意收集儿童个人信息而设计;儿童不应通过“胡说”提交个人或敏感信息,并应在适当的成人指导下使用。
9. 政策更新与联系
应用功能或法律要求变化时,我们可能更新本政策,并同步修改顶部生效日期。如有隐私问题或请求,请在公开的 Bluff King GitHub 仓库提交 issue;请勿在公开 issue 中填写敏感信息。
返回顶部 ↑