一、账户、资料与授权登录
信息包括邮箱、验证码验证挑战、加盐密码校验值、会话令牌摘要、账户 UUID、有效期和撤销记录,用于邮箱注册、登录、找回密码、安全验证及维持会话。昵称、签名、头像由你主动设置,用于个人资料。
Apple 登录使用第三方账户标识和你允许提供的姓名、邮箱等资料,用于建立登录关联和账户核验;不获取 Apple 密码。信息保存于相应账户服务,按账户存续和安全需要处理。
二、日记、分类与同步
信息包括日记正文、富文本、日期、分类、天气及地点文字、修改版本、操作标识、删除和恢复状态,用于本机记录、会员云同步、去重、冲突处理和跨设备恢复。成功同步的内容归属于当前账户,不向其他用户公开。
三、媒体与素材
信息包括你主动选择、拍摄或录制的媒体、媒体属性和日记关联;会员照片云备份处理照片(含 Live Photo 的必要配对文件)、上传对象、类型、大小、摘要、尺寸、时长及核验结果,用于保存、显示、上传、下载、额度和删除清理。Live Photo 按一张照片处理;已有视频及必要属性继续按原有身份、会员及功能规则用于查看、播放、下载、删除和必要的信息处理。未成功备份的本机文件不能被当作可从云端恢复。
系统信纸和字体请求处理必要的资源路径、时间和网络来源,用于素材分发与缓存。使用个人照片作为背景时,该照片按你使用的本机保存或同步操作处理。
四、地点、隐私锁与提醒
地点选择涉及系统定位、地图区域和搜索词,用于定位、查找与地址解析;日记记录你确认的地点文字。定位为可选权限,也可手动输入。
隐私锁的本地密码校验和锁定设置、系统生物识别验证结果用于解锁;App 不取得面容或指纹原始模板。提醒设置及系统通知授权状态用于安排日记提醒。
五、交易与导出
信息包括 Apple 商品与交易标识、交易环境、账户归属、状态及有效期,用于支付核验、交付、恢复及防止跨账户冒用;支付由 Apple 处理。
导出处理所选日记、附件及任务标识、快照摘要、格式、计次和结果状态;PDF 及其附件包在本机生成,计次回执不包含正文文件。Word 邮件导出额外处理已验证的收件邮箱、邮件正文、导出附件及投递状态,由发件和收件服务商完成传输。PDF 及其附件包交由你选择的系统分享目标处理。会员“日记分享”在本机生成单篇日记图片,并交由你选择的系统分享目标处理,不自动公开内容。
六、反馈、访问与安全
反馈包含问题类型、正文、账户关联及主动提供的联系方式,用于支持。请求来源地址及必要摘要、请求标识、状态和耗时用于安全限流、排障和防滥用;普通业务日志不主动记录密码、验证码或日记正文。资源保护还记录账号当日云读取预算及重置时间;人工账号限制保留原因、期限、操作者、时间和解除审计,用于执行、申诉复核及纠错。
规则核查和申诉可能涉及账户及会话标识、请求时间和频率、导出任务及对象标识、文件大小、结果和你主动提交的必要证明,用于核查盗用、攻击、绕过限额或其他资源滥用并纠正误判。按照实际服务记录及必要范围处理,不因规则核查额外获取无关日记或公开申诉资料;完整程序见隐私政策。
七、运行诊断
为排查崩溃、卡顿、异常退出及性能问题,启用新版诊断配置的 App 仅在你明确同意包含本次诊断说明的新版协议后初始化腾讯 Bugly iOS SDK 2.7.1.1;本机保存一次同意记录,后续启动沿用,旧版本同意或仅阅读协议不触发初始化。SDK 可能在前台或后台处理并联网发送设备标识(如 IDFV)、设备型号、操作系统版本、应用版本、崩溃堆栈及卡顿、异常退出、启动、内存和资源性能诊断。App 配置关闭系统内部版本、CPU 属性、内存/磁盘空间、网络/Wi-Fi 状态、进程内存、地区编码及越狱状态的可选采集,关闭自动页面轨迹和控制台日志;关闭这些项目不代表没有任何设备信息、性能或网络处理。自定义日志仅保留警告与错误。登录后以小陌账户 UUID 关联诊断,退出后清除该关联。
我们主动追加的业务诊断记录接口路由模板、状态、耗时、错误类型和应用版本,不主动将日记正文、密码、验证码或授权令牌写入这些诊断记录。Bugly 的信息处理规则及权利请求方式见Bugly SDK(iOS)个人信息保护规则。
产品使用统计
在你通过现有协议勾选入口明确提交包含友盟统计说明的新版同意后,由友盟移动统计(UMCommon 7.7.0、UMDevice 3.6.0;友盟同欣(北京)科技有限公司)处理功能使用、注册激活、写作留存、同步/导出可靠性及会员流程分析所需信息。旧版本同意、阅读和继续使用不触发统计初始化,未同意期间不预采或缓存待补发事件。
App 主动发送页面/入口、注册/登录方式、功能/结果类别、耗时/数量区间、登录和会员状态、购买前会员状态、套餐及交易环境等枚举,登录后使用内部账户 UUID 关联;退出、注销或换号清除绑定。SDK 基于 iOS 能力、系统授权与配置处理设备标识(如 IDFV、UMID/ZID;IDFA 等可选标识以实际授权和能力为限)、设备型号、系统/应用版本、渠道、网络类型/IP 地址、启动/会话及使用事件。由 SDK 在设备采集并联网向提供方发送,依相应目的与必要期限保存。
App 不主动向友盟发送日记正文、照片视频、地点/坐标、搜索词、邮箱、昵称、密码、验证码、交易收据或令牌;本次关闭 ASA/SKAN、进端和自动页面采集、调试日志,启用日志加密,但不把这些配置说成没有设备/网络信息处理。详见隐私政策统计说明及友盟隐私权政策;可通过本清单联系邮箱申请撤回统计同意或行使相关权利。
AI 文字整理与次数记录
触发条件为你主动选择“整理文字”,并在现有确认框点击“开始整理”。处理本篇正文、必要分段和保护标记,用于向 DeepSeek 请求文字整理;不向 AI 发送图片、视频文件或无关笔记,也不额外附带媒体地址或账户凭据。你自行写入正文的个人信息、网址或敏感内容仍属于发送范围,取消本次确认不发送正文。
小陌服务处理账户归属、请求标识、正文摘要、状态、临时整理结果、赠送/付费/预占余额及 Apple 交易标识,用于结果交付、断线恢复、防重复扣次、核验入账和退款纠正。DeepSeek 只接收整理所需文字及必要标记,不接收这些账户账务记录。
小陌不额外持久化整理原文;临时结果加密保存最长 24 小时,到期不可读取并有界清理,必要摘要和账务按相应目的及最短必要期限保存。该期限不代替第三方处理或已保存日记的期限。具体接收方、操作触发条件和权利渠道见隐私政策及第三方服务清单。
XMNotes · Agreements and Privacy
Personal Information Collection List
Version: 0.4 · Updated: October 24, 2026
1. Accounts, profiles, and authorized sign-in
Information includes email addresses, verification-code challenges, salted password verification values, session-token digests, account UUIDs, validity periods, and revocation records, used for email registration, sign-in, password recovery, security verification, and maintaining sessions. You actively set your nickname, signature, and avatar for your profile.
Sign in with Apple uses a third-party account identifier and the name, email address, or other details you allow Apple to provide, to establish a sign-in association and verify your account; it does not obtain your Apple password. Information is stored in the corresponding account service and processed according to account duration and security needs.
2. Diaries, categories, and sync
Information includes diary text, rich text, dates, categories, weather and location text, modification versions, operation identifiers, and deletion and restoration status. It is used for local records, membership cloud sync, deduplication, conflict handling, and cross-device restoration. Successfully synced content belongs to the current account and is not made public to other users.
3. Media and resources
Information includes media you actively select, photograph, or record, its attributes, and its diary associations. Membership photo cloud backup processes photos (including the necessary paired files for Live Photos), uploaded objects, types, sizes, digests, dimensions, durations, and verification results for saving, displaying, uploading, downloading, quota management, and deletion cleanup. A Live Photo counts as one photo. Existing videos and their necessary attributes continue to be used for viewing, playback, downloading, deletion, and necessary information processing under the original identity, membership, and feature rules. Local files that have not been successfully backed up cannot be treated as recoverable from the cloud.
Requests for built-in stationery and fonts process the necessary resource paths, times, and network sources for resource distribution and caching. If you use a personal photo as a background, it is processed according to your local saving or sync operation.
4. Locations, privacy lock, and reminders
Location selection involves system location services, map regions, and search terms for positioning, searching, and address resolution. A diary records the location text you confirm. Location permission is optional; you can also enter text manually.
Local password verification and lock settings for the privacy lock, and system biometric authentication results, are used for unlocking. The App does not obtain raw facial or fingerprint templates. Reminder settings and system notification permission status are used to schedule diary reminders.
5. Transactions and exports
Information includes Apple product and transaction identifiers, transaction environments, account ownership, status, and validity periods for payment verification, delivery, restoration, and preventing misuse across accounts. Apple processes payments.
Exports process selected diaries, attachments, task identifiers, snapshot digests, formats, usage counts, and result status. PDFs and their attachment packages are generated on your device; usage receipts do not contain the document body files. Word email exports additionally process the verified recipient address, email body, exported attachments, and delivery status, with transmission performed by the sending and receiving service providers. PDFs and their attachment packages are handled by the system share destination you choose. The membership “Share Diary” feature generates an image of a single diary on your device and passes it to your chosen system share destination; it does not automatically make content public.
6. Feedback, access, and security
Feedback includes the issue type, text, account association, and any contact details you actively provide, for support purposes. Request source addresses and necessary digests, request identifiers, statuses, and durations are used for security rate limits, troubleshooting, and abuse prevention. Ordinary business logs do not proactively record passwords, verification codes, or diary text. Resource protection also records each account's daily cloud-read budget and reset time. Manual account restrictions retain the reason, duration, operator, time, and lifting audit records for enforcement, appeal review, and correction.
Rule checks and appeals may involve account and session identifiers, request times and frequencies, export task and object identifiers, file sizes, results, and necessary evidence you actively submit, to investigate unauthorized use, attacks, quota circumvention, or other resource abuse and correct errors. Processing stays within actual service records and the necessary scope. Rule checks do not justify additionally obtaining unrelated diaries or making appeal materials public. See the Privacy Policy for the full procedure.
7. Runtime diagnostics
To investigate crashes, hangs, abnormal exits, and performance issues, the App with the new diagnostic configuration initializes Tencent Bugly iOS SDK 2.7.1.1 only after you explicitly agree to the updated agreement containing this diagnostic description. A consent record is saved once locally and reused on later launches. Consent to an older version or merely reading the agreement does not trigger initialization. In the foreground or background, the SDK may process and transmit over the network device identifiers (such as IDFV), device models, operating system versions, app versions, crash stacks, and diagnostics for hangs, abnormal exits, startup, memory, and resource performance. The App configuration disables optional collection of system build versions, CPU attributes, memory/disk space, network/Wi-Fi status, process memory, region codes, and jailbreak status, and disables automatic page traces and console logs. Disabling these items does not mean there is no processing of device information, performance, or network information. Custom logs retain only warnings and errors. After sign-in, diagnostics are associated with the XMNotes account UUID; this association is cleared after sign-out.
The business diagnostics we actively add record API route templates, statuses, durations, error types, and app versions. We do not proactively write diary text, passwords, verification codes, or authorization tokens into those records. For Bugly's information-processing rules and rights request channels, see Bugly SDK (iOS) Personal Information Protection Rules.
Product usage analytics
After you explicitly submit updated consent containing the Umeng analytics description through the existing agreement checkbox, Umeng Mobile Analytics (UMCommon 7.7.0 and UMDevice 3.6.0; 友盟同欣(北京)科技有限公司) processes information needed to analyze feature usage, registration and activation, writing retention, sync/export reliability, and membership flows. Consent to older versions, reading, or continued use does not trigger analytics initialization. Events are not pre-collected or cached for later transmission while you have not consented.
The App actively sends enumerated values for pages/entry points, registration/sign-in methods, feature/result categories, duration/count ranges, sign-in and membership status, pre-purchase membership status, plans, and transaction environments. After sign-in, it associates these with the internal account UUID; sign-out, account deletion, or switching accounts clears the binding. Based on iOS capabilities, system authorization, and configuration, the SDK processes device identifiers (such as IDFV and UMID/ZID; optional identifiers such as IDFA are limited by actual authorization and capabilities), device models, system/app versions, channels, network types/IP addresses, launches/sessions, and usage events. The SDK collects this information on the device and sends it to the provider over the network; it is retained for the respective purposes and necessary periods.
The App does not proactively send Umeng diary text, photos or videos, locations/coordinates, search terms, email addresses, nicknames, passwords, verification codes, transaction receipts, or tokens. This configuration disables ASA/SKAN, inbound collection, automatic page collection, and debug logs, and enables log encryption. These settings do not mean device/network information is not processed. See the Privacy Policy's analytics description and the Umeng Privacy Policy. You may use the contact email in this list to request withdrawal of analytics consent or exercise related rights.
8. Retention and management
The above information is stored on the device, in account services, or with the relevant providers as required by each feature, and is handled according to the shortest necessary retention period, deletion and account deletion processes, and legal retention requirements. For the full rules, see the Privacy Policy; for the processors, see Third-Party Services and Components.
You can manage your profile, diaries, permissions, or account deletion on the relevant pages. Information rights requests you cannot complete directly may be sent to xiaomonotes@163.com, without being restricted by membership export-tool permissions.
AI text organization and usage records
Processing is triggered when you actively select “Organize Text” and click “Start Organizing” in the existing confirmation dialog. It processes this diary's text and necessary segmentation and protection markers to request text organization from DeepSeek. Images, video files, and unrelated notes are not sent to AI, and media addresses or account credentials are not additionally attached. Personal information, URLs, or sensitive content that you write into the text yourself remain within the transmission scope. Canceling this confirmation does not send the text.
The XMNotes service processes account ownership, request identifiers, text digests, status, temporary organized results, free/paid/reserved balances, and Apple transaction identifiers for result delivery, recovery after disconnection, prevention of duplicate credit deductions, purchase verification and crediting, and refund corrections. DeepSeek receives only the text and necessary markers needed for organization, not these account and billing records.
XMNotes does not additionally persist the original text submitted for organization. Temporary results are stored encrypted for no longer than 24 hours; they become unreadable on expiration and are cleaned up in bounded batches. Necessary digests and accounting records are retained for their respective purposes and the shortest necessary periods. This period does not replace third-party processing periods or retention periods for saved diaries. For specific recipients, action triggers, and rights channels, see the Privacy Policy and the Third-Party Services List.
一、帳戶、資料與授權登入
資訊包括郵箱、驗證碼驗證挑戰、加鹽密碼校驗值、會話權杖摘要、帳戶 UUID、有效期和撤銷記錄,用於郵箱註冊、登入、找回密碼、安全驗證及維持會話。暱稱、簽名、頭像由你主動設定,用於個人資料。
Apple 登入使用第三方帳戶標識和你允許提供的姓名、郵箱等資料,用於建立登入關聯和帳戶核驗;不獲取 Apple 密碼。資訊保存於相應帳戶服務,按帳戶存續和安全需要處理。
二、日記、分類與同步
資訊包括日記正文、富文本、日期、分類、天氣及地點文字、修改版本、操作標識、刪除和恢復狀態,用於本機記錄、會員雲同步、去重、衝突處理和跨設備恢復。成功同步的內容歸屬於當前帳戶,不向其他使用者公開。
三、媒體與素材
資訊包括你主動選擇、拍攝或錄製的媒體、媒體屬性和日記關聯;會員照片雲備份處理照片(含 Live Photo 的必要配對檔案)、上傳物件、類型、大小、摘要、尺寸、時長及核驗結果,用於保存、顯示、上傳、下載、額度和刪除清理。Live Photo 按一張照片處理;已有影片及必要屬性繼續按原有身份、會員及功能規則用於查看、播放、下載、刪除和必要的資訊處理。未成功備份的本機檔案不能被當作可從雲端恢復。
系統信紙和字體請求處理必要的資源路徑、時間和網路來源,用於素材分發與快取。使用個人照片作為背景時,該照片按你使用的本機保存或同步操作處理。
四、地點、隱私鎖與提醒
地點選擇涉及系統定位、地圖區域和搜索詞,用於定位、查找與地址解析;日記記錄你確認的地點文字。定位為可選權限,也可手動輸入。
隱私鎖的本地密碼校驗和鎖定設定、系統生物辨識驗證結果用於解鎖;App 不取得面容或指紋原始範本。提醒設定及系統通知授權狀態用於安排日記提醒。
五、交易與匯出
資訊包括 Apple 商品與交易標識、交易環境、帳戶歸屬、狀態及有效期,用於支付核驗、交付、恢復及防止跨帳戶冒用;支付由 Apple 處理。
匯出處理所選日記、附件及任務標識、快照摘要、格式、計次和結果狀態;PDF 及其附件包在本機生成,計次回執不包含正文檔案。Word 郵件匯出額外處理已驗證的收件郵箱、郵件正文、匯出附件及投遞狀態,由發件和收件服務商完成傳輸。PDF 及其附件包交由你選擇的系統分享目標處理。會員“日記分享”在本機生成單篇日記圖片,並交由你選擇的系統分享目標處理,不自動公開內容。
六、意見回饋、訪問與安全
意見回饋包含問題類型、正文、帳戶關聯及主動提供的聯繫方式,用於支持。請求來源地址及必要摘要、請求標識、狀態和耗時用於安全限流、排障和防濫用;普通業務日誌不主動記錄密碼、驗證碼或日記正文。資源保護還記錄帳號當日雲讀取預算及重置時間;人工帳號限制保留原因、期限、操作者、時間和解除審計,用於執行、申訴復核及糾錯。
規則核查和申訴可能涉及帳戶及會話標識、請求時間和頻率、匯出任務及物件標識、檔案大小、結果和你主動提交的必要證明,用於核查盜用、攻擊、繞過限額或其他資源濫用並糾正誤判。按照實際服務記錄及必要範圍處理,不因規則核查額外獲取無關日記或公開申訴資料;完整程序見隱私政策。
七、運行診斷
為排查崩潰、卡頓、異常退出及性能問題,啟用新版診斷配置的 App 僅在你明確同意包含本次診斷說明的新版協議後初始化騰訊 Bugly iOS SDK 2.7.1.1;本機保存一次同意記錄,後續啟動沿用,舊版本同意或僅閱讀協議不觸發初始化。SDK 可能在前景或背景處理並聯網發送設備標識(如 IDFV)、設備型號、操作系統版本、應用版本、崩潰堆棧及卡頓、異常退出、啟動、記憶體和資源性能診斷。App 配置關閉系統內部版本、CPU 屬性、記憶體/磁碟空間、網路/Wi-Fi 狀態、處理程序記憶體、地區編碼及越獄狀態的可選採集,關閉自動頁面軌跡和主控台日誌;關閉這些項目不代表沒有任何設備資訊、性能或網路處理。自訂日誌僅保留警告與錯誤。登入後以小陌帳戶 UUID 關聯診斷,退出後清除該關聯。
我們主動追加的業務診斷記錄介面路由範本、狀態、耗時、錯誤類型和應用版本,不主動將日記正文、密碼、驗證碼或授權權杖寫入這些診斷記錄。Bugly 的資訊處理規則及權利請求方式見Bugly SDK(iOS)個人資訊保護規則。
產品使用統計
在你通過現有協議勾選入口明確提交包含友盟統計說明的新版同意後,由友盟移動統計(UMCommon 7.7.0、UMDevice 3.6.0;友盟同欣(北京)科技有限公司)處理功能使用、註冊啟用、寫作留存、同步/匯出可靠性及會員流程分析所需資訊。舊版本同意、閱讀和繼續使用不觸發統計初始化,未同意期間不預採或快取待補發事件。
App 主動發送頁面/入口、註冊/登入方式、功能/結果類別、耗時/數量區間、登入和會員狀態、購買前會員狀態、套餐及交易環境等枚舉,登入後使用內部帳戶 UUID 關聯;退出、註銷或換號清除綁定。SDK 基於 iOS 能力、系統授權與配置處理設備標識(如 IDFV、UMID/ZID;IDFA 等可選標識以實際授權和能力為限)、設備型號、系統/應用版本、管道、網路類型/IP 地址、啟動/會話及使用事件。由 SDK 在設備採集並聯網向提供方發送,依相應目的與必要期限保存。
App 不主動向友盟發送日記正文、照片影片、地點/坐標、搜索詞、郵箱、暱稱、密碼、驗證碼、交易收據或權杖;本次關閉 ASA/SKAN、進端和自動頁面採集、調試日誌,啟用日誌加密,但不把這些配置說成沒有設備/網路資訊處理。詳見隱私政策統計說明及友盟隱私權政策;可通過本清單聯繫郵箱申請撤回統計同意或行使相關權利。
AI 文字整理與次數記錄
觸發條件為你主動選擇“整理文字”,並在現有確認框點擊“開始整理”。處理本篇正文、必要分段和保護標記,用於向 DeepSeek 請求文字整理;不向 AI 發送圖片、影片檔案或無關筆記,也不額外附帶媒體地址或帳戶憑據。你自行寫入正文的個人資訊、網址或敏感內容仍屬於發送範圍,取消本次確認不發送正文。
小陌服務處理帳戶歸屬、請求標識、正文摘要、狀態、臨時整理結果、贈送/付費/預佔餘額及 Apple 交易標識,用於結果交付、斷線恢復、防重複扣次、核驗入帳和退款糾正。DeepSeek 只接收整理所需文字及必要標記,不接收這些帳戶帳務記錄。
小陌不額外持久化整理原文;臨時結果加密保存最長 24 小時,到期不可讀取並有界清理,必要摘要和帳務按相應目的及最短必要期限保存。該期限不代替第三方處理或已保存日記的期限。具體接收方、操作觸發條件和權利管道見隱私政策及第三方服務清單。