CardChat Google Play Privacy Policy

Effective November 19, 2026 · Developer: Wang Sen (王森)

This policy applies to the Android edition of CardChat distributed through Google Play, including its closed testing releases. It does not replace the separate policies for other CardChat editions. CardChat is an AAC app used by people with communication difficulties, including children and families.

1. Data kept on your device

Cards, text, categories, schedules, selected images and videos, recordings, imported audio, scene files, progress saved by web scenes, scene training records, training plans, backups prepared in the app, preferences, trial dates, and purchase entitlement are primarily kept in the app's private storage on your device. A training plan may include a plan title, designer or recipient name, description, start date, schedule, and referenced scenes. Scene training records may include the scene name and type, question or step text, completion and answer outcome, stars earned, wrong-attempt and hint counts, skipped steps, plan context, HTML-practice summaries, and start and end times so that CardChat can show training history in the app. For the two optional lifetime products—Unlimited Cards and Scene Training—CardChat stores only the local unlocked or not-unlocked entitlement state. This edition does not require a CardChat account and does not automatically upload your cards, scenes, training plans, training records, trial dates, or entitlement state to CardChat servers. It does not include advertising or an advertising SDK.

You can edit or remove content in the app. A scene export contains the selected scenes and their scene files and thumbnails; it does not contain saved web-scene progress or web media-permission choices. Practice records are excluded by default. If you select “Export practice records”, an ordinary scene export also includes practice records and related archive information for the selected scenes. Contribution exports never include practice records. A training-plan export may contain the plan fields described above and its included scenes. Do not share export files containing private information with others. Deleting a scene removes the scene file, thumbnail, and remembered web media permission stored by CardChat for that scene. Progress saved by the webpage itself and earlier training records may remain as local app data. Clearing CardChat's app data or uninstalling the app removes the corresponding local copies. Files you exported or shared must be managed separately at their destination. Device-level backups, if enabled, are controlled by your device and Google account settings.

2. Offline web scenes

You can use Android's system file picker to import an HTML, HTM, or ZIP offline web scene. CardChat checks the file, extracts it when needed, stores the scene in the app's private storage, and runs it in an isolated web view. Each scene may save progress in its own local web storage and cannot read another scene's web storage.

Offline web scenes are loaded for offline use, and CardChat applies offline network restrictions to prevent the webpage from connecting to external websites or services. A webpage can use a limited scene interface to tell CardChat when a training run starts or finishes and whether a next action should be shown. CardChat uses this signal to update training history and stars on the device. The interface does not provide the webpage with the user's card library, other scene content, or app settings.

An offline webpage can request camera or microphone access only after the user selects the related feature on the page. CardChat asks whether to allow it once or remember the choice for that scene, and Android may also show a permission prompt. Users can revoke access from the scene's web-permission control or Android settings. When a webpage uses a system picker for a photo or file, it receives only the item selected by the user. Camera, microphone, and selected items are made available to the current scene on the device; CardChat does not upload this content as part of running the offline scene.

3. Camera, photos, microphone, and Eye Control

When you choose to add media, Android's system picker gives CardChat access only to the photos and videos you select. The app does not ask for broad photo-library access. Camera permission is requested when you choose to take a photo, start Eye Control, or allow an offline web scene to use the camera; microphone permission is requested when you choose to record audio or allow an offline web scene to use the microphone. Photos and recordings used in cards remain on your device unless you choose to export or share them. You can revoke these permissions in Android settings. Offline web-scene permissions are described in Section 2.

Optional Eye Control uses the front camera and the bundled MediaPipe model only after you start calibration or enable the feature. It calculates gaze direction, blink state, and head pose on the device to select AAC cards and controls. CardChat does not save or upload camera images. Calibration results and settings are stored locally for later use, are not shared with third parties or included in card exports, and are replaced when you recalibrate. New processing stops when Eye Control is turned off, the app leaves the foreground, or camera permission is revoked.

4. Speech and reminders

Local speech playback and voice previews use the speech facilities available on the device. The Google Play edition disables CardChat's cloud-generated audio feature: it does not send card or picture-book text to the CardChat speech relay for audio generation. You can still record or import your own audio.

If you enable schedule reminders, the app uses Android notifications and, where granted, alarm and full-screen alert access to remind you at the chosen time. Schedule content is not sent to CardChat for push notifications. You can change these permissions in Android settings.

5. Network requests and other services

The app may request version information and free-tier limits from CardChat's resource server. The Scene Library requests its catalogue, covers and previews from that server. If you choose to add a scene, the app requests that scene's download package. These requests do not upload your cards, media, schedules, local scenes, training plans, training records, or app settings.

The resource server may log standard request information, such as IP address, user agent, request time, requested resource and response status, to operate and protect the service. CardChat also counts successful package requests per scene to show aggregate download counts and rank popular scenes. The ranking does not use IP addresses or user-agent information and does not identify individual learners. CardChat does not use these logs for advertising profiles.

When you open online materials, a website, or a video outside an offline web scene, its provider receives the request and handles data under its own policy. User-entered links may be outside CardChat's control. Imported offline web scenes are handled as described in Section 2 and do not open external web content. If you export or share a backup, training plan, or media file, the destination app or service you choose receives that file. CardChat-owned network endpoints use HTTPS.

6. Voluntary scene contributions and purchases

If you choose to contribute scenes, CardChat creates a ZIP containing the selected scenes and submission details, such as the title, description, language, tags and keywords, and your choice of public attribution or anonymity. Contribution ZIP files never include practice records. You choose where to save the ZIP, then manually attach and send it from your mail app. The app does not upload the ZIP. If you send it, your mail provider handles the email and the CardChat developer receives the sender address, message and attachment for review.

If the submission is accepted, the scenes, catalogue details and attribution you elect to publish may appear in the public Scene Library and on the resource website. Choosing anonymous submission hides the author or brand name and introduction from the public listing. The developer still receives your email address when you send the submission. Remove private information from scene content and media before submitting. If you report a library scene by email, the developer receives your sender address, the reported resource, the reason and any details you choose to send, for review and moderation.

Optional lifetime purchases are processed by Google Play Billing. To show products, complete a purchase, restore access, and reflect refunds or revocations, the app queries Google Play for product details and active purchases and processes the product ID, purchase state, purchase or transaction identifier, and acknowledgement state. CardChat uses this information on the device to grant or restore the corresponding feature and to acknowledge the purchase to Google Play. It does not send purchase tokens, order details, or entitlement state to CardChat servers, and it never receives your full payment-card details. Google handles payment and purchase records under Google's privacy policy and applicable terms.

7. Retention, security, and contact

Local content stays on your device until you remove it, clear app data, or uninstall the app, subject to the details in Section 1 about web-scene progress and earlier training records. CardChat does not keep a server-side copy of that content in this edition. Clearing app data or uninstalling CardChat removes the local entitlement flag, but it does not delete Google Play's purchase record; access can be restored from Google Play. Contribution emails and accepted public submissions are managed separately from local app data. Operational records of resource-server requests may be retained only as needed to run and secure the service. To ask about information held by CardChat or request its deletion, or to raise a privacy concern concerning a child, contact leowang.lw90@gmail.com. We do not sell personal data.

Information entered in Google Play's Data safety form should be read together with this policy. If the Play edition's data practices change, this page will be updated before the changed feature is released.

CardChat Google Play 版隐私政策

生效日期:2026 年 11 月 19 日 · 开发者:王森

本政策适用于通过 Google Play 分发的 CardChat Android 版本,包括封闭测试版本,不替代 CardChat 其他版本的独立隐私政策。CardChat 是面向沟通障碍人群的 AAC 应用,也供儿童与家庭使用。

1. 保存在设备上的数据

卡片、文字、分类、日程、选取的图片和视频、录音、导入的音频、场景文件、网页场景保存的本地进度、场景训练记录、训练计划、应用内准备的备份、设置、试用日期和购买解锁状态主要保存在设备的应用私有空间。训练计划可能包含计划名称、设计者或学员名称、说明、开始日期、训练安排及引用的场景。场景训练记录可能包含场景名称和类型、题目或步骤文字、完成和作答结果、获得的星星、错误尝试及提示次数、跳过的步骤、训练计划上下文、HTML 练习摘要以及开始和结束时间,用于在应用内显示训练历史。对于“无限卡片数量版”和“场景训练终身版”两项可选买断商品,CardChat 仅在本机保存已解锁或未解锁的权益状态。本版本无需注册 CardChat 账号,不会自动把卡片、场景、训练计划、训练记录、试用日期或权益状态上传到 CardChat 服务器,也不包含广告或广告 SDK。

你可以在应用内编辑或删除内容。场景导出包含所选场景及其场景文件和缩略图,不包含网页场景的本地进度或网页媒体权限选择。普通场景导出默认不含练习记录;用户勾选“导出练习记录”后,文件会附带所选场景的练习记录及相关归档信息。投稿导出不包含练习记录。训练计划导出可能包含上文所列计划字段及其中的场景。请勿将含有隐私数据的导出文件分享给他人。删除场景会删除 CardChat 保存的场景文件、缩略图和该场景已记住的网页媒体权限;网页自身保存的本地进度和以往训练记录可能作为本机应用数据继续保留。清除 CardChat 应用数据或卸载应用会移除相应本机副本;已导出或分享的文件需在目标位置另行管理。若启用系统设备备份,备份行为受设备及 Google 账号设置管理。

2. 离线网页场景

你可以通过 Android 系统文件选择器导入 HTML、HTM 或 ZIP 离线网页场景。CardChat 会检查并在需要时解压文件,将场景保存在应用的私有空间,并在隔离的网页视图中运行。每个场景可在自己的本地网页存储中保存进度,不能读取其他场景的网页存储。

离线网页场景按离线方式加载,CardChat 会应用离线网络限制,以阻止网页连接外部网站或服务。网页可通过有限的场景接口通知 CardChat 一轮训练开始或完成,以及是否显示下一步;CardChat 据此在本机更新训练记录和星星。该接口不向网页提供用户的卡片库、其他场景内容或应用设置。

离线网页只有在用户点击网页中的相关功能后,才可请求使用相机或麦克风。CardChat 会按场景询问是否仅本次允许或记住选择,Android 也可能显示权限提示;用户可在场景中的网页权限入口或 Android 设置中撤销。网页通过系统选择器取得照片或文件时,只会收到用户选中的项目。相机、麦克风和所选项目供当前场景在设备上使用,CardChat 不会因运行离线场景而将这些内容上传到服务器。

3. 相机、照片、麦克风和眼控

你主动添加媒体时,Android 系统选择器只向 CardChat 提供你选中的照片或视频;应用不申请整个相册的广泛读取权限。你主动拍照、开启眼控或允许离线网页场景使用相机时才请求相机权限,主动录音或允许离线网页场景使用麦克风时才请求麦克风权限。用于卡片的照片和录音保存在本机,除非你自行导出或分享。你可在 Android 设置中撤销这些权限;离线网页场景的权限方式见第 2 节。

可选眼控功能仅在你主动开始校准或开启后,使用前置相机和内置 MediaPipe 模型,在设备上计算注视方向、眨眼状态和头部姿态,以选择 AAC 卡片及控件。CardChat 不保存或上传相机画面。校准结果和设置保存在本机供下次使用,不向第三方共享,也不包含在卡片导出文件中;重新校准会替换相应设置。关闭眼控、应用离开前台或撤销相机权限后,会停止新的处理。

4. 语音与提醒

本地朗读和语音试听使用设备可用的语音能力。Google Play 版暂时关闭 CardChat 云端生成音频功能,不会为生成音频而将卡片或绘本文字发送至 CardChat 语音中转服务器。你仍可自行录音或导入音频。

启用日程提醒后,应用会使用 Android 系统通知,以及在获得授权时使用闹钟和全屏提醒权限,在设定时间提醒。日程内容不会发送给 CardChat 用于远程推送。你可在 Android 设置中调整这些权限。

5. 网络请求与其他服务

应用可能从 CardChat 资源服务器读取版本信息和免费版额度。场景库会向该服务器请求目录、封面和预览;你选择添加场景时,应用会请求相应的场景包。这些请求不会上传你的卡片、媒体、日程、本机场景、训练计划、训练记录或应用设置。

资源服务器可能记录 IP 地址、User-Agent、请求时间、所请求的资源和响应状态等标准请求信息,用于运行和保护服务。CardChat 也会按场景汇总成功的场景包请求次数,用于展示下载量和热门排序。排序不使用 IP 地址或 User-Agent,也不识别个别学员。CardChat 不使用这些日志建立广告画像。

你在离线网页场景之外打开在线素材、网站或视频时,内容提供方会收到请求并按其政策处理信息。用户自行填写的链接可能不受 CardChat 控制。导入的离线网页场景按第 2 节处理,不会打开外部网页内容。你主动导出或分享备份、训练计划或媒体文件时,所选目标应用或服务会收到该文件。CardChat 自有网络端点使用 HTTPS。

6. 主动场景投稿与购买

你主动投稿时,CardChat 会生成 ZIP,其中包含所选场景及标题、简介、语言、标签、关键词和公开署名或匿名选择等投稿信息。投稿 ZIP 始终不包含练习记录。你自行选择保存位置,再在邮件客户端手动附加 ZIP 并发送。应用不会上传 ZIP。发送后,邮件服务商会处理邮件,CardChat 开发者会收到发件地址、邮件正文和附件,用于审核。

投稿审核通过后,场景、目录信息以及你选择公开的署名可能在公开场景库和资源网站展示。选择匿名时,公开页面不显示作者或品牌名称及介绍;开发者收到投稿邮件时仍可看到发件地址。投稿前请移除场景内容和媒体中的私人信息。如果你通过邮件举报场景库素材,开发者会收到发件地址、被举报的素材、举报原因及你选择提交的补充说明,用于审核和处理。

可选终身版购买由 Google Play Billing 处理。为展示商品、完成购买、恢复权益,以及同步退款或撤销结果,应用会向 Google Play 查询商品和有效购买,并处理商品 ID、购买状态、购买或交易标识及确认状态。CardChat 仅在设备上使用这些信息解锁或恢复相应功能,并向 Google Play 确认交易;不会把购买令牌、订单明细或权益状态发送到 CardChat 服务器,也不会取得完整银行卡资料。付款及购买记录由 Google 按其隐私政策和适用条款处理。

7. 保存期限、安全与联系

本机内容会保留至你删除内容、清除应用数据或卸载应用,网页场景进度和以往训练记录按第 1 节说明处理;本版本不在 CardChat 服务器保存这些内容的副本。清除应用数据或卸载 CardChat 会移除本地权益标记,但不会删除 Google Play 保存的购买记录,权益可通过 Google Play 恢复。投稿邮件和已审核发布的公开投稿与本机应用数据分别管理。资源服务器的运行记录可能仅在提供和保护服务所需期间保留。如需了解或要求删除 CardChat 持有的信息,或有涉及儿童隐私的疑问,请联系 leowang.lw90@gmail.com。我们不出售个人数据。

Google Play“数据安全”表单应与本政策一同阅读。若 Play 版的数据处理方式发生变化,我们会在相关功能发布前更新本页面。