Calendoc Privacy Policy

Last updated: October 1, 2026

Calendoc ("the app") is a calendar app for iOS / macOS / Android developed by イズミアプリケーション, an independent developer ("the developer"). This policy applies to all editions of Calendoc, including Free and Pro. The app is built on one design principle: your schedule content is never sent to the developer's servers.

1. Calendar and Reminder Data

On iOS / macOS, the app reads and writes your device's calendars and reminders via Apple's EventKit. On Android, it reads and writes your device's calendars via CalendarProvider.
The app processes this data on your device and never sends it to the developer's servers (the developer operates no servers).
Syncing with iCloud, Google, or other services is performed by your device's operating system or the services you have connected, under their respective privacy policies.

2. Google Account Integration (Optional)

If you enable the Google Calendar enhancements (working location, event colors, RSVP, Google Tasks), the app requests your permission through Google's OAuth flow.

The app obtains your Google account identifier, email address, and display name to identify and display the connected account.
The content of Google user data (including events, tasks, and working locations) is used solely to display and edit your data, and is never used for advertising, profiling, or sharing with third parties. The app may send an anonymous feature-usage signal indicating that a Google integration feature was used, but the signal contains no Google user-data content, account information, or authentication information.
Google user data is not used to develop, improve, or train generalized artificial intelligence or machine learning models.
Calendoc's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

3. Protection of Google User Data

All communication between the app and Google APIs is encrypted in transit using HTTPS/TLS.
On iOS / macOS, your Google account identifier, email address, display name, and OAuth access and refresh tokens are stored only in Apple Keychain on your device. Keychain encrypts stored data and protects it with operating-system-level access controls.
On Android, Google Identity Services manages authentication tokens. The app temporarily holds obtained access tokens in memory and does not store access or refresh tokens in its own persistent storage. Account profiles (identifier, email address, display name, and connection date) are encrypted with AES/GCM using an Android Keystore key and stored in DataStore on your device. This profile storage is excluded from operating-system backups and device transfers.
The app does not create or maintain an app-managed persistent database for event, task, working-location, or other content obtained from Google APIs. This content is processed as transient application state as needed to display and edit it.
The app communicates directly from your device to Google APIs. No developer-operated backend receives Google user data, and the developer cannot access its content.

4. Retention and Deletion of Google User Data

No long-term retention period applies to event, task, working-location, or other content obtained from Google APIs. The app does not store this content in an app-managed persistent database. Transient application state needed for the current display or operation is replaced or discarded when data is reloaded, the app process ends, or it is no longer needed. It is never retained on developer-operated servers.
On iOS / macOS, your Google account information and OAuth credentials remain in Keychain only while that account is connected to the app. On Android, connected account profiles remain in the encrypted storage described above, and obtained access tokens are held temporarily in memory.
You can disconnect an account at any time in the app's Settings. On iOS / macOS, disconnection deletes that account's information and OAuth credentials from Keychain. On Android, it deletes the account's local profile and access tokens cached in the app's memory. After disconnection, the app no longer accesses Google user data for that account. If a device storage error or similar issue prevents deletion and you need assistance, contact the developer using the details at the end of this policy.
Disconnecting an account within the Android app does not revoke Google's access permission. You can revoke the app's access from your Google Account at https://myaccount.google.com/permissions.
Because the developer does not store Google user data on any server, there is no developer-held server data to retain or delete. If you need assistance with deletion, contact the developer using the details at the end of this policy.

5. Anonymous Usage Statistics (Opt-out Available)

To improve the app, Calendoc may collect anonymous usage statistics via TelemetryDeck (e.g., which screens are opened, which features are used).

No usage statistics are sent if a valid TelemetryDeck App ID is not configured for the distributed app.
Event, task, and working-location content, Google account information, and OAuth credentials are never sent to TelemetryDeck.
Collected signals are anonymized and cannot identify you. The app performs no cross-app or cross-site tracking.
You can turn this off anytime in Settings ("Send anonymous usage statistics").

6. Data the Developer Does Not Collect or Use

The developer does not collect events, tasks, working locations, or Google account information on developer-operated servers.
The app does not access your device contacts or current location.
No advertising SDKs.
Events, tasks, working locations, and Google account information are never sold, used for advertising, or shared with third parties.

7. Children's Privacy

The app is not designed for children and does not knowingly collect personal information from children.

8. Changes

If this policy changes, this page will be updated, and material changes will be announced in the app.

9. Contact

イズミアプリケーション — calendoc@izumiapps.com