YiHub

APP PRIVACY

App 隐私政策

适用于 YiHub 应用及配套 Apple Watch 功能 · 更新于 2026-11-01

Read in English

本次更新:补充 2.0 的定位与主动帮助、联网查询与推荐、手册,以及每天自动排今天、到达闹钟和在外地暂停/恢复的数据处理。此前说明中的「14 天」对应常规备份轮换,不能据此认定迁移或演练副本也已清除;如你已提出删除请求,可联系我们核查具体状态。本次说明不撤销你依法享有的权利或我们已承担的义务。

YiHub 由深圳市泽润文化推广有限公司(Shenzhen Zerun Culture Promotion Co., Ltd.,下称「我们」)运营,帮助你安排、记录和持续开展行动。本说明适用于 App 及其 AI 代理服务;网站浏览另见官网隐私政策。

本地记录与备份

个人资料、头像、行动、Flag、日程安排、完成结果、累计用时、轨迹、记忆、交代记录、手册和保存的链接保存在应用本地。当前没有这些业务记录的云端同步数据库;使用 AI 时,相关内容仍可能发送处理。安装证明和 AI 连接凭证保存在设备 Keychain 中。配套 Apple Watch 从已配对的 iPhone 接收行动等必要信息,并通过手机处理相应操作。

打开底部的「设置」,可在「导出与备份」保存和导入备份。导出的文件未加密,可能包含个人资料及业务记录,请自行保管;换机或卸载前应先导出需要保留的数据。

手册正文与照片、行动上的链接,以及你确认的地点坐标和半径随业务数据进入备份。交代面板的历史、到访线索和主动卡缓存不在该业务备份内。

AI 会接收什么、由谁处理

首次使用 AI 前,App 会请你明确同意。你同意后,交代或转写的文字,以及本次功能参考的个人介绍、行动、Flag、日程、记忆、完成结果、轨迹和近期交代等上下文,可能经 YiHub 小云发送给 DeepSeek,用于理解交代、安排与修改、记忆整理、接续判断及轨迹回顾。不是只发送你刚输入的一句话。

小云部署在腾讯云的中国大陆服务器。模型服务由 DeepSeek 开放平台提供,其公开协议列明运营主体为杭州深度求索人工智能基础技术研究有限公司。境外使用 AI 也会将上述内容传送至中国大陆的小云,并转交 DeepSeek。DeepSeek 的公开规则和说明可参阅其开放平台协议、其纳入的服务协议及隐私政策。其一般隐私政策并非对经 YiHub 提交的终端用户数据处理的完整说明;本账户 API 的具体保留、训练退出和删除协助尚未逐项确认。我们不承诺该 API 零留存、不用于训练,或在你删除 YiHub 数据时同步删除服务商的全部副本。

你可以拒绝使用 AI,继续使用本地功能。不要提交你不愿发送给上述服务商的敏感内容;截图、日历或交代涉及他人资料时,也请避免提供无关信息,并确保有权提供。

开启 AI 且具备使用资格时,每天首次打开可自动排今天;你也可以说一句要求重新排。这两种请求会发送本次候选行动的标题、所属 Flag 名称、截止日期、时长、投入档、原时刻和可用空档,以及相关习惯、当天已有交代和实际结果。重新排还会发送当前和先前的要求,以及今天不可挪动安排的标题、时刻和原因。Apple 日历占用和硬约束先在手机上换算为空档,这两种请求不另附 Apple 日历事件的标题、备注或地点;你自己写进要求、习惯或交代记录的内容仍可能包含这些信息。

普通交代还可参考当天的操作、完成和卡片选择摘要,以及今天最近八轮原话;「另起一段」只清原话层,不清当天摘要。白天发现 Apple 日历冲突后的自动挪动由手机按规则处理,不为这一步调用 AI;相关已保存安排和操作结果,之后使用 AI 时仍可能作为上下文发送。

联网查询、读取链接与保存

联网查询和读取链接经 YiHub 小云调用 DeepSeek 的搜索/网页读取服务。搜索接口的内容字段是查询词和结果数量,读取接口的内容字段是网址;这些接口不另附完整行动、日历、记忆或手册。App 发给小云的请求还携带必要的鉴权、计次及可选推荐标识;这些 YiHub 标识不转交 DeepSeek。查询词或网址本身可能包含你交代的内容;生成查询、理解网页和形成回复的 AI 请求仍可能使用上文所述业务上下文,不能理解为整个联网过程只发送几个关键词。

查询结果可包含来源标题、网址和摘要。保存在行动上的链接及其说明留在本机并进入备份;使用 AI 时,相关链接文字可作为上下文发送。主动打开外部链接后,目标网站按自己的规则处理访问。小云记录联网用量及推荐登记等必要元数据;Plus 每月 100 次联网交代、免费体验及推荐收尾的计次规则见服务条款。

Flag 主动推荐

在 AI 和「联网推荐」开启、具备相应使用资格时,YiHub 可为进行中的 Flag 查找下一步机会。发给 AI 的相关内容可包括 Flag 名称、目标、方向与期限,关联行动的标题、状态、说明和日期,近期完成、进展和相关交代,以及角色设置;AI 还可按需要读取相关业务记录。搜索仍走上述小云与 DeepSeek 路径。推荐卡保存在本机,不会自动替你报名、下单或完成行动。

你可以在「设置 → 提醒 → 主动帮助」关闭「联网推荐」,停止后续自动推荐并隐藏该类主动卡;关闭「使用 AI」可停止后续 AI 请求。已登记推荐的免费收尾有期限和请求上限,并非永久或无限免费,具体见服务条款。

日本用户的境外处理补充

上述传送的目的地包括中国。关于中国个人信息保护制度及依法向主管机关提供信息的情况,可参阅日本个人信息保护委员会的中国制度说明;其中基础调查时点为 2022 年,不代表对当前所有制度的全面审定。YiHub 本方采用 HTTPS 传输、连接凭证核验和安装隔离,业务正本保存在设备本地。DeepSeek 的公开 API 材料未逐项说明本账户正文保留、训练退出和删除协助的具体安排,因此我们尚不能提供这些更具体的保证;其公开规则见上文。你可以拒绝 AI、继续使用本地功能,也可联系我们请求进一步说明。

截图识别

你主动选择或通过快捷指令交给 App 的截图,由 iPhone 在本地提取文字;原图不发送给 YiHub 小云或 DeepSeek。为了理解截图语境,整屏提取的文字及行位置会先发送给 AI,不仅是最终勾选的事项。之后,相关事项及原文依据进入正常交代流程,供你检查、确认并创建行动。请先检查截图中是否包含不愿发送的内容。

手册与识字

手册正文和你选择保存的照片在本机保存并进入备份。照片识字使用设备上的系统能力,照片文件不上传小云或 DeepSeek。使用交代或「按 SOP 安排」时,手册名称及按需要读取的正文、照片说明、已插入正文的识字文字可能发送给 AI;按 SOP 生成的行动草稿由你确认后保存,原手册不会因此被改写。

语音、手表与系统权限

iPhone 的按住说话使用麦克风和设备上的系统转写能力,YiHub 不保存录音文件,也不向小云或 DeepSeek 上传该录音;提交的转写文字按上述 AI 规则处理。需要的语音资源可能由系统下载。你可以拒绝麦克风权限,改用文字。

Apple Watch 使用 Apple 提供的系统输入/听写界面,文字传给配对手机后进入相应流程。系统听写是否联网及其录音处理由 Apple、设备和系统设置决定,不能理解为 YiHub 保证所有手表听写均离线;适用 Apple 的隐私说明。

Apple 日历权限用于读取日程、显示占用和避开冲突,YiHub 当前不会创建、修改或删除 Apple 日历内容。你选择「导入为 YiHub 行动」后,带具体时间的事件会一次性复制为本机的普通行动,此后按业务记录处理,不再跟随 Apple 日历变化。普通交代仍可能把有关日程信息作为 AI 上下文发送,自动排与重新排的范围见上文。地点和城市到达消息使用系统的时效性通知,仍受通知权限、时效性开关和系统投递影响;你可以在 iPhone「设置 → 通知 → YiHub」管理。它不等于保证静音时响铃;系统闹钟另需 AlarmKit 授权。

定位、到访与在外地

「使用 App 期间」的位置权限用于你设置的地点和城市到达系统提醒,以及打开 App 时判断行程中的到达或返回。「始终允许」支持三种你开启的用途:到访后建议补记、到达闹钟,以及在外地自动暂停家里的周期并在返回后恢复。App 在你主动开启相关功能、查看说明后才申请,不在启动或后台自行索取授权。不授予「始终允许」仍可手动安排、记录和使用 AI;具备相应权限时,地点提醒可用系统消息,在外地的暂停/恢复则在打开 App 或点通知后判断办理。

系统地点提醒、后台地点/城市监测和到访补记需要「精确位置」。开启「做过后补记」并授予「始终允许」和「精确位置」后,已开启补记的周期行动,以及当天已安排、有确认地点的单次行动,可按到访线索建议记录;单次无需逐条开启,确认后才记完成。地点范围用于允许定位误差,不保证每次经过都能识别或即时提醒。

到访匹配、到达闹钟资格和城市暂停/恢复只在手机上判断。由定位推断出的到达城市、到过地点和停留时长,以及设备定位坐标、原始到访线索和后台监测事件队列,不发送给 YiHub 小云或 DeepSeek。地点搜索使用 Apple 地图,城市识别使用 Apple 的联网逆地理编码服务,必要查询或坐标会交给 Apple 按其规则处理。你自己写入或确认的行动地点、行程城市、补记完成记录和暂停中的规则仍可作为 AI 上下文;相关卡片供 AI 使用的摘要只保留业务对象和你的选择,不带定位推断的问题或结果原文。

你确认的地点名称、坐标和半径保存在本机业务数据中并进入备份。到访补记线索只在本机保存匹配的行动/地点身份、到达及离开时间等,不保存一条连续轨迹、不进入业务备份,并标记为不随系统备份保存;只使用最近 7 天的线索,加载或刷新时清理过期缓存。

到达闹钟开启后,手机收到有效的地点进入事件,核对行动仍可提醒,再交给 AlarmKit 尝试排铃;排不上时尝试消息提醒。已在范围内时刚开启不会立即响,须离开后再进入,同一行动每天最多处理一次。完成、取消、关闭到达提醒或强提醒后撤掉对应闹钟。后台城市监测会按你保存的行程直接暂停家里的适用周期;返回或行程结束后只恢复这一趟暂停的部分,结果在助理气泡中可查看、撤销。这些判断和写入本身不调用 AI。

地点/城市监测在本机保存所设范围、关联行动或行程、最近进出状态与时间、待处理事件;到达闹钟另存当天投递资格和系统闹钟身份,用于重启恢复和防止重复,均不进入 YiHub 业务导出备份。暂停/恢复及其撤销依据属于业务记录,会随业务备份保存。自动排的当天执行状态保存在本机,已保存的安排和撤销依据也属于业务记录。

免费体验、会员与云端记录

YiHub 不要求注册登录。新人免费 30 次按设备上的应用安装登记,不先要求核验 Apple 账户;不同设备可分别获得体验次数。小云接收安装标识、安装证明及必要的连接信息,保存免费次数余量和计次记录。重装是否恢复原安装身份,取决于设备保存的凭证,不能保证重装会重新获赠。当前不再按月赠送次数。

购买、恢复或兑换 Plus 时,App 将 Apple 签发的应用/订阅交易凭证及必要核验信息发给小云,用于核实会员身份。小云保存应用交易及订阅原始交易标识、商品、状态、到期时间和续订信息,并接收或查询 Apple 的状态变化。会员恢复以购买时使用的 Apple 账户为基础;免费次数仍按安装管理。我们不接收你的 Apple 账户名、邮箱、支付卡或付款密码,付款由 Apple 处理。

为转发请求、核对资格、计次、防重复及排查故障,小云还保存请求标识、用于校验的内容哈希、模型、时间、状态和用量等元数据;内容哈希不是可阅读的交代正文。网络连接会涉及 IP 地址等技术信息,鉴权限流使用来源地址的哈希。

联网与推荐还会保存账户对应的联网月份用量、交代轮次标识、随机推荐标识、首次登记时间和已用请求数,用于核对联网余额、推荐免费收尾及防止重复登记;云端推荐登记不保存 Flag 或卡片正文。删除云端账户也会删除该账户的联网用量和推荐登记;备份仍按下述规则处理。

正文缓存、保留与删除

小云应用不把 AI 请求或回复正文写入数据库或应用日志,相应数据库备份不包含这些正文。为在断线后返回同一次请求的结果,回复可在服务器内存中短暂缓存,当前缓存期限最多 10 分钟,也可能更早清除。这项说明不代表 DeepSeek 不缓存、不保存或不使用收到的内容。

联网查询词、读取的网址和网页正文也不写入小云数据库或应用日志;联网结果同样可在服务器内存中缓存最多 10 分钟。推荐免费期届满不等于其登记记录立即删除,登记元数据仍适用下面的保留规则。

账户、订阅及运行元数据在提供服务、核对权益和用量、排查故障及履行适用法律义务所需期间保存;当前没有对所有类别统一设定按天自动删除的期限。常规数据库备份按备份任务轮换,迁移、恢复演练或故障处理副本可能采用不同的保留周期;不能将常规备份轮换理解为所有副本都在 14 天内删除。你可以通过下述入口删除云端账户,或联系我们提出具体数据请求。

你可以怎样控制

为维持删除状态、防止旧请求恢复账户及重复赠送,小云会保留安装或应用交易标识的摘要、证明摘要、删除时间和删除代际等必要标记,不保存交代正文。同一安装删除后重新开启 AI 不会重新赠送 30 次;需要使用已有会员时可恢复购买。删除 App、删除本地数据或取消订阅不会自动删除云端账户;删除云端账户也不会取消 Apple 订阅,停止续费请到 Apple 订阅管理。

你可以在适用法律范围内请求查询、访问、更正、删除、限制有关处理或撤回同意,并就处理方式提出问题或投诉。请通过下方邮箱说明请求;我们会根据涉及的数据、适用要求和必要的身份核实处理,不要求你发送密码或完整交易凭证。Apple、DeepSeek 及邮件服务中的数据还须按各自规则处理。

反馈、邮件与广告

TestFlight 反馈可能由 Apple 向开发者提供你提交的截图、文字、设备、崩溃和测试信息,适用 Apple 的 TestFlight 规则和隐私政策。支持邮件包含你的邮箱地址及主动提供的内容,经邮件服务传输和保存,用于回复、排查及处理数据请求;保留以这些用途及适用义务所需为限。请勿发送密码、验证码或 API Key。

YiHub 不接入广告投放或跨应用广告追踪,不出售个人信息。用量记录用于提供服务、计算次数、排查问题和管理成本。

联系与更新

隐私和数据请求由运营公司深圳市泽润文化推广有限公司受理:liuxiao@yihub.chat。如处理方式变化,我们会更新说明和日期;需要新的 AI 数据授权时,会在 App 中告知并取得同意。此说明不限制适用法律赋予你的权利。


App Privacy Policy

YiHub and its companion Apple Watch features · Updated 1 November 2026

中文说明

What changed: this update adds location and proactive help, web lookup and recommendations, manuals, daily automatic planning, arrival alarms and pausing or resuming routines while away. The earlier “14 days” describes routine backup rotation; it does not establish that migration or rehearsal copies have also been removed. If you have submitted a deletion request, contact us to check its specific status. This update does not cancel your legal rights or obligations we have already undertaken.

YiHub is operated by Shenzhen Zerun Culture Promotion Co., Ltd. (深圳市泽润文化推广有限公司, “we”). This policy covers the app and its AI proxy service. Website browsing is covered by our Website Privacy Policy.

Local records and backups

Your profile, avatar, actions, Flags, schedules, completion results, accumulated time, activity history, memories, instructions, manuals and saved links are stored locally in the app. There is currently no cloud database synchronising these business records, although relevant information may be sent for AI processing. Installation proofs and AI connection credentials are kept in the device Keychain. The companion Apple Watch receives necessary information from the paired iPhone and uses the phone to process relevant operations.

Open the Settings tab, then choose Export & Backup to export or import a backup. Exported files are not encrypted and may contain personal and business records; keep them secure and export records you need before changing devices or uninstalling.

Manual text and photos, action links, and the coordinates and radii of places you confirm are included in business-data backups. Instruction-panel history, visit clues and proactive-card caches are not included in those backups.

Information sent to AI and its recipients

The app asks for your explicit permission before you first use AI. After you agree, your typed or transcribed instructions, together with information relevant to the feature, may be sent through the YiHub proxy to DeepSeek. Context can include your introduction, actions, Flags, schedules, memories, completion results, activity history and recent instructions. It is not limited to the sentence you just typed. Uses include understanding instructions, arranging or updating actions, organising memories, deciding follow-up steps and reviewing activity.

The proxy runs on Tencent Cloud servers in mainland China. The model service is provided through the DeepSeek Open Platform; its public agreement identifies the operator as 杭州深度求索人工智能基础技术研究有限公司. Using AI outside mainland China also transfers the information described above to the mainland China proxy and onward to DeepSeek. DeepSeek’s public rules and information can be found in its Open Platform Terms, the incorporated Terms of Use and its Privacy Policy. Its general privacy policy is not a complete explanation of how end-user data submitted through YiHub is processed; this API account’s specific retention, training opt-out and deletion-assistance arrangements have not been individually confirmed. We do not promise zero API retention, exclusion from training, or simultaneous deletion of all provider copies when you delete YiHub data.

You can decline AI and continue using local features. Do not submit sensitive information you do not wish to send to these providers. Where screenshots, calendars or instructions include other people’s information, avoid unnecessary content and ensure you are entitled to provide it.

With AI enabled and access available, YiHub can arrange today when you first open it each day; you can also give a short request to rearrange today. These requests send candidate action titles, Flag names, deadlines, durations, effort levels, original times and available time slots, together with relevant preferences and that day’s instructions and actual results. Rearranging also sends your current and earlier requirements, plus the titles, times and reasons for arrangements that cannot be moved. Apple Calendar busy time and hard constraints are converted into available slots on your phone; these two requests do not separately attach Apple Calendar event titles, notes or locations. Requirements, preferences or instruction records you wrote may still contain such information.

Ordinary instructions can also use summaries of that day’s operations, completions and card choices, plus the original wording of the day’s eight most recent instructions. Starting a new segment clears only the original-wording layer, not the daily summary. Automatic moves in response to daytime Apple Calendar conflicts are handled by rules on the phone, without an AI call for that step. Saved arrangements and operation results may later be sent as context when you use AI.

Web search, reading links and storage

Web search and link reading use DeepSeek’s search and webpage-reading services through the YiHub proxy. The search endpoint’s content fields are the query and result count; the reading endpoint’s content field is the URL. These endpoints do not separately attach full actions, calendars, memories or manuals. App-to-proxy requests also carry necessary authentication, usage and optional recommendation identifiers; these YiHub identifiers are not forwarded to DeepSeek. A query or URL may itself contain information from your instructions. AI requests that formulate queries, interpret pages or prepare replies may still use the business context described above; the overall process is not limited to sending a few keywords.

Results may contain source titles, URLs and summaries. Links and descriptions saved on actions remain on your device and are included in backups; relevant link text may be sent as AI context. When you open an external link, the destination handles visits under its own rules. The proxy records necessary metadata for web usage and recommendation registration. See the Terms of Service for Plus’s 100 web-enabled instructions per month, free-trial use and recommendation follow-up limits.

Proactive Flag recommendations

When AI and Web recommendations are enabled and you have the required access, YiHub may search for next steps for active Flags. Relevant information sent to AI can include the Flag’s name, goal, direction and deadline; related action titles, status, notes and dates; recent completions, progress and related instructions; and role settings. AI may also read relevant business records as needed. Searches use the proxy and DeepSeek path above. Recommendation cards are stored locally and do not automatically enrol you, place orders or mark actions complete.

Turn off Web recommendations under Settings → Reminders → Proactive help to stop subsequent automatic recommendations and hide that category’s proactive cards. Disabling Use AI stops subsequent AI requests. Free follow-up for registered recommendations has a time limit and request cap; it is not permanent or unlimited. See the Terms of Service.

Additional overseas-processing information for users in Japan

The destinations described above include China. For information on its personal-information protection system and disclosures to authorities under local law, see the Japanese Personal Information Protection Commission’s China information. Its underlying research dates to 2022 and is not a complete assessment of all current rules. YiHub uses HTTPS, connection-credential verification and installation isolation, while the primary business records remain on your device. DeepSeek’s public API materials do not individually set out this account’s specific arrangements for content retention, training opt-out or deletion assistance, so we cannot currently give more specific assurances on those points; its public rules are linked above. You may decline AI and keep using local features, or contact us for further information.

Screenshot recognition

Text is extracted locally on the iPhone from screenshots you select or pass to the app through a Shortcut. The original image is not sent to the YiHub proxy or DeepSeek. To understand the screen, the full extracted text and line-position information are first sent to AI, not just the tasks you eventually select. Relevant items and supporting source text then enter the normal instruction flow for your review, confirmation and action creation. Check screenshots for information you do not wish to send.

Manuals and text recognition

Manual text and photos you choose to save are stored locally and included in backups. Photo text recognition uses on-device system capabilities; photo files are not uploaded to the proxy or DeepSeek. When you give instructions or arrange actions from an SOP, manual names and relevant text, photo descriptions and recognised text inserted into the manual may be sent to AI. You confirm the proposed actions before saving them; this does not rewrite the original manual.

Voice, Apple Watch and system permissions

Press-to-speak on iPhone uses the microphone and on-device system transcription. YiHub does not save recording files or upload that audio to the proxy or DeepSeek. Submitted transcripts follow the AI rules above. The system may download required speech resources. You can decline microphone access and type instead.

Apple Watch uses Apple’s system input or dictation interface. Text is passed to the paired iPhone for the relevant flow. Whether system dictation uses a network and how its audio is processed depend on Apple, the device and system settings; we do not guarantee that all Watch dictation is offline. Apple’s privacy information applies.

Calendar permission lets YiHub read Apple Calendar events, display busy time and avoid conflicts. YiHub currently does not create, change or delete Apple Calendar events. If you choose to import events as YiHub actions, timed events are copied once into ordinary local actions, which are then treated as business records and no longer follow Apple Calendar. Ordinary instructions may still include relevant calendar information as AI context; the scope for automatic planning and rearranging is described above. Place and city-arrival messages use system Time Sensitive notifications, subject to notification permission, the Time Sensitive setting and system delivery. Manage them under iPhone Settings → Notifications → YiHub. This does not guarantee sound in silent mode; system alarms require separate AlarmKit permission.

Location, visits and being away

While Using the App location permission supports place and city-arrival system reminders you set, and checks for arrival or return when you open the app. Always permission supports three uses you enable: visit follow-up, arrival alarms, and automatically pausing home routines while away and resuming them on return. The app requests permission only after you actively enable a relevant feature and see an explanation, not automatically at launch or in the background. Without Always access, manual planning, recording and AI remain available; with the relevant permissions, place reminders can use system messages, and away-related pause or resume checks run when you open the app or its notification.

System place reminders, background place and city monitoring, and visit follow-up need Precise Location. With Log after a visit enabled and Always and Precise Location granted, visit clues can prompt logging for recurring actions with visit logging enabled and one-off actions scheduled for that day with a confirmed place. One-off actions need no individual switch; completion is recorded only after confirmation. Place ranges allow for positioning error and do not guarantee detection or immediate delivery every time you pass by.

Visit matching, arrival-alarm eligibility and city-related pause or resume decisions run only on your phone. Location-derived inferences about city arrivals, places visited or time spent there, along with device coordinates, raw visit clues and the background monitoring event queue, are not sent to the YiHub proxy or DeepSeek. Place search uses Apple Maps, and city identification uses Apple’s network-based reverse geocoding; necessary queries or coordinates are sent to Apple under its rules. Business content you write or confirm, such as action places, trip cities, completed-action records and paused routines, can still enter AI context. AI summaries of related cards retain only the business object and your choice, without the original location-derived questions or results.

Confirmed place names, coordinates and radii are stored in local business data and included in backups. Visit-follow-up clues retain matched action and place identities, arrival and departure times and similar information only on the device, without a continuous movement trail or inclusion in business-data backups; their storage is also marked as excluded from system backups. Only clues from the last seven days are used; expired cache entries are removed when loaded or refreshed.

With an arrival alarm enabled, the phone receives a valid place-entry event, checks that the action is still eligible and asks AlarmKit to schedule an alarm; if scheduling fails, it attempts a message reminder. Enabling it while already inside the area does not ring immediately: you must leave and enter again. Each action is handled at most once per day. Completing or cancelling it, or turning off arrival reminders or strong reminders, removes its alarm. Background city monitoring can directly pause eligible home routines for your saved trip. On return or after the trip ends, only routines paused for that trip are resumed; results can be viewed and undone in the assistant bubble. These decisions and writes do not themselves call AI.

Place and city monitoring stores configured ranges, related action or trip identities, the latest inside/outside state and time, and pending events on the device. Arrival alarms also keep the day’s delivery eligibility and system alarm identities for restart recovery and duplicate prevention. These are not included in YiHub business-data export backups. Pause and resume results and their undo records are business data and are included in those backups. The daily automatic-planning run status stays on the device; saved arrangements and their undo records are also business data.

Free use, membership and cloud records

YiHub does not require registration or sign-in. The initial 30 free AI uses are registered for the app installation on each device, without first requiring Apple-account verification. Different devices may receive separate allowances. The proxy receives an installation identifier, proof of installation and necessary connection information, and records the allowance and usage. Whether a reinstall retains its earlier installation identity depends on credentials kept by the device; reinstalling does not guarantee a new allowance. There is no monthly free top-up.

When you purchase, restore or redeem Plus, the app sends Apple-signed app or subscription transaction credentials and necessary verification information to the proxy. It records app and original subscription transaction identifiers, product, status, expiry and renewal information, and receives or queries Apple status changes. Membership restoration is based on the Apple account used for the purchase; the free allowance remains installation-based. We do not receive your Apple account name, email address, payment card or payment password. Apple handles payments.

To forward requests, check access, count use, prevent duplicates and investigate faults, the proxy also keeps request identifiers, verification hashes of content, model, time, status and usage metadata. These hashes are not readable copies of your instructions. Network connections involve technical information such as IP addresses; authentication rate limits use a hash of the source address.

Web lookup and recommendations also retain account-associated monthly web usage, instruction-turn identifiers, random recommendation identifiers, initial registration times and request counts to check allowances, free follow-up and duplicate registrations. Cloud recommendation registrations do not store Flag or card content. Cloud-account deletion also removes that account’s web usage and recommendation registrations; backups follow the rules below.

Content caching, retention and deletion

The proxy application does not write AI request or reply bodies to its database or application logs; backups of that database therefore do not contain those bodies. Replies may be cached briefly in server memory to return the same request’s result after a connection failure. The current cache lifetime is at most 10 minutes and entries may be cleared sooner. This does not mean DeepSeek does not cache, retain or use received content.

Search queries, fetched URLs and webpage bodies are likewise not written to the proxy database or application logs. Web results may also be cached in server memory for at most 10 minutes. Expiry of free recommendation follow-up does not immediately delete its registration; that metadata follows the retention rules below.

Account, subscription and operational metadata are retained as needed to provide the service, check entitlement and usage, investigate faults and comply with applicable legal obligations. Not every category currently has a uniform automatic deletion period measured in days. Routine database backups rotate under the backup process; migration, recovery-rehearsal or troubleshooting copies may have different retention periods. Routine rotation does not mean every copy is deleted within 14 days. You can delete the cloud account or contact us about specific data using the routes below.

Your controls

To maintain deletion, prevent older requests from reviving an account and prevent repeated gifts, the proxy retains necessary markers such as a hash derived from an installation or app-transaction identifier, proof hash, deletion time and deletion generation, without instruction bodies. Re-enabling AI after cloud-account deletion on the same installation does not grant another 30 uses; restore purchases to use an existing membership. Uninstalling, deleting local data or cancelling a subscription does not automatically delete the cloud account. Deleting the cloud account does not cancel an Apple subscription; use Apple’s subscription management to stop renewal.

Where applicable law provides, you may request information, access, correction, deletion, restriction or withdrawal of consent, and raise questions or complaints about processing. Email the address below with your request. We handle it according to the data involved, applicable requirements and necessary identity checks; do not send passwords or full transaction credentials. Data held by Apple, DeepSeek or email providers is also subject to their respective rules.

Feedback, email and advertising

For TestFlight feedback, Apple may provide developers with screenshots and text you submit, device details, crash reports and testing information, subject to TestFlight rules and Apple’s privacy policy. Support email includes your address and the content you provide; email services transmit and store it so we can reply, investigate and handle data requests. Retention is limited by those purposes and applicable obligations. Do not send passwords, verification codes or API keys.

YiHub has no advertising or cross-app advertising tracking and does not sell personal information. Usage records support service provision, allowance counting, troubleshooting and cost management.

Contact and updates

Privacy and data requests are handled by Shenzhen Zerun Culture Promotion Co., Ltd.: liuxiao@yihub.chat. We update this policy and its date when processing changes. Where new AI data permission is needed, the app will explain and ask for consent. This policy does not limit rights granted by applicable law.