Skip to content
Cursuum

Encryption

Protection you can understand.

Your calendar holds more than appointments. Here is what stays on your Mac, what travels securely, and what a service needs to read to do its job.

Follow your data

Choose a feature to see its path. Encryption and access controls protect different parts of that journey.

Importing an .ics calendar is a local action. It does not upload the file.

  1. Your Mac

    Encrypted storage

    Selected busy times and preferences are saved in encrypted local files.

  2. In transit

    Stays here

    The import itself makes no upload.

  3. Services

    Not needed

    No cloud service is needed to import your file.

  4. Other people

    Private by default

    Importing is not publishing. Sharing is a separate choice.

Who can read it?

Your app reads the data while you use it. Your original .ics file remains wherever you saved it; Cursuum does not encrypt that original file.

Reconnect reminders · you choose each action

“Find a time” selects that person in your calendar view so you can review availability. “We met” records today as your last meeting with that person and updates your reminder. Neither action sends a message or invitation, or creates a calendar event. These controls do not change calendar access or sharing permissions.

Settings · separate privacy choices

In Mac 0.2.33, Settings groups your account, profile and plan together, with account security available when signed in outside the sample experience. The app saves your palette and grid-line preference on this device. To manage calendar connections, open the separate Calendar section. Under Preferences, local learning, contact reminders and background calendar checks each have their own explicit choice; enabling one does not enable the others. Opening Settings does not connect or share a calendar. The browser demo labels Mac-only reminders, background checks and update controls as unavailable instead of presenting their absence as a service failure. This organization does not change encryption, access permissions or the limits described here.

Schedule workspaces · private event details

The event editor lets you review dates, repetition and whether an event blocks availability before saving. In Mac 0.2.31, Personal, Social, School, Academic and Professional workspaces offer separate layouts, custom calendars and weekly events. Course and project filters change the view, not saved events or busy time. Event details stay in encrypted local storage. Availability synchronization sends only busy times and device/synchronization metadata, not titles or notes. The service can read those times; this is not end-to-end encryption. This does not write events to Google or another calendar provider. The app distinguishes local saves from pending, failed and completed availability updates. Stop sharing clears stored intervals and revokes sharing links. Local events remain; reopening an authorized workspace may synchronize busy times again, but does not restore revoked links or calendar connections.

Living rituals · shared plans and private choices

Creating a shared ritual requires choosing people, activities and an existing availability scope, then reviewing and explicitly confirming those choices. Selecting participant checkboxes in the creation form does not send a ritual request. You still review the choices and confirm before the request is sent. The ritual service stores agreed activities, cadence, membership, chosen availability-share references and proposal confirmations. It also processes each member’s flexibility and time preferences. Other participants receive common options, not another person’s private flexibility settings or preference scores. These records use server access controls, not end-to-end encryption. Members choose which existing availability scope to use; agreement does not widen it. Suggestions are rechecked before sending or acceptance. Pausing stops new matching. Withdrawing removes the shared ritual for everyone but does not remove existing calendar events or information someone already viewed. Rare-window notices describe only the checked coverage and are off by default. Personal learned ranking history stays on the device and is not used by this service.

Website introductions

The careers form on cursuum.com and cursuum.app sends your name, email, message and optional portfolio link over HTTPS to Cursuum, then through Resend to Charles at Predictive Company. Email is not end-to-end encrypted. Request identifiers and hashes help limit abuse and duplicate delivery; the introduction text is not stored in the service database. The email provider and recipient can process and retain the message. Success means provider acceptance, not confirmed inbox delivery.

App and website languages

Interface translations are bundled locally. The Mac app remembers your language on this device. When signed in, your language choice is also saved in account metadata for authentication emails. Cloud assistance requests include the selected language; access invitations use the recipient language chosen by the sender. This does not change access or sharing permissions. Built-in choices are translated; names, messages, custom labels and profile notes remain unchanged. Changing the interface language does not send that content to a translation service.

Email language and delivery

Authentication and access-invitation emails support the five app languages. Starting with Mac 0.2.25, sign-up confirmation links return to a page in the selected language. Missing or unsupported account-language metadata falls back to English. The authentication and email providers process the message and recipient address; email is not end-to-end encrypted by Cursuum. Action links, verification tokens and access codes are not translated. An accepted send request is not proof of inbox delivery. Corrected translations apply to new purchase emails; previously issued agreements keep their original content. Provider and operating-system interfaces keep their own language behavior.

Keys stay outside the interface

Starting with Mac 0.2.28, Cursuum encrypts local workspace, session and reminder files with AES-256-GCM using an app-managed key. The key and encrypted files have owner-only permissions; signing in and saving no longer require Keychain. Session tokens persist across launches and stay in the privileged app process, outside the web interface. Encryption failures never fall back to plaintext. Another process running as your Mac user, or with root access, can read both the key and data. This is not the same isolation as operating-system secure storage. The authentication service rejects known breached passwords. New password sign-ups require 12–256 characters; existing shorter passwords can still be used to sign in.

A second factor, with a way back

Starting with Mac version 0.2.20, add an authenticator in Settings → Account security and verify its code before it becomes active. Once enabled, a password alone cannot unlock your account in the app. You can verify a separate backup authenticator and use its fresh code to remove a lost primary factor. Keep that backup independently accessible. Losing every factor has no automatic bypass; a backup factor is not a recovery code or a backup of your calendar.

Recovery needs testing too

Previous Keychain-encrypted files are preserved. Recovering those files is a separate action that may still need their original Keychain; a failed recovery does not overwrite them. New local files require their app-managed key: losing that key does not make the data recoverable by creating a replacement. The 0.2.28 synthetic-file drill restored workspace and session data using a copied app-managed key, verified account separation, and refused a backup missing its key without replacing files. Earlier recovery tests covered operating-system-encrypted synthetic files on the same Mac and revoked sessions. We also restored a hosted production backup into a temporary isolated project, checked records, row-level security, permissions and session invalidation, then deleted the clone. Production was not overwritten. Restoring an old database can restore old permissions and sessions, which must be reconciled. These tests do not establish recovery after key loss or verify external files or provider secrets. No recovery time is promised; point-in-time recovery is not enabled.

Protection has more than one layer

Encrypted local files and HTTPS address storage and transport. The app sandbox, restricted navigation, account separation, server ownership checks and conversation membership limit what each part of the system may do. Signing and Apple notarization help you verify the Mac app’s origin; they are not a guarantee that software has no bugs.

Sharing remains a deliberate choice

Native availability codes expire and can be revoked. An eligible signed-in user who has the code can view the allowed availability, and a forwarded code may give someone else access. Revoke it to stop future reads. Revocation cannot erase screenshots or copies already made.

Checks before app code runs

Starting with Mac version 0.2.18, Cursuum checks its packaged code for changes and refuses an unpacked fallback. Developer tools are disabled in the packaged interface. The installer contains runtime assets without development sources or source maps. Minification makes casual inspection harder; it is not encryption, and someone controlling a device can still analyze its code.

Updates checked before you open them

When you update inside Mac version 0.2.19, the app verifies an Ed25519 signature using a public key built into the app. It then downloads the installer into a private folder within Downloads and checks its exact size and SHA-256 digest before revealing it in Finder. Failed downloads are discarded. Installation stays manual. These checks authenticate the update; they do not encrypt the installer or apply to a separate browser download.

A session must still be valid

The 0.2.19 service update checks that a signed-in session still exists, belongs to the account and has not expired, alongside existing ownership and membership checks. The updated private database and account-service paths reject revoked sessions and banned or deleted accounts. Public availability links still use their separate capability-token rules. Starting with the 0.2.20 service release, enrolled accounts must also present a session verified with a second factor, and privileged billing requests gain the same active-session check. Signing out does not erase copies already read or cancel an operation already in progress.

Closing access during account changes

Starting with Mac version 0.2.21, private responses are discarded if the current sign-in token changes while a request is running. In Mac 0.2.28, app-access status is checked against the current verified session. If that session changes during the status check, the app retries this read once with the newly verified session and never reuses the old access grant. Operations that change data are not retried. Choosing Sign out closes private access immediately, even when the authentication service or local cleanup fails. Background events cannot reopen it in that process. If encrypted credentials cannot be removed, the app stays locked and asks you to retry; preserved credentials may remain after restart, and remote revocation is not guaranteed until confirmed. These checks cannot undo a request already processed by a service.

Privacy controls when access ends

If your account is signed in but app access is locked, Stop sharing remains available. After confirmation, it revokes your shares and conversation invitations, leaves your conversations, closes conversations you own and disconnects your Cursuum calendar. Local files and existing messages are not erased. Google account permissions must be removed separately in Google.

Learning stays on your Mac

In 0.2.36, personal suggestions give your latest explicit feedback priority whenever an eligible time fits it. For a group, your feedback has less weight as the group grows and stays on your Mac. Mac versions after 0.2.23 include an optional, experimental Learn from my choices setting. When you turn it on, the times you choose and explicit feedback are stored as coarse time features (local hour, weekday, duration, lead time), without titles, people or notes, inside the same encrypted local workspace. Ordering runs on the Mac with a small model included in the app; its SHA-256 checksum is verified before use, it has no network access and contains no executable code. It only reorders windows that already passed the shared-availability check. Entries expire after 180 days; turning it off or resetting it deletes them. The browser demo keeps sample feedback in that browser only.

Less data where less is enough

Availability sharing uses time windows rather than event titles, guests or notes. Optional shared activity preferences are chosen explicitly. Google connection credentials are stored encrypted in Supabase Vault; the calendar service decrypts them only to perform authorized operations.

What encryption cannot promise

Local encryption does not protect against a process running as your Mac user or someone who obtains both the local key and encrypted files. A compromised device or an authorized service may access data while it is being used. Cursuum does not claim that hosted messages or cloud AI are end-to-end encrypted. No system is unhackable; security requires maintenance, testing and honest limits.

Read the privacy notice

Security work continues

We use synthetic accounts to check what each participant can see after sharing. We review account boundaries, sharing, requests and dependencies, and add tests when we find a failure. Security changes require a fresh English and French review of this page before release. Before a website release is marked complete, Cursuum checks that the published pages in all five languages match the reviewed copies and link to each other. We also open the public pages at desktop and phone sizes, switch languages, expand FAQ answers and try each journey in the encryption map. In the public demo, we also try planning alone and with a group and replying in a sample conversation, in all five languages, with the fine grid on and off for each of the four palettes. We also save and reopen an edited sample profile, record a meetup to clear its reminder, and follow the guided tour to the end. Feature changes require updated demo checks before release, and every registered check must pass in all five languages and all eight appearance combinations. These checks verify the website controls, not the strength of the encryption. We keep improving the app without promising that encryption prevents reverse engineering.

Report a security concern

Describe the issue without sending passwords, tokens or private calendar data.

Encryption — Cursuum