小日历 · 更新日期:2026-11-10

隐私说明

English version below / 英文版见下方

本说明适用于小日历 iOS 和安卓版本。iOS 版通过 App Store 提供,1.2 起支持中英双语;安卓版不上应用商店,仅在 xiaorili.aistella.net 提供 APK 下载,1.3 起支持邮箱账号、同步和 App 内检查更新,1.4 起提供与 iOS 相同的提醒、出差统计和足迹等本机工具。

记录保存与联网服务

您可以不登录使用日历和记录。启用邮箱同步后,账号资料、个人记录及受支持版本的账号设置会发送至开发者自有的云服务(腾讯云中国内地广州服务器);天气、假期和人机验证也涉及第三方服务。本页说明这些数据的用途、保存位置、保留期限及删除方式。

私人记录如何保存

您输入的出差地点、起止日期、生日、其他重要日子和备注,保存在设备上本 App 的独立沙盒文件中。不登录也能使用日历和记录。访客记录不会自动上传为账号资料;这些记录也不会附带在公开天气或假期请求中。登录后的记录按下文的账号同步流程处理。

您选择的天气城市、国家或州级假日地区和公司补休开关,保存在 App 沙盒的本机设置文件中。访客与每个邮箱账号分别保存,新安装没有预设私人城市,公司补休默认关闭。安卓 1.3 起、iOS 1.3 起,登录后这些设置随账号同步至同一云服务,按账号保存;访客或未登录时只保存在本机。这些设置仍不包含在 version 1 JSON 备份中。公开天气、节假日缓存保存在 App 的本机存储中。

本 App 免费,无广告、订阅或第三方广告跟踪 SDK,不以这些数据建立广告画像。账号人机验证使用 Cloudflare 安全组件及安全分析统计,数据处理另见下文;无广告不代表没有分析或所有数据都留在设备。

当前使用本机文件保存记录,不提供独立的密码加密功能。设备本身的安全和系统备份取决于您的系统设置;iOS 和安卓的系统备份可能包含部分 App 数据,这与 App 自行提供账号云同步不同。iOS 起卦记录保存在 App 本机数据中,可能随 iPhone/iCloud 系统备份;安卓起卦记录和登录令牌已排除在系统备份之外。两端起卦记录均不随账号同步,也不包含在 App 导出的 version 1 JSON 备份文件中。

本机提醒与日历工具(iOS 1.3、安卓 1.4 起)

提醒由设备本机根据当前访客或账号的重要日子、出差记录,以及随 App 提供的节气内容生成,不为提醒上传额外数据。提醒开关和时间只保存在这台设备,不进入 version 1 JSON 备份或账号同步;开启时需允许系统通知。

出差统计、拼假助手、里程碑和生日资料都在本机计算,节气介绍随 App 提供。拼假助手使用已缓存或内置的中国大陆放假调休数据;1.4 起可选择其他国家或地区,按需获取该地区的公开假日数据(来源见下文“联网时发送哪些信息”),请求不发送私人记录;复制摘要或方案时,内容写入系统剪贴板。里程碑补充的起始年份和未知年份设置只保存在本机,不进入 App 导出的 JSON 备份或账号同步,换设备后需重新补充;原有出差和重要日子记录仍按上述规则备份和同步。本机资料仍可能随 iPhone/iCloud 系统备份。删除账号也会清除此账号在本机补充的起始年份资料。黄历及节气内容仅供民俗文化参考。

1.4 起:“足迹”页和年度足迹分享卡在本机计算和绘制。足迹地图使用随 App 提供的陆地轮廓点阵(由公有领域的 Natural Earth 陆地数据生成,不含国界),城市位置取自已保存城市的坐标或下文城市名称缓存中的坐标;坐标未知的城市不画。分享卡图片只在您点“分享图片”时生成并交给系统分享面板,可关闭“显示城市”隐藏城市名和城市点;图片不包含行程名称和备注。iOS 仅在您于分享面板选择“存储图像”时请求“添加到照片”权限。中国大陆的“公司不调休,只放法定假日”及“法定假日逢周末,顺延补休”开关只保存在本机,不随账号同步,也不进入 JSON 备份。

1.6 起:“随手记”每天一条,标题、正文、清单和照片只保存在本机 App 沙盒,不上传、不随账号同步;同一台设备上的访客和各账号共用这份随手记。照片由您在系统照片选择器中逐张选择,App 不申请照片图库权限,只保存压缩后的副本;删掉随手记或照片后,副本随之清理。导出 JSON 备份时会一并导出随手记和照片,恢复时合并到本机。

联网时发送哪些信息

获取公开天气和节假日需要 HTTPS 请求。提供方会收到请求参数及普通网络信息,包括您的网络 IP 地址;因此不能把当前版本理解为“任何数据都不会离开设备”。请求不附带您的出差、生日、备注或备份内容。

1.6 起:节日介绍随 App 提供,查看介绍不联网。在介绍里点“用必应搜索”时,App 内会打开必应(Microsoft Bing)搜索该节日名称,必应会收到搜索词以及 IP 地址等普通网络信息,并按其规则处理;只有您点按时才会打开。

Open-Meteo 的免费 API 隐私条款说明,其可能为技术维护和防滥用处理 IP 信息,排障日志可能包含请求坐标,并在 90 天后删除日志。这里传递的是您主动选择的城市坐标,不是设备实时位置。该条款没有逐字段说明免费地名搜索日志是否保存 name,不能据此断言每条搜索必然被保存 90 天。第三方的具体处理以其最新政策为准。来源:Open-Meteo Terms & Privacy及 Geocoding API 文档。其他国家假日服务的条款见 Nager Terms of Service。

其他公开数据提供方也可能接收或记录网络请求;开发者不控制其日志处理。账号人机验证使用第三方安全脚本,并包含挑战交互、来源和验证结果的安全统计,其数据流另见下文。您选择打开外部链接时,相关网站适用自己的隐私规则。

备份、分享与删除

在“更多”导出 JSON 备份,会把当前访客或账号的出差、重要日子及备注写入您选择的文件位置;不包含天气城市、常用假日地区或公司补休偏好。JSON 文件包含可直接读取的私人记录。选择 iCloud Drive、其他云盘或分享对象,是您的手动文件操作;对应服务或收件人可能获得文件内容。App 不自动把导出的备份文件上传到第三方;账号记录本身按账号同步流程处理。

恢复备份先完整校验,再由您确认替换当前访客或账号的全部记录。账号恢复后的记录可能进一步同步,访客文件仍独立保存。删除记录会更新本机当前记录文件;账号记录在下一次成功同步时更新云端资料。

记录文件损坏时,App 会保留原文件并提示读取失败;损坏的账号记录不能直接打开继续编辑。记录恢复过程可能在沙盒内保留可恢复副本。删号时会清理能明确归属于该账号的记录及恢复副本;无法归属的损坏副本会保留,避免误删其他资料,需通过卸载 App 或联系支持安排人工清理。本说明不承诺删号会擦除所有沙盒文件。

删除当前记录不会自动删除您导出的文件、别人已收到的副本或已有系统备份。要移除这些副本,请分别管理对应文件和系统备份;卸载 App 通常会移除本机 App 沙盒数据。

邮箱账号与个人同步

账号同步从 iOS 1.0 起、安卓 1.3 起提供;天气城市、假日地区和公司补休开关的设置同步从 iOS 1.3 起、安卓 1.3 起提供。

账号功能使用邮箱验证码注册或登录,无需设置密码。邮箱用于验证身份、发送账号验证码及识别您的账号。验证码邮件由腾讯云 SES 香港服务通过 noreply@mail.aistella.net 发送;1.3 起,App 会按界面语言请求中文或英文验证码邮件;英文邮件启用前统一发送中文邮件。该邮件服务接收收件邮箱和验证码邮件内容,不接收您的出差或重要日子;验证码通过普通邮件传递,不是端到端加密通信。邮件提供方和您的邮箱服务可能按各自规则处理邮件及投递记录。参见 腾讯云隐私保护声明及 Tencent Cloud Privacy Policy。

选择登录和同步后,邮箱、随机用户编号及您的出差、重要日子与备注保存在开发者自有的云服务(腾讯云中国内地广州服务器)。各账号的数据分别保存,服务端按登录身份限制访问。安卓 1.3 起、iOS 1.3 起,天气城市、假日地区和公司补休开关也按账号保存并同步至同一云服务;访客或未登录时这些设置只在本机保存。账号请求通过 https://calendar-api.aistella.net 的 HTTPS 连接传输;iOS 登录令牌保存在 Keychain;安卓登录令牌使用 Android Keystore 中的密钥以 AES-GCM 加密后保存在本机,不进入系统备份。设备上的账号记录和访客记录分别保存。首次登录不会自动导入访客的出差、重要日子和备注。仅当账号从未保存过云端设置,且本机账号设置为默认值时,会自动沿用并同步此设备的访客天气城市、假日地区和公司补休开关。访客记录可由您选择导入后再同步。服务器需要处理同步内容,这不是端到端加密同步;本说明不承诺数据库或备份具有静态加密。

同步遇到同一记录的不同修改时会要求您选择。删除一条记录后,下一次成功同步会更新云端资料。退出只退出当前设备,不删除账号或云端资料;本机按账号保存的离线记录仍保留。卸载和外部备份仍由设备系统及您选择的存储服务管理。

可在“账号与同步”申请删除账号:向当前邮箱重新获取验证码,再确认删除。成功后服务端删除在线业务资料中的账号、个人记录、账号设置(天气城市、假日地区和公司补休开关)、相关登录会话与验证码;此设备的清理包括账号记录、上述账号设置和账号天气缓存。独立访客记录、访客偏好及您自行导出的备份不属于账号数据,不会因此删除。若本机清理失败,按 App 提示完成后续处理。

为防止恢复旧业务备份时重新开放已删除账号,成功删号时会在独立审计库中保存旧用户编号(UUID)、规范化邮箱的 SHA-256 摘要及删除时间。标记不包含邮箱明文、行程、重要日子、备注、验证码或登录令牌,但仍能关联同一旧账号,并非匿名数据。这些标记不会随账号删除而清除,具体保留方式见下文。

为限制验证码发送、错误尝试和服务预算,服务器保存邮箱及网络 IP 的摘要计数。摘要仍用于区分同一邮箱或网络,不将其表述为完全匿名数据。删除账号不会立即清空全部短期限流计数或全服务累计预算,其保留方式如下。

服务器保留期限、日志与备份

应用日志只输出固定运行或错误状态,不记录请求内容、邮箱、验证码、登录凭据或私人记录。应用容器日志按容量轮转,最多保留 3 个文件、每个 2 MiB,没有固定的保留天数。当前反向代理未启用访问日志。以上仅说明本服务自身的日志设置;操作系统、云厂商或邮件提供方的日志处理以各自规则为准。

业务数据库计划每日在 03:20 UTC 备份,最多约 2 分钟随机延迟。备份目录和文件限制为服务器管理员访问;每次成功备份后,删除文件修改时间超过 7 天的业务备份。删除在线账号不会立即擦除已生成的历史业务备份,旧资料可能保留至到期清理;到期后仍需等待下一次成功任务,运维故障可能进一步延迟。独立删号审计及其导出文件另行保存,不随这些业务备份到期删除。

历史业务备份只用于故障恢复。恢复期间会关闭账号服务访问,依据仍保留的独立审计逐一核对并删除旧账号 UUID,清除恢复出的登录会话和验证码,经校验后才重新开放。后来用同一邮箱注册的新 UUID 不会仅因邮箱相同而被删除。缺少相符审计标识的旧备份会被拒绝,包括删号审计启用前生成的备份,不能作为自动恢复并开放服务的基线。

上述保护针对保留独立审计的业务备份恢复,不保证整套 MySQL 存储卷回退、损坏或审计资料丢失时仍能保留全部删除效果;周期性导出的审计也可能尚未包含最新删除,不能仅凭旧导出文件认定可以重新开放服务。您自行导出的文件、别人收到的副本及设备系统备份,不受本服务业务备份的 7 天清理规则控制。

人机验证与 Cloudflare

账号获取验证码时使用免费的 Cloudflare Turnstile,通过 App 内网页加载 Cloudflare 验证脚本,阻止机器人滥发邮件;1.3 起安全验证页提供英文版。免费方案也涉及第三方数据处理。

Cloudflare 可能处理客户端 IP、TLS 指纹、User-Agent、sitekey 和来源等安全信号,用于识别人机、阻止机器人并改进防机器人能力。服务器还将验证令牌与请求的客户端 IP(remoteip)发送到 Cloudflare Siteverify API,核实验证结果。处理规则见 Cloudflare Turnstile 隐私补充条款。

Turnstile 还提供跨请求的安全分析:按来源 IP、国家、浏览器、User-Agent 和操作系统统计挑战请求;统计挑战完成、失败、放弃及是否需要点击等交互;统计 Siteverify 验证成功或失败。这些统计用于发现异常来源、机器人活动或验证配置问题,评估并改善防滥用效果。本 App 不把这些统计用于广告画像或广告跨应用跟踪。来源:Turnstile Analytics、挑战结果统计及 验证结果统计。

Free 方案的 最长 7 天分析查询窗口指可查看的统计时间范围,不等于 Cloudflare 全部原始信号的删除期限。验证 token 的 5 分钟有效期和本服务防重放摘要的 10 分钟保存期,也不能解释为 Cloudflare 会在这些时间后删除所有资料。本服务不替第三方承诺未核实的原始信号保留期限。

安卓下载与检查更新

安卓版仅从 xiaorili.aistella.net 下载 APK,不通过应用商店分发。安卓 1.3 起,打开或切回 App 时最多每 12 小时请求一次 https://xiaorili.aistella.net/download/android.json 检查更新。该请求只获取版本信息,不发送个人数据;站点会收到 IP 地址等普通网络信息。网站服务器只按天统计首页打开、安装包下载和检查更新的总次数(同一设备当天只算一次),用于了解使用情况;统计不保存 IP 地址,当天用于去重的临时数据次日删除。

更新包从同一站点下载,安装前校验 SHA-256 和签名。第一次使用 App 内更新时,需要允许小日历“安装未知应用”;之后在 App 内点“更新”。Android 12 及以上,部分系统版本可能直接完成安装,不再弹出系统确认;Android 11 及以下,每次安装更新都由系统提示您确认。iOS 版本通过 App Store 获取和更新。

黄历、周易与起卦记录

起卦记录保存在 App 本机数据中,不随账号同步,也不包含在 App 导出的 version 1 JSON 备份文件中。iOS 起卦记录可能随 iPhone/iCloud 系统备份;安卓起卦记录已排除在系统备份之外。黄历和周易仅供娱乐和民俗文化参考,不作决策依据。健康相关内容不能替代医疗建议、诊断或治疗;如有健康问题,请及时就医。

欧盟/欧洲经济区用户(GDPR)

本 App 的数据控制者为个人开发者 Felix Wang,联系邮箱:mywy8866@gmail.com。

联系与生效信息

个人开发者:Felix Wang。支持邮箱:mywy8866@gmail.com。如需了解、导出或删除账号数据,或在 App 中无法完成删除,请通过此邮箱联系支持。请不要在反馈中提供验证码、登录令牌或云服务密钥。

本说明更新于 2026-11-10;功能或数据处理发生变化时会更新本页。页面地址:隐私说明;使用帮助:支持页面。

Xiaorili · Updated: 2026-11-10

Privacy Notice

This notice applies to Xiaorili for iOS and Android. The iOS app is available through the App Store and supports Chinese and English from version 1.2. The Android app is not distributed through app stores; its APK is available only at xiaorili.aistella.net. Email accounts, sync and in-app update checks are available on Android from version 1.3, and the same reminders, travel statistics, footprint and other local tools as on iOS from version 1.4.

Record storage and online services

You can use the calendar and records without signing in. When you enable email account sync, account details, personal records and account settings in supported versions are sent to the developer’s own cloud service (Tencent Cloud servers in Guangzhou, mainland China). Weather, holidays and security verification also involve third-party services. This page explains how this data is used, where it is stored, how long it is retained and how to delete it.

How private records are stored

Business trip destinations, start and end dates, birthdays, other important dates and notes you enter are stored in separate files within the app’s sandbox on your device. You can use the calendar and records without signing in. Guest records are not automatically uploaded to an account or included in public weather or holiday requests. Records used after signing in are handled as described under account sync below.

Your weather cities, country or state holiday regions and company compensatory leave toggle are stored in local settings files in the app’s sandbox, separately for guests and each email account. A fresh installation has no preset personal cities, and company compensatory leave is off by default. From Android 1.3 and iOS 1.3, these settings sync to the same cloud service when you sign in and are stored per account. In guest mode or while signed out, they stay on the device. These settings are still excluded from version 1 JSON backups. Public weather and holiday caches are stored locally by the app.

The app is free, with no ads, subscriptions or third-party advertising tracking SDKs. It does not use this data to build advertising profiles. Account security verification uses Cloudflare security components and security analytics, as described below. Having no ads does not mean there is no analytics or that all data stays on the device.

Records are currently stored in local files without a separate password-based encryption feature. Device security and system backups depend on your system settings. iOS and Android system backups may contain some app data; these are separate from the app’s account sync. On iOS, I Ching casting history is stored in the app’s local data and may be included in iPhone/iCloud system backups. On Android, casting history and login tokens are excluded from system backups. On both platforms, casting history is not synced to an account or included in version 1 JSON backup files exported by the app.

Local reminders and calendar tools (iOS 1.3 and Android 1.4 or later)

Your device generates reminders from the current guest or account’s important dates and trip records, and solar term content bundled with the app. No additional data is uploaded for reminders. Reminder switches and times stay on this device, outside version 1 JSON backups and account sync; enabling reminders requires system notification permission.

Travel statistics, the leave planner, milestones and birthday details are calculated on your device; solar term descriptions come with the app. The leave planner uses cached or bundled mainland China holiday and adjusted workday schedules; from version 1.4 it can also use another country or region, retrieving that region’s public holiday data when needed from the sources listed under network requests, without sending private records. Copying summaries or plans writes their content to the system clipboard. Supplementary starting years and unknown-year settings for milestones stay on this device, outside exported JSON backups and account sync, and must be entered again on another device. Existing trip and important date records still follow the backup and sync rules above. Local data may still be included in iPhone/iCloud system backups. Deleting an account also removes its supplementary starting-year details from this device. Almanac and solar term content is for folk culture reference only.

From version 1.4, the Footprint page and the Year in Travel card are calculated and drawn on your device. The footprint map uses land-outline dots bundled with the app (generated from public-domain Natural Earth land data, without borders). City positions come from the coordinates of saved cities or from the city name cache described below; cities without known coordinates are not drawn. A card image is created only when you tap “Share Image” and is passed to the system share sheet. You can turn off “Show cities” to hide city names and city dots, and the image never includes trip names or notes. On iOS, permission to add to Photos is requested only if you choose “Save Image” in the share sheet. The mainland China switches “No make-up workdays (statutory holidays only)” and “Weekend holidays move to the next workday” stay on this device, outside account sync and JSON backups.

From version 1.6, Notes (one per day: title, body, checklists and photos) are stored only in the app’s sandbox on your device. They are not uploaded or synced to an account, and guests and accounts on the same device share them. You choose photos one by one in the system photo picker; the app does not request photo library permission and keeps only compressed copies, which are removed when you delete the note or photo. Exported JSON backups include Notes and their photos, and restoring merges them on the device.

Information sent in network requests

Public weather and holiday data require HTTPS requests. Providers receive request parameters and ordinary network information, including your IP address. The current app should therefore not be understood as keeping all data on the device. Requests do not include your business trip records, birthdays, notes or backup contents.

  • City search: the city search text you enter is sent to geocoding-api.open-meteo.com in the name parameter to obtain matching cities, administrative areas, countries, coordinates and time zones. A result is saved only after you select it. Weather cities sync after sign-in in the versions described above. Searching for and selecting business trip cities uses the same service. The provider processes search text; its documentation does not specify every detail of per-query logging or retention, so immediate disposal cannot be guaranteed.
  • City name lookup: From iOS 1.3 and Android 1.4, when displaying saved weather cities or cities linked to trips, Xiaorili may query Open-Meteo using the city ID and app language if no usable name is cached. The ID can indicate a city you selected, and the provider also receives ordinary network information such as your IP address. Requests do not include trip dates, notes, important dates or account credentials. Names are cached on the device, excluded from account sync and exported JSON backups; if a query fails, saved names are used. From version 1.4, the city coordinates returned by the same request are also cached on the device for the footprint map; older cache entries without coordinates are filled in under the same rules. Cached coordinates are likewise excluded from account sync and JSON backups.
  • Weather: requests to api.open-meteo.com include the selected city’s latitude and longitude, weather fields, time zone parameter and a six-day forecast range. Adding a business trip city also adds it to the weather list. City coordinates may indicate a destination you selected, but requests do not include the full itinerary, dates, notes, email address or important dates. Neither the iOS nor Android app requests location permission or reads your device’s GPS location.
  • Mainland China holidays: the app first requests a mirror of the NateScarlet/holiday-cn data for the relevant year from Xiaorili’s own sync server (calendar-api.aistella.net), and uses cdn.jsdelivr.net if that fails. The request contains only the year, not personal data.
  • Malaysia holidays: requests to malaysia-holiday.dydxsoft.my send only the year and download the list for all regions for that year. Filtering by state or federal territory happens on your device. “Nationwide holidays” includes entries applying to all 16 regions, rather than a combined list of every state-specific holiday.
  • Hong Kong public holidays: the app downloads the official Simplified Chinese JSON from a fixed URL at www.1823.gov.hk, then selects the year locally. The request does not send your selected year, city or private records. Hong Kong Government 1823 provides actual public holidays and announced substitute dates as published in the Gazette. As of 2026-10-12, this rolling dataset covers 2025–2027; uncovered years are shown as unavailable. See the official dataset.
  • Other supported countries: the app requests the country directory from nagerholidays.com, or sends a country code and year to retrieve holiday dates from Nager Community v4. This source does not provide actual substitute or observed dates; follow local announcements for days off. Austria can be filtered by state on the device. For other supported countries, this version uses only entries marked nationwide by the source. These do not represent every region’s or employer’s days off. US data is not presented as a complete federal employee or state leave schedule. Data is not guaranteed for every country or year. China, Malaysia and Hong Kong use their respective sources above.

From version 1.6, Holiday Details are built into the app and viewing them does not go online. Tapping Search with Bing opens a Microsoft Bing search for the holiday name inside the app; Bing receives the search terms and ordinary network information such as your IP address and handles them under its own rules. This happens only when you tap it.

Open-Meteo’s free API privacy terms state that it may process IP information for technical maintenance and abuse prevention; troubleshooting logs may include requested coordinates, and logs are deleted after 90 days. The coordinates sent are those of cities you actively select, rather than your device’s live location. The terms do not explain field by field whether the free geocoding service logs name, so they do not establish that every search is necessarily retained for 90 days. Third-party processing is subject to the provider’s latest policies. Sources: Open-Meteo Terms & Privacy and Geocoding API documentation. For other countries’ holiday service terms, see Nager Terms of Service.

Other public data providers may also receive or log network requests; the developer does not control their logging practices. Account security verification uses third-party security scripts and includes security statistics about challenge interactions, sources and verification results, as described below. When you choose to open external links, those websites apply their own privacy rules.

Backups, sharing and deletion

Exporting a JSON backup from “More” writes the current guest’s or account’s business trips, important dates and notes to a file location you choose. It excludes weather cities, preferred holiday regions and company compensatory leave preferences. JSON files contain directly readable private records. Choosing iCloud Drive, another cloud drive or a sharing recipient is a manual file operation; that service or recipient may receive the file contents. The app does not automatically upload exported backup files to third parties. Account records themselves are handled through account sync.

When restoring a backup, the app validates the entire file before asking you to confirm replacement of all records for the current guest or account. Restored account records may then sync; guest files remain separate. Deleting a record updates the current local record file, and account records are updated in the cloud on the next successful sync.

If a record file is damaged, the app preserves the original and reports a read failure. Damaged account records cannot simply be opened for further editing. Record recovery may leave recoverable copies in the sandbox. Account deletion removes records and recovery copies that can be clearly attributed to that account. Damaged copies that cannot be attributed are kept to avoid deleting other data; uninstalling the app or contacting support for manual cleanup is required to address them. This notice does not promise that account deletion erases every sandbox file.

Deleting current records does not automatically delete exported files, copies received by others or existing system backups. Manage those files and system backups separately. Uninstalling the app generally removes its local sandbox data.

Email accounts and personal sync

Account sync is available from iOS 1.0 and Android 1.3. Sync of weather cities, holiday regions and the company compensatory leave toggle is available from iOS 1.3 and Android 1.3.

Accounts use email verification codes to register or sign in, without a password. Your email address is used to verify your identity, send account verification codes and identify your account. Verification emails are sent through Tencent Cloud SES in Hong Kong from noreply@mail.aistella.net. From version 1.3, the app requests Chinese or English verification emails according to its interface language. Until English emails are enabled, all verification emails are sent in Chinese. The email service receives the recipient’s address and verification email contents, but not your business trips or important dates. Codes are delivered by ordinary email, without end-to-end encryption. The email provider and your mailbox provider may process emails and delivery records under their own rules. See the Tencent Cloud privacy statement in Chinese and Tencent Cloud Privacy Policy.

When you choose to sign in and sync, your email address, random user ID, business trips, important dates and notes are stored on the developer’s own cloud service (Tencent Cloud servers in Guangzhou, mainland China). Each account’s data is stored separately, with server access restricted by the signed-in identity. From Android 1.3 and iOS 1.3, weather cities, holiday regions and the company compensatory leave toggle are also stored per account and synced to that same service. In guest mode or while signed out, these settings are stored only on the device. Account requests use HTTPS connections to https://calendar-api.aistella.net. On iOS, login tokens are stored in Keychain. On Android, login tokens are encrypted locally with AES-GCM using a key held in Android Keystore and are excluded from system backups. Account records and guest records are stored separately on the device. Signing in for the first time does not automatically import guest trips, important dates or notes. Only if the account has never saved cloud settings and its local account settings are at their defaults are guest weather cities, holiday regions and the company rest day toggle copied into the account and synced automatically. You can choose to import guest records and then sync. The server must process sync contents; this is not end-to-end encrypted sync, and this notice does not promise encryption at rest for databases or backups.

If sync encounters different edits to the same record, you will be asked to choose. Deleting a record updates cloud data on the next successful sync. Signing out affects only the current device and does not delete the account or cloud data; offline records stored locally for the account remain. Uninstallation and external backups are managed by your device’s system and the storage services you choose.

You can request account deletion in “Account & Sync”: obtain a new code at your current email address and confirm deletion. After success, the server deletes the account, personal records, account settings (weather cities, holiday regions and the company compensatory leave toggle), related login sessions and verification codes from live business data. Cleanup on this device includes account records, those account settings and the account’s weather cache. Separate guest records, guest preferences and backups you exported yourself are not account data and are not deleted as part of this process. If local cleanup fails, follow the app’s instructions.

To prevent deleted accounts from being reopened when old business backups are restored, successful deletion stores the old user ID (UUID), a SHA-256 digest of the normalized email address and the deletion time in a separate audit database. These markers do not contain the email address in plain text, itineraries, important dates, notes, verification codes or login tokens. They can still be linked to the same old account and are not anonymous data. They are not removed by account deletion; retention is described below.

To limit code delivery, incorrect attempts and service costs, the server stores digest-based counters for email addresses and network IPs. These digests still distinguish the same email address or network and are not described as fully anonymous. Account deletion does not immediately clear all short-term rate-limit counters or the service-wide cumulative sending count. Retention is described below.

Server retention, logs and backups

  • Live account email addresses, user IDs, cloud records and account settings are retained until you successfully delete your account. Old user IDs and email digests remain in the separate deletion audit described below. Individual records are removed from live data after their deletion successfully syncs. Signing out or uninstalling the app does not delete the cloud account.
  • Verification codes and verification records: codes are valid for 10 minutes. Login sessions are valid for 30 days. Security verification tokens are accepted only for results up to 5 minutes old; replay-prevention digests are stored for 10 minutes. Expired entries can no longer be used for verification and are cleaned up hourly; physical deletion may occur after expiry.
  • Live email/IP rate-limit digests: hourly, minute and daily windows are retained for one additional day after the window ends and cleaned up hourly. In normal operation, these short-term live digests are generally removed no later than about 2 days and 1 hour after the window starts. Operational failures may delay cleanup; deletion on schedule during failures is not guaranteed. Copies of digest-based counters temporarily placed in the separate audit database during recovery to preserve security limits are not covered by this live-data cleanup period.
  • Service-wide cumulative email count: only a service-wide total is stored, without email addresses or IPs. It is retained until manually reset by an administrator and is not cleared by account deletion.
  • Separate deletion audit and recovery copies: old UUIDs, email SHA-256 digests and deletion times are retained to check deleted accounts in old backups. Automatic expiry is not currently configured, nor is automatic cleanup of daily exported deletion audit files. Temporary recovery copies of rate-limit digest counters likewise have no automatic cleanup. The 7-day business backup rule does not apply to these items. Before cleanup, an administrator must review recoverable backups and the deletion protections that still need to be maintained, then arrange safe handling. You may contact support about how this data is handled.

Application logs output only fixed operational or error states, without request contents, email addresses, verification codes, login credentials or private records. Application container logs rotate by size, retaining at most 3 files of 2 MiB each, with no fixed retention period in days. Reverse-proxy access logging is currently disabled. These statements describe only this service’s own logging settings; operating system, cloud provider and email provider logs are subject to their respective rules.

Business database backups are scheduled daily at 03:20 UTC, with a random delay of up to about 2 minutes. Backup directories and files are restricted to server administrators. After each successful backup, business backups with file modification times more than 7 days old are deleted. Deleting a live account does not immediately erase historical business backups; old data may remain until cleanup is due. Cleanup must still wait for the next successful task, and operational failures may cause further delay. The separate deletion audit and its exports are stored independently and do not expire with these business backups.

Historical business backups are used only for disaster recovery. Account service access is closed during recovery. Old account UUIDs are checked individually against the retained separate audit and deleted; restored login sessions and verification codes are cleared. Access is reopened only after validation. A new UUID registered later with the same email address is not deleted merely because the address matches. Old backups without matching audit identifiers are rejected, including backups created before deletion auditing was enabled; they cannot serve as a basis for automatic recovery and reopening.

These protections apply to business backup recovery with the separate audit retained. They do not guarantee preservation of every deletion if the entire MySQL storage volume is rolled back or damaged, or audit data is lost. Periodic audit exports may also omit the latest deletions, so an old export alone cannot establish that service access may safely reopen. Files you export, copies received by others and device system backups are outside this service’s 7-day business backup cleanup rule.

Security verification and Cloudflare

Requests for account verification codes use the free Cloudflare Turnstile service. An in-app web page loads Cloudflare verification scripts to prevent automated email abuse. An English security verification page is available from version 1.3. The free plan also involves third-party data processing.

Cloudflare may process security signals such as client IP, TLS fingerprint, User-Agent, sitekey and origin to distinguish people from bots, block bots and improve its bot prevention capabilities. The server also sends the verification token and the request’s client IP (remoteip) to the Cloudflare Siteverify API to verify the result. See the Cloudflare Turnstile Privacy Addendum.

Turnstile also provides security analytics across requests: challenge requests grouped by source IP, country, browser, User-Agent and operating system; challenge completion, failure, abandonment and whether a click was needed; and Siteverify validation success or failure. These statistics help identify unusual sources, bot activity or verification configuration problems, and assess and improve abuse prevention. The app does not use these statistics for advertising profiles or cross-app advertising tracking. Sources: Turnstile Analytics, challenge outcomes and token validation.

The free plan’s analytics query window of up to 7 days describes the time range of viewable statistics, rather than the deletion deadline for all raw Cloudflare signals. The verification token’s 5-minute validity and this service’s 10-minute replay-prevention digest retention likewise do not mean Cloudflare deletes all data after those periods. This service does not make unverified promises about a third party’s raw signal retention.

Android downloads and update checks

The Android APK is available only at xiaorili.aistella.net, without app store distribution. From Android 1.3, opening or returning to the app requests https://xiaorili.aistella.net/download/android.json at most once every 12 hours to check for updates. This request retrieves only version information and sends no personal data; the site receives ordinary network information such as your IP address. The website server only keeps daily totals of homepage visits, installer downloads and update checks (each device counted once per day) to understand usage; these statistics do not store IP addresses, and the temporary data used for de-duplication is deleted the next day.

Update packages are downloaded from the same site and checked for SHA-256 and signature before installation. The first time you use in-app updates, you must allow “Install unknown apps” for Xiaorili; after that, tap “Update” in the app. On Android 12 and later, some system versions may complete installation directly without another system confirmation prompt. On Android 11 and earlier, the system asks you to confirm each update installation. The iOS app is obtained and updated through the App Store.

Almanac, I Ching and casting history

I Ching casting history is stored in the app’s local data. It is not synced to an account or included in version 1 JSON backup files exported by the app. On iOS, it may be included in iPhone/iCloud system backups. On Android, it is excluded from system backups. The almanac and I Ching are for entertainment and cultural reference only, not a basis for decision-making. Health-related content cannot replace medical advice, diagnosis or treatment. If you have a health concern, seek medical care promptly.

Users in the EU/EEA (GDPR)

The data controller for this app is its individual developer, Felix Wang. Contact: mywy8866@gmail.com.

  • Legal bases: processing necessary to provide the features you request, including accounts, sync and account deletion, is based on performance of a contract. Turnstile security verification, rate limiting and other abuse prevention are based on legitimate interests in protecting accounts, the service and email resources. We do not carry out marketing or user profiling.
  • Data and recipients: see private records, network requests and account sync above for data categories and purposes. Service providers include Tencent Cloud (servers in Guangzhou, mainland China, and SES verification emails in Hong Kong), Cloudflare (Turnstile security verification) and Open-Meteo (weather and place name queries, receiving selected city coordinates, city IDs, language and ordinary network information; active city searches also send your search text). Other holiday data providers and request parameters are listed above. These public queries do not include your private records or account credentials.
  • International transfers and choice: your synced email address, records and account settings are stored on Tencent Cloud servers in Guangzhou, mainland China, outside the EU/EEA. When accessed from networks outside mainland China, the encrypted connection is relayed unchanged through the developer’s server in Hong Kong, which does not decrypt or store this data. You can choose to stay signed out and keep records and settings on your device. Online features such as weather and holidays still send request data to providers as described above.
  • Retention: live account details, records and settings are kept while the account exists and removed after successful account deletion. After each successful business backup, files with modification times more than 7 days old are removed; failures may delay cleanup. The separate deletion audit, its exports and recovery copies of rate-limit digest counters currently have no automatic expiry or cleanup and are outside that 7-day rule. See server retention, logs and backups for full periods and handling after deletion.
  • Your rights: where applicable, you may request access, rectification, erasure, data export or portability, restriction of processing, object to processing based on legitimate interests, and withdraw consent where relevant, without affecting the lawfulness of processing based on consent before withdrawal. You may also complain to the data protection supervisory authority in your country.
  • How to exercise them: view and edit records in the app; deleting online records requires a successful sync. For account deletion, go to “More → Account & sync → Delete account & cloud records”. Export a JSON backup from “More” for the current guest’s or account’s business trips, important dates and notes; see backup details for its scope and limitations. Email the contact above for other data exports, rights requests or actions you cannot complete in the app. We will respond within one month of receiving your request.

Contact and effective information

Individual developer: Felix Wang. Support email: mywy8866@gmail.com. Contact this address to ask about, export or delete account data, or if deletion cannot be completed in the app. Do not include verification codes, login tokens or cloud service keys in feedback.

This notice was updated on 2026-11-10 and will be updated when features or data processing change. Page address: Privacy Notice. For help, see Support.