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.
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.comin thenameparameter 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.cominclude 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 usescdn.jsdelivr.netif that fails. The request contains only the year, not personal data. - Malaysia holidays: requests to
malaysia-holiday.dydxsoft.mysend 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.