Skip to content
Cursuum

Know what you are sharing.

Your time is personal.

A social calendar should make it easier to meet without making your whole life visible. Here is how Cursuum separates identity, calendar access, availability, conversations and optional AI—and where the current limits are.

Explore on Mac

Signing in is not calendar permission.

Google sign-in provides the identity needed to authenticate your account. It does not silently connect your calendar or request Gmail, Drive or contacts. Connecting Google Calendar is a separate, optional authorization. Email and password authentication is also available through Supabase.

Your device and the hosted service have different roles.

Manual availability, local relationship records, preferences and selected busy intervals are saved in encrypted, account-specific files on your Mac. The signed-out workspace is separate. Account authentication, connected-calendar processing, shared availability and conversations use hosted services. This is not a claim that all data stays on your device or that all services are end-to-end encrypted.

Busy intervals, not a public event diary.

You select the calendars and events that affect your free time. Google event titles can appear temporarily in your private event picker, but stored availability uses identifiers and time intervals rather than event titles, guest lists or notes. Sharing a code exposes authorized free windows and only the preferences you explicitly include.

  • Choose the date range and daily hours to share.
  • Keep activity preferences private unless you choose to include them.
  • Revoke a code to stop future access; stale or expired data is shown as unknown.

Calendar writes are deliberate.

Google’s permission bundles event viewing, creation, editing and deletion on calendars you own. Cursuum currently provides creation and editing after review, with no event-deletion action. The editor does not send attendee invitations. Disconnecting removes stored connection credentials, selections and associated busy intervals and requests Google token revocation; any unconfirmed revocation is reported separately.

AI has its own consent boundary.

Local matching does not contact an AI provider. Consented cloud requests send your typed request and selected free windows to OpenAI using participant references. Raw events, notes and messages are not automatically included. Cursuum uses the provider’s no-storage request setting, while generated results may be kept for up to seven days for safe retries. Provider security and legal retention may differ.

  • Free profile analysis has a separate title-review and consent step: only approved titles are processed for tentative activities and atmosphere, with individual confirmation.
  • Your own prompt can contain identifying information; avoid private details.
  • Cursuum does not use Google API data for advertising, data brokerage or model training.
  • Review AI suggestions; valid time windows do not guarantee perfect interpretation of preferences.

The services involved.

Supabase provides authentication and hosted data; the current project is in US East, North Virginia, so some data is processed outside Canada. Google provides sign-in and connected-calendar access. OpenAI processes optional cloud planning and separately consented free profile analysis. Stripe processes payments; Resend delivers transactional messages and purchase agreements. Vercel hosts the website, and Cloudflare delivers native downloads. Providers may keep operational or security logs under their own policies.

Access controls are not a blanket promise.

Hosted features check account and membership permissions. Google credentials are encrypted in Supabase Vault. Payment-card details are entered with Stripe rather than stored by Cursuum. Private chat is not end-to-end encrypted. No security certification, independent audit or guarantee of zero vulnerabilities is claimed here. Google’s public calendar data-access review remains under review.

Control, export and deletion.

For access, correction, export, deletion or help removing local copies, contact charles@predictive.company, preferably from your account email. These requests are handled manually with an ownership check. Signing out does not delete local files, and deleting the app may leave application data behind. Financial records may need to be retained; provider backups and logs have separate retention.

  • Disconnect Google Calendar in the app or revoke access in your Google Account.
  • Stop the optional background job in Settings.
  • Do not send passwords, sign-in codes, private calendar exports or payment details in a support message.

The details matter

Your questions. Clear answers.

Does Cursuum sell my Google Calendar data?

No. Google API data is used for the account, calendar and availability features described in the privacy notice, subject to Google’s Limited Use requirements.

Are my conversations end-to-end encrypted?

No. Conversations are hosted in Supabase with membership-based access controls. They should not be described as end-to-end encrypted.

Does revoking a code erase what someone already saw?

No. Revocation stops future access through that code. It cannot remove information a recipient previously viewed, copied or saved.

Where do I report a privacy or security concern?

Email charles@predictive.company with a description and steps to reproduce, without credentials or other people’s private data. The full privacy notice provides the current processing and contact details.

At your own pace

Start with one moment together.

Find your plan
Trust — Cursuum