Calendar Privacy Policy
Effective date: September 30, 2026
Operator: the developer of 日历 / Calendar ("we")
Privacy contact: qbj@outlook.com
Address or other required contact details: Shenzhen, Guangdong, China; contact us by email above for correspondence
This policy explains how the Android and iOS versions of “日历 / Calendar” and its official website handle information. The Android package name and iOS bundle ID are com.shishuliyue.calender. The app does not operate a developer-hosted calendar account or advertising service. A mail, calendar, or file service you choose to connect is governed by its own privacy practices.
1. Information and purposes
| Feature | Information handled | Purpose and trigger |
|---|---|---|
| Local events | Titles, dates and times, recurrence, location, invitee email addresses, reminders, notes, URLs, and attachments you select | Display, edit, search, and remind you about events on your device. The app obtains access to a document only when you select it. The iOS app copies selected attachments into private app storage; the Android app stores their names and access links. The app does not copy attachment content to an operator server. |
| Device calendars | With your permission, calendar names, account identifiers, and events already synchronized on your device; events you choose to save to a device calendar | Show existing calendars together and save new events to a calendar you select. Android uses its calendar provider; iOS uses EventKit. The relevant system account service controls subsequent synchronization and invitations. |
| Remote calendars you add | Exchange EWS or CalDAV server address, username, password, and calendar content; ICS feed address and events | Connect directly to the HTTPS service you specify, read events, and create events where supported. On Android, remote account and feed configuration is encrypted with a key protected by Android Keystore. On iOS, connection URLs, usernames, and passwords are stored in the device Keychain. A feed URL containing a token is treated as a secret. |
| ICS import and sharing | ICS events you open or import, and a single event you explicitly share | Import a local event or hand its ICS file to an app you choose. The receiving app obtains the content you share. |
| Moon observation location | Device location you permit; the date and time zone come from your device settings | Estimate local moonrise, moonset, and lunar position on the device. Location is not used for ads or movement tracking, and the app does not request background location or persist coordinates. The Android app releases the observation point when the moon screen closes and clears any observation point saved by an older version when that screen opens. Without location, you can still view phase information that does not depend on a place. |
| Preferences and cached public data | Week start, selected holiday regions, display and reminder settings, holiday cache | Keep your choices and show holidays offline. |
| App usage statistics | This release creates no new analytics identifier and sends no in-app activity or feature events | This release has no in-app analytics control or developer-operated usage analytics. Download and usage metrics supplied by an app store depend on that platform and the user's analytics-sharing choices. |
| Website and APK delivery | Website visits and download requests; when download counting is enabled, the statistics database stores daily totals of APK download requests only | Deliver the website, legal pages, and Android package, and understand download demand. A download request does not prove that a download finished or an app was installed. Website statistics use no tracking cookies and do not store IP addresses or browser identifiers in the statistics database; the hosting network still processes connection data and may create security logs. |
The app contains no advertising or third-party behavioral analytics SDK, and we do not sell personal information. This release sends no in-app usage events to the operator; calendar event content, account secrets, and location are not sent to the operator's analytics service either. The app still contacts the website, third-party sites, and services you choose for the features below.
2. Network requests and other services
- Holiday updates. When you view a year for selected regions, the app may request country/year holiday data from
date.nager.atornagerholidays.com. It may obtain annual Chinese holiday data from GitHub (raw.githubusercontent.com) or jsDelivr (cdn.jsdelivr.net). These services and their network infrastructure may see normal connection information such as your IP address and the requested region and year. The requests do not include event text or device location. Some holiday data is bundled for offline use. - Website. The website uses ChatGPT Sites hosting. OpenAI processes hosted data for the site operator and may use subprocessors including Cloudflare. The hosting network processes IP addresses, device information, and access logs to serve pages and the APK; the project's statistics database does not persist IP addresses or User-Agent headers. A fixed data-residency country or region has not been provided for this project, so website requests may be processed across borders. The app operator does not fully control retention or deletion of the host's own security logs.
- Calendar services you choose. When you add Exchange EWS, CalDAV, or an ICS feed, the app contacts the address you enter directly. Depending on the feature, that service may receive credentials, date ranges, events, and invitee details that you choose to write; it may store or synchronize them or send invitations under its own rules. Only add a service you trust and are authorized to use. We do not control its retention or international transfers.
- Platform and other apps. The Android calendar provider, iOS EventKit, system account sync service, operating system backup, document provider, and sharing destination process data under their operators’ practices. The current Android app allows platform backup of some app data; direct Exchange and remote-calendar credentials are excluded from Android cloud backup and device transfer. iOS remote connection details use device-only Keychain items that are not synchronized or backed up. Manage other backup settings through your device. We do not receive a copy merely because the operating system backs up the app.
These services may operate outside your country or region. If you choose a remote calendar service in another jurisdiction, events may be transferred under that service’s rules. Before release, the operator must verify applicable international-transfer requirements and disclosures in each launch market.
3. Permissions and choices
Read-calendar permission displays existing device events; write-calendar permission saves new events to a device calendar you select. Notification permission delivers local reminders. Foreground location permission supports location-based moonrise and moonset. You can decline or revoke a permission in device settings. ICS import uses a file you open; attachments use the system document picker rather than broad library access.
This release has no in-app usage analytics entry and does not create or send first-party usage events. If an older release stored analytics consent or an identifier, upgrading revokes that consent and clears ordinary events queued on the device. To request deletion of any older server records that remain linked to you, contact the privacy address above. Events and holidays are unaffected.
You can use local events without connecting a remote account. You can turn off device-calendar display, remove a remote source, or delete local events in the app. Declining a permission affects only its related feature. Events saved to a system or remote calendar must also be managed in that account or service.
4. Retention, security, and deletion
Local events and preferences are stored in the app’s private device storage. Remote account and feed configuration is encrypted on Android. On iOS, connection URLs, usernames, and passwords use device-only Keychain items; local event files and copied attachments have iOS file protection. Network connections use HTTPS and the device’s certificate validation. No safeguard can promise absolute security; use a device lock and choose calendar services carefully.
This release creates no new in-app usage analytics records. Any analytics ID and unsent ordinary events left by an older release are cleared after upgrading. You may request deletion of older linked server records through the privacy address above; anonymous historical aggregates cannot be reduced for one person. If website APK download counting is enabled in the future, only daily request totals will be kept, without visitor profiles; a download request is not an installation count. The hosting provider's operational and security logs may follow separate retention rules.
Deleting a local event removes it from the app’s local event record. Removing a remote source deletes the connection configuration stored by this app; it does not delete the remote account or existing server events. Clearing app data or uninstalling normally removes its private storage, although an operating system backup may retain a restorable copy; iOS may retain Keychain items after uninstall, so a fresh installation checks for and clears old connection details that do not belong to the current installation. System and remote calendar copies must be deleted in their respective services. An attachment’s original remains with its document provider; the iOS app also holds a copy in private app storage.
To exercise applicable access, correction, deletion, or other rights, contact the privacy address above. Because we currently do not host calendar cloud data, data held only on your device or by a separate calendar service can usually be managed directly in this app, your device, or that service.
5. Children, changes, and contact
This app is not designed specifically for children. Do not enter another person’s sensitive information without appropriate authority. We will give notice in the app or release materials about material changes to this policy or data handling, and seek a new choice where required. Questions and requests: qbj@outlook.com.