Privacy is the architecture.

Jikoku does not require a Jikoku account to open the application and use its core workspace. There is no Jikoku login that becomes the owner of your calendar, reminders, contacts, Jikoku notes or meeting transcripts.

The application is not designed around an advertising profile. It does not need to study your behavior in order to sell attention, place ads or build an audience segment from your plans.

Jikoku also does not operate a content server that stores your personal notes, meetings, contacts and tasks as a second cloud copy. The Mac application works with Apple's system data and local application files instead.

On-device speech recognition and meeting transcription use WhisperKit. Local AI features use Gemma 4 12B running through Apple MLX. In the Public Beta you download both models yourself from the application settings. Audio and text can be transcribed, summarized and reviewed for possible tasks without being sent to a Jikoku AI endpoint, a cloud AI provider or Apple Intelligence.

The models account for roughly 8.4 GB, downloaded straight from their pinned sources to your Mac and verified by checksum before use. Application state and local support files live in the Mac's Application Support area. The operating system controls access to protected data such as Calendar, Reminders, Contacts and the microphone.

Notes are created and stored inside Jikoku's local app data on the Mac. They do not synchronize through iCloud. You can export them to a destination you choose when you want to use a copy elsewhere.

Permissions are explicit. macOS asks before Jikoku can read calendars, reminders or contacts, or capture audio from the microphone. A denied permission limits the related function rather than creating a hidden route around the system.

Privacy language should describe the real system, not a perfect imaginary one. If you obtain Jikoku through an app marketplace, that marketplace can know about the download or purchase. Any official distribution channel may also keep the ordinary records required to deliver the application.

When Apple Calendar, Reminders or Contacts synchronize through iCloud, Apple participates in that synchronization. Jikoku notes are not part of this iCloud path.

If you connect a work Exchange calendar, CalDAV account or another system calendar provider, that provider receives the information required for its own service. Jikoku cannot make a work account private from the organization operating that account.

These facts do not weaken the local architecture. They define its boundary. Jikoku's promise is that it does not add a Jikoku content cloud or a remote Jikoku AI processor to those existing relationships.

Calendar and Reminders access is provided through EventKit. Contacts access is requested for the people workspace. Jikoku notes use the application's own local storage and require no permission for another notes application. Microphone access is used for recording, and Screen Recording permission is requested only when capturing system audio from an online meeting. Every system permission can be reviewed or revoked in macOS System Settings.

Credentials for a connected work service are kept in the Mac Keychain. When Jikoku connects to an Apple iCloud CalDAV calendar or a configured Microsoft Exchange account, the application connects directly to that provider. A Jikoku server does not sit between the Mac and the configured service.

This site does not have access to the calendars, reminders, notes, contacts or transcripts inside the Mac application. Product data is not exposed to a marketing page simply because the product and site share a name.

The site does not use an analytics script, advertising cookies or user-action tracking. It does not create a profile of pages viewed, buttons pressed or product interests. The launch-email form is the only part of the current site that intentionally sends user-provided personal data to an external service.

The product video uses a local preview image. YouTube is not contacted until you press play. Playing it loads an embedded player from YouTube's privacy-enhanced domain, so Google and YouTube receive the network request under their own terms. Jikoku does not use that interaction for its own analytics.

A language stated in the page URL or chosen from the header menu always takes priority. A manual choice is stored for one year in the jikoku-locale cookie, which contains only the language code. Without a saved choice, Russian is selected only when the hosting infrastructure supplies Belarus, Kazakhstan or Russia as the coarse country code; every other visitor receives English. The site does not request precise location, store the country or use the signal for analytics or advertising.

Submitting the form opens the free Public Beta page and lets Jikoku keep your address to write about beta updates and the launch. It is not a purchase, a paid trial or a recurring newsletter. The beta page itself is hosted by Contra, so opening it is a visit to their website under their terms. The signup can also include the site language, signup date, source page and coarse technical context supplied by the delivery infrastructure, such as country, city and device platform. It does not include data from the Jikoku application.

The address is stored in a private Cloudflare D1 database and added to a Resend Audience for email delivery. Resend processes it as the storage and delivery provider. Jikoku does not sell the address or share it for advertising.

You can request deletion at any time by emailing support@jikoku.app. The address will be removed from the launch-email database and Resend Audience.

Jikoku is a general-purpose productivity product and is not directed to children under 13. The privacy description may change when distribution, permissions or integrations change. Material changes should be reflected here before the corresponding service is used.

Questions about privacy, a particular build or the handling of a launch-email address can be sent to support@jikoku.app.

No privacy page can turn a changing product into a permanent promise by itself. Distribution, entitlements and system integrations can change as Jikoku moves toward a signed public release. Claims on this page should be reviewed whenever the architecture changes.

The useful rule is simple: the product should show when data leaves the device, name the service receiving it and avoid describing a future capability as if it were already available.

If a statement here conflicts with the behavior of a particular early build, the behavior should be investigated and the statement corrected. Marketing language is not a substitute for technical truth.

Read the Public Beta page for current system and distribution information.