プライバシーポリシー kichijitsu Privacy Policy

Privacy Policy (English)

kichijitsu is a calendar client for Google Calendar. When you use this instance (kichijitsu.love-rox.cc), the following is stored on the server (Cloudflare D1 and Durable Objects). Data for a feature is only created if you use that feature.

• Your Google account identifier and email address — for sign-in and to tell connected accounts apart
• Google OAuth tokens — for calendar sync. Refresh tokens are encrypted at rest with AES-256-GCM (the decryption key is held separately from the database). Short-lived access tokens (about one hour) are cached temporarily in the Durable Object that performs the sync
• Sync state — incremental sync cursors (syncTokens, per calendar and device), polling state, and the push-notification subscriptions used to receive updates from Google (channel ID, target calendar, expiry)
• Your choice of visible calendars — so the same selection applies across your devices
• Calendar blocking settings — if you use the feature that mirrors events onto another calendar as busy/out-of-office: the source and target calendars, and a mapping from original event ID to generated block ID. That mapping holds IDs and update timestamps only, never event contents
• GitHub connection details — if you connect GitHub: your GitHub user ID, login name and granted scopes, plus an access token encrypted with AES-256-GCM
• Hashes of MCP tokens — if you issue tokens for agent access (MCP): their SHA-256 hash, label and last-used time. The raw token is shown once at issuance and is never stored

Work logs

If you record work time — either manually in the app's right pane or through an agent over MCP — your work logs are stored on the server: repository name, issue reference, branch name, agent name, and start/end times. This is a record of your own activity created within kichijitsu, with no original held by Google — and it is currently the only such data the server keeps. Everything else listed above is either a pointer to data that lives in Google or a setting of yours. Nothing is created unless you use the feature.

About event contents

Your calendar event contents (titles, descriptions, attendees) are never stored on our servers — events are synced directly to your browser's local storage (IndexedDB). Everything listed above that relates to events consists of IDs, timestamps and settings, not the events themselves. Summaries of the events MCP returns to an agent are likewise sent straight back as the response and never stored on the server.

In addition, if you use event reminder notifications in the desktop app, a record of which notifications have already been shown is kept in that device's browser storage (localStorage) so the same notification is not shown twice. Each entry contains the calendar ID (often in the form of an email address), the event ID and the event's start time — never the event's title, description or attendees. This record stays on the device, is never sent to our servers or to Google, and entries are discarded automatically 24 hours after the event's start time.

We use this information solely to provide calendar display, sync, and editing. We do not use it for advertising, sell it, or share it with third parties. kichijitsu's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

The data above is retained for as long as the connection exists; nothing (work logs included) is deleted automatically on a schedule. Disconnecting an account from within the app stops that account's push-notification subscriptions with Google, revokes its Google token, and deletes that account's credentials, calendar selection, sync state, subscription records, and any calendar blocking settings involving it — the whole rule if the disconnected account was the target, or just the affected reference if it was one of several sources. Disconnecting the last remaining account also deletes the GitHub connection, MCP tokens and work logs belonging to that profile, and signs you out. You can also revoke access at any time from your Google Account settings. To clear local data, use Log out in settings — it removes this device's copy of your events, tasks and GitHub list. Time blocks and manual timer records stay, because this device is the only place they exist. To erase everything, clear the site's data in your browser.

What happens to busy/out-of-office blocks the blocking feature already created in Google Calendar depends on whether the rule survives the disconnect. If you disconnect only some of a rule's source calendars, the rule lives on through the remaining sources and the blocks derived from the disconnected calendar are deleted right away (that is the surviving rule following its sources, and only brings forward a deletion that the next change to a remaining source would have made anyway). If the rule itself goes away — you disconnected its destination calendar, or all of its sources — the blocks remain in that calendar. Disconnecting offers no moment to ask whether they should be deleted, so the app does not delete them, not even when the destination account is still connected (as it is when you disconnect all of a rule's sources); the server-side mapping is deleted as well, so the app can no longer manage them. Delete them in Google Calendar if you no longer want them. Apart from that, the only case where the app deletes those blocks is when you delete a blocking rule in the app and leave "delete the blocks already created" checked; changing a rule's destination calendar alone never deletes blocks that were already created.

Operator: love-rox

Contact: kichijitsu@love-rox.cc