mingrize — Privacy

Updated November 20, 2026. This notice covers mingrize on iPhone and iPad, the web experience, and the optional account service. Availability of a particular app version is shown by its distribution channel.

Operator and contact

mingrize is a brand operated by an individual developer. For privacy questions or requests concerning your information, contact glgx2099@gmail.com. The brand name is not a claim that the operator is a registered company.

Guest reading, recitation and records on this device

You can browse the five sutras, adjust reading appearance, use bookmarks, and follow traditional recitation or the daily ritual without creating an account. Reading position, bookmarks, language and appearance preferences, and voluntarily saved ritual records are stored in the app or browser on that device. Reading progress and bookmarks are not uploaded to the account service by the reader.

The iOS practice store uses file protection and excludes its practice directory from backup. Removing the app's data, clearing browser site data, or losing the device can make local records unavailable. The app lets you remove bookmarks and saved ritual records. The separate older guest-record controls apply to the records shown there. Clearing local data and deleting an optional account are separate actions.

Read Aloud uses the system speech synthesizer on iOS. On the web, it uses the browser's available speech service, and a voice may depend on a network service provided by the browser or system. The reader supplies public sutra text to that service and does not use the microphone or send private account records to it.

Information used by the optional account service

If you choose to use private cloud records or account settings, account email, user identifier, display name, language and time zone support sign-in and settings. Passwords are stored as password hashes, and the server stores session-token hashes. Account security and recovery use permission versions, request identifiers, token hashes and record times.

If you allow practice storage, your topic choices, feedback, favorites, three-step progress, results, submitted reflection text, content versions and record times are stored with your account. Reflection text is optional and is preserved as submitted, including spaces and line breaks. Do not submit information you do not want stored.

Sign-in uses your chosen email method or Apple or Google identity service. The provider processes its own sign-in information under its policy. The email verification flow sends a six-digit code through Alibaba Cloud DirectMail over an encrypted connection. When you choose Google Sign-In, Google’s SDK privacy manifest lists name, email address, phone number, coarse location and user ID for app functionality, user ID and other data for analytics, and device ID and other usage data for analytics. The SDK also lists other data for app functionality. It declares these categories as linked to identity and declares no tracking. Google states it may use the IP address to estimate general location for fraud prevention. See Google’s sign-in disclosure. If you save birth details in your profile, your selected date, time or time uncertainty, and birth city are processed for your account and the profile features you choose. Birth details and account access are optional for the library and ritual. If you use an available signed-in situation reflection, your submitted text and selected check-in or exercise completion can be saved with that situation in your account. Notification preferences and a device delivery token are used if you choose to enable supported push notifications.

Device storage and recovery

In the iOS account implementation, entered passwords remain in the sign-in or identity-confirmation fields and request memory; they are not stored in the Energy recovery journal. The current access token normally remains in session/request memory. A refresh token is held in an API-scoped Apple Keychain vault using a device-only protection setting. Signing out or an accepted account-deletion response clears that scoped vault. Reinstalling the app must not be assumed to erase Keychain information.

Separate protected Keychain journals hold the original pending business request's identifiers, permission version and content version, or a pending permission decision. These older practice recovery journals contain neither the password nor reflection text. Unconfirmed or superseded metadata can remain across ordinary sign-out so an unknown save is not silently treated as never executed. Accepted whole-account deletion clears the current account's active and archived recovery lanes; it does not clear another account's lanes.

Account deletion has a different recovery journal: before an acknowledgement, it can contain the original authorization token, fresh reauthentication grant and request key needed to recover that exact deletion. After an accepted response, it uses the private deletion receipt and progress status and removes the original request secrets. This is not credential-free metadata. Do not share these protected recovery values.

For signed-in cloud practices, reflection drafts and results are held in transient app/view/request memory, not a durable Energy text-draft journal. This is separate from the guest file described above. Withdrawal clears visible practice/draft/export references and prevents earlier replies from restoring them. This is not a guarantee that all operating-system memory, keyboard or clipboard copies are instantly erased. The basic request transport uses an ephemeral session without an app disk response cache or cookie store; infrastructure and system copies can still exist.

Exporting creates a protected temporary file in the app's sandbox. The app attempts to remove its own export file on withdrawal, account switch, cache clear or accepted account deletion; a cleanup failure remains blocked and retryable rather than being reported as successful removal. Copies made through sharing, recipients, system services or backups are separate and cannot be recalled by the app.

Public content and older account features

The classics and ritual text are delivered as public content. Edition, language, source and license information appear in the reader. The library does not use birth details or private reflection records to select a text. Information for older optional reflection and account records appears in the storage and deletion sections below.

Storage, withdrawal and account deletion

For account-backed cloud practices, the current practice-storage setting is 365 days. This cloud setting does not govern guest records stored only on your device. The service's displayed setting governs record validity. Reading a record does not extend its expiry; some updates renew the storage period. Expired records are no longer available through ordinary service reads. Physical removal is a separate process; this notice does not promise that every copy is erased at the instant of expiry.

Withdrawing practice-storage permission clears the Energy database's saved choices, feedback, favorites, practices and operation receipts. Your permission decision and version remain so earlier requests cannot silently resume storage after you withdraw. A save whose result was unknown must not be treated as never executed or reused with a later permission version.

Deleting a single practice is not whole-account deletion. Whole-account deletion uses the separate in-app action and fresh identity confirmation. The basic server removes its account-linked service data and sessions during deletion processing. A minimal deleted-account marker and deletion-progress information can remain; a completed deletion receipt expires after 30 days. Receipt expiry does not promise instantaneous removal from every backup. If a provider authorization must be revoked, processing can remain pending; the current implementation does not specify a fixed maximum for that pending period. A pending status is not completion.

Hosting, diagnostics and other copies

This website and its account API are hosted by Alibaba Cloud in Hong Kong. The account API uses a separate database from legacy hosted services. Service delivery and security can involve network addresses, request metadata and diagnostic errors processed by hosting infrastructure. Edge-service and database diagnostic logging are configured on the existing website/shared-service host. This notice does not claim that all logging is disabled or that no infrastructure provider processes information.

The inspected existing host has scoped log-rotation configurations keeping 7 edge-service rotations and 14 service/database rotations, with size-related rules, and local database-backup files and a scheduled backup script. These are configuration and file-presence facts, not a promise of deletion after 7 or 14 days. Some private startup logs lie outside those configured path patterns. The backup script has an age-based cleanup rule, but its complete coverage, successful restoration and a fixed physical-erasure deadline have not been verified. Those existing-host observations do not establish that the account database is included in those backups.

Operational logs and backups have a separate lifecycle from practice records. Cloud snapshots, off-host copies, their locations and their removal responsibility and deadlines have not been fully verified; this is not a claim that they do not exist. Deleting a record from the active database is not a claim that every infrastructure copy has already been removed. Contact the privacy address for questions or requests about these limits.

Optional divination reflection reports

Your question and reflection stay on your device unless you choose to generate a report. The report request sends the question you confirm to Mingrize to prepare the response. Mingrize processes it for the request and does not add it to your account or save it as a server-side practice record. If you separately choose DeepSeek assistance, DeepSeek receives the confirmed question and related public scripture context to help write the response. Please remove private details before sending. You can cancel or choose the Mingrize report without DeepSeek. DeepSeek privacy policy.

Your choices and help

You can use guest features without an account and clear their local data. If you choose account-backed cloud storage, you can withdraw that permission, delete individual cloud practices, export cloud records or request account deletion. Requests to the privacy contact should not include passwords, sign-in tokens or private deletion-progress tokens. General reflection is not emergency or medical care.

Support


mingrize 隐私说明

更新于 2026 年 11 月 20 日。本说明覆盖 iPhone、iPad、浏览器版 mingrize 及可选账号服务。各版本的可用状态以其分发渠道显示为准。

运营与联系

mingrize 为个人开发者运营的品牌,不据此声明为注册公司。隐私问题或信息处理请求请联系 glgx2099@gmail.com。

免登录读经、修持与本机记录

无需注册或登录即可阅读五部经典、调整阅读外观、收藏经文,并跟随传统读诵或日用仪轨。阅读位置、书签、语言和外观偏好,以及主动保存的修持记录留在当前设备的应用或浏览器中。阅读器不会把阅读位置和书签上传到账号服务。

iOS 修持存储使用文件保护,并将修持目录设为不参与备份。移除应用数据、清除浏览器站点数据或丢失设备后,本机记录可能无法恢复。可在应用中取消书签及删除已保存的修持记录。原有游客记录使用对应页面的清理入口。清除本机记录与删除可选账号是不同的操作。

iOS 朗读使用系统语音合成。浏览器版使用浏览器可用语音,部分语音可能由浏览器或系统提供方联网处理。朗读功能只向语音服务提供公开经文,不使用麦克风,也不将私人账号记录交给语音服务。

可选账号服务的信息与用途

当你选择使用私人云端记录或账号设置时,账号邮箱、用户标识、显示名称、语言和时区用于登录及设置。服务端保存密码和会话令牌的哈希;授权版本、请求编号、令牌哈希和记录时间用于安全与恢复。允许练习存储后,主题选择、反馈、收藏、三个步骤的进度、结果、提交的复盘原文、内容版本和记录时间会与账号关联保存。复盘为可选,提交文字保留原有空格和换行;请勿提交不希望存储的信息。

登录使用你选择的邮箱方式、Apple 或 Google 身份服务。身份提供方按其政策处理登录信息。 邮箱验证使用阿里云邮件推送,通过加密连接发送六位验证码。选择 Google 登录时,Google SDK 的隐私清单声明用于应用功能的类别包括姓名、邮箱、电话号码、粗略位置、用户 ID 和其他数据,用于分析的类别包括用户 ID、设备 ID、其他使用数据和其他数据。清单将这些类别标记为与身份关联,并声明不用于跟踪。Google 说明 IP 地址可用于估计大致区域以防止欺诈。参阅 Google 登录披露说明。如果你选择保存出生资料,所填写的日期、时间或不确定选项、出生城市会用于你的账号及所选择的个人资料功能。经典阅读和修持无需登录或提供出生资料。如果登录后使用已开放的情境复盘,提交的文字、所选复访反馈或练习完成记录可能随该情境保存到账号。选择开启受支持的推送时,会使用通知偏好和设备送达令牌。

设备存储与请求恢复

iOS 账号功能中,输入的密码保留在登录或身份确认输入框及请求内存中,不存入 Energy 恢复 journal。当前访问令牌通常保留在会话和请求内存中;刷新令牌保存在按 API 隔离、采用仅限本设备保护设置的 Apple Keychain 中。退出登录或收到账号删除的接受响应后,会清除相应令牌存储。重新安装应用不应被视为已经清除 Keychain。

独立的受保护 Keychain journal 保存原待确认业务请求的标识、授权版本和内容版本,或待确认的授权决定。既有练习恢复 journal 不含密码或复盘原文。未确认或已被新版本替代的恢复元数据可能在普通退出登录后保留,避免把结果未知的保存静默当作从未执行。整账号删除被接受后,会清除当前账号的活动及归档恢复记录,不清除其他账号的恢复记录。

账号删除另有独立恢复 journal:收到确认前,可能包含用于恢复原删除请求的原授权令牌、重新验证 grant 和请求 key;收到接受响应后,改为保留私有删除回执及进度状态,并移除原请求的敏感凭据。这类记录不能笼统视为不含凭据。请勿分享这些受保护的恢复值。

已登录的云端练习,其复盘草稿与结果保留在应用、界面或请求的临时内存中,不使用持久化的 Energy 文字草稿 journal;这与上文的游客本机文件相互独立。撤回时会清除可见练习、草稿和导出引用,并阻止较早响应恢复这些内容;不据此保证操作系统内存、键盘或剪贴板中的全部副本瞬间清除。基础请求传输使用临时会话,不设置应用磁盘响应缓存或 cookie 存储;基础设施及系统副本仍可能存在。

导出会在应用沙盒中生成受保护的临时文件。撤回、切换账号、清除缓存或账号删除被接受后,应用尝试删除自身导出文件;清理失败时继续阻止相关操作并允许重试,不谎报已经删除。经分享、接收方、系统服务或备份形成的副本另有生命周期,应用不能将它们召回。

公开内容与既有账号功能

经典和仪轨正文以公开内容提供。阅读器中可查看版本、语言、来源和授权。书架不会根据出生资料或私人复盘记录选取经文。既有可选复盘和账号记录的存储及删除方式见下文。

保存、撤回与删除

账号云端练习的当前存储设置为 365 天,以服务实际显示为准;此云端期限不适用于仅存本机的游客记录。读取不延长到期时间,部分更新会续期。到期记录不能通过普通服务读取;物理清理是另一个过程,不承诺到期瞬间所有副本都已清除。

撤回练习存储授权会清除 Energy 数据库中的选择、反馈、收藏、练习及操作回执,保留授权决定和版本,以阻止旧请求在撤回后静默恢复存储。结果未知的请求不能被当作从未执行,也不能用于后来重新授权的版本。

删除单条练习不等于删除整个账号。整账号删除使用应用内独立入口并重新验证身份;基础服务端在删除处理期间清除其账号关联服务数据与会话。最小已删除账号标记及删除进度资料可能保留,完成回执在 30 天后到期;回执到期不保证所有备份瞬间清除。如需撤销第三方授权,可能继续处于处理中,现有实现尚未规定该状态的固定最长时限;处理中不等于已完成。

托管、诊断与副本

本网站与账号 API 由阿里云托管,位于香港。账号 API 使用与既有旧服务分开的数据库。网络地址、请求元数据及诊断错误可能由托管基础设施用于服务交付和安全。现有网站及共用服务主机的边缘服务和数据库已配置诊断日志,不声明全部无日志或没有基础设施提供方处理信息。

已检查的现有主机配置了按项目路径限定的日志轮转,分别保留 7 份边缘日志轮转和 14 份服务、数据库日志轮转,并包含大小相关规则;存在本地数据库备份文件及定时备份脚本。这些仅是配置与文件存在的事实,不承诺 7 天或 14 天后删除。部分私有启动日志位于这些路径规则之外。备份脚本有按文件年龄清理的规则,但完整覆盖范围、成功恢复及固定物理擦除期限尚未核实。这些现有主机事实也不证明独立账号数据库已纳入相同备份。

运行日志与备份和练习记录有不同生命周期。云快照、异地副本及其位置、清除责任和期限尚未完整核实,不据此声明它们不存在。活动数据库中的记录已删除,不等于所有基础设施副本都已清除。相关问题或请求请联系隐私邮箱。

可选的占察反观报告

所问和体会默认留在本机。选择生成反观报告并确认后,明智日常会临时处理你确认发送的问题。该问题不会加入账号或存为服务端修持记录。如果你另行同意 DeepSeek 辅助,DeepSeek 将接收你确认的问题和相关公开经文资料,用来组织报告文字。发送前请去掉私人资料。你可以取消,或选择由明智日常生成经义报告。DeepSeek 隐私政策。

你的选择

你可以免登录使用游客功能并清空其本机数据。选择账号云端存储后,可撤回云端授权、删除单条云端练习、导出云端记录或申请删除账号。联系隐私邮箱时,不要发送密码、登录令牌或私有删除进度令牌。通用反思不能替代紧急服务或医疗照护。

支持